[openstack-dev] [openstack-ansible] [os-ansible-deployment] Kilo -> Liberty Upgrade Problems
jesse.pretorius at gmail.com
Fri Jul 31 18:27:30 UTC 2015
On 31 July 2015 at 16:59, Ian Cordasco <ian.cordasco at 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.
> Giving a more concrete example (which I should have done in the original
> If we're upgrading Glance in the containers, we'll be upgrading from
> glance==2015.1.0 (obviously not exactly that, but for the sake of this
> example bear with me)
> And we'll use the version that yaprt reports to do
> # pip install glance==11.0.0
> So the repositories that we build can have both 2015.1.0 and 11.0.0 in it
> and pip will always install 11.0.0.
> This allows for
> 1. In-place upgrades
> 2. Reproducibility
> 3. Stability
> 4. Side-stepping upstream refusing to use epochs
Perfect, this is exactly what I was hoping for.
> Does that make sense?
Perfectly. +1 from me on the approach.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev