Open Stack

Armando, have a happy holiday!

From: "Armando M." <armamig at gmail.com>
Reply-To: OpenStack List <openstack-dev at lists.openstack.org>
Date: Thursday, November 24, 2016 at 11:09 PM
To: OpenStack List <openstack-dev at lists.openstack.org>
Subject: Re: [openstack-dev] [neutron] stable/newton 'broken'



On 24 November 2016 at 11:12, Gary Kotton <gkotton at vmware.com<mailto:gkotton at vmware.com>> wrote:
The breakage is due to the fact that the projects do not have stable/newton branches cut.
This is something that I would have expected the neutron team to take care of as long as it was under the stadium/tent or whatever we want to call it.

Before [1] and [2] you were pulling from master all the time. You are in charge of your own project, so you are solely at fault of the issue you're complaining about.

[1] https://review.openstack.org/#/c/400462/
[2] https://review.openstack.org/#/c/402070/

The fact that the l2gw was removed may have been an indication that it should not have been there. But we have a clear responsibility to the community about this. Was there are mail indicating that it is excluded from the stadium/tent. I do not recall. I just woke up one morning discovering that you did that. There was not much discussion there.

LOL, you genuinely made me laugh. If you don't stay plugged, whose fault is that again? The discussion for the governance update did not happen overnight.


It is really unclear how the patches that you added below would have solved the problem.
We have made sure that the vmware-nsx code is back up and running. I just hope that others are unaffected by this.

My patch specifically would have not solved the problem you claim it's caused by the recent neutron master changes. I am just highlighting that prior to that you were always pulling from master. With my change you could simply set BRANCH=stable/newton in [3] in the appropriate branch and you'd be good to go.

[3] https://review.openstack.org/#/c/400462/1/tools/tox_install_project.sh@22

What I would like to see happen:

1.       L2gw gets a stable branch. At the moment the l2gw release team is non existent so community please advise how we can add cores
You can get hold of people [1] and ask them to make you join the team.

[1] https://review.openstack.org/#/admin/groups/532,members

2.       Tap-as-a-service is added to the stadium and tent.
 How is this relevant to this discussion?


A luta continua

From: "Armando M." <armamig at gmail.com<mailto:armamig at gmail.com>>
Reply-To: OpenStack List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Thursday, November 24, 2016 at 7:03 PM
To: OpenStack List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: Re: [openstack-dev] [neutron] stable/newton 'broken'



On 24 November 2016 at 02:38, Thierry Carrez <thierry at openstack.org<mailto:thierry at openstack.org>> wrote:
Gary Kotton wrote:
> Please see - http://logs.openstack.org/82/401882/1/check/gate-vmware-nsx-python27-db-ubuntu-xenial/1ac0686/console.html#_2016-11-24_06_58_38_520273
> Here we are pulling trunk as there is no stable version to use

Is neutron stable/newton really broken (like your subject seems to
indicate) ? Or only vmware-nsx stable/newton ? Since networking-l2gw and
tap-as-a-service are unofficial projects we can't guarantee that they
will create branches that match the official stable ones, so we should
try to avoid depending on them if possible...

This happens because the referenced projects have no newton branch and the consuming project's stable newton was pulling from the master branch (and [1] is the hack referenced below). The right fix would be to backport [2], create the stable branches of the projects to which vmware-nsx depends on and set the branch appropriately. This is what the neutron team does for the projects we look after.

This breakage was waiting to happen, and it just did.

[1] https://github.com/openstack/vmware-nsx/commit/9a455781e4db9fc360c3264b72c381c91dfa6a15<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openstack_vmware-2Dnsx_commit_9a455781e4db9fc360c3264b72c381c91dfa6a15&d=DgMFaQ&c=uilaK90D4TOVoH58JNXRgQ&r=PMrZQUSXojEgJQPh7cZrz1Lvja0OwAstg0U82FalZrw&m=9RMdQBJlmqlbq0DHIHP9NTT4ot9qb0nfNG5qMMfoE2o&s=v8Iagz-K729O8YOVJ-6w_1lXYa6UNXJt65nAnaHPBns&e=>
[2] https://github.com/openstack/vmware-nsx/commit/a951f5f9299ffdce268c54dc427a71706b8e41da<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openstack_vmware-2Dnsx_commit_a951f5f9299ffdce268c54dc427a71706b8e41da&d=DgMFaQ&c=uilaK90D4TOVoH58JNXRgQ&r=PMrZQUSXojEgJQPh7cZrz1Lvja0OwAstg0U82FalZrw&m=9RMdQBJlmqlbq0DHIHP9NTT4ot9qb0nfNG5qMMfoE2o&s=IjsdHWFgL__ygsTjKpo2YJsfuaX6AIuy4Jn82vkfZQg&e=>


--
Thierry Carrez (ttx)

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161125/c4199acf/attachment.html>