[openstack-dev] [neutron] [drivers] Cancelling weekly meeting on November 23rd

[Miguel Lavalle]

Dear Neutron team,

Due to the Thanksgiving Holiday in the USA, several members of the team
will not be able to attend the weekly meeting. Let's cancel it and resume
normally on the 30th of November

Best regards

Miguel
__
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] hi neutorn core team would you help to review this pr. it has blocked our pr merged.Thanks advance!

[songbai...@szzt.com.cn]

https://review.openstack.org/#/c/616211/ 



songbai...@szzt.com.cn
__
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] [drivers] Cancelling weekly meeting on November 16th

[Miguel Lavalle]

Hi Neutron Team,

The majority of the drivers team (Akihiro, Takashi and myself) are
attending the Berlin Summit and will be travelling the day of the meeting.
As a consequence, let's cancel it.

Best regards

Miguel
__
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] [Upgrade] No meetings on Nov. 15th and 22nd

[Lujin Luo]

Hi everyone,

I won't be able to chair the Neutron Upgrade subteam meeting on 15th,
and some team members are at the summit. Let's skip it. Also, since
22nd is Thanksgiving in the US, let skip the meeting on that day too.

We will resume the meeting on 29th.

Happy early Thanksgiving!

Best regards,
Lujin

__
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] Cancelling weekly meeting on November 12th

[Miguel Lavalle]

Dear Neutron Team,

Due to the OpenStack Summit in Berlin and the activities around it, let's
cancel the weekly IRC meeting on November 12th. We will resume normally on
the 20th.

Best regards

Miguel
__
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][neutron-release] feature/graphql branch rebase

[Gilles Dubreuil]

On 10/11/18 12:03 am, Jeremy Stanley wrote:

On 2018-11-09 16:35:22 +1100 (+1100), Gilles Dubreuil wrote:

Could you please provide permission [1] to upload commit merges?

I'm getting the following error after merging HEAD:

$ git review -R feature/graphql
remote:
remote: Processing changes: refs: 1
remote: Processing changes: refs: 1, done
To ssh://review.openstack.org:29418/openstack/neutron.git
  ! [remote rejected]   HEAD -> refs/publish/feature/graphql/bug/1802101
(you are not allowed to upload merges)
error: failed to push some refs to
'ssh://q-1ille...@review.openstack.org:29418/openstack/neutron.git'

[...]

Per openstack/neutron's ACL[*] you need to be made a member of the
neutron-release group in Gerrit[**]. (This permission is tightly
controlled to avoid people accidentally pushing merge commits, which
is all too easy if you're not careful to keep your branches clean.)


That's fair enough.

I'll ask the neutron-release group then.

Thanks



[*] 
https://git.openstack.org/cgit/openstack-infra/project-config/tree/gerrit/acls/openstack/neutron.config
[**] https://review.openstack.org/#/admin/groups/neutron-release

__
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][neutron-release] feature/graphql branch rebase

[Jeremy Stanley]

On 2018-11-09 16:35:22 +1100 (+1100), Gilles Dubreuil wrote:
> Could you please provide permission [1] to upload commit merges?
> 
> I'm getting the following error after merging HEAD:
> 
> $ git review -R feature/graphql
> remote:
> remote: Processing changes: refs: 1
> remote: Processing changes: refs: 1, done
> To ssh://review.openstack.org:29418/openstack/neutron.git
>  ! [remote rejected]   HEAD -> refs/publish/feature/graphql/bug/1802101
> (you are not allowed to upload merges)
> error: failed to push some refs to
> 'ssh://q-1ille...@review.openstack.org:29418/openstack/neutron.git'
[...]

Per openstack/neutron's ACL[*] you need to be made a member of the
neutron-release group in Gerrit[**]. (This permission is tightly
controlled to avoid people accidentally pushing merge commits, which
is all too easy if you're not careful to keep your branches clean.)

[*] 
https://git.openstack.org/cgit/openstack-infra/project-config/tree/gerrit/acls/openstack/neutron.config
[**] https://review.openstack.org/#/admin/groups/neutron-release
-- 
Jeremy Stanley


signature.asc
Description: PGP signature
__
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] CI meeting on 13.11.2018 cancelled

[Slawomir Kaplonski]

Hi,

Due to summit in Berlin Neutron CI meeting on 13.11.2018 is cancelled. Next 
meeting will be as usual on 20.11.2018.

— 
Slawek Kaplonski
Senior software engineer
Red Hat


__
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][neutron-release] feature/graphql branch rebase

[Gilles Dubreuil]

Hi Miguel,

Could you please provide permission [1] to upload commit merges?

I'm getting the following error after merging HEAD:

$ git review -R feature/graphql
remote:
remote: Processing changes: refs: 1
remote: Processing changes: refs: 1, done
To ssh://review.openstack.org:29418/openstack/neutron.git
 ! [remote rejected]   HEAD -> 
refs/publish/feature/graphql/bug/1802101 (you are not allowed to upload 
merges)
error: failed to push some refs to 
'ssh://q-1ille...@review.openstack.org:29418/openstack/neutron.git'


Thanks,
Gilles

[1] 
https://github.com/openstack-infra/gerrit/blob/master/Documentation/error-not-allowed-to-upload-merges.txt



On 23/10/18 7:30 pm, Gilles Dubreuil wrote:


Hi Miguel,

Thank you for your help.

I'll use those precious instructions next time.

Cheers,
Gilles

On 16/10/18 1:32 am, Miguel Lavalle wrote:

Hi Gilles,

The merge of master into feature/graphql  has been approved: 
https://review.openstack.org/#/c/609455. In the future, you can 
create your own merge patch following the instructions here: 
https://docs.openstack.org/infra/manual/drivers.html#merge-master-into-feature-branch. 
The Neutron team will catch it in Gerrit and review it


Regards

Miguel

On Thu, Oct 4, 2018 at 11:44 PM Gilles Dubreuil > wrote:


Hey Neutron folks,

I'm just reiterating the request.

Thanks


On 20/06/18 11:34, Gilles Dubreuil wrote:
> Could someone from the Neutron release group rebase
feature/graphql
> branch against master/HEAD branch please?
>
> Regards,
> Gilles
>
>


--
Gilles Dubreuil
Senior Software Engineer - Red Hat - Openstack DFG Integration
Email:gil...@redhat.com
GitHub/IRC: gildub
Mobile: +61 400 894 219


--
Gilles Dubreuil
Senior Software Engineer - Red Hat - Openstack DFG Integration
Email: gil...@redhat.com
GitHub/IRC: gildub
Mobile: +61 400 894 219

__
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] os-ken report for last week

[Hongbin Lu]

Hi all,

I am used to report the os-ken related progress in the neutron team meeting. 
After switching to winter time, I am not able to attend the meeting at Tuesday 
1400 UTC. I sent out the report in the ML instead. Below is the progress in 
last week.

* The os-ken 0.2.0 is released: https://review.openstack.org/#/c/614315/
* The os-ken is added to global requirement: 
https://review.openstack.org/#/c/609018/
* There are experimental patches for testing the switchover from Ryu to os-ken:
** neutron: https://review.openstack.org/#/c/607008/
** neutron-dynamic-routing: https://review.openstack.org/#/c/608357/
* The os-ken patches in the review queue: 
https://review.openstack.org/#/q/project:openstack/os-ken+AND+status:open

Best regards,
Hongbin

__
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] Bug deputy report

[270162781]

Hi all, I'm zhaobo, I was the bug deputy for the last week and I'm afraid that 
cannot attending the comming upstream meeting so I'm sending out this report: 
Last week there are some high priority bugs for neutron . What a quiet week. 
;-) Also some bugs need to attention, I list them here: [High] Race conditions 
in neutron_tempest_plugin/scenario/test_security_groups.py 
https://bugs.launchpad.net/neutron/+bug/1801306 TEMPEST CI FAILURE, the result 
is caused by some tempest tests operate the default SG, that will affect other 
test cases. Migration causes downtime while doing bulk_pull 
https://bugs.launchpad.net/neutron/+bug/1801104 Seems refresh the local cache 
so frequently, also if the records we want from neutron-server are so large, 
could we improve the query filter for improve performance on agent rpc? [Need 
Attention] Network: concurrent issue for create network operation 
https://bugs.launchpad.net/neutron/+bug/1800417 This looks like an exist issue 
for master. I think this must be an issue, but the bug lacks some logs for deep 
into, so hope the reporter can provider more details about it at first. 
[RFE]Neutron API Server: unexpected behavior with multiple long live clients 
https://bugs.launchpad.net/neutron/+bug/1800599 I have changed this bug to a 
new RFE, as it introduces an new mechanism to make sure each request can be 
processed to the maximum extend if possible, without long time waiting on 
client side. Thanks, Best Regards, ZhaoBo__
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 stadium project Tempest plugins

[Ghanshyam Mann]

  On Wed, 24 Oct 2018 05:08:11 +0900 Slawomir Kaplonski 
 wrote  
 > Hi,
 > 
 > Thx Miguel for raising this.
 > List of tempest plugins is on 
 > https://docs.openstack.org/tempest/latest/plugin-registry.html - if URL for 
 > Your plugin is the same as Your main repo, You should move Your tempest 
 > plugin code.

Thanks mlavalle, slaweq for bringing up this discussion. 

Separating the Tempest plugin from service repo was Queens goal and that goal 
clearly state the benefit of having the separate plugins repo [1]. For Neturon, 
that goal was marked as Complete after creating the neutron-temepst-plugin[2] 
and work to separate the neutron stadium project's tempest plugins was left 
out. I think many of the projects did not all. 

This came up while discussing the tempest plugins CI setup [3]. If you need any 
help from QA team, feel free to ping us on #openstack-qa channel. 


[1] https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html
[2] https://review.openstack.org/#/c/524605/
[3] 
https://etherpad.openstack.org/p/tempest-plugins-ci-release-tagging-clarification


-gmann

 > 
 > 
 > > Wiadomość napisana przez Miguel Lavalle  w dniu 
 > > 23.10.2018, o godz. 16:59:
 > > 
 > > Dear Neutron Stadium projects,
 > > 
 > > In a QA session during the recent PTG in Denver, it was suggested that the 
 > > Stadium projects should move their Tempest plugins to a repository of 
 > > their own or added to the Neutron Tempest plugin repository 
 > > (https://github.com/openstack/neutron-tempest-plugin). The purpose of this 
 > > message is to start a conversation for the Stadium projects to indicate 
 > > what is their preference. Please respond to this thread indicating how do 
 > > you want to move forward.
 > > 
 > > Best regards
 > > 
 > > Miguel
 > > __
 > > 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
 > 
 > — 
 > Slawek Kaplonski
 > Senior software engineer
 > Red Hat
 > 
 > 
 > __
 > 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][tc] Seeking feedback on the OpenStack cloud vision

[Zane Bitter]

Greetings, Neutron team!
As you may be aware, I've been working with other folks in the community 
on documenting a vision for OpenStack clouds (formerly known as the 
'Technical Vision') - essentially to interpret the mission statement in 
long-form, in a way that we can use to actually help guide decisions. 
You can read the latest draft here: https://review.openstack.org/592205


We're trying to get feedback from as many people as possible - in many 
ways the value is in the process of coming together to figure out what 
we're trying to achieve as a community with OpenStack and how we can 
work together to build it. The document is there to help us remember 
what we decided so we don't have to do it all again over and over.


The vision is structured with two sections that apply broadly to every 
project in OpenStack - describing the principles that we believe are 
essential to every cloud, and the ones that make OpenStack different 
from some other clouds. The third section is a list of design goals that 
we want OpenStack as a whole to be able to meet - ideally each project 
would be contributing toward one or more of these design goals.


Neutron pretty obviously falls under the goals of 'Basic Physical Data 
Center Management' and 'Hardware Virtualisation'.


The last paragraph of the 'Plays Well With Others' design goal (about 
offering standalone layers) was prompted by discussions in Cinder. My 
sense is that this is less relevant to Neutron because of the existence 
of OpenDaylight, but it might be something to pay particular attention 
to when reviewing the document.


If you would like me or another TC member to join one of your team IRC 
meetings to discuss further what the vision means for your team, please 
reply to this thread to set it up. You are also welcome to bring up any 
questions in the TC IRC channel, #openstack-tc - there's more of us 
around during Office Hours 
(https://governance.openstack.org/tc/#office-hours), but you can talk to 
us at any time.


Feedback can also happen either in this thread or on the review 
https://review.openstack.org/592205


If the team is generally happy with the vision as it is and doesn't have 
any specific feedback, that's cool but I'd like to request that at least 
the PTL leave a vote on the review. It's important to know whether we 
are actually developing a consensus in the community or just talking to 
ourselves :)


many thanks,
Zane.

__
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 stadium project Tempest plugins

[Slawomir Kaplonski]

Hi,

Thx Miguel for raising this.
List of tempest plugins is on 
https://docs.openstack.org/tempest/latest/plugin-registry.html - if URL for 
Your plugin is the same as Your main repo, You should move Your tempest plugin 
code.


