Bug 1300637
Summary: | Make use of Volume Containers when deploying RHGS pods | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Humble Chirammal <hchiramm> |
Component: | rhgs-server-container | Assignee: | Mohamed Ashiq <mliyazud> |
Status: | CLOSED ERRATA | QA Contact: | Prasanth <pprakash> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | rhgs-3.1 | CC: | annair, asriram, asrivast, bmohanra, hchiramm, mliyazud, pprakash, rcyriac, sankarshan, ssaha, ssampat |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | RHGS 3.1.2 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: |
The data volume container will have all the default volume mounts assigned to it so that it can then be attached to Red Hat Gluster Storage containers. The following option bind mounts all the volumes of the data volume container to the Red Hat Gluster Storage container.
--volumes-from <data-volume-container>
The data volume container is started along with the setup.sh script. This script moves the backup of gluster configuration file to the expected directories for persistence. Hence, this enhancement simplifies the gluster configuration setup for the Red Hat Gluster Storage container.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-03-01 05:21:13 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
Humble Chirammal
2016-01-21 10:30:06 UTC
Hi Ashiq, The doc text is edited. Please review the same and share your comments. If it looks ok, then do sign-off on the same. (In reply to Bhavana from comment #12) > Hi Ashiq, > > The doc text is edited. Please review the same and share your comments. If > it looks ok, then do sign-off on the same. looks good to me. Thanks. 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://rhn.redhat.com/errata/RHEA-2016-0327.html |