Bug 1042059

Summary:	[RFE][horizon]: Swift Object Versioning
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	python-django-horizon	Assignee:	Radomir Dopieralski <rdopiera>
Status:	CLOSED WONTFIX	QA Contact:	Ido Ovadia <iovadia>
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	athomas, beth.white, markmc, mrunge, nbarcet, srevivo
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/horizon/+spec/swift-object-versioning
Whiteboard:	upstream_milestone_next upstream_status_needs-code-review upstream_definition_obsolete
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-23 15:34:17 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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

Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/swift-object-versioning.

Description:

Allow the user to toggle versioning of a container on/off in the UI via manipulation of the X-Versions-Location container metadata attribute

Specification URL (additional information):

None

Comment 3 Matthias Runge 2015-12-15 10:23:03 UTC

patch needs some love upstream; it is ancient and needs a rebase.

Comment 4 Itxaka 2016-01-27 11:38:58 UTC

Will take care of following this upstream.

Comment 5 Itxaka 2016-03-29 09:46:10 UTC

upstream patch is updated, seem to be some confusion on how this affects the new ngswift interface.

Comment 7 Itxaka 2016-04-18 08:59:18 UTC

Upstream patch is not useful anymore as the interface used now is a pure angular one.