> Wiadomość napisana przez Miguel Lavalle  w dniu 
> 23.10.2018, o godz. 16:59:
> 
> Dear Neutron Stadium projects,
> 
> In a QA session during the recent PTG in Denver, it was suggested that the 
> Stadium projects should move their Tempest plugins to a repository of their 
> own or added to the Neutron Tempest plugin repository 
> (https://github.com/openstack/neutron-tempest-plugin). The purpose of this 
> message is to start a conversation for the Stadium projects to indicate what 
> is their preference. Please respond to this thread indicating how do you want 
> to move forward.
> 
> Best regards
> 
> Miguel
> __
> 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

— 
Slawek Kaplonski
Senior software engineer
Red Hat


__
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 stadium project Tempest plugins

[Miguel Lavalle]

Dear Neutron Stadium projects,

In a QA session during the recent PTG in Denver, it was suggested that the
Stadium projects should move their Tempest plugins to a repository of their
own or added to the Neutron Tempest plugin repository (
https://github.com/openstack/neutron-tempest-plugin). The purpose of this
message is to start a conversation for the Stadium projects to indicate
what is their preference. Please respond to this thread indicating how do
you want to move forward.

Best regards

Miguel
__
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] Bug deputy report week of October 15th

[Brian Haley]

Hi,

I was Neutron bug deputy last week. Below is a short summary about 
reported bugs.


Note: I will not be at the team meeting this morning, sorry for the late 
notice.


-Brian


Critical bugs
-
None

High bugs
-

* https://bugs.launchpad.net/neutron/+bug/1798472 - Fullstack tests 
fails because process is not killed properly

  - gate failure

* https://bugs.launchpad.net/neutron/+bug/1798475 - Fullstack test 
test_ha_router_restart_agents_no_packet_lost failing

  - gate failure

* https://bugs.launchpad.net/neutron/+bug/1799124 - Path MTU discovery 
fails for VMs with Floating IP behind DVR routers

  - Needs confirmation, I took ownership

Medium bugs
---

* https://bugs.launchpad.net/neutron/+bug/1798577
  - Fix proposed, https://review.openstack.org/#/c/606007/

* A number of port-forwarding bugs were filed by Liu Yulong
  - https://bugs.launchpad.net/neutron/+bug/1799135
  - https://bugs.launchpad.net/neutron/+bug/1799137
  - https://bugs.launchpad.net/neutron/+bug/1799138
  - https://bugs.launchpad.net/neutron/+bug/1799140
  - https://bugs.launchpad.net/neutron/+bug/1799150
  - https://bugs.launchpad.net/neutron/+bug/1799155
  - Will discuss with Liu if he is working on them

Wishlist bugs
-

* https://bugs.launchpad.net/neutron/+bug/146 - When use ‘neutron 
net-update’, we cannot change the 'vlan-transparent' dynamically

  - not a bug as per the API definition, asked if proposing extension
  - perhaps possible to implement in backward-compatible way

* https://bugs.launchpad.net/neutron/+bug/1799178 - l2 pop doesn't 
always provide the whole list of fdb entries on agent restart

  - Need a smarter way to detect agent restarts

Invalid bugs


* https://bugs.launchpad.net/neutron/+bug/1798536 - OpenVswitch: qg-XXX 
goes to br-int instead of br-ext


* https://bugs.launchpad.net/neutron/+bug/1798689 -
Fullstack test test_create_one_default_qos_policy_per_project failed
  - Fixed by https://review.openstack.org/#/c/610280/

Further triage required
---

* https://bugs.launchpad.net/neutron/+bug/1798588 - 
neutron-openvswitch-agent break network connection on second reboot

  - Asked for more information from submitter

* https://bugs.launchpad.net/neutron/+bug/1798688 - iptables_hybrid 
tests 
tempest.api.compute.servers.test_servers_negative.ServersNegativeTestJSON.test_shelve_shelved_server 
failed

  - tempest.lib.exceptions.NotFound: Object not found
Details: {u'message': u'Instance None could not be found.', 
u'code': 404}

Not sure if issue with shelve/unshelve since the instance is gone

* https://bugs.launchpad.net/bugs/1798713 - [fwaas]wrong judgment in 
_is_supported_by_fw_l2_driver method

  - Fix proposed, https://review.openstack.org/#/c/605988
Need someone from FWaaS team to confirm and set priority

__
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][neutron-release] feature/graphql branch rebase

[Gilles Dubreuil]

Hi Miguel,

Thank you for your help.

I'll use those precious instructions next time.

Cheers,
Gilles

On 16/10/18 1:32 am, Miguel Lavalle wrote:

Hi Gilles,

The merge of master into feature/graphql  has been approved: 
https://review.openstack.org/#/c/609455. In the future, you can create 
your own merge patch following the instructions here: 
https://docs.openstack.org/infra/manual/drivers.html#merge-master-into-feature-branch. 
The Neutron team will catch it in Gerrit and review it


Regards

Miguel

On Thu, Oct 4, 2018 at 11:44 PM Gilles Dubreuil > wrote:


Hey Neutron folks,

I'm just reiterating the request.

Thanks


On 20/06/18 11:34, Gilles Dubreuil wrote:
> Could someone from the Neutron release group rebase feature/graphql
> branch against master/HEAD branch please?
>
> Regards,
> Gilles
>
>


--
Gilles Dubreuil
Senior Software Engineer - Red Hat - Openstack DFG Integration
Email: gil...@redhat.com
GitHub/IRC: gildub
Mobile: +61 400 894 219

__
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] [drivers] Cancelling drivers meeting on October 19th

[Miguel Lavalle]

Dear Neutron team,

We don't have triaged RFEs to be discussed during the drivers meeting on
October 19th. So let's skip that meeting and we will resume normally on the
26th.

Best regards

Miguel
__
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][neutron-release] feature/graphql branch rebase

[Miguel Lavalle]

Hi Gilles,

The merge of master into feature/graphql  has been approved:
https://review.openstack.org/#/c/609455. In the future, you can create your
own merge patch following the instructions here:
https://docs.openstack.org/infra/manual/drivers.html#merge-master-into-feature-branch.
The Neutron team will catch it in Gerrit and review it

Regards

Miguel

On Thu, Oct 4, 2018 at 11:44 PM Gilles Dubreuil  wrote:

> Hey Neutron folks,
>
> I'm just reiterating the request.
>
> Thanks
>
>
> On 20/06/18 11:34, Gilles Dubreuil wrote:
> > Could someone from the Neutron release group rebase feature/graphql
> > branch against master/HEAD branch please?
> >
> > Regards,
> > Gilles
> >
> >
>
>
__
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] Bug deputy report - week 42

[Slawomir Kaplonski]

Hi,

I was on bug deputy in week of 8.10.2018 to 15.10.2018.
Below is summary of reported bugs for Neutron:


Bugs which needs some look to confirm them:
* https://bugs.launchpad.net/neutron/+bug/1795432 - neutron does not create the 
necessary iptables rules for dhcp agents when linuxbridge is used
This one should be confirmed on multinode environment with Linuxbridge, 
I didn’t have such env to work on that.

* https://bugs.launchpad.net/neutron/+bug/1797368 - Trunk: different behavior 
of admin_state_up attribute between trunk and port
I have no experience with trunks and I would like someone else to take 
a look on that. From description it looks for me that it’s valid issue

* https://bugs.launchpad.net/neutron/+bug/1795816 - neutron_dynamic_routing Bgp 
floatingip_update KeyError: 'last_known_router_id
Should be good that someone more familiar with neutron-dynamic-routing 
could take a look on it.
I don’t have environment to confirm it but from bug report it looks as 
valid bug.
Importance set to medium


Bugs triaged or triage in progress already:
* https://bugs.launchpad.net/neutron/+bug/1796491 - DVR Floating IP setup in 
the SNAT namespace of the network node and also in the qrouter namespace in the 
compute node 
Swami is checking if it wasn’t already fixed…

* https://bugs.launchpad.net/neutron/+bug/1796824 - Port in some type of 
device_owner should not allow update IP address
Importance set to Medium

* https://bugs.launchpad.net/neutron/+bug/1797037 - Extra routes configured on 
routers are not set in the router namespace and snat namespace with DVR-HA 
routers
already in progress, importance Medium

* https://bugs.launchpad.net/neutron/+bug/1796854 - Neutron doesn't respect 
advscv role while creating port
Importance set to Medium, this is an neutron-lib issue

* https://bugs.launchpad.net/neutron/+bug/1796976 - neutron.conf needs 
lock_path set for router to operate 
Docs issue - importance Low,

* https://bugs.launchpad.net/neutron/+bug/1797084 - Stale namespaces when 
fallback tunnels are present
Importance Low, patch already proposed by dalvarez

* https://bugs.launchpad.net/neutron/+bug/1797298 - Router gateway device are 
repeatedly configured When ha changed
Importance Low, patch already proposed

* https://bugs.launchpad.net/neutron/+bug/1796703 - HA router interfaces in 
standby state 
Needs look by some L3 experts - I already raised this on on L3 Sub-team 
meeting and Brian is triaging it now

* https://bugs.launchpad.net/neutron/+bug/1796230 - no libnetfilter-log1 
package on centos 
Waiting for reply for Brian’s question now….

* https://bugs.launchpad.net/neutron/+bug/1763608 - Netplan ignores Interfaces 
without IP Addresses 
I asked how it’s related to neutron as I don’t understand that. Waiting 
for reply now.

* https://bugs.launchpad.net/neutron/+bug/1795222 - [l3] router agent side 
gateway IP not changed if directly change IP address
Importance medium, patch already proposed

* https://bugs.launchpad.net/neutron/+bug/1797663 - refactor def 
_get_dvr_sync_data from neutron/db/l3_dvr_db.py
Importance wishlist,

* https://bugs.launchpad.net/neutron/+bug/1796629 - Incorrectly passing ext_ips 
as gw_ips after creating router gateway
Importance set to medium


RFEs:
* https://bugs.launchpad.net/neutron/+bug/1796925 - [RFE] port forwarding 
floating IP QoS
* https://bugs.launchpad.net/neutron/+bug/1797140 - [RFE] create port by 
providing parameters subnet_id only

Potential RFEs maybe:
* https://bugs.launchpad.net/neutron/+bug/1792890 - The user can delete a 
security group which is used as remote-group-id
It looks like maybe potential RFE as it may change current API behavior


— 
Slawek Kaplonski
Senior software engineer
Red Hat


__
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] Stable Core Team Update

[Matt Riedemann]

On 10/9/2018 11:08 AM, Miguel Lavalle wrote:
Since it has been more than a week since this nomination was posted and 
we have received only positive feedback, can we move ahead and add 
Bernard Cafarelli to Neutron Stable core team?


Done:

https://review.openstack.org/#/admin/groups/539,members

--

Thanks,

Matt

__
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] Stable Core Team Update

[Miguel Lavalle]

Hi Stable Team,

Since it has been more than a week since this nomination was posted and we
have received only positive feedback, can we move ahead and add Bernard
Cafarelli to Neutron Stable core team?

Thanks and regards

Miguel

On Wed, Oct 3, 2018 at 8:32 AM Nate Johnston 
wrote:

> On Tue, Oct 02, 2018 at 10:41:58AM -0500, Miguel Lavalle wrote:
>
> > I want to nominate Bernard Cafarrelli as a stable core reviewer for
> Neutron
> > and related projects. Bernard has been increasing the number of stable
> > reviews he is doing for the project [1]. Besides that, he is a stable
> > maintainer downstream for his employer (Red Hat), so he can bring that
> > valuable experience to the Neutron stable team.
>
> I'm not on the stable team, but an enthusiastic +1 from me!
>
> Nate
>
> __
> 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][stadium][networking] Seeking proposals for non-voting Stadium projects in Neutron check queue

[Michel Peterson]

On Sun, Sep 30, 2018 at 3:43 AM Miguel Lavalle  wrote:

> The next step is for each project to propose the jobs that they want to
> run against Neutron patches.
>

This is fantastic. Do you plan to have all patches under a single topic for
easier tracking? I'll be handling the proposal of these jobs for
networking-odl and would like to know this before sending them for review.

In addition, since these will be non-voting for Stadium projects, how will
the mechanics be to avoid breakage of such projects?
__
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][neutron-release] feature/graphql branch rebase

[Gilles Dubreuil]

Hey Neutron folks,

I'm just reiterating the request.

Thanks


On 20/06/18 11:34, Gilles Dubreuil wrote:
Could someone from the Neutron release group rebase feature/graphql 
branch against master/HEAD branch please?


Regards,
Gilles





__
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] Please opt-in for neutron-lib patches

[Boden Russell]

On 10/3/18 10:16 AM, Eric Fried wrote:
> We would like networking-powervm to be included, and have proposed [5],
> but are wondering why we weren't picked up in [6]. Your email [1] says
>
> "If your project isn't in [3][4],
> but you think it should be; it maybe missing a recent neutron-lib
> version in your requirements.txt."
>
> What's "recent"? I see the latest (per the requirements project) is
> 1.19.0 and we have 1.18.0. Should we bump?
I must've accidentally missed powervm; thanks for following up.
The fact that you're not using neutron-lib 1.19.0 has nothing to do with it;
this was a user error.

It's probably a good idea to move up to 1.19.0 once neutron does [1].
Typically I will propose the bump for all such projects, but I was waiting
for the list of opt-in consumers before doing so.

[1] https://review.openstack.org/#/c/605690


__
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] Please opt-in for neutron-lib patches

[Eric Fried]

Hi Boden.

Love this initiative.

We would like networking-powervm to be included, and have proposed [5],
but are wondering why we weren't picked up in [6]. Your email [1] says

"If your project isn't in [3][4],
but you think it should be; it maybe missing a recent neutron-lib
version in your requirements.txt."

What's "recent"? I see the latest (per the requirements project) is
1.19.0 and we have 1.18.0. Should we bump?

Thanks,
efried

[5] https://review.openstack.org/#/c/607625/
[6] https://etherpad.openstack.org/p/neutron-sibling-setup

On 10/03/2018 10:43 AM, Boden Russell wrote:
> Just a friendly reminder that networking projects now need to opt-in for
> neutron-lib consumption patches [1].
> 
> Starting next week (September 8) I'd like to start basing consumption
> patches on those projects that have opted-in. If there are exceptions
> please let me know so we can track them accordingly.
> 
> Thanks
> 
> [1]
> http://lists.openstack.org/pipermail/openstack-dev/2018-September/135063.html
> 
> __
> 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] Please opt-in for neutron-lib patches

