| Summary: | [RFE][horizon]: Add support for public container | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | RHOS Integration <rhos-integ> | |
| Component: | python-django-horizon | Assignee: | RHOS Maint <rhos-maint> | |
| Status: | CLOSED ERRATA | QA Contact: | Amit Ugol <augol> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | unspecified | CC: | aberezin, aortega, augol, dnavale, jpichon, markmc, mrunge, yeylon | |
| Target Milestone: | Upstream M1 | Keywords: | FutureFeature, Triaged | |
| Target Release: | 5.0 (RHEL 7) | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| URL: | https://blueprints.launchpad.net/horizon/+spec/swift-container-public-access | |||
| Whiteboard: | upstream_milestone_icehouse-1 upstream_status_implemented upstream_definition_approved | |||
| Fixed In Version: | python-django-horizon-2014.1-5.el7ost | Doc Type: | Enhancement | |
| Doc Text: |
With this update, support for public container is added. This allows the user to set ACL as 'read' for the container to either public or private. This can be set at the container creation time or can also be updated at a later time by the user.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1084287 (view as bug list) | Environment: | ||
| Last Closed: | 2014-07-08 15:43:20 UTC | Type: | --- | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Bug Depends On: | ||||
| Bug Blocks: | 1084287 | |||
|
Description
RHOS Integration
2013-12-12 20:25:09 UTC
Moving to POST based on upstream status (Implemented). about testing: from bp: 1. When creating the container, allow the user to set the container access: - Public - Set the x-container read to ".r:*" - means public read and ".rlistings" to allow public listing of contents - Private - Set the container-read to empty 2, Allow the user to shortcut to update the Container Access from the Container browser. 3. When the access is Public, provide the user the Public URL for that container. tested with above stepps. Also tried some basic Brute-force attack to verify that the private remains private. 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. http://rhn.redhat.com/errata/RHEA-2014-0855.html |