Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1696476 - [RFE] Support for connecting director-deployed manila to an external Ganesha and Ceph cluster
Summary: [RFE] Support for connecting director-deployed manila to an external Ganesha ...
Status: NEW
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 13.0 (Queens)
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact: Sasha Smolyak
Depends On: 1696717
TreeView+ depends on / blocked
Reported: 2019-04-04 23:15 UTC by August Simonelli
Modified: 2019-04-11 16:16 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description August Simonelli 2019-04-04 23:15:56 UTC
Description of problem:

There is no defined procedure or supporting templates to deploy the OpenStack Shared File System service (Manila) with a remotely hosted (ie NOT director-deployed) NFS/Ganesha. 

There are guides and templates to do this with director-deployed ceph/ganesha/manila; however, we are looking for a guide and templates supporting the following:

Manila - director deployed
Ganesha - standalone external
Ceph - standalone external

Version-Release number of selected component (if applicable):

How reproducible:
There is no method to easily connect a director-deployed manila install to an external independently installed and managed Ganesha install.

Steps to Reproduce:
1. Deploy manila with director

Actual results:
No templates or process exists to easily connect manila to a remote ganesha

Expected results:
A tested, shipped director template(s) allowing for an easy connection to Ganesha.

Additional info:

Note You need to log in before you can comment on or make changes to this bug.