[Boden Russell]

Just a friendly reminder that networking projects now need to opt-in for
neutron-lib consumption patches [1].

Starting next week (September 8) I'd like to start basing consumption
patches on those projects that have opted-in. If there are exceptions
please let me know so we can track them accordingly.

Thanks

[1]
http://lists.openstack.org/pipermail/openstack-dev/2018-September/135063.html

__
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][stadium][networking] Seeking proposals for non-voting Stadium projects in Neutron check queue

[Miguel Lavalle]

Thomas, Miguel,

Next step is just push a patch for review with the definition of your job.
We can discuss the details in Gerrit

Cheers

On Wed, Oct 3, 2018 at 4:39 AM Miguel Angel Ajo Pelayo 
wrote:

> That's fantastic,
>
>I believe we could add some of the networking ovn jobs, we need to
> decide which one would be more beneficial.
>
> On Tue, Oct 2, 2018 at 10:02 AM  wrote:
>
>> Hi Miguel, all,
>>
>> The initiative is very welcome and will help make it more efficient to
>> develop in stadium projects.
>>
>> legacy-tempest-dsvm-networking-bgpvpn-bagpipe would be a candidate, for
>> networking-bgpvpn and networking-bagpipe (it covers API and scenario
>> tests for the BGPVPN API (networking-bgpvpn) and given that
>> networking-bagpipe is used as reference driver, it exercises a large
>> portion of networking-bagpipe as well).
>>
>> Having this one will help a lot.
>>
>> Thanks,
>>
>> -Thomas
>>
>>
>> On 9/30/18 2:42 AM, Miguel Lavalle wrote:
>> > Dear networking Stackers,
>> >
>> > During the recent PTG in Denver, we discussed measures to prevent
>> > patches merged in the Neutron repo breaking Stadium and related
>> > networking projects in general. We decided to implement the following:
>> >
>> > 1) For Stadium projects, we want to add non-voting jobs to the Neutron
>> > check queue
>> > 2) For non stadium projects, we are inviting them to add 3rd party CI
>> jobs
>> >
>> > The next step is for each project to propose the jobs that they want
>> > to run against Neutron patches.
>> >
>> > Best regards
>> >
>> > Miguel
>> >
>> >
>> __
>> > 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
>>
>>
>> _
>>
>> Ce message et ses pieces jointes peuvent contenir des informations
>> confidentielles ou privilegiees et ne doivent donc
>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
>> recu ce message par erreur, veuillez le signaler
>> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
>> electroniques etant susceptibles d'alteration,
>> Orange decline toute responsabilite si ce message a ete altere, deforme
>> ou falsifie. Merci.
>>
>> This message and its attachments may contain confidential or privileged
>> information that may be protected by law;
>> they should not be distributed, used or copied without authorisation.
>> If you have received this email in error, please notify the sender and
>> delete this message and its attachments.
>> As emails may be altered, Orange is not liable for messages that have
>> been modified, changed or falsified.
>> Thank you.
>>
>>
>> __
>> 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
>>
>
>
> --
> Miguel Ángel Ajo
> OSP / Networking DFG, OVN Squad Engineering
> __
> 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] Stable Core Team Update

[Nate Johnston]

On Tue, Oct 02, 2018 at 10:41:58AM -0500, Miguel Lavalle wrote:
 
> I want to nominate Bernard Cafarrelli as a stable core reviewer for Neutron
> and related projects. Bernard has been increasing the number of stable
> reviews he is doing for the project [1]. Besides that, he is a stable
> maintainer downstream for his employer (Red Hat), so he can bring that
> valuable experience to the Neutron stable team.

I'm not on the stable team, but an enthusiastic +1 from me!

Nate

__
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][stadium][networking] Seeking proposals for non-voting Stadium projects in Neutron check queue

[Miguel Angel Ajo Pelayo]

That's fantastic,

   I believe we could add some of the networking ovn jobs, we need to
decide which one would be more beneficial.

On Tue, Oct 2, 2018 at 10:02 AM  wrote:

> Hi Miguel, all,
>
> The initiative is very welcome and will help make it more efficient to
> develop in stadium projects.
>
> legacy-tempest-dsvm-networking-bgpvpn-bagpipe would be a candidate, for
> networking-bgpvpn and networking-bagpipe (it covers API and scenario
> tests for the BGPVPN API (networking-bgpvpn) and given that
> networking-bagpipe is used as reference driver, it exercises a large
> portion of networking-bagpipe as well).
>
> Having this one will help a lot.
>
> Thanks,
>
> -Thomas
>
>
> On 9/30/18 2:42 AM, Miguel Lavalle wrote:
> > Dear networking Stackers,
> >
> > During the recent PTG in Denver, we discussed measures to prevent
> > patches merged in the Neutron repo breaking Stadium and related
> > networking projects in general. We decided to implement the following:
> >
> > 1) For Stadium projects, we want to add non-voting jobs to the Neutron
> > check queue
> > 2) For non stadium projects, we are inviting them to add 3rd party CI
> jobs
> >
> > The next step is for each project to propose the jobs that they want
> > to run against Neutron patches.
> >
> > Best regards
> >
> > Miguel
> >
> >
> __
> > 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
>
>
> _
>
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
> recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou
> falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and
> delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been
> modified, changed or falsified.
> Thank you.
>
>
> __
> 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
>


-- 
Miguel Ángel Ajo
OSP / Networking DFG, OVN Squad Engineering
__
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] Stable Core Team Update

[Thomas Morin]

+1 !

-Thomas

On 10/2/18 5:41 PM, Miguel Lavalle wrote:

Hi Stable Team,

I want to nominate Bernard Cafarrelli as a stable core reviewer for 
Neutron and related projects. Bernard has been increasing the number 
of stable reviews he is doing for the project [1]. Besides that, he is 
a stable maintainer downstream for his employer (Red Hat), so he can 
bring that valuable experience to the Neutron stable team.


Thanks and regards

Miguel

[1] 
https://review.openstack.org/#/q/(project:openstack/neutron+OR+openstack/networking-sfc+OR+project:openstack/networking-ovn)++branch:%255Estable/.*+reviewedby:%22Bernard+Cafarelli+%253Cbcafarel%2540redhat.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] [neutron][stable] Stable Core Team Update

[Brian Haley]

+1 from me :)

-Brian

On 10/02/2018 11:41 AM, Miguel Lavalle wrote:

Hi Stable Team,

I want to nominate Bernard Cafarrelli as a stable core reviewer for 
Neutron and related projects. Bernard has been increasing the number of 
stable reviews he is doing for the project [1]. Besides that, he is a 
stable maintainer downstream for his employer (Red Hat), so he can bring 
that valuable experience to the Neutron stable team.


Thanks and regards

Miguel

[1] 
https://review.openstack.org/#/q/(project:openstack/neutron+OR+openstack/networking-sfc+OR+project:openstack/networking-ovn)++branch:%255Estable/.*+reviewedby:%22Bernard+Cafarelli+%253Cbcafarel%2540redhat.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] [neutron][stable] Stable Core Team Update

[Sean McGinnis]

On Tue, Oct 02, 2018 at 01:45:38PM -0500, Matt Riedemann wrote:
> On 10/2/2018 10:41 AM, Miguel Lavalle wrote:
> > Hi Stable Team,
> > 
> > I want to nominate Bernard Cafarrelli as a stable core reviewer for
> > Neutron and related projects. Bernard has been increasing the number of
> > stable reviews he is doing for the project [1]. Besides that, he is a
> > stable maintainer downstream for his employer (Red Hat), so he can bring
> > that valuable experience to the Neutron stable team.
> > 
> > Thanks and regards
> > 
> > Miguel
> > 
> > [1] 
> > https://review.openstack.org/#/q/(project:openstack/neutron+OR+openstack/networking-sfc+OR+project:openstack/networking-ovn)++branch:%255Estable/.*+reviewedby:%22Bernard+Cafarelli+%253Cbcafarel%2540redhat.com%253E%22
> >  
> > 
> 
> +1 from me.
> 
> -- 
> 
> Thanks,
> 
> Matt

+1 from me as well.

Sean


__
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] Stable Core Team Update

[Matt Riedemann]

On 10/2/2018 10:41 AM, Miguel Lavalle wrote:

Hi Stable Team,

I want to nominate Bernard Cafarrelli as a stable core reviewer for 
Neutron and related projects. Bernard has been increasing the number of 
stable reviews he is doing for the project [1]. Besides that, he is a 
stable maintainer downstream for his employer (Red Hat), so he can bring 
that valuable experience to the Neutron stable team.


Thanks and regards

Miguel

[1] 
https://review.openstack.org/#/q/(project:openstack/neutron+OR+openstack/networking-sfc+OR+project:openstack/networking-ovn)++branch:%255Estable/.*+reviewedby:%22Bernard+Cafarelli+%253Cbcafarel%2540redhat.com%253E%22 



+1 from me.

--

Thanks,

Matt

__
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] Stable Core Team Update

[Miguel Lavalle]

Hi Stable Team,

I want to nominate Bernard Cafarrelli as a stable core reviewer for Neutron
and related projects. Bernard has been increasing the number of stable
reviews he is doing for the project [1]. Besides that, he is a stable
maintainer downstream for his employer (Red Hat), so he can bring that
valuable experience to the Neutron stable team.

Thanks and regards

Miguel

[1]
https://review.openstack.org/#/q/(project:openstack/neutron+OR+openstack/networking-sfc+OR+project:openstack/networking-ovn)++branch:%255Estable/.*+reviewedby:%22Bernard+Cafarelli+%253Cbcafarel%2540redhat.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] [neutron][stadium][networking] Seeking proposals for non-voting Stadium projects in Neutron check queue

[thomas.morin]

Hi Miguel, all,

The initiative is very welcome and will help make it more efficient to 
develop in stadium projects.


legacy-tempest-dsvm-networking-bgpvpn-bagpipe would be a candidate, for 
networking-bgpvpn and networking-bagpipe (it covers API and scenario 
tests for the BGPVPN API (networking-bgpvpn) and given that 
networking-bagpipe is used as reference driver, it exercises a large 
portion of networking-bagpipe as well).


Having this one will help a lot.

Thanks,

-Thomas


On 9/30/18 2:42 AM, Miguel Lavalle wrote:

Dear networking Stackers,

During the recent PTG in Denver, we discussed measures to prevent 
patches merged in the Neutron repo breaking Stadium and related 
networking projects in general. We decided to implement the following:


1) For Stadium projects, we want to add non-voting jobs to the Neutron 
check queue

2) For non stadium projects, we are inviting them to add 3rd party CI jobs

The next step is for each project to propose the jobs that they want 
to run against Neutron patches.


Best regards

Miguel

__
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


_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.


__
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] Bug deputy report week of Sept 24

[Nate Johnston]

All,

Here is my Bug Deputy report for the week of 9/24 - 10/1.  It was a busy
week!  It is my recollection that prety much anything that doesn't have
a patchset next to it is probably unowned and available for working.

High priority
==
* https://bugs.launchpad.net/bugs/1794406 - neutron.objects lost PortFording in 
setup.cfg
- Fix released: https://review.openstack.org/605302

* https://bugs.launchpad.net/bugs/1794545 - 
PlacementAPIClient.update_resource_class wrong client call, missing argument
- Fix in progress: https://review.openstack.org/605455

* https://bugs.launchpad.net/bugs/1795280 - netns deletion on newer kernels 
fails with errno 16
- May or may not be a Neutron issue, applies at kernel version 4.18 but not 
3.10.  Left unconfirmed but checking it out within Red Hat.

* https://bugs.launchpad.net/bugs/1795482 - Deleting network namespaces 
sometimes fails in check/gate queue with ENOENT
- Fix in progress: https://review.openstack.org/607009

Medium priority
==
* https://bugs.launchpad.net/bugs/1794305 - [dvr_no_external][ha] centralized 
fip show up in the backup snat-namespace on the restore host (restaring or 
down/up
- Fix in progress: https://review.openstack.org/605359  
https://review.openstack.org/606384

* https://bugs.launchpad.net/bugs/1794809 - Gateway ports are down after reboot 
of control plane nodes
- Fix in progress: https://review.openstack.org/606085

* https://bugs.launchpad.net/bugs/1794865 - Failed to check policy on listing 
loggable resources

* https://bugs.launchpad.net/bugs/1794870 - NetworkNotFound failures on network 
test teardown because of retries due to the initial request taking >60 seconds

* https://bugs.launchpad.net/bugs/1794809 - Gateway ports are down after reboot 
of control plane nodes
- Similar to https://bugs.launchpad.net/neutron/+bug/1793529 but not quite 
the same
- Fix in progress: https://review.openstack.org/606085

* https://bugs.launchpad.net/bugs/1794259 - rocky upgrade path broken 
requirements pecan too low
- Fix released: https://review.openstack.org/605027

* https://bugs.launchpad.net/bugs/1794535 - Consider all router ports for dvr 
arp updates
- Fix in progress: https://review.openstack.org/605434

* https://bugs.launchpad.net/bugs/1795126 - Race condition of DHCP agent 
updating port after ownership removed and given to another agent will cause 
extra port creation
* Fix in progress: https://review.openstack.org/606383

* https://bugs.launchpad.net/bugs/1794424 - trunk: can not delete bound trunk 
for agent which allow create trunk on bound port
- Fix in progress: https://review.openstack.org/605589 

Low priority
==
* https://bugs.launchpad.net/bugs/1795127 - [dvr][ha] router state change cause 
unnecessary router_update

Invalid/Won't Fix
==
* https://bugs.launchpad.net/bugs/1794569 - DVR with static routes may cause 
routed traffic to be dropped
- Marked invalid since it was filed against Newton (neutron 9.4.1)

* https://bugs.launchpad.net/bugs/1794695 - resources can't be filtered by 
tag-related parameterso
- Marked 'Won't Fix' because neutronclient is deprecated, but the 
functionality works correctly in openstackclient.

* https://bugs.launchpad.net/bugs/1794919 - [RFE] To decide create port with 
specific IP version
- Marked 'Opinion'; can accomplish the same goal with current parameters 
for creating a port.

RFE/Wishlist
==
* https://bugs.launchpad.net/bugs/1795212 - [RFE] Prevent DHCP agent from 
processing stale RPC messages when restarting up

* https://bugs.launchpad.net/bugs/1794771 - SRIOV trunk port - multiple vlans 
on same VF

Still Under Discussion
==
* https://bugs.launchpad.net/bugs/1794450 - When creating a server instance 
with an IPv4 and an IPv6 addresses, the IPv6 is not assigned

* https://bugs.launchpad.net/bugs/1794991 - Inconsistent flows with DVR l2pop 
VxLAN on br-tun

* https://bugs.launchpad.net/bugs/1795432 - neutron does not create the 
necessary iptables rules for dhcp agents when linuxbridge is used
- Reporter notes that this is a variant scenario of 
https://bugs.launchpad.net/neutron/+bug/1720205, which was fixed in June

Thanks,

Nate

__
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][stadium][networking] Seeking proposals for non-voting Stadium projects in Neutron check queue

