Re: [openstack-dev] [Neutron] Propose Slawek Kaplonski for Neutron core

+1 from me , (even though my vote does not count) I know Slawek since Tokyo summit and I’m impressed of his knowledge and hands-on experience to improve Neutron quality and functionality! It is great to see him joining the core reviewers team! Congrats Sławek! From: Miguel Angel Ajo Pelayo

Re: [openstack-dev] [neutron] - Neutron team social in Atlanta on Thursday

+1 From: Kevin Benton [mailto:ke...@benton.pub] Sent: Friday, February 17, 2017 8:19 PM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [neutron] - Neutron team social in Atlanta on Thursday Hi all, I'm organizing a Neutron social event for Thursday evening in Atlanta somewhere

Re: [openstack-dev] [Neutron] Neutron team social event in Barcelona

+1 From: Oleg Bondarev [mailto:obonda...@mirantis.com] Sent: Monday, October 17, 2016 9:52 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron] Neutron team social event in Barcelona +1 On Mon, Oct 17,

Re: [openstack-dev] [neutron][ovo] Need help to understand the exception of NeutronSyntheticFieldMultipleForeignKeys

t;manjeet.s.bha...@intel.com>; Korzeniewski, Artur <artur.korzeniew...@intel.com> Subject: [neutron][ovo] Need help to understand the exception of NeutronSyntheticFieldMultipleForeignKeys hi neutron ovo hacker: Recently I am working on neutron OVO blue print, and found there are some

[openstack-dev] [neutron][upgrades] Bi-weekly upgrades work status. 8/2/2016

Hi Neutrinos, As we are progressing with object implementation for neutron database resources, I would like to summarize the status. Please find the etherpad as up-to-date work status on object progress, TODOs/In progress/Done items: https://etherpad.openstack.org/p/newton-ovo-progress This

[openstack-dev] [neutron][api] Passing random filters on neutron API calls

Hi all, During integration of Subnet OVO into db code get_subnet/update_subnet/delete [1], I have found and issue in API behavior and strict object implementation for NeutronDbObject base class. The issue is that on REST API level, you can pass random filters and it will not affect the result

[openstack-dev] [neutron][upgrades] Bi-weekly upgrades work status. 7/11/2016

Hi, Starting another round of bi-weekly update presented once in a 3-week time period. Let's kick it: 1. We are still working on porting existing resources to use OVO What was merged: - objects: Introduce the DNSNameServer OVO in the code: https://review.openstack.org/326477

[openstack-dev] [neutron][upgrades] Bi-weekly upgrades work status. 6/2/2016

Hi Neutrinos, I would like to start the first bi-weekly upgrades work report. TLDR: In order to inform community what is going on in upgrades field, we would like to start bi-weekly reporting. We would like to show progress in database resource transition to Oslo VersionedObjects. Also list

Re: [openstack-dev] [neutron][ovo] NeutronDbObject concurrency issues

Hi Ilya, Thanks for investigating the concurrency issue. It is indeed a problem from multithreaded neutron-server point of view. Regarding the opt.2, there is ongoing work to add the revision number[1] to main neutron resources (port, network, subnet...) This is connected to spec [2] and

Re: [openstack-dev] [neutron] Social at the summit

Sign me up :) Artur IRC: korzen -Original Message- From: Darek Smigiel [mailto:smigiel.dari...@gmail.com] Sent: Monday, April 25, 2016 7:19 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron]

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade - Nova metadata failure

Hi, I have re-spin the grenade multimode dvr config [1]. In my understanding, this job would install multinode environment, with L3 agent and metadata agent running on subnode. Also to take advantage of this setup: a) Grenade tests should create DVR router as resource, b) the Tempest smoke tests

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

I have submitted patch for DVR Grenade multinode job: https://review.openstack.org/#/c/250215 Without DVR upgrade - we won't be able to tell if L3 upgrade is working. What is left to be done, it is the DVR support in Grenade. DVR has the multinode job, but I do not see DVR in grenade - creation

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

I have run the multimode grenade job twice: Failed: [1] http://logs.openstack.org/69/143169/60/experimental/gate-grenade-dsvm-neutron-multinode/bf6bae1/ Success: [2] http://logs.openstack.org/69/143169/60/experimental/gate-grenade-dsvm-neutron-multinode/7c05ff0/ The [1] failed because it

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

Yes, this file is complete fine. The Grenade is running smoke test before resource creation. The workflow is like this: 1. Install old devstack on main and subnode 2. Run tempest smoke 3. Create resources 4. Verify resources 5. Shutdown the services 6. Verify if shutdown does not affect the

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

From what I understand – the Sean case did not get to upgrade [1]– it has ended after creating the VM and trying to ping/ssh it. So we do not have restart logs of q-agt and no logs in new [2] The subnode will have only ‘old’ logs because the grenade multimode scenario assumes that subnode will

