On 01/23/2016 02:32 AM, Steven Dake (stdake) wrote:
> Hello,
>
> In our weekly IRC meeting, all developers and others in attendance
> were in unanimous agreement that upgrades are the #1 priority for
> Kolla to solve [1]. inc0 has developed both a simple database
> migration implementation
Well we still can perform upgrades with some API downtime, so it's not
like we're bound to rolling upgrades on architectural level. I'll talk
to you after midcycle and we'll find a good way to tackle it.
Cheers,
Michal
On 26 January 2016 at 08:40, Michał Dulko wrote:
>
On 01/26/2016 10:11 AM, Michał Jastrzębski wrote:
> Well we still can perform upgrades with some API downtime, so it's not
> like we're bound to rolling upgrades on architectural level. I'll talk
> to you after midcycle and we'll find a good way to tackle it.
Sure, this will work. projects.yaml
On Mon, Jan 25, 2016 at 11:44 AM, Sean M. Collins
wrote:
> Just an FYI for anyone taking the Neutron piece, please feel free to
> attend the upgrades subteam - we have a meeting today.
>
> https://wiki.openstack.org/wiki/Meetings/Neutron-Upgrades-Subteam
> --
> Sean M.
On 1/26/16, 8:35 AM, "Michał Dulko" wrote:
>On 01/26/2016 10:11 AM, Michał Jastrzębski wrote:
>> Well we still can perform upgrades with some API downtime, so it's not
>> like we're bound to rolling upgrades on architectural level. I'll talk
>> to you after midcycle and
Just an FYI for anyone taking the Neutron piece, please feel free to
attend the upgrades subteam - we have a meeting today.
https://wiki.openstack.org/wiki/Meetings/Neutron-Upgrades-Subteam
--
Sean M. Collins
__
OpenStack
Hello,
In our weekly IRC meeting, all developers and others in attendance were in
unanimous agreement that upgrades are the #1 priority for Kolla to solve [1].
inc0 has developed both a simple database migration implementation around
keystone [2] as well as a more complex playbook around