- openstack-discuss - lists.openstack.org

[nova] Can we drop the cells v1 docs now?
by Matt Riedemann 12 Feb '19

12 Feb '19

I have kind of lost where we are on dropping cells v1 code at this point, but it's probably too late in Stein. And technically nova-network won't start unless cells v1 is configured, and we've left the nova-network code in place while CERN is migrating their deployment to neutron*. CERN is running cells v2 since Queens and I think they have just removed this [1] to still run nova-network without cells v1. There has been no work in Stein to remove nova-network [2] even though we still have a few API related things we can work on removing [3] but that is very low priority. To be clear, CERN only cares about the nova-network service, not the APIs which is why we started removing those in Rocky. As for cells v1, if we're not going to drop it in Stein, can we at least make incremental progress and drop the cells v1 related docs to further signal the eventual demise and to avoid confusion in the docs about what cells is (v1 vs v2) for newcomers? People can still get the cells v1 in-tree docs on the stable branches (which are being published [4]). [1] https://github.com/openstack/nova/blob/bff3fd1cd/nova/cmd/network.py#L43 [2] https://blueprints.launchpad.net/nova/+spec/remove-nova-network-stein [3] https://etherpad.openstack.org/p/nova-network-removal-rocky [4] https://docs.openstack.org/nova/queens/user/cells.html#cells-v1 *I think they said there are parts of their deployment that will probably never move off of nova-network, and they will just maintain a fork for that part of the deployment. -- Thanks, Matt

3 2

[tripleo][openstack-ansible] collaboration on os_tempest role update X - Feb 12, 2019
by Chandan kumar 12 Feb '19

12 Feb '19

Hello, Here is the 10th update (Feb 06 to Feb 12, 2019) on collaboration on os_tempest[1] role between TripleO and OpenStack-Ansible projects. Summary: This week we basically worked on clearing up/merging the existing patches like: * For debugging networking issue for os_tempest, we have router ping * Added telemetry tempest plugin support * The os_tempest overview page got rewrite: https://docs.openstack.org/openstack-ansible-os_tempest/latest/overview.html * Added use of user/password for secure image download And from myside, not to much work as busy with ruck/rover on TripleO Side. Things got merged OS_TEMPEST: * Update all plugin urls to use https rather than git - https://review.openstack.org/633752 * venv: use inventory_hostname instead of ansible_hostname - https://review.openstack.org/635187 * Add telemetry distro plugin install for aodh - https://review.openstack.org/632125 * Add user and password for secure image download (optional) - https://review.openstack.org/625266 * Ping router once it is created - https://review.openstack.org/633883 * Improve overview subpage - https://review.openstack.org/633934 python-venv_build: * Add tripleo-ci-centos-7-standalone-os-tempest job - https://review.openstack.org/634377 In Progress work: OS_TEMPEST * Use the correct heat tests - https://review.openstack.org/#/c/630695/ * Add option to disable router ping - https://review.openstack.org/636211 * Add tempest_service_available_mistral with distro packages - https://review.openstack.org/635180 * Added tempest.conf for heat_plugin - https://review.openstack.org/632021 TripleO: * Reuse the validate-tempest skip list in os_tempest - https://review.openstack.org/634380 Goal of this week: * Unblock os_heat gate due to mpi4py dependency and other issue * Complete skip list reuse on tripleo side Thanks to jrosser, mnaser, odyssey4me, guilhermesp on router_ping, os_heat help, arxcruz on reuse skip list & mkopec for improving doc. Here is the 9th update [2]. Have queries, Feel free to ping us on #tripleo or #openstack-ansible channel. Links: Links: [1.] http://git.openstack.org/cgit/openstack/openstack-ansible-os_tempest [2.] http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002382… Thanks, Chandan Kumar

1 0

[Neutron] Multi segment networks
by Ricardo Noriega De Soto 12 Feb '19

12 Feb '19

Hello guys, Quick question about multi-segment provider networks. Let's say I create a network and a subnet this way: neutron net-create multinet --segments type=dict list=true provider:physical_network='',provider:segmentation_id=1500,provider:network_type=vxlan provider:physical_network=physnet_sriov,provider:segmentation_id=2201,provider:network_typ e=vlan neutron subnet-create multinet --allocation-pool start=10.100.5.2,end=10.100.5.254 --name mn-subnet --dns-nameserver 8.8.8.8 10.100.5.0/24 Does it mean, that placing two VMs (with regular virtio interfaces), one in the vxlan segment and one on the vlan segment, would be able to ping each other without the need of a router? Or would it require an external router that belongs to the owner of the infrastructure? Thanks in advance! -- Ricardo Noriega Senior Software Engineer - NFV Partner Engineer | Office of Technology | Red Hat irc: rnoriega @freenode

2 1

[dev] [neutron] bug deputy report of the week of Feb 4
by Akihiro Motoki 12 Feb '19

12 Feb '19

Hi neutrinos, I was a bug deputy last week. The last week was relatively quiet. The following * Needs investigation * https://bugs.launchpad.net/neutron/+bug/1815463 (New) [dev] Agent RPC version does not auto upgrade if neutron-server restart first * ovsdbapp.exceptions.TimeoutException in functional tests (gate failure) https://bugs.launchpad.net/bugs/1815142 * In Progress * https://bugs.launchpad.net/bugs/1815345 (Medium, In Progress) neutron doesnt delete port binding level when deleting an inactive port binding * Incomplete * https://bugs.launchpad.net/bugs/1815424 (Incomplete) Port gets port security disabled if using --no-security-groups I cannot reproduce it. Requesting the author more information. * FYI * https://bugs.launchpad.net/bugs/1815433 Code crash with invalid connection limit of listener neutron-lbaas bug needs to be filed to storyboard. I requested it to the bug author and he/she filed it. [1] https://storyboard.openstack.org/#!/project/openstack/neutron-lbaas Best Regards, Akihiro Motoki (irc: amotoki)

