Re: [openstack-dev] [openstack-ansible] [os-ansible-deployment] Kilo - Liberty Upgrade Problems

2015-07-31 Thread Jesse Pretorius
I'm adding openstack-operators too as this is a discussion that I think it would be useful to have their input for. On 30 July 2015 at 19:18, Ian Cordasco ian.corda...@rackspace.com wrote: Hey all, As you may have seen elsewhere on openstack-dev, OpenStack is changing the versioning for the

Re: [openstack-dev] [openstack-ansible] [os-ansible-deployment] Kilo - Liberty Upgrade Problems

2015-07-31 Thread Ian Cordasco
On 7/31/15, 07:40, Jesse Pretorius jesse.pretor...@gmail.com wrote: I'm adding openstack-operators too as this is a discussion that I think it would be useful to have their input for. I've removed them from the CC since I don't think we're supposed to cross-post. So what would the resulting

Re: [openstack-dev] [openstack-ansible] [os-ansible-deployment] Kilo - Liberty Upgrade Problems

2015-07-31 Thread Jesse Pretorius
On 31 July 2015 at 16:59, Ian Cordasco ian.corda...@rackspace.com wrote: So, I'm not proposing that yaprt be updated to forcibly add epochs or anything else. What yaprt will generate is exactly what upstream specifies. For example, glance would be version 11.0.0, nova would be 12.0.0, etc.

[openstack-dev] [openstack-ansible] [os-ansible-deployment] Kilo - Liberty Upgrade Problems

2015-07-30 Thread Ian Cordasco
Hey all, As you may have seen elsewhere on openstack-dev, OpenStack is changing the versioning for the service projects. This means our previous upgrade solution will not continue to work. For context, one of our project's goals is to have in-place upgrades be a reality. Previously, using our