[Miguel Lavalle]

Hi Takashi,

We are open to your suggestion. What job do you think will be helpful in
minimizing the possibility of Neutron patches breaking your project?

Best regards

On Sun, Sep 30, 2018 at 11:25 PM Takashi Yamamoto 
wrote:

> hi,
>
> what kind of jobs should it be?  eg. unit tests, tempest, etc...
> On Sun, Sep 30, 2018 at 9:43 AM Miguel Lavalle 
> wrote:
> >
> > Dear networking Stackers,
> >
> > During the recent PTG in Denver, we discussed measures to prevent
> patches merged in the Neutron repo breaking Stadium and related networking
> projects in general. We decided to implement the following:
> >
> > 1) For Stadium projects, we want to add non-voting jobs to the Neutron
> check queue
> > 2) For non stadium projects, we are inviting them to add 3rd party CI
> jobs
> >
> > The next step is for each project to propose the jobs that they want to
> run against Neutron patches.
> >
> > Best regards
> >
> > Miguel
> >
> __
> > 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][stadium][networking] Seeking proposals for non-voting Stadium projects in Neutron check queue

[Takashi Yamamoto]

hi,

what kind of jobs should it be?  eg. unit tests, tempest, etc...
On Sun, Sep 30, 2018 at 9:43 AM Miguel Lavalle  wrote:
>
> Dear networking Stackers,
>
> During the recent PTG in Denver, we discussed measures to prevent patches 
> merged in the Neutron repo breaking Stadium and related networking projects 
> in general. We decided to implement the following:
>
> 1) For Stadium projects, we want to add non-voting jobs to the Neutron check 
> queue
> 2) For non stadium projects, we are inviting them to add 3rd party CI jobs
>
> The next step is for each project to propose the jobs that they want to run 
> against Neutron patches.
>
> Best regards
>
> Miguel
> __
> 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][neutron-lib] Seeking neutron-lib developers

[Miguel Lavalle]

Dear Neutron community,

As everybody knows, neutron-lib "is an OpenStack library project used by
Neutron, Advanced Services, and third-party projects that aims to provide
common functionality across all such consumers" (
https://docs.openstack.org/neutron-lib/latest/). In general terms, the
effort in neutron-lib consists of two steps:

   1. Extract common functionality from Neutron and re-home it in
   neutron-lib.
   2. Consume the re-homed functionality by Neutron and all its related
   networking projects.

This has been an on-going effort for several cycles and there is still a
lot do. During the recent Stein PTG in Denver, the team agreed to send a
message to the mailing list to invite community developers to help with
this effort. If you are interested in participating, please add your name
to this etherpad:
https://etherpad.openstack.org/p/neutron-lib-volunteers-and-punch-list.
Once we have a group of volunteers, Boden Russel (itc: boden) has agreed to
create a to-do list.

Best regards

Miguel
__
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][stadium][networking] Seeking proposals for non-voting Stadium projects in Neutron check queue

[Miguel Lavalle]

Dear networking Stackers,

During the recent PTG in Denver, we discussed measures to prevent patches
merged in the Neutron repo breaking Stadium and related networking projects
in general. We decided to implement the following:

1) For Stadium projects, we want to add non-voting jobs to the Neutron
check queue
2) For non stadium projects, we are inviting them to add 3rd party CI jobs

The next step is for each project to propose the jobs that they want to run
against Neutron patches.

Best regards

Miguel
__
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][lbaas][neutron-lbaas][octavia] Update on the previously announced deprecation of neutron-lbaas and neutron-lbaas-dashboard

[Michael Johnson]

During the Queens release cycle we announced the deprecation of
neutron-lbaas and neutron-lbaas-dashboard[1].

Today we are announcing the expected end date for the neutron-lbaas
and neutron-lbaas-dashboard deprecation cycles.  During September 2019
or the start of the “U” OpenStack release cycle, whichever comes
first, neutron-lbaas and neutron-lbaas-dashboard will be retired. This
means the code will be be removed and will not be released as part of
the "U" OpenStack release per the infrastructure team’s “retiring a
project” process[2].

We continue to maintain a Frequently Asked Questions (FAQ) wiki page
to help answer additional questions you may have about this process:
https://wiki.openstack.org/wiki/Neutron/LBaaS/Deprecation

For more information or if you have additional questions, please see
the following resources:

The FAQ: https://wiki.openstack.org/wiki/Neutron/LBaaS/Deprecation

The Octavia documentation: https://docs.openstack.org/octavia/latest/

Reach out to us via IRC on the Freenode IRC network, channel #openstack-lbaas

Weekly Meeting: 20:00 UTC on Wednesdays in #openstack-lbaas on the
Freenode IRC network.

Sending email to the OpenStack developer mailing list: openstack-dev
[at] lists [dot] openstack [dot] org. Please prefix the subject with
'[openstack-dev][Octavia]'

Thank you for your support and patience during this transition,

Michael Johnson
Octavia PTL





[1] http://lists.openstack.org/pipermail/openstack-dev/2018-January/126836.html

[2] https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project

__
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] subnet pool can not delete prefixes

[Brian Haley]

On 09/26/2018 10:11 PM, wenran xiao wrote:

Relation bug: https://bugs.launchpad.net/neutron/+bug/1792901
Any suggestion is welcome!


Removing a prefix from a subnetpool is not supported, there was an 
inadvertent change to the client that made it seem possible.  We are in 
the process of reverting it:


https://review.openstack.org/#/c/599633/

-Brian

__
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] subnet pool can not delete prefixes

[wenran xiao]

Relation bug: https://bugs.launchpad.net/neutron/+bug/1792901
Any suggestion is welcome!

Cheers,
-wenran
__
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] Different behavior of admin_state_up attribute between trunk and port

[Le, Huifeng]

Hi,

When using neutron, it is found that the behavior of admin_state_up attribute 
is different between port and trunks which may impact user experience. e.g. for 
port, Setting admin_state_up = FALSE will set port status to "Down", then 
disable the port to block send/receive packages (e.g. set port's tap device 
state to down or move the port to DEAD_VLAN etc.); and for trunks, Setting the 
admin_state_up = FALSE locks the trunk in that it prevents operations such as 
adding/removing subports, but the trunk can still operational (e,g. the trunk 
sub-port can still send/receive packages), and.

So does it make sense to make a change (e.g. submit a bug or RFE) which aligns 
the behavior between trunk and port (e.g. setting admin_state_up= FALSE on a 
trunk will disable that trunk on the vswitch - stop processing VLAN packets 
arriving from that VM instance) to avoid potential confusing of usage?

Thanks much!

Best Regards,
Le, Huifeng
__
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] Opting-in to receive neutron-lib consumption patches

[Boden Russell]

Please read on if your project uses neutron-lib.


During the PTG [1] we decided that projects wanting to receive
neutron-lib consumption patches [2] (for free) need to explicitly opt-in
by adding the string "neutron-lib-current" to a comment in their
requirements.txt.

Based on the list of identified current networking projects [3], I've
submitted an opt-in patch for each [4]. If your project isn't in [3][4],
but you think it should be; it maybe missing a recent neutron-lib
version in your requirements.txt.

By landing the opt-in patch for your project's repo [4], you are
effectively agreeing to:
- Stay current with neutron, TC and infra initiatives thereby allowing
consumption patches to work with the latest and greatest.
- Help review and land consumption patches when they come into your
review queue. As we've discussed before there's about a 2 week window to
land such patches [5].

For project's that don't opt-in, you can continue to consume older
versions of neutron-lib from PyPI manually updating your project to
consume as you go.

Thanks

[1] https://etherpad.openstack.org/p/neutron-stein-ptg
[2]
https://docs.openstack.org/neutron-lib/latest/contributor/contributing.html#phase-4-consume
[3] https://etherpad.openstack.org/p/neutron-sibling-setup
[4]
https://review.openstack.org/#/q/topic:neutron-lib-current-optin+(status:open+OR+status:merged)
[5] http://lists.openstack.org/pipermail/openstack-dev/2018-June/131841.html

__
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] Bug deputy report week of Sept 17

[Boden Russell]

Below is a summary of last weeks bug activity.
I've tried to organize the summary to highlight those bugs that still
need attention.
Thanks


Needs additional technical triage:
- [dvr][ha][dataplane down] router_gateway port binding host goes wrong
after the 'master' host down/up
https://bugs.launchpad.net/neutron/+bug/1793529
- q-dhcp crashes with guru meditation on ironic's grenade
https://bugs.launchpad.net/neutron/+bug/1792925
- [RFE] Enable other projects to extend l2pop fdb information
https://bugs.launchpad.net/neutron/+bug/1793653

Under discussion:
- Egress UDP traffic is dropped
https://bugs.launchpad.net/neutron/+bug/1793244
- ha_vrrp_health_check_interval causes constantly VRRP transitions
https://bugs.launchpad.net/neutron/+bug/1793102
- subnet pool can not delete prefixes
https://bugs.launchpad.net/neutron/+bug/1792901
- external_gateway_info enable_snat attribute should be owner-modifiable
https://bugs.launchpad.net/neutron/+bug/1793207

Triaged, but no assignee:
- DB deadlock when delete subnet
https://bugs.launchpad.net/neutron/+bug/1793516
- public-subnet not explained
https://bugs.launchpad.net/neutron/+bug/1793103
- adding 0.0.0.0/0 address pair to a port bypasses all other vm security
groups https://bugs.launchpad.net/neutron/+bug/1793029
- The user can delete a security group which is used as remote-group-id
https://bugs.launchpad.net/neutron/+bug/1792890

In progress:
- [dvr_no_external][ha][dataplane down]centralized floating IP nat rules
not install in every HA node https://bugs.launchpad.net/neutron/+bug/1793527
- Subnet update with the subnet's current segment_id fail with:
NoUpdateSubnetWhenMultipleSegmentsOnNetwork
https://bugs.launchpad.net/neutron/+bug/1793391
- Changing of_interface between native and ovs-ofctl causes packet drops
https://bugs.launchpad.net/neutron/+bug/1793354
- Router: add port doesn't take IP from allocation pool
https://bugs.launchpad.net/neutron/+bug/1793094

__
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] heads up to long time ovs users...

[Akihiro Motoki]

The important point of this notice is that packet drops will happen when
switching of_interface option from ovs-ofctl (which was the default value
in the old releases) to native (which is the current default ).

Once neutron drops the option, if deployers use the legacy value
"ovs-ofctl", they will hit some packet losses when upgrading neutron to
Stein.

We have no actual data on large deployments so far and don't know how this
change impacts real deployments.

Your feedback would be really appreciated.

Best regards,
Akihiro Motoki (irc: amotoki)

2018年9月21日(金) 10:37 IWAMOTO Toshihiro :

> The neutron team is finally removing the ovs-ofctl option.
>
> https://review.openstack.org/#/c/599496/
>
> The ovs-ofctl of_interface option wasn't default since Newton and was
> deprecated in Pike.
>
> So, if you are a long time ovs-agent user and upgrading to a new
> coming release, you must switch from the ovs-ofctl implementation to
> the native implementation and are affected by the following issue.
>
> https://bugs.launchpad.net/neutron/+bug/1793354
>
> The loss of communication mentioned in this bug report would be a few
> seconds to a few minutes depending on the number of network
> interfaces.  It happens when an ovs-agent is restarted with the new
> of_interface (so only once during the upgrade) and persists until the
> network interfaces are set up.
>
> Please speak up if you cannot tolerate this during upgrades.
>
> IIUC, this bug is unfixable and I'd like to move forward as
> maintaining two of_interface implementation is a burden for the
> neutron team.
>
> --
> IWAMOTO Toshihiro
>
>
> __
> 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][nova] Small bandwidth demo on the PTG

[Bence Romsics]

Hi,

At the demo it turned out that people were interested in a written
version of the demo, so here you can find a blog post about the
current state of the guaranteed minimum bandwidth feature:

https://rubasov.github.io/2018/09/21/openstack-qos-min-bw-demo.html

Cheers,
Bence
On Thu, Sep 13, 2018 at 4:48 AM Balázs Gibizer
 wrote:
