Bug 1042060

Summary:	[RFE][horizon]: Allow users to create pseudo directories independent from object upload
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	python-django-horizon	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED ERRATA	QA Contact:	nlevinki <nlevinki>
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	aberezin, aortega, 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-pseudo-directory
Whiteboard:	upstream_milestone_icehouse-1 upstream_status_implemented upstream_definition_new
Fixed In Version:	python-django-horizon-2014.1-5.el7ost	Doc Type:	Enhancement
Doc Text:	Pseudo-folders are similar to folders in your desktop operating system. They are virtual collections defined by a common prefix on the object's name. With this update, users can create pseudo directories using the Create Pseudo-folder button without uploading an object.	Story Points:	---
Clone Of:
Clones:	1082433 (view as bug list)		Environment:
Last Closed:	2014-07-08 15:43:55 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:	1082433

Description RHOS Integration 2013-12-12 20:46:55 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/swift-pseudo-directory.

Description:

This should include a "create directory" or "create folder" button at the top of the object browsing table. Additionally, add a "delete directory" button as a row action.

Specification URL (additional information):

None

Comment 2 Stephen Gordon 2014-01-23 20:47:54 UTC

Moving to POST based on upstream status (Implemented).

Comment 8 errata-xmlrpc 2014-07-08 15:43:55 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.

http://rhn.redhat.com/errata/RHEA-2014-0855.html