Bug 1393893

Summary: [RFE][manila] Add the Ability to Disable the Creation of Manila Public Shares
Product: Red Hat OpenStack Reporter: Dustin Schoenbrun <dschoenb>
Component: openstack-manila-uiAssignee: Tom Barron <tbarron>
Status: CLOSED ERRATA QA Contact: Dustin Schoenbrun <dschoenb>
Severity: medium Docs Contact:
Priority: medium    
Version: 10.0 (Newton)CC: apevec, cschwede, dhill, dschoenb, egafford, hguemar, jliberma, jomurphy, lhh, mlopes, nlevinki, pgrist, rcernin, rhos-maint, sclewis, scohen, tbarron, tvignaud, vimartin
Target Milestone: Upstream M3Keywords: FutureFeature, Triaged
Target Release: 11.0 (Ocata)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-manila-ui-2.7.1-0.20170127105750.b67e7e6.el7ost Doc Type: Enhancement
Doc Text:
With this enhancement, you can now enable the creation of non-public shares in the Dashboard. You can configure Dashboard to hide the checkbox that enables users to mark shares as public during the creation process. The default option will be to create shares as private without the box checked.
Story Points: ---
Clone Of: 1326279
: 1423349 (view as bug list) Environment:
Last Closed: 2017-05-17 19:45:22 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: 1326279, 1433492    
Bug Blocks: 1423349    

Comment 7 Thierry Vignaud 2017-02-14 17:04:21 UTC
Change is present in openstack-manila-ui-2.7.1-0.20170127105750.b67e7e6.el7ost

Comment 9 Dustin Schoenbrun 2017-03-27 19:09:22 UTC
Using the 2017-03-08.3 puddle, openstack-manila-ui-2.7.1-0.20170214092823.2e2ae51.el7ost.noarch, and the workaround where we tell Horizon to use the v2 Keystone API endpoint instead of the v3 API endpoint, I was able to successfully disable the ability to create publicly available shares and was then able to re-enable the ability again.

Comment 10 errata-xmlrpc 2017-05-17 19:45:22 UTC
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/RHEA-2017:1245