>
> Hi,
>
> It seems that the Nova room (Ballroom A) does not have any projection
> possibilities. In the other hand the Neutron room (
> Vail Meeting Room, Atrium Level) does have a projector. So I suggest to
> move the demo to the Neutron room.
>
> Cheers,
> gibi
>
> On Fri, Aug 31, 2018 at 2:29 AM, Balázs Gibizer
>  wrote:
> >
> >
> > On Thu, Aug 30, 2018 at 8:13 PM, melanie witt 
> > wrote:
> >> On Thu, 30 Aug 2018 12:43:06 -0500, Miguel Lavalle wrote:
> >>> Gibi, Bence,
> >>>
> >>> In fact, I added the demo explicitly to the Neutron PTG agenda from
> >>>   1:30  to 2, to give it visiblilty
> >>
> >> I'm interested in seeing the demo too. Will the demo be shown at the
> >>  Neutron room or the Nova room? Historically, lunch has ended at
> >> 1:30,  so this will be during the same time as the Neutron/Nova
> >> cross  project time. Should we just co-locate together for the demo
> >> and the  session? I expect anyone watching the demo will want to
> >> participate  in the Neutron/Nova session as well. Either room is
> >> fine by me.
> >>
> >
> > I assume that the nova - neturon cross project session will be in the
> > nova room, so I propose to have the demo there as well to avoid
> > unnecessarily moving people around. For us it is totally OK to start
> > the demo at 1:30.
> >
> > Cheers,
> > gibi
> >
> >
> >> -melanie
> >>
> >>> On Thu, Aug 30, 2018 at 3:55 AM, Balázs Gibizer
> >>> >>> >   wrote:
> >>>
> >>> Hi,
> >>>
> >>> Based on the Nova PTG planning etherpad [1] there is a need to
> >>>   talk
> >>> about the current state of the bandwidth work [2][3]. Bence
> >>> (rubasov) has already planned to show a small demo to Neutron
> >>>   folks
> >>> about the current state of the implementation. So Bence and I
> >>> are
> >>> wondering about bringing that demo close to the nova - neutron
> >>>   cross
> >>> project session. That session is currently planned to happen
> >>> Thursday after lunch. So we are think about showing the demo
> >>>   right
> >>> before that session starts. It would start 30 minutes before the
> >>> nova - neutron cross project session.
> >>>
> >>> Are Nova folks also interested in seeing such a demo?
> >>>
> >>> If you are interested in seeing the demo please drop us a line
> >>> or
> >>> ping us in IRC so we know who should we wait for.
> >>>
> >>> Cheers,
> >>> gibi
> >>>
> >>> [1] https://etherpad.openstack.org/p/nova-ptg-stein
> >>> 
> >>> [2]
> >>>
> >>>   
> >>> https://specs.openstack.org/openstack/neutron-specs/specs/rocky/minimum-bandwidth-allocation-placement-api.html
> >>>
> >>>   
> >>> 
> >>> [3]
> >>>
> >>>   
> >>> https://specs.openstack.org/openstack/nova-specs/specs/rocky/approved/bandwidth-resource-provider.html
> >>>
> >>>   
> >>> 
> >>>
> >>>
> >>>
> >>>   
> >>> __
> >>> 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
> >
> >
> > __
> > 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] heads up to long time ovs users...

[IWAMOTO Toshihiro]

The neutron team is finally removing the ovs-ofctl option.

https://review.openstack.org/#/c/599496/

The ovs-ofctl of_interface option wasn't default since Newton and was
deprecated in Pike.

So, if you are a long time ovs-agent user and upgrading to a new
coming release, you must switch from the ovs-ofctl implementation to
the native implementation and are affected by the following issue.

https://bugs.launchpad.net/neutron/+bug/1793354

The loss of communication mentioned in this bug report would be a few
seconds to a few minutes depending on the number of network
interfaces.  It happens when an ovs-agent is restarted with the new
of_interface (so only once during the upgrade) and persists until the
network interfaces are set up.

Please speak up if you cannot tolerate this during upgrades.

IIUC, this bug is unfixable and I'd like to move forward as
maintaining two of_interface implementation is a burden for the
neutron team.

--
IWAMOTO Toshihiro


__
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 drivers meeting on September 21st

[Miguel Lavalle]

Hi,

Since we just came back from the PTG in Denver and we reviewed / discussed
many RFEs, let's skip the Drivers meeting tomorrow, Friday 21st. We will
resume the meeting on the 28th

Best regards

Miguel
__
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] Core status

[Bhatia, Manjeet S]

Good luck for new role !

From: Gary Kotton [mailto:gkot...@vmware.com]
Sent: Wednesday, September 19, 2018 11:20 AM
To: OpenStack List 
Subject: [openstack-dev] [neutron] Core status

Hi,
I have recently transitioned to a new role where I will be working on other 
parts of OpenStack. Sadly I do not have the necessary cycles to maintain my 
core responsibilities in the neutron community. Nonetheless I will continue to 
be involved.
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

Re: [openstack-dev] [neutron] Core status

[Miguel Lavalle]

Hi Gary,

As I say during our private conversation, we don't like to see you going,
but we understand that you have other career opportunities. I wish you luck
in your next challenge and please remember that you will always be welcome
here

Best regards

Miguel

On Thu, Sep 20, 2018 at 9:49 AM Brian Haley  wrote:

> On 09/19/2018 02:19 PM, Gary Kotton wrote:
> > Hi,
> >
> > I have recently transitioned to a new role where I will be working on
> > other parts of OpenStack. Sadly I do not have the necessary cycles to
> > maintain my core responsibilities in the neutron community. Nonetheless
> > I will continue to be involved.
>
> Thanks for all your work over the years, especially in keeping the
> reviews moving along on the neutron stable branches.  Good luck in your
> new role!
>
> -Brian
>
> __
> 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] Core status

[Brian Haley]

On 09/19/2018 02:19 PM, Gary Kotton wrote:

Hi,

I have recently transitioned to a new role where I will be working on 
other parts of OpenStack. Sadly I do not have the necessary cycles to 
maintain my core responsibilities in the neutron community. Nonetheless 
I will continue to be involved.


Thanks for all your work over the years, especially in keeping the 
reviews moving along on the neutron stable branches.  Good luck in your 
new role!


-Brian

__
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] Core status

[Slawomir Kaplonski]

Hi,

Thanks for all Your work for Neutron and good luck in Your new role :)

> Wiadomość napisana przez Gary Kotton  w dniu 19.09.2018, 
> o godz. 20:19:
> 
> Hi,
> I have recently transitioned to a new role where I will be working on other 
> parts of OpenStack. Sadly I do not have the necessary cycles to maintain my 
> core responsibilities in the neutron community. Nonetheless I will continue 
> to be involved.
> 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

— 
Slawek Kaplonski
Senior software engineer
Red Hat


__
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] Core status

[Akihiro Motoki]

Thanks Gary for long years on Neutron.
You are the only core before I became quantum-core. I lose you now
Anyway good luck for your new role.

Thanks,
Akihiro

2018年9月20日(木) 3:20 Gary Kotton :

> Hi,
>
> I have recently transitioned to a new role where I will be working on
> other parts of OpenStack. Sadly I do not have the necessary cycles to
> maintain my core responsibilities in the neutron community. Nonetheless I
> will continue to be involved.
>
> 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

Re: [openstack-dev] [neutron] Core status

[Miguel Angel Ajo Pelayo]

Good luck Gary, thanks for all those years on Neutron! :)

Best regards,
Miguel Ángel

On Wed, Sep 19, 2018 at 9:32 PM Nate Johnston 
wrote:

> On Wed, Sep 19, 2018 at 06:19:44PM +, Gary Kotton wrote:
>
> > I have recently transitioned to a new role where I will be working on
> other parts of OpenStack. Sadly I do not have the necessary cycles to
> maintain my core responsibilities in the neutron community. Nonetheless I
> will continue to be involved.
>
> Thanks for everything you've done over the years, Gary.  I know I
> learned a lot from your reviews back when I was a wee baby Neutron
> developer.  Best of luck on what's next!
>
> Nate
>
> __
> 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
>


-- 
Miguel Ángel Ajo
OSP / Networking DFG, OVN Squad Engineering
__
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] Core status

[Nate Johnston]

On Wed, Sep 19, 2018 at 06:19:44PM +, Gary Kotton wrote:

> I have recently transitioned to a new role where I will be working on other 
> parts of OpenStack. Sadly I do not have the necessary cycles to maintain my 
> core responsibilities in the neutron community. Nonetheless I will continue 
> to be involved.

Thanks for everything you've done over the years, Gary.  I know I
learned a lot from your reviews back when I was a wee baby Neutron
developer.  Best of luck on what's next!

Nate

__
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] Core status

[Gary Kotton]

Hi,
I have recently transitioned to a new role where I will be working on other 
parts of OpenStack. Sadly I do not have the necessary cycles to maintain my 
core responsibilities in the neutron community. Nonetheless I will continue to 
be involved.
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

Re: [openstack-dev] [Neutron] Removing external_bridge_name config option

[Akihiro Motoki]

Hi,

I would like to share some information to help the migration from
external_network_bridge.

The background of the deprecation is described in
https://bugs.launchpad.net/neutron/+bug/1491668

I also shared a slide to explain the detail.
https://www.slideshare.net/ritchey98/neutron-brex-is-now-deprecated-what-is-modern-way
Neutron: br-ex is now deprecated! what is modern way?

I hope these help you to push away the usage of external_network_bridge.

Thanks,
Akihiro Motoki (IRC: amotoki)

2018年9月19日(水) 23:02 Slawomir Kaplonski :
>
> Hi,
>
> Some time ago I proposed patch [1] to remove config option 
> „external_network_bridge”.
> This option was deprecated to removal in Ocata so I think it’s time to get 
> rid of it finally.
>
> There is quite many projects which still uses this option [2]. I will try to 
> propose patches for those projects to remove it also from there but if You 
> are maintainer of such project, it would be great if You can remove it. If 
> You would do it, please use same topic as is in [1] - it will allow me easier 
> track which projects already removed it.
> Thx a lot in advance for any help :)
>
> [1] https://review.openstack.org/#/c/567369
> [2] 
> http://codesearch.openstack.org/?q=external_network_bridge&i=nope&files=&repos=
>
> —
> Slawek Kaplonski
> Senior software engineer
> Red Hat
>
>
> __
> 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] Removing external_bridge_name config option

[Slawomir Kaplonski]

Hi,

Some time ago I proposed patch [1] to remove config option 
„external_network_bridge”.
This option was deprecated to removal in Ocata so I think it’s time to get rid 
of it finally.

There is quite many projects which still uses this option [2]. I will try to 
propose patches for those projects to remove it also from there but if You are 
maintainer of such project, it would be great if You can remove it. If You 
would do it, please use same topic as is in [1] - it will allow me easier track 
which projects already removed it.
Thx a lot in advance for any help :)

[1] https://review.openstack.org/#/c/567369
[2] 
http://codesearch.openstack.org/?q=external_network_bridge&i=nope&files=&repos=

— 
Slawek Kaplonski
Senior software engineer
Red Hat


__
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] bug deputy report week Sep 10 - 12

[Akihiro Motoki]

Hi,

I was the bug deputy for neutron last week.

The last week was really quiet, but all of them are gate failures and
need attentions.

grenade-dvr-multinode job fails
https://bugs.launchpad.net/neutron/+bug/1791989
This continuously happens last week with high failure rate.
http://grafana.openstack.org/d/Hj5IHcSmz/neutron-failure-rate?panelId=20&fullscreen&orgId=1

neutron_tempest_plugin: test_floatingip_port_details occasionally fails
https://bugs.launchpad.net/neutron/+bug/1792472

q-dhcp crashes with guru meditation on ironic's grenade
https://bugs.launchpad.net/neutron/+bug/1792925
This was reported this Monday. It continues to occur since at least Sep 10.

Best Regards,
Akihiro Motoki (irc: amotoki)

__
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] Pep8 job failures

[Slawomir Kaplonski]

Hi,

As patch [1] is finally merged You can now rebase Your neutron patches and pep8 
tests should be good.

[1] https://review.openstack.org/#/c/589382/

> Wiadomość napisana przez Slawomir Kaplonski  w dniu 
> 07.09.2018, o godz. 01:30:
> 
> Hi,
> 
> Recently bump of eventlet to 0.24.0 was merged in requirements repo [1]. 
> That caused issue in Neutron and pep8 job is now failing. See [2]. So if You 
> have pep8 failed in Your patch with error like in [3] please don’t recheck 
> job - it will not help :)
> Patch to fix that is already proposed [4]. When it will be merged, please 
> rebase Your patch and this issue should be solved.
> 
> [1] https://review.openstack.org/#/c/589382/
> [2] https://bugs.launchpad.net/neutron/+bug/1791178
> [3] 
> http://logs.openstack.org/37/382037/73/gate/openstack-tox-pep8/7f200e6/job-output.txt.gz#_2018-09-06_17_48_34_700485
> [4] https://review.openstack.org/600565
> 
> — 
> Slawek Kaplonski
> Senior software engineer
> Red Hat
> 

— 
Slawek Kaplonski
Senior software engineer
Red Hat


__
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][nova] Small bandwidth demo on the PTG

[Balázs Gibizer]

Hi,

It seems that the Nova room (Ballroom A) does not have any projection 
possibilities. In the other hand the Neutron room (
Vail Meeting Room, Atrium Level) does have a projector. So I suggest to 
move the demo to the Neutron room.


Cheers,
gibi

On Fri, Aug 31, 2018 at 2:29 AM, Balázs Gibizer 
 wrote:



On Thu, Aug 30, 2018 at 8:13 PM, melanie witt  
wrote:

On Thu, 30 Aug 2018 12:43:06 -0500, Miguel Lavalle wrote:

Gibi, Bence,

In fact, I added the demo explicitly to the Neutron PTG agenda from 
1:30 to 2, to give it visiblilty


I'm interested in seeing the demo too. Will the demo be shown at the 
Neutron room or the Nova room? Historically, lunch has ended at 
1:30, so this will be during the same time as the Neutron/Nova 
cross project time. Should we just co-locate together for the demo 
and the session? I expect anyone watching the demo will want to 
participate in the Neutron/Nova session as well. Either room is 
fine by me.




