Hello,
M->P will be non trivial. One way to do it, a bit slow but safest would be
to upgrade step by step through every intermediate release.
Make sure to read and follow every projects upgrade notes, for example Nova
added placement api during o->n upgrade which requires additional steps.
Good
I can moderate HA session if you want (although there is one listed in
schedule?). Feel free to sign me up
On 28 April 2017 at 06:07, Jay Pipes wrote:
> On 04/28/2017 08:22 AM, Shamail Tahir wrote:
>>
>> Hi everyone,
>>
>> Most of the proposed/accepted Forum sessions
Hey Saverio!
That's great news:) We, Kolla community, would love to hear your
feedback and help you with any questions/issues you might have.
Please, join us in #openstack-kolla if you're not yet there.
Cheers,
Michal "inc0" Jastrzebski
On 3 February 2017 at 17:05, Saverio Proto
Hello Gilles,
Don't worry, debian images means debian *inside* container, we don't
really care about host OS. Techncially you could now do kolla-build
--base debian, but there is no maintenance of this distro and we're
planning to remove it alltogether. That's what this thread is about.
If you
Hello,
Kolla deprecates Heka in Ocata cycle, because Mozilla doesn't support
this project any more. During Ocata cycle we will prepare migration
plan and alternative to fill this missing functionality. As part of
N->O cycle we will migrate Heka to alternative we will decide upon in
following
t; (Adding back ops@)
>
> Michał Jastrzębski <inc...@gmail.com> wrote:
>
>> Yes, but it's a bit different. Difference being if you're doing it
>> right, you can keep nova running during upgrade. Can't say the same
>> for neutron.
>
>
> There is ongoing work