1 1

[cinder] Help with Fedora 29 devstack volume/iscsi issues
by Ian Wienand 12 Feb '19

12 Feb '19

Hello, I'm trying to diagnose what has gone wrong with Fedora 29 in our gate devstack test; it seems there is a problem with the iscsi setup and consequently the volume based tempest tests all fail. AFAICS we end up with nova hitting parsing errors inside os_brick's iscsi querying routines; so it seems whatever error path we've hit is outside the usual as it's made it pretty far down the stack. I have a rather haphazard bug report going on at https://bugs.launchpad.net/os-brick/+bug/1814849 as I've tried to trace it down. At this point, it's exceeding the abilities of my cinder/nova/lvm/iscsi/how-this-all-hangs-together knowledge. The final comment there has a link the devstack logs and a few bits and pieces of gleaned off the host (which I have on hold and can examine) which is hopefully useful to someone skilled in the art. I'm hoping ultimately it's a rather simple case of a missing package or config option; I would greatly appreciate any input so we can get this test stable. Thanks, -i

2 2

[Cyborg][IRC] The Cyborg IRC meeting will be held Wednesday at 0300 UTC
by Li Liu 12 Feb '19

12 Feb '19

Happy Chinese New Year! The IRC meeting will be resumed Wednesday at 0300 UTC, which is 10:00 pm est(Tuesday) / 7:00 pm pst(Tuesday) /11 am Beijing time (Wednesday) -- Thank you Regards Li

1 0

Fwd: UC Candidacy
by Amy Marrich 12 Feb '19

12 Feb '19

This email is my nomination to re-run for the OpenStack User Committee election. I have been involved with OpenStack as an operator since the Grizzly release working with both private and public cloud environments. I have been an upstream contributor since the Mitaka release cycle and I am currently a Core Reviewer for OpenStack-Ansible which works closely with operators to help them set up their deployments and insight for our direction. I believe I bring valuable insight to the User Committee being involved as both an AUC and ATC. Through my involvement with the OpenStack Upstream Institute and Diversity Working Group, I have been very active in helping to bring new members to our community and more importantly working to find new ways to keep them involved once they join. There is still work I would like to continue working on, such as the OPS Meetups and the OpenStack mentoring programs to help get more Operators involved in the community. Thanks, Amy (spotz)

1 0

[ops] OpenStack operators meetup, Berlin, March 6th,7th
by Chris Morgan 12 Feb '19

12 Feb '19

Dear All, The Evenbrite for the next ops meetup is now open, see https://www.eventbrite.com/e/openstack-ops-meetup-berlin-tickets-55034908894 Thanks for Allison Price from the foundation for making this for us. We'll be sharing more details on the event soon. Chris on behalf of the ops meetups team -- Chris Morgan <mihalis68(a)gmail.com>

3 5

[ptg][nova][placement] Etherpad & collector started
by Eric Fried 12 Feb '19

12 Feb '19

I needed to brain-dump some topics to be discussed at the PTG in a couple of months. I asked if there was already an etherpad and the two people who happened to hear my question weren't aware of one, so I started one [1]. I also started the collector wiki page [2], templated on the Stein one [3]. Enjoy. -efried [1] https://etherpad.openstack.org/p/nova-ptg-train [2] https://wiki.openstack.org/wiki/PTG/Train/Etherpads [3] https://wiki.openstack.org/wiki/PTG/Stein/Etherpads

1 0

[dev][keystone] Keystone Team Update - Week of 4 February 2019
by Colleen Murphy 11 Feb '19

11 Feb '19

# Keystone Team Update - Week of 4 February 2019 ## News ### Performance of Loading Fernet/JWT Key Repositories Lance noticed that it seems that token signing/encryption keys are loaded from disk on every request and is therefore not very performant, and started investigating ways we could improve this[1][2]. [1] http://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%23openstack-k… [2] http://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%23openstack-k… ## Recently Merged Changes Search query: https://bit.ly/2pquOwT We merged 10 changes this week. ## Changes that need Attention Search query: https://bit.ly/2RLApdA There are 73 changes that are passing CI, not in merge conflict, have no negative reviews and aren't proposed by bots. ## Bugs This week we opened 2 new bugs and closed 3. Bugs opened (2) Bug #1814589 (keystone:High) opened by Guang Yee https://bugs.launchpad.net/keystone/+bug/1814589 Bug #1814570 (keystone:Medium) opened by Guang Yee https://bugs.launchpad.net/keystone/+bug/1814570 Bugs fixed (3) Bug #1804483 (keystone:Medium) fixed by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1804483 Bug #1805406 (keystone:Medium) fixed by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1805406 Bug #1801095 (keystone:Wishlist) fixed by Artem Vasilyev https://bugs.launchpad.net/keystone/+bug/1801095 ## Milestone Outlook https://releases.openstack.org/stein/schedule.html Feature freeze is in four weeks. Be mindful of the gate and try to submit and review things early. ## Shout-outs Congratulations and thank you to our Outreachy intern Islam for completing the first step in refactoring our unit tests to lean on our shiny new Flask framework! Great work! ## Help with this newsletter Help contribute to this newsletter by editing the etherpad: https://etherpad.openstack.org/p/keystone-team-newsletter

2 1