I assume that the nova - neturon cross project session will be in the 
nova room, so I propose to have the demo there as well to avoid 
unnecessarily moving people around. For us it is totally OK to start 
the demo at 1:30.


Cheers,
gibi



-melanie

On Thu, Aug 30, 2018 at 3:55 AM, Balázs Gibizer 
> wrote:


Hi,

Based on the Nova PTG planning etherpad [1] there is a need to 
talk

about the current state of the bandwidth work [2][3]. Bence
(rubasov) has already planned to show a small demo to Neutron 
folks
about the current state of the implementation. So Bence and I 
are
wondering about bringing that demo close to the nova - neutron 
cross

project session. That session is currently planned to happen
Thursday after lunch. So we are think about showing the demo 
right

before that session starts. It would start 30 minutes before the
nova - neutron cross project session.

Are Nova folks also interested in seeing such a demo?

If you are interested in seeing the demo please drop us a line 
or

ping us in IRC so we know who should we wait for.

Cheers,
gibi

[1] https://etherpad.openstack.org/p/nova-ptg-stein

[2]

https://specs.openstack.org/openstack/neutron-specs/specs/rocky/minimum-bandwidth-allocation-placement-api.html



[3]

https://specs.openstack.org/openstack/nova-specs/specs/rocky/approved/bandwidth-resource-provider.html






__

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



__
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] [router] status bug

[Bhatia, Manjeet S]

Hi neutrinos,

I was looking at Bug [1], and noticed that router status stays ACTIVE even 
after -disable ?

-openstack router -set disable router1

/opt/stack/neutron$ openstack router set --disable routerr1
vagrant@allinone:/opt/stack/neutron$ neutron router-show router1
neutron CLI is deprecated and will be removed in the future. Use openstack CLI 
instead.
+-+--+
| Field   | Value|
+-+--+
| admin_state_up  | False|
| availability_zone_hints |  |
| availability_zones  |  |
| created_at  | 2018-09-08T00:30:46Z |
| description |  |
| distributed | True |
| external_gateway_info   |  |
| flavor_id   |  |
| ha  | False|
| id  | 6f88b5f4-dc94-44bd-89cd-9c0f2b374f79 |
| name| router1   |
| project_id  | 05d72b0eff534ccf81e37b5d6e3402f6 |
| revision_number | 1|
| routes  |  |
| status  | ACTIVE   |
| tags|  |
| tenant_id   | 05d72b0eff534ccf81e37b5d6e3402f6 |
| updated_at  | 2018-09-08T00:31:18Z |





Shouldn't it update the status to DOWN  ? before I open a ticket for bug I just 
wanted to confirm it ?

[1]. https://bugs.launchpad.net/neutron/+bug/1789434



Regards !
Manjeet Singh Bhatia
__
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] Pep8 job failures

[Slawomir Kaplonski]

Hi,

Recently bump of eventlet to 0.24.0 was merged in requirements repo [1]. 
That caused issue in Neutron and pep8 job is now failing. See [2]. So if You 
have pep8 failed in Your patch with error like in [3] please don’t recheck job 
- it will not help :)
Patch to fix that is already proposed [4]. When it will be merged, please 
rebase Your patch and this issue should be solved.

[1] https://review.openstack.org/#/c/589382/
[2] https://bugs.launchpad.net/neutron/+bug/1791178
[3] 
http://logs.openstack.org/37/382037/73/gate/openstack-tox-pep8/7f200e6/job-output.txt.gz#_2018-09-06_17_48_34_700485
[4] https://review.openstack.org/600565

— 
Slawek Kaplonski
Senior software engineer
Red Hat


__
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] Bug status

[Gary Kotton]

Hi,
It has been a relatively quiet week and not many issues opened. There are a few 
bugs with IPv6 subnets. Most have missing information and I have asked the 
reporters for some extra information. Not any blockers are issues that are 
concerning.
Wishing everyone a productive PTG.
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-dev] [Neutron] [Upgrades] Cancel meeting on 13th Sept.

[Lujin Luo]

Hello everyone,

We are canceling our next Upgrades subteam meeting on 13th September
due to PTG. Should you have any questions, please reach out to me on
#openstack-neutron.

Best regards,
Lujin

__
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 CI meeting on Tuesday 11.09

[Slawomir Kaplonski]

Hi,

Due to PTG in Denver CI meeting on Tuesday 11.09 is cancelled.
Next one will be at 18.09

— 
Slawek Kaplonski
Senior software engineer
Red Hat


__
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] [Cyborg] Cyborg-Neutron interaction for programmable NICs

[Nadathur, Sundar]

Hello Neutron folks,
 There is emerging interest in programmable NICs that combine FPGAs 
and networking in different ways. I wrote up about one category of them 
here:


   https://etherpad.openstack.org/p/fpga-networking

This was discussed at the Neutron meeting on Sep 3 [1]. This approach to 
programmable networking raises many questions. I have summarized them in 
this etherpad and proposed a possible solution.


Please review this. We have a session in the PTG on Thursday (Sep 13) 
from 3:15 to 4:15 pm on this topic.


Given the level of interest that we are seeing, I hope we get some 
agreement early enough that we can do at least some POCs in Stein cycle.


[1] 
http://eavesdrop.openstack.org/irclogs/%23openstack-meeting/%23openstack-meeting.2018-09-03.log.html#t2018-09-03T21:43:48 



Regards,
Sundar
__
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][SONA][networking-onos] Releasing stable/rocky branch for networking-onos

[Sangho Shin]

Hello, all

stable/rocky branch for networking-onos project 
(https://github.com/openstack/networking-onos 
) has been released.
If you want to test it, please follow all-in-one install instruction, 
https://wiki.onosproject.org/display/ONOS/All-in-one+Installation+Guide 
, 
replacing queens to rocky in local.conf file.

For more detail, please check it out our SONA wiki page, 
https://wiki.onosproject.org/display/ONOS/SONA%3A+DC+Network+Virtualization 


Thank you,

Sangho

SONA and networking-onos development team


__
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] Tungsten Fabric (formally OpenContrail) at Denver PTG

[Sukhdev Kapur]

Folks,

This is a reminder of this event at OpenStack PTG in Denver. If you have
not already RSVP'd please use the link below to do so.
Couple of changes - this event is from 9-5 (not 9-6), and lunch is from
12:30-1:30pm (not 1:00-2:00).

Look forward to seeing you there.

regards
-Sukhdev


On Tue, Aug 28, 2018 at 6:36 PM Sukhdev Kapur 
wrote:

> The Tungsten Fabric community invites you to join us at the OpenStack
> 
>  PTG in Denver
> 
> to discuss and contribute to two great projects: Tungsten
> 
>  Fabric
> 
> and Networking-OpenContrail
> 
> .
>
>
> We’ll be meeting on Tuesday, September 11, in Room Telluride B of Renaissance
> Denver Stapleton Hotel from 9am - 6pm. Here’s the agenda:
>
>
> 9am - 1:00 pm: *Networking-OpenContrail*
>
>Networking-OpenContrail is the OpenStack Neutron ML2 driver to
> integrate Tungsten Fabric to OpenStack. It is designed to eventually
> replace the old monolithic driver.
>
>This session will provide an update on the project, and then we’ll
> discuss the next steps.
>
>
> 1:00-2:00: Lunch
>
>
> 2:00-6:00: *Tungsten **Fabric *
>
> In this session, we’ll start with a brief overview of Tungsten
> Fabric for the benefit of those who may be new to the project.
>
> Then we’ll dive in deeper, discussing the Tungsten Fabric
> architecture, developer workflow, getting patches into Gerrit, and building
> and testing TF for OpenStack and Kubernetes.
>
>
>
> We hope you’ll join us:
>
>
> *Register* for the PTG here
> ,
> and
>
> Please let us know if you’ll attend these sessions: RSVP
> 
>
>
>
> Sukhdev Kapur and TF Networking Team
>
> IRC - Sukhdev
>
> sukhdevka...@gmail.com
>
>
>
>
>
>
__
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] PTG agenda

[Miguel Lavalle]

Dear Neutron Team,

I have scheduled all the topics that were proposed for the PTG in Denver
here: https://etherpad.openstack.org/p/neutron-stein-ptg. Please go to line
128 and onwards to see the detailed schedule. Please reach out to me should
we need to make any changes or adjustments

Best regards

Miguel
__
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] Weekly meeting canceled on Tuesday 11th

[Miguel Lavalle]

Dear Neutron Team,

Due to the PTG in Denver, the Neutron weekly team on Tuesday 11th at 1400
UTC is canceled. We will resume our meeting on Monday September 17th at
2100 UTC

Best regards

Miguel
__
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] Bug deputy report week August 27 - September 2

[Gary Kotton]

Thanks for the update. I have taken the baton from the 2nd. Thankfully last few 
days have been quite.
A luta continua

From: Hirofumi Ichihara 
Reply-To: OpenStack List 
Date: Monday, September 3, 2018 at 11:54 AM
To: OpenStack List 
Subject: [openstack-dev] [neutron] Bug deputy report week August 27 - September 
2

Hi,

I was the bug deputy for the week of August 27 - September 2.

There is no Ctirical bug.

High:
https://bugs.launchpad.net/neutron/+bug/1789878<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fneutron%2F%2Bbug%2F1789878&data=02%7C01%7Cgkotton%40vmware.com%7C5c12a4d883854caef0e308d6117ad09c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C636715616531197778&sdata=0S6ya9j5VyYYW%2By1gDqtdqwBbzyIDpTJEqbJl4lwObM%3D&reserved=0>
https://bugs.launchpad.net/neutron/+bug/1789846<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fneutron%2F%2Bbug%2F1789846&data=02%7C01%7Cgkotton%40vmware.com%7C5c12a4d883854caef0e308d6117ad09c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C636715616531197778&sdata=a2gCIck80VE%2Fm9doRJgLLEt5eEfgU%2FdSx4PyNhi2ZSE%3D&reserved=0>
https://bugs.launchpad.net/neutron/+bug/1789579<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fneutron%2F%2Bbug%2F1789579&data=02%7C01%7Cgkotton%40vmware.com%7C5c12a4d883854caef0e308d6117ad09c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C636715616531207795&sdata=dofOi%2Bd%2BJyE0IkpDDhu5%2BmqRx18%2Fcno4VlV6WsWTS6g%3D&reserved=0>
https://bugs.launchpad.net/neutron/+bug/1789434<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fneutron%2F%2Bbug%2F1789434&data=02%7C01%7Cgkotton%40vmware.com%7C5c12a4d883854caef0e308d6117ad09c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C636715616531207795&sdata=PrB%2BA6KLM2VzOR7xSF0RezQYQRXpg0X3maJEMAKvcQ0%3D&reserved=0>
https://bugs.launchpad.net/neutron/+bug/1789403<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fneutron%2F%2Bbug%2F1789403&data=02%7C01%7Cgkotton%40vmware.com%7C5c12a4d883854caef0e308d6117ad09c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C636715616531217795&sdata=9bBYD5vDsdJx2jDiv4LBtZee%2BdMM77SzyXLCCvSon9w%3D&reserved=0>

Medium:
https://bugs.launchpad.net/neutron/+bug/1790143<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fneutron%2F%2Bbug%2F1790143&data=02%7C01%7Cgkotton%40vmware.com%7C5c12a4d883854caef0e308d6117ad09c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C636715616531217795&sdata=wkEix9dSp8RxrYT0DvL4dxkWK0Lq3%2FIiWmZlEeOW48s%3D&reserved=0>
https://bugs.launchpad.net/neutron/+bug/1789499<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fneutron%2F%2Bbug%2F1789499&data=02%7C01%7Cgkotton%40vmware.com%7C5c12a4d883854caef0e308d6117ad09c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C636715616531227803&sdata=U%2Fe1BQHAxCmTHuh6ICztzvjH7Q7DI%2BcfiH%2BGFKJKw64%3D&reserved=0>

New:
https://bugs.launchpad.net/neutron/+bug/1790084<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fneutron%2F%2Bbug%2F1790084&data=02%7C01%7Cgkotton%40vmware.com%7C5c12a4d883854caef0e308d6117ad09c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C636715616531237811&sdata=iB7I1%2BwmcVBIO9VhMaXPOtLGm7zCBnnxQHGH4YQT4Cs%3D&reserved=0>
 This is needed to triage by l3-dvr-backlog lieutenants.
https://bugs.launchpad.net/neutron/+bug/1790038<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fneutron%2F%2Bbug%2F1790038&data=02%7C01%7Cgkotton%40vmware.com%7C5c12a4d883854caef0e308d6117ad09c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C636715616531237811&sdata=yBAZmVVbmkI8HvdCF1pqyJfOz5UZJB67Dt9e36rmbw8%3D&reserved=0>
 This is needed to triage by l3-dvr-backlog lieutenants.
https://bugs.launchpad.net/neutron/+bug/1789334<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fneutron%2F%2Bbug%2F1789334&data=02%7C01%7Cgkotton%40vmware.com%7C5c12a4d883854caef0e308d6117ad09c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C636715616531247820&sdata=q9dGetLlNtSV18z1Ca5dBoDQEo0jHBWgj67sLN1xxho%3D&reserved=0>
 This is needed to triage by troubleshooting lieutenants or Osprofier forks.

Incomplete:
https://bugs.launchpad.net/neutron/+bug/1790023<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fneutron%2F%2Bbug%2F1790023&data=02%7C01%7Cgkotton%40vmware.com%7C5c12a4d883854caef0e308d6117ad09c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C636715616531247820&sdata=4nkVnxKdK3pyDZ5Sz12YdpKJahB9PEiYqTQWIFNE6%2Bw%3D&reserved=0>
https://bugs.launchpad.net/neutron/+bug/1789870<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fneutron%2F%2Bbug%

