Re: [openstack-dev] [kolla] 40 hour time commitment requested from core reviewers before Feb 9th/10th midcycle

[Michał Dulko]

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  around keystone [2] as well as a more
> complex playbook around nova [3].  Keystone has merged – nova looks
> really solid but needs a little more attention.
>
> We have 10 core reviewers on the Kolla core review team.  I would ask
> that each core reviewer choose 1 or 2 services to solve upgrades on
> and spend 40 hours out of the next two weeks prior to our midcycle
> implementing the work items they have committed themselves to.  If you
> are not a core reviewer but feel you want to get involved in this
> work, please assign yourself to a maximum of one service and commit as
> described below.

In case of Cinder we're still in the process of deciding how *exactly*
will everything work in Mitaka and this will be a discussion point at
the current mid-cycle meetup There's a PoC based on latest Nova's
approach [1], which works, but we don't know if this will be the final
solution. If you're following the milestones then you will probably need
to merge pieces utilizing latest Cinder capabilities after M-3. Current
Cinder master will fail in a spectacular way when trying to run Liberty
and Mitaka services together (it isn't with patches [1] in place :)).

Anyone taking the Cinder piece - feel free to contact me with any questions.

Thanks,
Michal Dulko (IRC: dulek)

[1]
https://review.openstack.org/#/q/topic:bp/rpc-object-compatibility+owner:%22Michal+Dulko+%253Cmichal.dulko%2540intel.com%253E%22

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla] 40 hour time commitment requested from core reviewers before Feb 9th/10th midcycle

[Michał Jastrzębski]

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/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  around keystone [2] as well as a more
>> complex playbook around nova [3].  Keystone has merged – nova looks
>> really solid but needs a little more attention.
>>
>> We have 10 core reviewers on the Kolla core review team.  I would ask
>> that each core reviewer choose 1 or 2 services to solve upgrades on
>> and spend 40 hours out of the next two weeks prior to our midcycle
>> implementing the work items they have committed themselves to.  If you
>> are not a core reviewer but feel you want to get involved in this
>> work, please assign yourself to a maximum of one service and commit as
>> described below.
>
> In case of Cinder we're still in the process of deciding how *exactly*
> will everything work in Mitaka and this will be a discussion point at
> the current mid-cycle meetup There's a PoC based on latest Nova's
> approach [1], which works, but we don't know if this will be the final
> solution. If you're following the milestones then you will probably need
> to merge pieces utilizing latest Cinder capabilities after M-3. Current
> Cinder master will fail in a spectacular way when trying to run Liberty
> and Mitaka services together (it isn't with patches [1] in place :)).
>
> Anyone taking the Cinder piece - feel free to contact me with any questions.
>
> Thanks,
> Michal Dulko (IRC: dulek)
>
> [1]
> https://review.openstack.org/#/q/topic:bp/rpc-object-compatibility+owner:%22Michal+Dulko+%253Cmichal.dulko%2540intel.com%253E%22
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla] 40 hour time commitment requested from core reviewers before Feb 9th/10th midcycle

[Michał Dulko]

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 says that Kolla is released
independently, so I think you may tweak the process after the Mitaka
release when all the Cinder pieces will be in place.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla] 40 hour time commitment requested from core reviewers before Feb 9th/10th midcycle

[Sam Yaple]

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. Collins
>

Thanks Sean. I joined that meeting the other day and I will most likely
need to reach out again. Perhaps I can also get a +1 review from you and
your team once I have a patchset up for the upgrade of Neutron.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla] 40 hour time commitment requested from core reviewers before Feb 9th/10th midcycle

[Steven Dake (stdake)]

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 we'll find a good way to tackle it.
>
>Sure, this will work. projects.yaml says that Kolla is released
>independently, so I think you may tweak the process after the Mitaka
>release when all the Cinder pieces will be in place.

Note currently we are released-independently, but I would like to get us
to release-managed. I don't know if this will happen in Mitaka, or will
wait until the start of Newton.

Regards
-steve

>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla] 40 hour time commitment requested from core reviewers before Feb 9th/10th midcycle

[Sean M. Collins]

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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [kolla] 40 hour time commitment requested from core reviewers before Feb 9th/10th midcycle

[Steven Dake (stdake)]

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 nova [3].  Keystone has 
merged - nova looks really solid but needs a little more attention.

We have 10 core reviewers on the Kolla core review team.  I would ask that each 
core reviewer choose 1 or 2 services to solve upgrades on and spend 40 hours 
out of the next two weeks prior to our midcycle implementing the work items 
they have committed themselves to.  If you are not a core reviewer but feel you 
want to get involved in this work, please assign yourself to a maximum of one 
service and commit as described below.

The work for OpenStack services should be copy/paste/search/replace/test from 
inc0's work.  The work for infrastructure services (haproxy keepalived etc) is 
more R based around defining what needs to be done for these services.  If 
you take two playbooks, I recommend taking one of each type of service 
(infrastructure and an Openstack service).  Neutron, openvswitch, cinder and 
ceph will be the most difficult services remaining to upgrade, so if your in 
for a good challenge, pick up one of those ;)

To register for the 40 hour time commitment related to this critical 
development effort do the following:

  *ping me on IRC in the kolla IRC channel with a statement indicating you 
are able to commit 40 hours out of the next 2 weeks to focus on this critical 
development effort
  *   Find the appropriate upgrade-servicename and set yourself as the assignee
 *   https://launchpad.net/kolla/+milestone/mitaka-3
  *   identify yourself with a service under work items here:
 *   https://blueprints.launchpad.net/kolla/+spec/upgrade-kolla

The reason for the 40 hours?  I recognize I'm asking for a big time commitment 
from our community, but this effort is critical, critical, critical.  I want 
the attendees at the midcycle fully ramped up on our upgrades implementation.  
If we don't deliver upgrades in Mitaka, it will delay deployment of Kolla 
because there wont be a migration strategy between different versions.  That is 
why [1] was unanimous on upgrades ;)  This effort is critical for project 
progression.

Regards,
-steve

[1] 
http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-01-13-16.30.log.html#l-245
[2] https://blueprints.launchpad.net/kolla/+spec/upgrade-keystone
[3] https://blueprints.launchpad.net/kolla/+spec/upgrade-nova
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev