[openstack-dev] [grenade] future direction on partial upgrade support
rbryant at redhat.com
Wed Jul 8 16:27:27 UTC 2015
On 07/08/2015 08:48 AM, Sean Dague wrote:
> On 07/06/2015 09:31 PM, Anita Kuno wrote:
>> On 07/06/2015 09:02 PM, Armando M. wrote:
>>> Thanks Sean, comments inline.
>>> On 6 July 2015 at 16:58, Sean M. Collins <sean at coreitpro.com> wrote:
>>>> I'd also like to chime in - we've had some discussions on -infra today
>>>> about the partial upgrade issue, and collected the following notes on an
>>>> One of the things identified, was the complexity of the DVR feature in
>>>> Neutron, and an attempt to simplify the partial upgrade job by not
>>>> enabling the DVR feature.
>>> The DVR issue is entirely orthogonal to this, but I am willing to play
>>>> Clark Boylan has proposed a patch to create a new job that runs on
>>>> multiple nodes, but does not have DVR enabled, in the hopes that having
>>>> less moving parts will allow the multinode grenade work to continue on a
>>>> parallel track,
>>> Who is leading the Grenade effort? Is it Clark?
>> Actually in terms of who stirred the pot, it's me.
>> There were too many people talking in too small of groups for me to
>> stand aside any longer. The grenade job looked like it was going to
>> continue to get blocked without everyone understanding all the factors
>> so I wanted to have folks have a discussion.
> Was out last week, so still catching up on some of this. Thanks Anita
> for stirring the pot.
> I've got a POC approach proposed in the following 3 patches to do
> partial testing in multinode via a post-stack.sh script in grenade (a
> way to tell grenade to do another thing after the base stack call is done).
> The grenade change - https://review.openstack.org/#/c/199073/
> The devstack-gate change that would put subnode setup into post-stack.sh
> - https://review.openstack.org/#/c/199091/
> And the project-config change to make this experimental on devstack-gate
> and grenade is here - https://review.openstack.org/#/c/199103/
> The first job I created here was a nova-net one, because I know enough
> about the paths, and the partial upgrade story on nova (which has been
> voting for a year), to know that all bugs introduced here are probably
> my own. But if we can get that working, and the nova partial job moved
> over, I think expanding it to arbitrary configs is probably pretty simple.
> Assistance ploughing through on this direction would be appreciated.
That all sounds great. It still seems quite reasonable to merge the
neutron job, that works just like the nova one that has been voting for
a year, to run as non-voting against neutron-only in the meantime.
More information about the OpenStack-dev