Re: [openstack-dev] [neutron][upgrade] new 'all things upgrade' subteam

Mon 15 UTC works for me too. Was there the first meeting on past Monday? Or are we starting on Monday 23rd November? -Original Message- From: Akihiro Motoki [mailto:amot...@gmail.com] Sent: Wednesday, November 18, 2015 4:04 PM To: OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

Thanks Sean D. for explanation! I’ve taken a look into old Russell patches, and it seems that the project-config was already modified by him: Add check-grenade-dsvm-partial-ncpu-neutron: (project-config) https://review.openstack.org/#/c/189426 Add check-grenade-dsvm-partial-ncpu-neutron-dvr

[openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

Hi Sean, I'm interested in introducing to Neutron the multinode partial upgrade job in Grenade. Can you explain how multinode is currently working in Grenade and how Nova is doing the partial upgrade? Regards, Artur Korzeniewski IRC: korzen Intel

Re: [openstack-dev] [neutron][upgrade] new 'all things upgrade' subteam

My TZ is UTC +1:00. Do we have any favorite day? Maybe Tuesday? It is good idea to have at least 0,5h sync each week. Regards, Artur From: Anna Kamyshnikova [mailto:akamyshnik...@mirantis.com] Sent: Wednesday, November 11, 2015 10:43 AM To: OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [Neutron] Neutron Social Meetup in Tokyo

Hi, Please count me in also. I’ll be happy to meet with you folks! Regards, Artur From: Sukhdev Kapur [mailto:sukhdevka...@gmail.com] Sent: Tuesday, October 27, 2015 2:32 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron] Neutron Social

[openstack-dev] [neutron] Neutron rolling upgrade - are we there yet?

Hi all, I would like to gather all upgrade activities in Neutron in one place, in order to summarizes the current status and future activities on rolling upgrades in Mitaka. 1. RPC versioning a. It is already implemented in Neutron. b. TODO: To have the rolling upgrade we have

[openstack-dev] Merging DVR-HA into Liberty release

Hi Code Reviewers, I would like to ask if DVR-HA patches can be merged into Liberty release: https://bugs.launchpad.net/neutron/+bug/1365473 https://review.openstack.org/#/c/196893 https://review.openstack.org/#/c/143169 The proper patches has been implemented, the reviews has been addressed,

[openstack-dev] [neutron][dvr] DVR L2 agent is removing the br-int OVS flows

Hi all, After merging the Graceful ovs-agent restart[1] (great work BTW!), I'm seeing in DVR L2 agent code place where flows on br-int is removed in old style: File /neutron/plugins/ml2/drivers/openvswitch/agent/ovs_dvr_neutron_agent.py 200 def setup_dvr_flows_on_integ_br(self): 201

Re: [openstack-dev] [neutron][dvr][ha] DVR-HA router is not working.

of the patches. This reinforces the need to hold on merging these patches until they have an in-tree integration test. On Tue, Aug 11, 2015 at 4:13 PM, Korzeniewski, Artur artur.korzeniew...@intel.commailto:artur.korzeniew...@intel.com wrote: Hi, I’ve been playing around with DVR-HA patches [1][2

[openstack-dev] [neutron][dvr][ha] DVR-HA router is not working.

Hi, I've been playing around with DVR-HA patches [1][2], have them applied on Mondays master branch. The problem is that the dvr-ha router is not working with SNAT and floating ips. My setup: Devstack-34 - all in one (controller, compute, DVR agent, DHCP node) Devstack-35 - compute node and DVR

Re: [openstack-dev] [neutron][dvr] Removing fip namespace when restarting L3 agent.

namespace when restarting L3 agent. On Thu, Aug 6, 2015 at 5:23 PM, Korzeniewski, Artur artur.korzeniew...@intel.commailto:artur.korzeniew...@intel.com wrote: Thanks Kevin for that hint. But it does not resolve the connectivity problem, it is just not removing the namespace when it is asked

Re: [openstack-dev] [neutron][dvr] Removing fip namespace when restarting L3 agent.

/dc0944f2d4e347922054bba679ba7f5d1ae6ffe2/etc/l3_agent.ini#L97 On Wed, Aug 5, 2015 at 3:36 PM, Korzeniewski, Artur artur.korzeniew...@intel.commailto:artur.korzeniew...@intel.com wrote: Hi all, During testing of Neutron upgrades, I have found that restarting the L3 agent in DVR mode is causing the VM network downtime

[openstack-dev] [neutron][dvr] Removing fip namespace when restarting L3 agent.

Hi all, During testing of Neutron upgrades, I have found that restarting the L3 agent in DVR mode is causing the VM network downtime for configured floating IP. The lockdown is visible when pinging the VM from external network, 2-3 pings are lost. The responsible place in code is: DVR: destroy