[openstack-dev] [neutron] Bug deputy report week August 27 - September 2

[Hirofumi Ichihara]

Hi,

I was the bug deputy for the week of August 27 - September 2.

There is no Ctirical bug.

High:
https://bugs.launchpad.net/neutron/+bug/1789878
https://bugs.launchpad.net/neutron/+bug/1789846
https://bugs.launchpad.net/neutron/+bug/1789579
https://bugs.launchpad.net/neutron/+bug/1789434
https://bugs.launchpad.net/neutron/+bug/1789403

Medium:
https://bugs.launchpad.net/neutron/+bug/1790143
https://bugs.launchpad.net/neutron/+bug/1789499

New:
https://bugs.launchpad.net/neutron/+bug/1790084 This is needed to triage
by l3-dvr-backlog lieutenants.
https://bugs.launchpad.net/neutron/+bug/1790038 This is needed to triage
by l3-dvr-backlog lieutenants.
https://bugs.launchpad.net/neutron/+bug/1789334 This is needed to triage by
troubleshooting lieutenants or Osprofier forks.

Incomplete:
https://bugs.launchpad.net/neutron/+bug/1790023
https://bugs.launchpad.net/neutron/+bug/1789870
https://bugs.launchpad.net/neutron/+bug/1789844

Wishlist:
https://bugs.launchpad.net/neutron/+bug/1789378

RFE:
https://bugs.launchpad.net/neutron/+bug/1789592
https://bugs.launchpad.net/neutron/+bug/1789391

Thanks,
Hirofumi
__
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] Stepping down from Neutron core team

[Miguel Lavalle]

Kuba,

I made a last ditch awkward effort to convince you to stay a little longer
unsuccessfully. I understand, though, that now you have other commitments.
I know you will be successful in your new adventures, because you are
really smart and hard working. And please remember that we will take you
back with open arms at any moment in the future.

Finally, I wish you good luck, because we all need a little bit of it

Best regards

Miguel

On Fri, Aug 31, 2018 at 3:49 AM, Slawomir Kaplonski 
wrote:

> It’s sad news. Thanks Kuba for all Your help You gave me when I was
> newcomer in Neutron community.
> Good luck in Your next projects :)
>
> > Wiadomość napisana przez Jakub Libosvar  w dniu
> 31.08.2018, o godz. 10:24:
> >
> > Hi all,
> >
> > as you have might already heard, I'm no longer involved in Neutron
> > development due to some changes. Therefore I'm officially stepping down
> > from the core team because I can't provide same quality reviews as I
> > tried to do before.
> >
> > I'd like to thank you all for the opportunity I was given in the Neutron
> > team, thank you for all I have learned over the years professionally,
> > technically and personally. Tomorrow it's gonna be exactly 5 years since
> > I started hacking Neutron and I must say I really enjoyed working with
> > all Neutrinos here and I had privilege to meet most of you in person and
> > that has an extreme value for me. Keep on being a great community!
> >
> > Thank you again!
> > Kuba
> >
> > 
> __
> > 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
>
> —
> Slawek Kaplonski
> Senior software engineer
> Red Hat
>
>
> __
> 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][nova] Small bandwidth demo on the PTG

[Miguel Lavalle]

Nova room is fine. See you'all there

On Fri, Aug 31, 2018 at 3:29 AM, Balázs Gibizer  wrote:

>
>
> On Thu, Aug 30, 2018 at 8:13 PM, melanie witt  wrote:
>
>> On Thu, 30 Aug 2018 12:43:06 -0500, Miguel Lavalle wrote:
>>
>>> Gibi, Bence,
>>>
>>> In fact, I added the demo explicitly to the Neutron PTG agenda from
>>> 1:30  to 2, to give it visiblilty
>>>
>>
>> I'm interested in seeing the demo too. Will the demo be shown at the
>> Neutron room or the Nova room? Historically, lunch has ended at 1:30, so
>> this will be during the same time as the Neutron/Nova cross project time.
>> Should we just co-locate together for the demo and the session? I expect
>> anyone watching the demo will want to participate in the Neutron/Nova
>> session as well. Either room is fine by me.
>>
>>
> I assume that the nova - neturon cross project session will be in the nova
> room, so I propose to have the demo there as well to avoid unnecessarily
> moving people around. For us it is totally OK to start the demo at 1:30.
>
> Cheers,
> gibi
>
>
>
> -melanie
>>
>> On Thu, Aug 30, 2018 at 3:55 AM, Balázs Gibizer  <
>>> balazs.gibi...@ericsson.com > wrote:
>>>
>>> Hi,
>>>
>>> Based on the Nova PTG planning etherpad [1] there is a need to talk
>>> about the current state of the bandwidth work [2][3]. Bence
>>> (rubasov) has already planned to show a small demo to Neutron folks
>>> about the current state of the implementation. So Bence and I are
>>> wondering about bringing that demo close to the nova - neutron cross
>>> project session. That session is currently planned to happen
>>> Thursday after lunch. So we are think about showing the demo right
>>> before that session starts. It would start 30 minutes before the
>>> nova - neutron cross project session.
>>>
>>> Are Nova folks also interested in seeing such a demo?
>>>
>>> If you are interested in seeing the demo please drop us a line or
>>> ping us in IRC so we know who should we wait for.
>>>
>>> Cheers,
>>> gibi
>>>
>>> [1] https://etherpad.openstack.org/p/nova-ptg-stein
>>> 
>>> [2]
>>> https://specs.openstack.org/openstack/neutron-specs/specs/ro
>>> cky/minimum-bandwidth-allocation-placement-api.html
>>> >> ocky/minimum-bandwidth-allocation-placement-api.html>
>>> [3]
>>> https://specs.openstack.org/openstack/nova-specs/specs/rocky
>>> /approved/bandwidth-resource-provider.html
>>> >> y/approved/bandwidth-resource-provider.html>
>>>
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> >> subscribe>
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>> 
>>>
>>>
>>>
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.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:unsubscrib
>> e
>> 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] Stepping down from Neutron core team

[Slawomir Kaplonski]

It’s sad news. Thanks Kuba for all Your help You gave me when I was newcomer in 
Neutron community.
Good luck in Your next projects :)

> Wiadomość napisana przez Jakub Libosvar  w dniu 
> 31.08.2018, o godz. 10:24:
> 
> Hi all,
> 
> as you have might already heard, I'm no longer involved in Neutron
> development due to some changes. Therefore I'm officially stepping down
> from the core team because I can't provide same quality reviews as I
> tried to do before.
> 
> I'd like to thank you all for the opportunity I was given in the Neutron
> team, thank you for all I have learned over the years professionally,
> technically and personally. Tomorrow it's gonna be exactly 5 years since
> I started hacking Neutron and I must say I really enjoyed working with
> all Neutrinos here and I had privilege to meet most of you in person and
> that has an extreme value for me. Keep on being a great community!
> 
> Thank you again!
> Kuba
> 
> __
> 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

— 
Slawek Kaplonski
Senior software engineer
Red Hat


__
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] Stepping down from Neutron core team

[Daniel Alvarez Sanchez]

Thanks a lot Kuba for all your contributions!
You've been a great mentor to me since I joined OpenStack and I'm so happy
that I got to work with you. Great engineer and even better person!
All the best, my friend!

On Fri, Aug 31, 2018 at 10:25 AM Jakub Libosvar  wrote:

> Hi all,
>
> as you have might already heard, I'm no longer involved in Neutron
> development due to some changes. Therefore I'm officially stepping down
> from the core team because I can't provide same quality reviews as I
> tried to do before.
>
> I'd like to thank you all for the opportunity I was given in the Neutron
> team, thank you for all I have learned over the years professionally,
> technically and personally. Tomorrow it's gonna be exactly 5 years since
> I started hacking Neutron and I must say I really enjoyed working with
> all Neutrinos here and I had privilege to meet most of you in person and
> that has an extreme value for me. Keep on being a great community!
>
> Thank you again!
> Kuba
>
> __
> 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][nova] Small bandwidth demo on the PTG

[Balázs Gibizer]

On Thu, Aug 30, 2018 at 8:13 PM, melanie witt  
wrote:

On Thu, 30 Aug 2018 12:43:06 -0500, Miguel Lavalle wrote:

Gibi, Bence,

In fact, I added the demo explicitly to the Neutron PTG agenda from 
1:30 to 2, to give it visiblilty


I'm interested in seeing the demo too. Will the demo be shown at the 
Neutron room or the Nova room? Historically, lunch has ended at 1:30, 
so this will be during the same time as the Neutron/Nova cross 
project time. Should we just co-locate together for the demo and the 
session? I expect anyone watching the demo will want to participate 
in the Neutron/Nova session as well. Either room is fine by me.




I assume that the nova - neturon cross project session will be in the 
nova room, so I propose to have the demo there as well to avoid 
unnecessarily moving people around. For us it is totally OK to start 
the demo at 1:30.


Cheers,
gibi



-melanie

On Thu, Aug 30, 2018 at 3:55 AM, Balázs Gibizer 
mailto:balazs.gibi...@ericsson.com>> 
wrote:


Hi,

Based on the Nova PTG planning etherpad [1] there is a need to 
talk

about the current state of the bandwidth work [2][3]. Bence
(rubasov) has already planned to show a small demo to Neutron 
folks

about the current state of the implementation. So Bence and I are
wondering about bringing that demo close to the nova - neutron 
cross

project session. That session is currently planned to happen
Thursday after lunch. So we are think about showing the demo 
right

before that session starts. It would start 30 minutes before the
nova - neutron cross project session.

Are Nova folks also interested in seeing such a demo?

If you are interested in seeing the demo please drop us a line or
ping us in IRC so we know who should we wait for.

Cheers,
gibi

[1] https://etherpad.openstack.org/p/nova-ptg-stein

[2]

https://specs.openstack.org/openstack/neutron-specs/specs/rocky/minimum-bandwidth-allocation-placement-api.html



[3]

https://specs.openstack.org/openstack/nova-specs/specs/rocky/approved/bandwidth-resource-provider.html






__

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



__
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] Stepping down from Neutron core team

[Jakub Libosvar]

Hi all,

as you have might already heard, I'm no longer involved in Neutron
development due to some changes. Therefore I'm officially stepping down
from the core team because I can't provide same quality reviews as I
tried to do before.

I'd like to thank you all for the opportunity I was given in the Neutron
team, thank you for all I have learned over the years professionally,
technically and personally. Tomorrow it's gonna be exactly 5 years since
I started hacking Neutron and I must say I really enjoyed working with
all Neutrinos here and I had privilege to meet most of you in person and
that has an extreme value for me. Keep on being a great community!

Thank you again!
Kuba

__
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][nova] Small bandwidth demo on the PTG

[melanie witt]

On Thu, 30 Aug 2018 12:43:06 -0500, Miguel Lavalle wrote:

Gibi, Bence,

In fact, I added the demo explicitly to the Neutron PTG agenda from 1:30 
to 2, to give it visiblilty


I'm interested in seeing the demo too. Will the demo be shown at the 
Neutron room or the Nova room? Historically, lunch has ended at 1:30, so 
this will be during the same time as the Neutron/Nova cross project 
time. Should we just co-locate together for the demo and the session? I 
expect anyone watching the demo will want to participate in the 
Neutron/Nova session as well. Either room is fine by me.


-melanie

On Thu, Aug 30, 2018 at 3:55 AM, Balázs Gibizer 
mailto:balazs.gibi...@ericsson.com>> wrote:


Hi,

Based on the Nova PTG planning etherpad [1] there is a need to talk
about the current state of the bandwidth work [2][3]. Bence
(rubasov) has already planned to show a small demo to Neutron folks
about the current state of the implementation. So Bence and I are
wondering about bringing that demo close to the nova - neutron cross
project session. That session is currently planned to happen
Thursday after lunch. So we are think about showing the demo right
before that session starts. It would start 30 minutes before the
nova - neutron cross project session.

Are Nova folks also interested in seeing such a demo?

If you are interested in seeing the demo please drop us a line or
ping us in IRC so we know who should we wait for.

Cheers,
gibi

[1] https://etherpad.openstack.org/p/nova-ptg-stein

[2]

https://specs.openstack.org/openstack/neutron-specs/specs/rocky/minimum-bandwidth-allocation-placement-api.html


[3]

https://specs.openstack.org/openstack/nova-specs/specs/rocky/approved/bandwidth-resource-provider.html




__
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][nova] Small bandwidth demo on the PTG

[Miguel Lavalle]

Gibi, Bence,

In fact, I added the demo explicitly to the Neutron PTG agenda from 1:30 to
2, to give it visiblilty

Cheers

On Thu, Aug 30, 2018 at 3:55 AM, Balázs Gibizer  wrote:

> Hi,
>
> Based on the Nova PTG planning etherpad [1] there is a need to talk about
> the current state of the bandwidth work [2][3]. Bence (rubasov) has already
> planned to show a small demo to Neutron folks about the current state of
> the implementation. So Bence and I are wondering about bringing that demo
> close to the nova - neutron cross project session. That session is
> currently planned to happen Thursday after lunch. So we are think about
> showing the demo right before that session starts. It would start 30
> minutes before the nova - neutron cross project session.
>
> Are Nova folks also interested in seeing such a demo?
>
> If you are interested in seeing the demo please drop us a line or ping us
> in IRC so we know who should we wait for.
>
> Cheers,
> gibi
>
> [1] https://etherpad.openstack.org/p/nova-ptg-stein
> [2] https://specs.openstack.org/openstack/neutron-specs/specs/ro
> cky/minimum-bandwidth-allocation-placement-api.html
> [3] https://specs.openstack.org/openstack/nova-specs/specs/rocky
> /approved/bandwidth-resource-provider.html
>
>
> __
> 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][nova] Small bandwidth demo on the PTG

