Bug 745493

Summary: Need schema version in definition xml
Product: [Retired] CloudForms Cloud Engine Reporter: jrd <jrd>
Component: aeolus-configserverAssignee: Greg Blomquist <gblomqui>
Status: CLOSED ERRATA QA Contact: wes hayutin <whayutin>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, deltacloud-maint, dgao, slinaber
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-15 20:50:18 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 jrd 2011-10-12 14:07:57 UTC 
Description of problem:

We're about to let this code out into the wild, in a form which exposes xml for templates and things to users.  It is therefore absolutely imperative that there be some kind of a version field at the top level of a deployable (or assembly or whatever) designating what the schema version is.

I advocate that we set the version to 1, and check it in audrey, though one could argue that "no version" implies "version 1.

This should be added prior to declaring feature-complete for 1.0.
Comment 2 Greg Blomquist 2012-01-11 22:29:47 UTC 
https://fedorahosted.org/pipermail/aeolus-devel/2012-January/008025.html
Comment 3 wes hayutin 2012-01-12 16:35:05 UTC 
adding to ce-sprint
Comment 4 wes hayutin 2012-01-12 16:41:26 UTC 
removing ce-sprint-next tracker
Comment 5 Greg Blomquist 2012-01-12 21:12:03 UTC 
https://github.com/aeolusproject/conductor/commit/442a2ac6c45a5cbe5399286494f955cc3c3a2b8e
Comment 6 Steve Linabery 2012-01-16 20:15:12 UTC 
aeolus-conductor-0.8.0-7.el6.src.rpm
Comment 8 wes hayutin 2012-02-10 22:11:33 UTC 
<deployable version="1.0" name="importedAMI">
Comment 9 errata-xmlrpc 2012-05-15 20:50:18 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-2012-0585.html