[openstack-dev] [dragonflow] Weekly cancelled

[Omer Anson]

Hi,

The weekly meeting that is scheduled for today is cancelled. See you next
week.

Thanks,
Omer.
__
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 is not very priority for neutron function bug. But some CI 
failure related.


CI FAILURE:
https://bugs.launchpad.net/neutron/+bug/1733649 -- This is about fullstack one, 
Slawek Kaplonski had focused on it.


https://bugs.launchpad.net/neutron/+bug/1734265 -- This is about the 
neutron-dynamic-routing didn't met the new extension directory.


Other need concerned are:


https://bugs.launchpad.net/neutron/+bug/1733852 --  In DVR env, the arp 
entry generated is wrong if we use a port for VIP(we use in allowed address 
pairs) such as LoadBalancer things, the mac in generated arp entry will come 
from the notbound port. So need the best approach for it.




https://bugs.launchpad.net/neutron/+bug/1734136 -- would be good if Qos team 
could have a look to prioritize this bug, as this may be caused the backend 
does the wrong behavior.


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

[openstack-dev] [chef] Heads up - Chef 13 is incoming

[Samuel Cassiba]

Ohai!

With Chef 12 EOL approaching, Pike was originally intended to be the
final release exclusively supporting Chef 12, with Chef 13 being
deferred to Queens development. However, Chef 13 support is here at
long last. Chef 12 clients should be able to work using the same
cookbooks for now, as in, it works in Test Kitchen, but YMMV past
Pike.

Airgapped deployers need especially take notice, as MariaDB packages
are now coming from mariadb.org and not the distro repos. Software
Collections also comes configured out of the box for CentOS.

If you run into any problems, #openstack-chef is always open. Just
keep in mind that the team is very distributed, so park a client for a
while.

-- 
Best,
Samuel Cassiba

__
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] Removing internet access from unit test gates

[Clint Byrum]

Excerpts from Jens Harbott's message of 2017-11-24 13:22:23 +:
> 2017-11-21 15:04 GMT+00:00 Jeremy Stanley :
> > On 2017-11-21 09:28:20 +0100 (+0100), Thomas Goirand wrote:
> > [...]
> >> The only way that I see going forward, is having internet access
> >> removed from unit tests in the gate, or probably just the above
> >> variables set.
> > [...]
> ...
> > Removing network access from the machines running these jobs won't
> > work, of course, because our job scheduling and execution service
> > needs to reach them over the Internet to start jobs, monitor
> > progress and collect results.
> 
> I have tested a variant that would accomodate this: Run the tests in a
> new network namespace that no network configuration at all. There are
> some issues with this still:
> 
> - One needs sudo access in order to run something similar to "ip netns
> exec ns1 tox ...". This could still be set up in a way such that the
> tox user/environment itself does not need sudo.
> - I found some unit tests that do need to talk to localhost, so one
> still has to setup lo with 127.0.0.1/32.
> - Most important issue that prevents me from successfully running tox
> currently though is that even if I prepared the venv beforehand with
> "tox -epy27 --notest", the next tox run will still want to reinstall
> the project itself and most projects have something like
> 
> install_command =
> pip install -U
> -c{env:UPPER_CONSTRAINTS_FILE:https://git.openstack.org/cgit/openstack/requirements/plain/upper-constraints.txt}
> {opts} {packages}
> 
> in their tox.ini, which will obviously fail without network
> connectivity. Running something like
> 
> sudo ip netns exec ns1 su -c ".tox/py27/bin/stestr run" $USER
> 
> does work rather well though. Does anyone have an idea how to force
> tox to just run the tests without doing any installation steps? Then I
> guess one could come up with a small wrapper to handle the other
> steps.
> 

Tox can be run without tests first to build all the venvs:

  $ tox --notest

Then with a sufficiently new kernel or setuid bwrap, one can use
Bubblewrap to get a clean netns:

bwrap --unshare-net 

Unfortunately bubblewrap is pretty new, so it's only going to be there
in package repos with newer Fedora and Ubuntu.

Either way, this is pretty doable with Zuulv3 inheritance. Whatever
jobs are using as parent, make a -nonet child of that which runs tox
--notest with network access still intact, then by whatever means makes
the most sense, namespaces or firewalls, runs the tests themselves with
access restricted.

__
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] any flow-charts ?

[Gary Kotton]

Hi,
Please see 
https://docs.openstack.org/security-guide/networking/architecture.html for a 
starting point.
Thanks
Gary

From: Guru Desai 
Reply-To: OpenStack List 
Date: Saturday, November 25, 2017 at 1:00 PM
To: OpenStack List 
Subject: [openstack-dev] [Neutron] any flow-charts ?

Hello All,

I am new kid in the block !!   looking for info on few things of  
Neutron(pike). Apologies for such basic questions..

i am curious to understand how is the flow when a user creates a network 
through cli/ui.  what happens in the background ? are there some flow-charts 
about such things of neutron..

Any pointers would be very helpful.

Thanks
GD
__
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