July 2021 - openstack-discuss - lists.openstack.org

[tc][all] Please Help On Collecting Pain Points
by Rico Lin 16 Aug '21

16 Aug '21

Dear all As a proposal for pre-select goals for Yoga [1]. We need to figure out the possibility. *I would like to ask each project team, SIG, and pop-up if you can kindly provide the major pain point you have (and better to be fixable by bugs/features).* *What you can help with is added in pain point information in [2].* *Information like pain point topic, description, and ideas on how to targeting them.* *Why this is important?* I think this data allows us to see clearly if we can have goals like `eliminate pain points`. *What's after this?* If we can make sure this can be a goal material, we might be able to have this as a goal and allow project teams to focus on one of their most important issues. As an alternative, we might be able to collect from user side with a user survey, but that's more like a really long-term plan for this. [1] https://etherpad.opendev.org/p/y-series-goals [2] https://etherpad.opendev.org/p/pain-point-elimination *Rico Lin* OIF Board director, OpenStack TC, Multi-arch SIG chair, Heat PTL, Senior Software Engineer@EasyStack

3 4

Pls help newbie :) bare metal new Ansible deployment
by Nicola Ferrari (#554252) 14 Aug '21

14 Aug '21

Dears, I'm new to the list. We're just trying to introduce a demo install of openstack in our network. Our intention was to use 5 machine, already installed with ubuntu-mini 20.04. ostack1 as control node ostack2 -| ostack3 -| AS COMPUTE NODE ostack4 -| ostack5 -| ostack4 - ostack5 also as block storage node, they are connected on a direct storage (sas) where we deployed lvm with a vg named "cinder_volumes". All nodes both are on a /24 network (192.168.32.0/24) behind a router (32.254) and also on a "private" network (10.255.255.0/24) which just interconnect nodes themselves. We inteded to deploy openstack using openstack-ansible, available on github, last stable release. You can see our user_config as attachment. setup-hosts playbook runs with no errors. setup-infrastructure playbook hangs on RUNNING HANDLER [repo_server : reload nginx] **************************************************************************************** FAILED - RETRYING: reload nginx (1 retries left). fatal: [ostack1_repo_container-aabb6a12]: FAILED! => {"attempts": 5, "changed": false, "msg": "Unable to start service nginx: Job for nginx.service failed because the control process exited with error code.\nSee \"systemctl status nginx.service\" and \"journalctl -xe\" for details.\n"} Looking at log I can see that nginx coudn't start due to "Cannot assign requested address: 99" error. I suppose that must be a mistake in the deploy file? Many thanks for your suggestion, and pls, be sorry for my poor english :) Nick

2 2

[neutron] Status of networking-mlnx: Is it still maintained ?
by Takashi Kajinami 12 Aug '21

12 Aug '21

Hello, I noticed the networking-mlnx repo[1] is not updated for a while and looks unmaintained. The repo doesn't have a stable/wallaby release created, and its setup.cfg doesn't include python 3.8 as a supported platform. https://opendev.org/x/networking-mlnx Is anybody still maintaining this repo ? If the repo is no longer maintained, I'll propose deprecating support for the plugin from puppet-neutron. Please let me know if you have any concern with that deprecation. I appreciate any input about this $topic. Thank you, Takashi Kajinami

1 2

[PTLs][release] Xena Cycle Highlights
by helena＠openstack.org 11 Aug '21

11 Aug '21

Hello Everyone!It's that time of the year once again! It's time to start thinking about calling out 'cycle-highlights' in your deliverables! As PTLs, you probably get many pings towards the end of every release cycle by various parties (marketing, management, journalists, etc) asking for highlights of what is new and what significant changes are coming in the new release. By putting them all in the same place it makes them easy to reference because they get compiled into a pretty website like this from the last few releases: Ussuri[1], Victoria[2]. We don't need a fully fledged marketing message, just a few highlights (3-4 ideally), from each project team. Looking through your release notes might be a good place to start. The deadline for cycle highlights is the end of the R-5 week [3] on September 3.How To Reminder: -------------------------Simply add them to the deliverables/$RELEASE/$PROJECT.yaml in the openstack/releases repo like this: cycle-highlights: - Introduced new service to use unused host to mine bitcoin.The formatting options for this tag are the same as what you are probably used to with Reno release notes.Also, you can check on the formatting of the output by either running locally: tox -e docsAnd then checking the resulting doc/build/html/$RELEASE/highlights.html file or the output of the build-openstack-sphinx-docs job under html/$RELEASE/highlights.html. Feel free to add Kendall Nelson (diablo_rojo) as a reviewer on your patches. Can't wait to see you all have accomplished this release! Thanks :) -Helena Spease (hspease) [1] [ https://releases.openstack.org/ussuri/highlights.html ]( https://releases.openstack.org/ussuri/highlights.html ) [2] https://releases.openstack.org/victoria/highlights.html [3] https://releases.openstack.org/xena/schedule.html

1 1

[interop][cinder] review of next.json (part 2)
by Brian Rosmaita 09 Aug '21

09 Aug '21

Hello Interop WG, The Cinder team completed its discussion of what capabilities should be added as advisory in next.json at yesterday's weekly cinder meeting [0]. The tldr; is that we don't have anything to propose for inclusion in next.json at the present time. The team does have some general questions that would help us determine the suitability of some proposed capabilities. We'd like to invite someone from the Interop WG to the cinder xena R-9 virtual midcycle (Wednesday 4 August 2021, 1400-1600 UTC) so we can discuss this "live". So if someone could put 1400 UTC 4 August on their schedule for a 20 minute discussion, that would be very helpful. cheers, brian [0] http://eavesdrop.openstack.org/meetings/cinder/2021/cinder.2021-05-12-14.00…

3 8

Re: [neutron-vpnaas][kolla-ansible][victoria] Growing memory consumption with only one VPN connection
by at 09 Aug '21

09 Aug '21

Hi, 1. There is only one, bidirectional vpn connection between project networks in two regions 2. there is no (or almost no) traffic on this vpn link 3. second region is on one host (kolla all-in-one) and situation looks the same- with vpn service enabled there is excessive Memory use (growing also about 5-6MB/ minute and forcing the system to use swapfile) there is no big cpu usage (ofcourse also due to no traffic inside VPN) It's the same case even if there's no vpn connection configured. Best regards Adam Tomas Wysłane z iPhone'a > Wiadomość napisana przez Vinh Nguyen Duc <vinhducnguyen1708(a)gmail.com> w dniu 29.06.2021, o godz. 11:04: > > > Hi Adam, > Do you think the VPN connection is use CPU and memory to encrypt the VPN traffic? > > On Mon, Jun 28, 2021 at 14:30 Adam Tomas <bkslash(a)poczta.onet.pl <mailto:bkslash@poczta.onet.pl>> wrote: > Hi, > I have problem with neutron vpnaas - after enabling vpnaas plugin everything was ok at first. I was able to create VPN connection and communication is correct. But after a week of running vpnaas (only one VPN connection created/working!) I’ve noticed, that neutron-vpnaas takes more and more memory. I have 5 processes on each controller (there should be always five? Or it is changing dynamically?): > > 42435 1545384 0.6 8.6 5802516 5712412 ? S Jun15 110:50 /var/lib/kolla/venv/bin/python3.8 /var/lib/kolla/venv/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/neutron_vpnaas.conf > 42435 1545389 0.6 8.5 5735832 5645856 ? S Jun15 112:16 /var/lib/kolla/venv/bin/python3.8 /var/lib/kolla/venv/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/neutron_vpnaas.conf > 42435 1545378 0.5 8.5 5734192 5643620 ? S Jun15 108:09 /var/lib/kolla/venv/bin/python3.8 /var/lib/kolla/venv/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/neutron_vpnaas.conf > 42435 1545372 0.5 8.5 5731128 5641436 ? S Jun15 109:07 /var/lib/kolla/venv/bin/python3.8 /var/lib/kolla/venv/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/neutron_vpnaas.conf > 42435 1545369 0.6 8.4 5637084 5547392 ? S Jun15 114:21 /var/lib/kolla/venv/bin/python3.8 /var/lib/kolla/venv/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/neutron_vpnaas.conf > > now neutron_server takes over 27G of RAM on each controller: > > neutron_server running 10.2 27.2G > > After stopping all neutron containers and starting it again neutron takes a lot less memory: > > neutron_server running 0.5 583M > > but memory usage keeps growing (about 5-6 M every minute). > What’s wrong? When I disable vpnaas globally there’s no problem with excessive memory usage, so it’s vpnaas for sure… > > Best regards > Adam Tomas

3 2

[neutron][ops] VLAN Provider Network
by DHilsbos＠performair.com 06 Aug '21

06 Aug '21

All; We're using OpenStack Victoria, with OVS networking (no OVN). I'm having some problems with a VLAN provider network that I added to my OpenStack. I have other VLAN provider networks, that I based this one off of. Instances are getting the tap interfaces, but these interfaces are not getting IP addresses, and when a static IP is given, they can't ping either the DHCP address or the gateway address. I have checked the switch configuration, to verify the VLAN is bound appropriately. I rebooted the whole cluster to ensure the configuration change applied. Here's a snip our plugin.ini [ml2_type_vlan] network_vlan_ranges = provider_core:55:55,provider_core:64:64,... 64 works, 55, doesn't. I'm not seeing anything concerning in /var/log/openvswitch/ovs-vswitchd.log I'm sure it's something dumb, but I'm not seeing it. Any suggestions for what else to look at? Thank you, Dominic L. Hilsbos, MBA Vice President - Information Technology Perform Air International Inc. DHilsbos(a)PerformAir.com www.PerformAir.com

2 2

[wallaby][neutron][ovn] Multiple VLAN ranges and FLAT network
by Malik Obaid 06 Aug '21

06 Aug '21

Hi, I am using Openstack Wallaby release on Ubuntu 20.04. I am configuring openstack neutron for production and just want to know is there a way to specify different vlan ranges with multiple physical networks. I would really appreciate any input in this regard. Thank you. Regards, Malik Obaid

2 1

gerrit no longer lading from iphone
by Sorin Sbarnea 05 Aug '21

05 Aug '21

I am wondering if something was changed on our gerrit deployment recently as it seems to no longer load on ios safari. I know,… not the most common use case… still adding the usual recheck can prove useful after checking zuul comment. /zbr -- -- /zbr

5 7

Migrating VM's
by Derek O keeffe 04 Aug '21

04 Aug '21

Hi all, I have a question. If we have an old openstack deployment (Queens) that have VM's (with & without volumes attached) and we want to migrate those to a new deploy (Victoria) can this be achieved by the owners of the VM's through horizon in some way? We can take snapshots of the vm's that don't have volumes attached, copy them to the new controller and re instantiate them but we haven't found a solution for the volumes yet. This give us more work though as it all needs to be done over cli so the user is taken out of the loop and it falls on us 3 admins to move over 300 VM's. Any advice or info would be greatly appreciated. Thanks in advance. Derek

3 7