Open Stack

Some open source packages produce a list of commands that need to run in order to re-create a specific item. So, for a project, there would be a command to create the project, set quota, ... 

This is more friendly for tweaking afterwards (such as create me a project with "-devel" after the name) and can be made long term portable (assuming the commands are... )

Not sure it's the best approach for OpenStack but it is worth considering..

Tim

> -----Original Message-----
> From: Jay Pipes [mailto:jaypipes at gmail.com]
> Sent: 22 January 2014 20:24
> To: Salvo Rapisarda
> Cc: Openstack
> Subject: Re: [Openstack] Export tenant configuration
> 
> On Wed, 2014-01-22 at 20:06 +0100, Salvo Rapisarda wrote:
> > Il 22/01/2014 18.18, Jay Pipes ha scritto:
> > > On Wed, 2014-01-22 at 17:21 +0100, Salvo Rapisarda wrote:
> > >> But you surely know that MySQL is not the only SQL back-end for
> > >> OpenStack services. ;-)
> > >
> > > I don't see any mention of MySQL below by Nick Ma.
> >
> > Sorry, you are right.
> > MySQL is my OpenStack sql backend. :)
> >
> >
> > >> This is why I was looking for an alternative solution for
> > >> export/import the structure of my project.
> > >
> > > What do you mean by "structure of my project"? The data for the
> > > various resources consumed by your project is stored in a number of databases.
> > > Additionally, with data about the project itself is stored in the
> > > Keystone back-end storage (either RDBMS, KVS or LDAP).
> > >
> > > If you want to port the network configuration from Grizzly to
> > > Havana, UI would just make a snapshot of your Quantum database in
> > > Grizzly and start your Havana database from that snapshot, and run
> > > the db schema migrations on it.
> > >
> > > Best,
> > > -jay
> > >
> > I know, but I think can be helpful to use a tool for generate, for
> > example, an XML file of my Project that is compatible with the all
> > releases of OpenStack.
> 
> I think "helpful" and "XML file" should not be used in the same sentence.
> 
> That said, I'm not sure such a thing would really be possible. So many schema changes happen from one release to another, never mind
> changes in capabilities for underlying technologies like libvirt, OVS, etc...
> 
> Best,
> -jay
> 
> 
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack