RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1144531 - Use the sahara-all binary instead of only sahara-api
Summary: Use the sahara-all binary instead of only sahara-api
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RDO
Classification: Community
Component: openstack-sahara
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: Juno
Assignee: Michael McCune
QA Contact: Luigi Toscano
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-19 16:36 UTC by Luigi Toscano
Modified: 2014-10-28 23:08 UTC (History)
1 user (show)

Fixed In Version: openstack-sahara-2014.2-0.4.b3.fc22
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-28 23:08:59 UTC
Embargoed:


Attachments (Terms of Use)

Description Luigi Toscano 2014-09-19 16:36:25 UTC
Description of problem:
Sahara is going to move from a monolithic configuration to a distributed one, so sahara-api was split into sahara-api and sahara-engine.

In IceHouse, the unit for openstack-sahara-api was enough to start the entire system, from Juno it only starts sahara-pai but not sahara-engine. A new sahara-all binary has been introduced, because the split configuration is still experimental, and it should be used instead (maybe also the unit renamed).

Version-Release number of selected component (if applicable):
openstack-sahara-2014.2-0.3.b3.fc22.noarch

How reproducible:
Start openstack-sahara-api, the log file contains this warning:
WARNING sahara.main [-] Distributed mode is in the alpha state, it's recommended to use all-in-one mode by running 'sahara-all' binary.


There is no way (systemd units) to start sahara-engine.

Expected results:
Use openstack-sahara-all for now, until the splitted configuration is more stable (most likely post-Juno)


Note You need to log in before you can comment on or make changes to this bug.