Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

script to check for dependencies and to start all services #14

Closed
ElDeveloper opened this issue Feb 13, 2014 · 4 comments
Closed

script to check for dependencies and to start all services #14

ElDeveloper opened this issue Feb 13, 2014 · 4 comments
Milestone

Comments

@ElDeveloper
Copy link
Member

Ported from Qiita-pet.

We need to create 1 or 2 scripts to check for all dependencies and to start and perhaps stop all services.
 Daniel McDonald

 wasade commented 24 days ago
Ideally there is a single way to start qiita-pet, such as a foo.run()
method. The constructor for foo could do all the necessary service checks
and bail early. I understand there likely is a motive to support a similar
mechanism to print_qiime_config.py, but encapsulating the functionality
with the code that actually starts qiita-pet should simplify the tests and
the design. Then, something like print_qiitapet_config.py could effectively
just construct foo with, say, "print_service_state=True" or whatnot
…
 Joshua Shorenstein

squirrelo commented 24 days ago
I have an idea on how to do this. I'll include it in the next update I do once the iPython changeover is complete and we know all the dependencies needed.
 josenavas

josenavas commented 24 days ago
Agree with a script that check all the dependencies, but disagree with start all the services. If by services you mean redis, celery ipython, etc this is deployment-dependent. In the README we simply show an example for run a demo, but the actual deployment should be different. For example, the IPython cluster can be started as a single machine, distributed machine, with and without PBS backend. Similarly with Celery.

In my opinion, only the webserver should be started by QiiTa-pet.
 Antonio Gonzalez

 antgonza commented 24 days ago
What about a configuration file with the default sets for a local machine
and another for an Ubuntu EC2 instance, something similar to the qiime
deploy configuration file? I'm just thinking that a "regular" user will
struggle a lot starting all those pieces and what to make it easier. Let me
know if you have other suggestion on how to do this?
 josenavas

josenavas commented 24 days ago
Sounds good
 Joshua Shorenstein

squirrelo commented 24 days ago
Config file listing all the services, all off to begin with but the bare minimum, seems pretty easy.
@squirrelo squirrelo modified the milestone: Alpha 0.2 Sep 12, 2014
@adamrp
Copy link
Contributor

adamrp commented Sep 15, 2014

Can we close this?

@antgonza
Copy link
Member

I still think we need something that does this. Something like qiita start,
qiita stop, qiita check-installation

@adamrp
Copy link
Contributor

adamrp commented Sep 16, 2014

Okay, can you tackle this? Should just be:

  • start redis
  • start postgres
  • start ipython clusters
  • qiita_env make_env environments (test, production; probably won't be making the "demo" environment in the release version)
  • start webserver.py

@antgonza antgonza modified the milestones: Alpha 0.1, Pre-alpha Sep 16, 2014
@ElDeveloper
Copy link
Member Author

Fixed in #805

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

No branches or pull requests

4 participants