Skip to content
This repository has been archived by the owner on Feb 17, 2022. It is now read-only.

New install from scrach authentication issues #26

Open
mgailhac opened this issue Sep 4, 2017 · 5 comments
Open

New install from scrach authentication issues #26

mgailhac opened this issue Sep 4, 2017 · 5 comments

Comments

@mgailhac
Copy link

mgailhac commented Sep 4, 2017

We have deployed beehive-server from git using the install/beehiveInstallNew.bash script.
It had many path and silly issues we fixed, such as paths.
After it finished, we found that the RabbitMQ install has no users or maybe we have no passwords.
In short, none of the services are able to connect to MQ.
¿Is this expected?
¿Should we generate queues/users/credentials on behalf of the services?
It looks to me some part of the build failed and the users were not created.
Thank you in advance.

@seanshahkarami
Copy link
Member

seanshahkarami commented Sep 5, 2017

Thanks for your interest! Currently, we're working quickly to get the beehive server to a production ready mode, but as of now, it's not there yet. Many of these kinds of issues will get cleaned up in the near future. Thank you for understanding.

@smuniz-vates
Copy link

Hello Seanshahkarami,
I am working with mgailhac in the test deployment. Thanks for your quick answer!
We will try to provide feedback and patches.
Regards,
Sebastian,

@seanshahkarami
Copy link
Member

Hi Sebastian,

Ah, ok. Out of curiosity, where are you all from and what groups do you all work with?

Just to give you a heads up, there may be a significant simplifications which happens in terms of design and deployment, so I'm just giving you a fair warning before investing to much time in what's there now. For example, one hypothetical deployment alternative I've been putting together as an experiment outside of work is this: https://github.com/seanshahkarami/beehive-stack

Something like that could make it much easier for you all to see what needs to be defined to spin up all the containers.

Best,
Sean

@smuniz-vates
Copy link

Sean,
I don't think we can answer this on the forum. We will definitely check that repo you pointed.
I understand there has been some heavy changes in the architecture and engineering.
Do you feel confident using IRC? We could open a "#waggle" at freenode.

@seanshahkarami
Copy link
Member

Sorry for the "radio silence" - Raj and Pete mentioned which group you're with. If you'd like to talk more actively, I'm happy to open that IRC channel or add a Slack channel if you all use that.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants