Bug 1061963 - GlusterFS libgfapi configuration
Summary: GlusterFS libgfapi configuration
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: doc-Cloud_Administrator_Guide
Version: 4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 5.0 (RHEL 7)
Assignee: Don Domingo
QA Contact: Andrew Dahms
URL:
Whiteboard: docs-rhos5-ups docs-ups-patched
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-05 23:35 UTC by Eric Harney
Modified: 2014-11-19 04:44 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Test abc
Clone Of:
Environment:
Last Closed: 2014-09-04 13:07:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1281444 0 None None None Never

Description Eric Harney 2014-02-05 23:35:38 UTC 
Bug 1052336 added notes about required settings for libgfapi to the RHOS4 release notes.

I suspect we will want similar information in the configuration reference guide for the GlusterFS driver rather than only in release notes, as it is applicable for any installation using libgfapi.

https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/4/html/Configuration_Reference_Guide/GlusterFS-driver.html
Comment 2 Martin Lopes 2014-02-07 00:05:06 UTC 
This bug is being assigned to Don Domingo, who is now the designated docs specialist for cinder.
Comment 3 Don Domingo 2014-02-10 05:38:09 UTC 
For reference:
https://bugzilla.redhat.com/show_bug.cgi?id=1044773
Comment 4 Don Domingo 2014-02-21 05:02:43 UTC 
Just realized that I had already added this as a step to the GlusterFS backend setup instructions. 

Those instructions were submitted as part of https://review.openstack.org/#/c/74553/ to address https://launchpad.net/bugs/1281444. 

Marking as 'patched'.
Comment 5 Deepti Navale 2014-05-27 00:55:31 UTC 
Changing component as the change was merged to Cloud Admin guide.
Note You need to log in before you can comment on or make changes to this bug.