Bug 1270333

Summary:	[RFE] Add internal versioning system to OSP director
Product:	Red Hat OpenStack	Reporter:	jliberma <jliberma>
Component:	rhosp-director	Assignee:	Hugh Brock <hbrock>
Status:	CLOSED DUPLICATE	QA Contact:	Shai Revivo <srevivo>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0 (Kilo)	CC:	eaguilar, emacchi, jcoufal, jliberma, mburns, rhel-osp-director-maint
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	10.0 (Newton)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-27 03:40:31 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:

Description jliberma@redhat.com 2015-10-09 16:36:38 UTC

Description of problem:

Add an internal versioning system to OSP director. 



Additional info:

Reproducible OSP director configuration relies on many properly formatted text files. (JSON, YAML, Heat templates, etc.) Getting all of the files right is a time consuming and error prone process. Small changes in file syntax between releases complicates matters.

We already have many validators to ensure the files are properly formatted. We should add a facility for saving and version control on the undercloud. The same facility to integrate with an external versioning system.

Comment 2 Emilien Macchi 2015-12-01 21:16:43 UTC

One solution would be to create a custom fact in puppet-tripleo. That way, we could use this fact from Puppet manifests in TripleO Heat templates.

Comment 3 jliberma@redhat.com 2016-01-08 14:15:39 UTC

Integration with something like git would be nice so we could pull down updates from a central repository.

Comment 6 Mike Burns 2016-04-07 20:54:03 UTC

This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.

Comment 8 Jaromir Coufal 2016-09-27 03:40:31 UTC


*** This bug has been marked as a duplicate of bug 1296946 ***