Bug 919607
| Summary: | Need support for deploying via Packstack to use Gluster services | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Perry Myers <pmyers> |
| Component: | openstack-packstack | Assignee: | Giulio Fidente <gfidente> |
| Status: | CLOSED ERRATA | QA Contact: | Dafna Ron <dron> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2.0 (Folsom) | CC: | aortega, cctrieloff, derekh, eharney, enakai, gfidente, grajaiya, hateya, jclift, jkt, johnmark, mlopes, mmagr, tkatarki, vagarwal, vbellur |
| Target Milestone: | beta | Keywords: | FutureFeature |
| Target Release: | 4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | storage | ||
| Fixed In Version: | openstack-packstack-2013.2.1-0.1.dev691.el6ost | Doc Type: | Enhancement |
| Doc Text: |
Packstack now automatically configures Block Storage for GlusterFS when a full 'ip:/volume/name' remote GlusterFS volume path is provided. Consequently, Block Storage is configured to use GlusterFS instead of the local LVM. Prior to this enhancement, manual configuration of Block Storage for GlusterFS would have been required after Packstack installation.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-12-19 23:59:26 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 975499 | ||
|
Description
Perry Myers
2013-03-08 21:51:10 UTC
work in progress https://review.openstack.org/#/c/35162/3 changes were merged so I'm setting the status to ON_QA verified using openstack-packstack-2013.2.1-0.6.dev763.el6ost , the feature is there yet for selinux a boolean needs to be set manually after the setup, see https://bugzilla.redhat.com/show_bug.cgi?id=1015625 Adding FutureFeatures to RHOS 4 feature tracker 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. http://rhn.redhat.com/errata/RHEA-2013-1859.html |