Bug 1710358
| Summary: | [RFE] Support standalone deployments of ganesha (nfs role) | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Giulio Fidente <gfidente> |
| Component: | Ceph-Ansible | Assignee: | Guillaume Abrioux <gabrioux> |
| Status: | CLOSED ERRATA | QA Contact: | Yogev Rabl <yrabl> |
| Severity: | medium | Docs Contact: | Erin Donnelly <edonnell> |
| Priority: | medium | ||
| Version: | 4.0 | CC: | aschoen, ceph-eng-bugs, ceph-qe-bugs, edonnell, fiezzi, gabrioux, gmeno, nthomas, pasik, tchandra, tserlin, vashastr |
| Target Milestone: | rc | Keywords: | FutureFeature |
| Target Release: | 4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-ansible-4.0.0-0.1.rc9.el8cp | Doc Type: | Enhancement |
| Doc Text: |
.The `nfs-ganesha` service is now supported as a standalone deployment
Red Hat Openstack Directory (OSPd) requires the `ceph-ansible` utility to be able to deploy the `nfs-ganesha` service and configure it so that it points to an external, unmanaged, pre-existing, Ceph cluster. As of {product} {release}, `ceph-ansible` allows the deployment of an internal `nfs-ganesha` service with an external Ceph cluster.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-01-31 12:46:15 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1642481, 1696717, 1730176 | ||
|
Description
Giulio Fidente
2019-05-15 12:16:52 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri 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/RHBA-2020:0312 |