Bug 1214817
| Summary: | Add systemd unit files for sahara-api and sahara-engine | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Javier Peña <jpena> |
| Component: | openstack-sahara | Assignee: | Elise Gafford <egafford> |
| Status: | CLOSED ERRATA | QA Contact: | Luigi Toscano <ltoscano> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.0 (Kilo) | CC: | jpena, kbasil, lbopf, matt, mimccune, nlevinki, yeylon |
| Target Milestone: | ga | ||
| Target Release: | 7.0 (Kilo) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-sahara-2015.1.0-2.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
Prior to this release, Red Hat Enterprise Linux OpenStack Platform did not package or support the sahara-api or sahara-engine processes individually, because Sahara's "distributed" mode was in alpha testing. Now that this feature is stable, RHEL OpenStack Platform provides systemd unit files for the sahara-api and sahara-engine services, and users can use Sahara in distributed mode, with separation of api and engine node clusters.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-08-05 13:22:55 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Javier Peña
2015-04-23 15:13:24 UTC
Hi Javier, I believe this may be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1158163 (on which I am actively working now that Sahara's distributed mode is out of alpha as of the Kilo release.) Does that bug address your concern? Thanks Hi Ethan, I guess yes, it could be a duplicate, provided that the new packaging includes the systemd unit files. Feel free to close this bug if that is the case. Thanks! Oh, and just for the record: all my references to sahara-db should refer to sahara-engine. Sorry! (In reply to Ethan Gafford from comment #3) > Hi Javier, > > I believe this may be a duplicate of > https://bugzilla.redhat.com/show_bug.cgi?id=1158163 (on which I am actively > working now that Sahara's distributed mode is out of alpha as of the Kilo > release.) Does that bug address your concern? > > Thanks ethan, while this bz may be resolved as a side-effect of bz1158163, it's best to keep this as a top level activity to be prioritized. (In reply to Matthew Farrellee from comment #6) > > while this bz may be resolved as a side-effect of bz1158163, it's best to > keep this as a top level activity to be prioritized. Is there really any difference? The other bug has the same attention level and target as this one. mattf: For RHOS 7, as bz1158163 cannot be completed without performing this task, I'm not certain that resolving and adding notes for both to the next release increases clarity (particularly as these files exist in the recently merged master packaging, and in the builds I'm testing now for Kilo RDO and RHOS 7.) If this bug is attempting to address the lack of unit files in RHOS 6, of course, as per the potentially duplicate bug, that is a WONTFIX issue, as distributed mode was in alpha as of Juno per the Sahara project team. Still, it's certainly not a problem to ack and close this simultaneously, if you see tracking this for documentation purposes as specifically useful. Thanks. Sahara services are also packaged separately (see also rhbz#1158163), and install separate systemd units for -api and -engine in addition to the old (deprecated) -all unit, which enables the "all services mode", provided by openstack-sahara. Moving to VERIFIED. openstack-sahara-common-2015.1.0-2.el7ost.noarch openstack-sahara-api-2015.1.0-2.el7ost.noarch openstack-sahara-engine-2015.1.0-2.el7ost.noarch openstack-sahara-2015.1.0-2.el7ost.noarch Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2015:1548 |