[Miguel Lavalle]

Gibi, Bence,

Thanks for putting this demo together. Please count me in

Regards

On Thu, Aug 30, 2018 at 3:55 AM, Balázs Gibizer  wrote:

> Hi,
>
> Based on the Nova PTG planning etherpad [1] there is a need to talk about
> the current state of the bandwidth work [2][3]. Bence (rubasov) has already
> planned to show a small demo to Neutron folks about the current state of
> the implementation. So Bence and I are wondering about bringing that demo
> close to the nova - neutron cross project session. That session is
> currently planned to happen Thursday after lunch. So we are think about
> showing the demo right before that session starts. It would start 30
> minutes before the nova - neutron cross project session.
>
> Are Nova folks also interested in seeing such a demo?
>
> If you are interested in seeing the demo please drop us a line or ping us
> in IRC so we know who should we wait for.
>
> Cheers,
> gibi
>
> [1] https://etherpad.openstack.org/p/nova-ptg-stein
> [2] https://specs.openstack.org/openstack/neutron-specs/specs/ro
> cky/minimum-bandwidth-allocation-placement-api.html
> [3] https://specs.openstack.org/openstack/nova-specs/specs/rocky
> /approved/bandwidth-resource-provider.html
>
>
> __
> 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][python3] Neutron and stadium - python 3 community goal changes coming soon

[Doug Hellmann]

Excerpts from Andreas Jaeger's message of 2018-08-30 17:32:46 +0200:
> On 2018-08-30 17:16, Nate Johnston wrote:
> > On Thu, Aug 30, 2018 at 08:28:40AM -0400, Doug Hellmann wrote:
> >> Excerpts from Michel Peterson's message of 2018-08-30 14:38:00 +0300:
> >>> On Thu, Aug 30, 2018 at 12:14 AM, Nate Johnston 
> >>> wrote:
> >>>
>  Progress is also being tracked in a wiki page [4].
> 
>  [4] https://wiki.openstack.org/wiki/Python3
> 
> >>>
> >>> That wiki page should only track teams or subteams should also be included
> >>> there? I'm asking because it seems that some subteams appear there while
> >>> the majority doesn't and perhaps we want to standarize that.
> >>
> >> It would be great to include information about sub-teams. If there
> >> are several, like in the neutron case, it probably makes sense to
> >> create a separate section of the page with a table for all of them,
> >> just to keep things organized.
> > 
> > Great!  I'll do that today.
> > 
> > Nate
> > 
> > P.S. By the way, at the top there is a note encouraging people to join
> > #openstack-python3, but when I try to do so I get rejected:
> > 
> > 11:13  Error(473): #openstack-python3 Cannot join channel (+i) - 
> > you must be invited
> > 
> > I figure either the wiki page or the channel is out of sync, but I am
> > not sure which one.
> 
> wiki page is wrong - the channel is dead. I'll update the wiki page,
> 
> Andreas

Thanks, Andreas!

__
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][python3] Neutron and stadium - python 3 community goal changes coming soon

[Andreas Jaeger]

On 2018-08-30 17:16, Nate Johnston wrote:

On Thu, Aug 30, 2018 at 08:28:40AM -0400, Doug Hellmann wrote:

Excerpts from Michel Peterson's message of 2018-08-30 14:38:00 +0300:

On Thu, Aug 30, 2018 at 12:14 AM, Nate Johnston 
wrote:


Progress is also being tracked in a wiki page [4].

[4] https://wiki.openstack.org/wiki/Python3



That wiki page should only track teams or subteams should also be included
there? I'm asking because it seems that some subteams appear there while
the majority doesn't and perhaps we want to standarize that.


It would be great to include information about sub-teams. If there
are several, like in the neutron case, it probably makes sense to
create a separate section of the page with a table for all of them,
just to keep things organized.


Great!  I'll do that today.

Nate

P.S. By the way, at the top there is a note encouraging people to join
#openstack-python3, but when I try to do so I get rejected:

11:13  Error(473): #openstack-python3 Cannot join channel (+i) - you 
must be invited

I figure either the wiki page or the channel is out of sync, but I am
not sure which one.


wiki page is wrong - the channel is dead. I'll update the wiki page,

Andreas
--
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
   HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


__
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][python3] Neutron and stadium - python 3 community goal changes coming soon

[Nate Johnston]

On Thu, Aug 30, 2018 at 08:28:40AM -0400, Doug Hellmann wrote:
> Excerpts from Michel Peterson's message of 2018-08-30 14:38:00 +0300:
> > On Thu, Aug 30, 2018 at 12:14 AM, Nate Johnston 
> > wrote:
> > 
> > > Progress is also being tracked in a wiki page [4].
> > >
> > > [4] https://wiki.openstack.org/wiki/Python3
> > >
> > 
> > That wiki page should only track teams or subteams should also be included
> > there? I'm asking because it seems that some subteams appear there while
> > the majority doesn't and perhaps we want to standarize that.
> 
> It would be great to include information about sub-teams. If there
> are several, like in the neutron case, it probably makes sense to
> create a separate section of the page with a table for all of them,
> just to keep things organized.

Great!  I'll do that today.

Nate

P.S. By the way, at the top there is a note encouraging people to join
#openstack-python3, but when I try to do so I get rejected:

11:13  Error(473): #openstack-python3 Cannot join channel (+i) - you 
must be invited

I figure either the wiki page or the channel is out of sync, but I am
not sure which one.


__
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] tox-siblings alternative for local testing

[Boden Russell]

On 8/30/18 5:49 AM, Michel Peterson wrote:
> 
> There are pre releases available in PyPI [1]. You can use those from
> your requirements like we did in n-odl [2].
> 
> That might be an acceptable solution.
> 
> [1] https://pypi.org/project/neutron/#history
> [2] https://review.openstack.org/#/c/584791/
> 

IIUC, I don't think consuming pre-releases is really a solution; it's a
work-around for this particular case.

Any solution should be pulling the appropriate dependencies from source;
mimicking what tox-siblings does. This ensures the local testing is done
on the latest source regardless of what's on PYPI (a point-in-time
snapshot of the code).

I believe the same applies to [2] in your email; things aren't going to
work as expected locally until you account for pulling from source.

We can discuss this more at the PTG, but moving forward I think any
projects wanting to get the neutron-lib consumption patches (for free)
will need to make sure they have tox/zuul setup properly for both local
and gate testing.

__
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][nova] Small bandwidth demo on the PTG

[Jay Pipes]

On 08/30/2018 04:55 AM, Balázs Gibizer wrote:

Hi,

Based on the Nova PTG planning etherpad [1] there is a need to talk 
about the current state of the bandwidth work [2][3]. Bence (rubasov) 
has already planned to show a small demo to Neutron folks about the 
current state of the implementation. So Bence and I are wondering about 
bringing that demo close to the nova - neutron cross project session. 
That session is currently planned to happen Thursday after lunch. So we 
are think about showing the demo right before that session starts. It 
would start 30 minutes before the nova - neutron cross project session.


Are Nova folks also interested in seeing such a demo?

If you are interested in seeing the demo please drop us a line or ping 
us in IRC so we know who should we wait for.


+1 from me. I'd be very interested in seeing it.

Best,
-jay

__
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][python3] Neutron and stadium - python 3 community goal changes coming soon

[Doug Hellmann]

Excerpts from Michel Peterson's message of 2018-08-30 14:38:00 +0300:
> On Thu, Aug 30, 2018 at 12:14 AM, Nate Johnston 
> wrote:
> 
> > Progress is also being tracked in a wiki page [4].
> >
> > [4] https://wiki.openstack.org/wiki/Python3
> >
> 
> That wiki page should only track teams or subteams should also be included
> there? I'm asking because it seems that some subteams appear there while
> the majority doesn't and perhaps we want to standarize that.

It would be great to include information about sub-teams. If there
are several, like in the neutron case, it probably makes sense to
create a separate section of the page with a table for all of them,
just to keep things organized.

Doug

__
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] tox-siblings alternative for local testing

[Michel Peterson]

On Wed, Aug 29, 2018 at 9:06 AM, Takashi Yamamoto 
wrote:

> is there any preferred solution for this?
> i guess the simplest solution is to make an intermediate release of neutron
> and publish it on pypi.  i wonder if it's acceptable or not.
>

There are pre releases available in PyPI [1]. You can use those from your
requirements like we did in n-odl [2].

That might be an acceptable solution.

[1] https://pypi.org/project/neutron/#history
[2] https://review.openstack.org/#/c/584791/
__
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][python3] Neutron and stadium - python 3 community goal changes coming soon

[Michel Peterson]

On Thu, Aug 30, 2018 at 12:14 AM, Nate Johnston 
wrote:

> Progress is also being tracked in a wiki page [4].
>
> [4] https://wiki.openstack.org/wiki/Python3
>

That wiki page should only track teams or subteams should also be included
there? I'm asking because it seems that some subteams appear there while
the majority doesn't and perhaps we want to standarize that.
__
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] [neutron-fwaas] roadmap

[Glenn VAN DE WATER]

Hi,



The FWaaS V2 spec (https://specs.openstack.org/
openstack/neutron-specs/specs/mitaka/fwaas-api-2.0.html) describes quite
some changes.



Currently only some of that functionality seems to be implemented i.e.
applying firewall groups on a L2/L3 port.



Does a roadmap exist, describing when/whether other features will be
implemented as well?

Not implemented features mentioned in the spec include:

   - firewall group construct as well as a way to specify allowed sources
   and destinations in firewall rules
   - indirections through address group and service group
   - allow multiple firewall group associations for the same Neutron port



Best regards,

Glenn
__
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][nova] Small bandwidth demo on the PTG

[Balázs Gibizer]

Hi,

Based on the Nova PTG planning etherpad [1] there is a need to talk 
about the current state of the bandwidth work [2][3]. Bence (rubasov) 
has already planned to show a small demo to Neutron folks about the 
current state of the implementation. So Bence and I are wondering about 
bringing that demo close to the nova - neutron cross project session. 
That session is currently planned to happen Thursday after lunch. So we 
are think about showing the demo right before that session starts. It 
would start 30 minutes before the nova - neutron cross project session.


Are Nova folks also interested in seeing such a demo?

If you are interested in seeing the demo please drop us a line or ping 
us in IRC so we know who should we wait for.


Cheers,
gibi

[1] https://etherpad.openstack.org/p/nova-ptg-stein
[2] 
https://specs.openstack.org/openstack/neutron-specs/specs/rocky/minimum-bandwidth-allocation-placement-api.html
[3] 
https://specs.openstack.org/openstack/nova-specs/specs/rocky/approved/bandwidth-resource-provider.html



__
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][python3] Neutron and stadium - python 3 community goal changes coming soon

[Nate Johnston]

Neutrinos and contributors to stadium projects,

As part of the "Run under Python 3 by default" community goal [1] for
OpenStack in the Stein cycle, a group of goal champions has assembled
and have been programmatically generating changes to help projects with
the process of migrating to a python 3 compatible state [2][3].  Since
we are now early in the Stein release cycle, it is a good time to land
these patches and make sure we are in a good state relative to the
community goal early, when we have the most time to handle any issues
that may arise.  As our fearless leader mlavalle said, "If not now,
when?"

So please expect to see changes landing in your projects under the
topic "python3-first".  If these cause issues for you please feel free
to reach out to either me or the python 3 goal champions.  Progress is
also being tracked in a wiki page [4].

Thanks!

Nate Johnston

[1] https://governance.openstack.org/tc/goals/stein/python3-first.html
[2] http://lists.openstack.org/pipermail/openstack-dev/2018-August/133232.html
[3] http://lists.openstack.org/pipermail/openstack-dev/2018-August/133880.html
[4] https://wiki.openstack.org/wiki/Python3


__
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] Rocky PTG retrospective etherpad

[Miguel Lavalle]

Here's the etherpad:
https://etherpad.openstack.org/p/neutron-rocky-retrospective

On Wed, Aug 29, 2018 at 3:24 PM, Miguel Lavalle  wrote:

> Dear Neutrinos,
>
> In preparation for our PTG in Denver, I have started an etherpad to gather
> feedback for our retrospective session. Please add your comments there
>
> Best regards
>
> Miguel
>
__
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] Rocky PTG retrospective etherpad

[Miguel Lavalle]

Dear Neutrinos,

In preparation for our PTG in Denver, I have started an etherpad to gather
feedback for our retrospective session. Please add your comments there

Best regards

Miguel
__
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] tox-siblings alternative for local testing

[Boden Russell]

On 8/29/18 12:06 AM, Takashi Yamamoto wrote:
> is there any preferred solution for this?
> i guess the simplest solution is to make an intermediate release of neutron
> and publish it on pypi.  i wonder if it's acceptable or not.

What we've been doing to date is adding tox target(s) to the respective
repo for local testing. These local targets install the dependencies
from source where necessary (in place tox siblings). For more details
see the "How to setup dependencies for local tox targets" of [1]. This
is also a topic I wanted to bring up at the neutron PTG [2].

There maybe other solutions, but I'm unaware of them.


[1] https://etherpad.openstack.org/p/neutron-sibling-setup
[2] https://etherpad.openstack.org/p/neutron-stein-ptg

__
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] tox-siblings alternative for local testing

[Takashi Yamamoto]

hi,

after a recent change [1] ,
neutron-fwaas' unit tests need an unreleased version of neutron.
(the one including the corresponding change [2])
while it's handled by tox-siblings on the gate,
it requires extra steps if you want to run the tests locally.

is there any preferred solution for this?
i guess the simplest solution is to make an intermediate release of neutron
and publish it on pypi.  i wonder if it's acceptable or not.

[1] https://review.openstack.org/#/c/596971/
[2] https://review.openstack.org/#/c/586525/

__
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