Re: [openstack-dev] [neutron] stable/newton 'broken'

2016-11-24 Thread Gary Kotton 
Armando, have a happy holiday!

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



On 24 November 2016 at 11:12, Gary Kotton 
<gkot...@vmware.com<mailto:gkot...@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." <arma...@gmail.com<mailto:arma...@gmail.com>>
Reply-To: OpenStack List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, November 24, 2016 at 7:03 PM
To: OpenStack List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [neutron] stable/newton 'broken'



On 24 November 2016 at 02:38, Thierry Carrez 
<thie...@openstack.org<mailto:thie...@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=DgMFaQ=uilaK90D4TOVoH58JNXRgQ=PMrZQUSXojEgJQPh7cZrz1Lvja0OwAstg0U82FalZrw=9RMdQBJlmqlbq0DHIHP9NTT4ot9qb0nfNG5qMMfoE2o=v8Iagz-K729O8YOVJ-6w_1lXYa6UNXJt65nAnaHPBns=>
[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=DgMFaQ=uilaK90D4TOVoH58JNXRgQ=PMrZQUSXojEgJQPh7cZrz1Lvja0OwAstg0U82FalZrw=9RMdQBJlmqlbq0DHIHP9NTT4ot9qb0nfNG5qMMfoE2o=IjsdHWFgL__ygsTjKpo2YJsfuaX6AIuy4Jn82vkfZQg=>


--
Thierry Carrez (ttx)

__
OpenStack Development Mailing List (not for

Re: [openstack-dev] [neutron] stable/newton 'broken'

2016-11-24 Thread reedip banerjee 
I agree to tap-as-a-service being tech-preview for this release to get over
this issue , if it is still relevant.


On Fri, Nov 25, 2016 at 2:39 AM, Armando M. <arma...@gmail.com> wrote:

>
>
> On 24 November 2016 at 11:12, Gary Kotton <gkot...@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." <arma...@gmail.com>
>> *Reply-To: *OpenStack List <openstack-dev@lists.openstack.org>
>> *Date: *Thursday, November 24, 2016 at 7:03 PM
>> *To: *OpenStack List <openstack-dev@lists.openstack.org>
>> *Subject: *Re: [openstack-dev] [neutron] stable/newton 'broken'
>>
>>
>>
>>
>>
>>
>>
>> On 24 November 2016 at 02:38, Thierry Carrez <thie...@openstack.org>
>> wrote:
>>
>> Gary Kotton wrote:
>> > Please see - http://logs.openstack.org/82/4
>> 01882/1/check/gate-vmware-nsx-python27-db-ubuntu-xenial/1ac0
>> 686/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/9a455781e
>> 4db9fc360c3264b72c381c91dfa6a15
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openstack_vmware-2Dnsx_commit_9a455781e4db9fc360c3264b72c381c91dfa6a15=DgMFaQ=uilaK90D4TOVoH58JNXRgQ=PMrZQUSXojEgJQPh7cZrz1Lvja0OwAstg0U82FalZrw=9RMdQBJlmqlbq0DHIHP9NTT4ot9qb0nfNG5qMMfoE2o=v8Iagz-K729O8YOVJ-6w_1lXYa6UNXJt65nAnaHPBns=>
>>
>> [2] https://github.com/op

Re: [openstack-dev] [neutron] stable/newton 'broken'

2016-11-24 Thread Armando M. 
On 24 November 2016 at 11:12, Gary Kotton <gkot...@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." <arma...@gmail.com>
> *Reply-To: *OpenStack List <openstack-dev@lists.openstack.org>
> *Date: *Thursday, November 24, 2016 at 7:03 PM
> *To: *OpenStack List <openstack-dev@lists.openstack.org>
> *Subject: *Re: [openstack-dev] [neutron] stable/newton 'broken'
>
>
>
>
>
>
>
> On 24 November 2016 at 02:38, Thierry Carrez <thie...@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=DgMFaQ=uilaK90D4TOVoH58JNXRgQ=PMrZQUSXojEgJQPh7cZrz1Lvja0OwAstg0U82FalZrw=9RMdQBJlmqlbq0DHIHP9NTT4ot9qb0nfNG5qMMfoE2o=v8Iagz-K729O8YOVJ-6w_1lXYa6UNXJt65nAnaHPBns=>
>
> [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=DgMFaQ=uilaK90D4TOVoH58JNXRgQ=PMrZQUSXojEgJQPh7cZrz1Lvja0OwAstg0U82FalZrw=9RMdQBJlmqlbq0DHIHP9NTT4ot9qb0nfNG5qMMfoE2o=IjsdHWFgL__ygsTjKpo2YJsfuaX6AIuy4Jn82vkfZQg=>
>
>
>
>
> --
> Thierry Carrez (ttx)
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://l

Re: [openstack-dev] [neutron] stable/newton 'broken'

2016-11-24 Thread Gary Kotton 
Sukdev has updated the group ☺
Happy holidays

From: Gary Kotton <gkot...@vmware.com>
Reply-To: OpenStack List <openstack-dev@lists.openstack.org>
Date: Thursday, November 24, 2016 at 9:12 PM
To: OpenStack List <openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [neutron] stable/newton 'broken'

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

2.  Tap-as-a-service is added to the stadium and tent.

A luta continua

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



On 24 November 2016 at 02:38, Thierry Carrez 
<thie...@openstack.org<mailto:thie...@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=DgMFaQ=uilaK90D4TOVoH58JNXRgQ=PMrZQUSXojEgJQPh7cZrz1Lvja0OwAstg0U82FalZrw=9RMdQBJlmqlbq0DHIHP9NTT4ot9qb0nfNG5qMMfoE2o=v8Iagz-K729O8YOVJ-6w_1lXYa6UNXJt65nAnaHPBns=>
[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=DgMFaQ=uilaK90D4TOVoH58JNXRgQ=PMrZQUSXojEgJQPh7cZrz1Lvja0OwAstg0U82FalZrw=9RMdQBJlmqlbq0DHIHP9NTT4ot9qb0nfNG5qMMfoE2o=IjsdHWFgL__ygsTjKpo2YJsfuaX6AIuy4Jn82vkfZQg=>


--
Thierry Carrez (ttx)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://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] [neutron] stable/newton 'broken'

2016-11-24 Thread Gary Kotton 
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. 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.
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.
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

2.   Tap-as-a-service is added to the stadium and tent.

A luta continua

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



On 24 November 2016 at 02:38, Thierry Carrez 
<thie...@openstack.org<mailto:thie...@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=DgMFaQ=uilaK90D4TOVoH58JNXRgQ=PMrZQUSXojEgJQPh7cZrz1Lvja0OwAstg0U82FalZrw=9RMdQBJlmqlbq0DHIHP9NTT4ot9qb0nfNG5qMMfoE2o=v8Iagz-K729O8YOVJ-6w_1lXYa6UNXJt65nAnaHPBns=>
[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=DgMFaQ=uilaK90D4TOVoH58JNXRgQ=PMrZQUSXojEgJQPh7cZrz1Lvja0OwAstg0U82FalZrw=9RMdQBJlmqlbq0DHIHP9NTT4ot9qb0nfNG5qMMfoE2o=IjsdHWFgL__ygsTjKpo2YJsfuaX6AIuy4Jn82vkfZQg=>


--
Thierry Carrez (ttx)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://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] [neutron] stable/newton 'broken'

2016-11-24 Thread Armando M. 
On 24 November 2016 at 02:38, Thierry Carrez  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
[2]
https://github.com/openstack/vmware-nsx/commit/a951f5f9299ffdce268c54dc427a71706b8e41da


> --
> Thierry Carrez (ttx)
>
> __
> 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] [neutron] stable/newton 'broken'

2016-11-24 Thread Gary Kotton 
I have worked around the issue by pegging the l2gw and tap-aas to specific 
commits.
This is a hack at the moment and will update as soon as the branches are cut.

Thanks and happy holidays

On 11/24/16, 4:11 PM, "Gary Kotton"  wrote:



On 11/24/16, 12:38 PM, "Thierry Carrez"  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...

[Gary] I Know that the vmware_nsx and midonet are broken. Until a few weeks 
ago the l2gw project was part of the big tent/stadium and it was removed. That 
was in trunk, but until then we had an obligation to have this working in 
stable/newton.
In order for us to be able to work with and consume community feature we 
need to have links to this project. So at the moment we are between a rock and 
a hard place.

I think that the tap-as-a-service is creating a tech preview branch. Which 
will solve the issues

For L2GW the community has people using this stuff in production … So we 
just need to make sure that they do not upgrade to newton.

-- 
Thierry Carrez (ttx)


__
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


__
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] [neutron] stable/newton 'broken'

2016-11-24 Thread Gary Kotton 


On 11/24/16, 12:38 PM, "Thierry Carrez"  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...

[Gary] I Know that the vmware_nsx and midonet are broken. Until a few weeks ago 
the l2gw project was part of the big tent/stadium and it was removed. That was 
in trunk, but until then we had an obligation to have this working in 
stable/newton.
In order for us to be able to work with and consume community feature we need 
to have links to this project. So at the moment we are between a rock and a 
hard place.

I think that the tap-as-a-service is creating a tech preview branch. Which will 
solve the issues

For L2GW the community has people using this stuff in production … So we just 
need to make sure that they do not upgrade to newton.

-- 
Thierry Carrez (ttx)

__
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] [neutron] stable/newton 'broken'

2016-11-24 Thread Thierry Carrez 
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...

-- 
Thierry Carrez (ttx)

__
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] [neutron] stable/newton 'broken'

2016-11-24 Thread Gary Kotton 
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

On 11/24/16, 10:00 AM, "Takashi Yamamoto"  wrote:

can you give me an example of breakage?

On Thu, Nov 24, 2016 at 4:19 PM, Gary Kotton  wrote:
> Hi,
>
> The change https://review.openstack.org/#/c/386845/ that landed yesterday
> has caused a breakage in stable/newton. This is due to the fact that the
> following projects do not have stable/newton tags:
>
> -  
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openstack_tap-2Das-2Da-2Dservice=DgICAg=uilaK90D4TOVoH58JNXRgQ=PMrZQUSXojEgJQPh7cZrz1Lvja0OwAstg0U82FalZrw=rhTtJFUiMBfCpZ3j8zoxSr5mK0E8RukJ6ajV1ATnO0Y=dXUw9DykF46Tk1oluf1fQMVmbhNKHbwG_scuNyTpXrM=
 
>
> -  
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openstack_networking-2Dl2gw=DgICAg=uilaK90D4TOVoH58JNXRgQ=PMrZQUSXojEgJQPh7cZrz1Lvja0OwAstg0U82FalZrw=rhTtJFUiMBfCpZ3j8zoxSr5mK0E8RukJ6ajV1ATnO0Y=DFa6PGUhmT9xowY1VGPsddAUZYVmZX2YsX9NIHQMpK0=
 
>
> Can the relevant release teams of the projects above please create the
> relevant tags.
>
> Thanks
>
> Gary
>
>
> __
> 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


__
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] [neutron] stable/newton 'broken'

2016-11-24 Thread Takashi Yamamoto 
can you give me an example of breakage?

On Thu, Nov 24, 2016 at 4:19 PM, Gary Kotton  wrote:
> Hi,
>
> The change https://review.openstack.org/#/c/386845/ that landed yesterday
> has caused a breakage in stable/newton. This is due to the fact that the
> following projects do not have stable/newton tags:
>
> -  https://github.com/openstack/tap-as-a-service
>
> -  https://github.com/openstack/networking-l2gw
>
> Can the relevant release teams of the projects above please create the
> relevant tags.
>
> Thanks
>
> Gary
>
>
> __
> 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

[openstack-dev] [neutron] stable/newton 'broken'

2016-11-23 Thread Gary Kotton 
Hi,
The change https://review.openstack.org/#/c/386845/ that landed yesterday has 
caused a breakage in stable/newton. This is due to the fact that the following 
projects do not have stable/newton tags:

-  https://github.com/openstack/tap-as-a-service

-  https://github.com/openstack/networking-l2gw
Can the relevant release teams of the projects above please create the relevant 
tags.
Thanks
Gary
__
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