- openstack-discuss - lists.openstack.org

[neutron][ovn] enable_distributed_floating_ip
by Tony Liu 23 Sep '20

23 Sep '20

Hi, Could anyone elaborate what difference this option makes to Neutron OVN ML2 driver? I assume the driver will program OVN NB differently based on true or false? Any detail is appreciated. Thanks! Tony

1 0

[election][tc] TC Candidacy
by Ghanshyam Mann 23 Sep '20

23 Sep '20

Hello Everyone, I want to announce my candidacy for another term on the TC. First of all, thanks for giving me the opportunity as the technical committee in the previous terms. It's my 7th year in upstream developer activities and overall 9th year associated with OpenStack. I really enjoy my current role in the community. I've served as QA PTL for 2 years and currently a core developer in QA projects and Nova. Also, helping Tempest plugins for bug/Tempest compatible fixes and co-leader in the policy-popup team to make Openstack API policy more consistent and secure. With my QA, Nova, policy popup team role, I mainly target cross projects work as my TC responsibility; helping all projects team for the common work like Migrating the OpenStack CI/CD from Ubuntu Xenial to Bionic in Stein cycle and Ubuntu Bionic to Focal in Victoria, dropping python2.7 and, IPv6 deployment testing are the key activities in recent cycles. In my 3rd continuous cycle as community-wide goal champion, I tried my best to help in coding/investigation across many projects. I am actively involved in programs helping new contributors in OpenStack like a mentor in the Upstream Institute Training since Barcelona Summit (Oct 2016)[1] and an active member in FirstContact SIG [2]. It's always a great experience to introduce OpenStack upstream workflow to new contributors and encourage them to start contributing which is very much needed in OpenStack. TC direction has always been valuable and helps to keep the common standards in OpenStack. There is always room for improvement and so does in TC. I expect more involvement from the community and share what they expect from TC, and bring up discussions during TC office hours or meetings. In my next term, I would like to continue doing cross-project teams work for solving the common problem in OpenStack. In the next one or two-cycle, my main target is to make OpenStack API policy more consistent and secure as part of the policy popup team. Also, improving TC and team interaction. More interaction and involvement is the key to improve OpenStack. With the merging of UC into TC, it's a great opportunity to work together with the users/operators and collect valuable feedback to implement the required or priority things. Thank you for reading and considering my candidacy. Refernce: * Blogs: https://ghanshyammann.com * Review: http://stackalytics.com/?release=all&metric=marks&user_id=ghanshyammann&pro… * Commit: http://stackalytics.com/?release=all&metric=commits&user_id=ghanshyammann&p… * Foundation Profile: https://www.openstack.org/community/members/profile/6461 * IRC (Freenode): gmann [1] https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute_Occasions https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute [2] https://wiki.openstack.org/wiki/First_Contact_SIG - Ghanshyam Mann (gmann)

1 0

[ptl][release] RC1 Deadline Tomorrow
by Sean McGinnis 23 Sep '20

23 Sep '20

Hey everyone, Just a reminder that tomorrow, September 24, is the RC1 deadline for the Victoria cycle. If you have any cycle-based deliverables, there should have been a patch proposed earlier this week. If your project is ready, and if you've merged any final critical patches for Victoria, please +1 that patch so the release team knows it is safe to proceed. If you are working on any final patches, please update the release patch as soon as those merge to point to the commit hash for the tag and branch. After RC1 and the stable/victoria branch is created, any additional bugfixes will need to merge to the master branch first, then be backported to stable/victoria. Thanks, Sean

1 0

Community voting for the 2020 Open Infrastructure Summit Superuser Awards is now open!
by Ashlee Ferguson 23 Sep '20

23 Sep '20

Hi everyone, It’s time for the community to help determine the winner of the 2020 Open Infrastructure Summit <https://www.openstack.org/summit/2020/> Superuser Awards. The Superuser Editorial Advisory Board <https://superuser.openstack.org/about> will review the nominees and determine the finalists and overall winner after the community has had a chance to review and rate nominees. Now, it’s your turn. Review the nominees <https://superuser.openstack.org/articles/meet-the-2020-superuser-awards-nom…> and rate them <https://www.surveymonkey.com/r/Superuser2020> before the deadline September 28 at 11:59 p.m. PDT <http://www.thetimenow.com/worldclock.php>. Share your top pick for the Superuser Awards on Twitter <https://twitter.com/hashtag/OpenInfraSummit?src=hashtag_click>, Facebook <https://www.facebook.com/hashtag/openinfrasummit>, and LinkedIn <https://www.linkedin.com/feed/hashtag/?keywords=openinfrasummit> with #OpenInfraSummit! Cheers, Ashlee Ashlee Ferguson Community & Events Coordinator OpenStack Foundation

1 0

Trove images for Cluster testing.
by ARUNKUMAR PALANISAMY 23 Sep '20

23 Sep '20

Hello Team, My name is ARUNKUMAR PALANISAMY, As part of our project requirement, we are evaluating trove components and need your support for experimental datastore Image for testing cluster. (Redis, Cassandra, MongoDB, Couchbase) 1.) We are running devstack enviorment with Victoria Openstack release and with this image (trove-master-guest-ubuntu-bionic-dev.qcow2<https://tarballs.opendev.org/openstack/trove/images/trove-master-guest-ubun…>), we are able to deploy mysql instance and and getting below error while creating mongoDB instances. "ModuleNotFoundError: No module named 'trove.guestagent.datastore.experimental' " 2.) While tried creating mongoDB image with diskimage-builder<https://opendev.org/openstack/diskimage-builder> tool, but we are getting "Block device " element error. Regards, Arunkumar Palanisamy Cell: +49 172 6972490 =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you

2 4

Can't delete a vm
by Szabo, Istvan (Agoda) 23 Sep '20

23 Sep '20

Hello, I have vm which is stuck in the build phase: openstack server list --all-projects --long --limit -1 | grep 94ab55d3-3e39-48d3-a9b2-505838ceb6e7 | 94ab55d3-3e39-48d3-a9b2-505838ceb6e7 | hk-qaciapp-2020 | BUILD | scheduling | NOSTATE | | CentOS-7-x86_64-1511 (14.11.2017) | 2caaef01-e2f9-4e93-961a-c2b2d4a6be82 | QA_VLAN62 | None I've tried to delete with openstack server delete, nova delete force, restarted the nova services on all management nodes, restarted the nova compute service where it was originally spawned but still visible. I see in the database in couple of places either the id and either the hostname, like in instance mapping table, instances table, nova_cell0 database ... I have an idea how to delete, so I'd spawn just a vm and check which tables are created the entries, and I would go through all tables with the problematic one and delete 1 by 1 but this will takes me hours .... Any faster way you might suggest me please? Thank you ________________________________ This message is confidential and is for the sole use of the intended recipient(s). It may also be privileged or otherwise protected by copyright or other legal rules. If you have received it by mistake please let us know by reply email and delete it from your system. It is prohibited to copy this message or disclose its content to anyone. Any confidentiality or privilege is not waived or lost by any mistaken delivery or unauthorized disclosure of the message. All messages sent to and from Agoda may be monitored to ensure compliance with company policies, to protect the company's interests and to remove potential malware. Electronic messages may be intercepted, amended, lost or deleted, or contain viruses.

5 9

[election][nova] PTL Candidacy for Wallaby
by Balázs Gibizer 23 Sep '20

23 Sep '20

Hi, I would like to continue serving as a Nova PTL in the Wallaby cycle. In Victoria I helped keeping Nova alive and kicking: * The team merged 56% (9/16) of the blueprints we approved for Victoria. I think the renewed runway process helped making that achievement happen. * We was also managed to reduce Nova's non triaged bug backlog from more than 100 to less than 10. * We had a productive virtual PTG and the organization of the second PTG is already underway. I intend to continue what I have started. Cheers, gibi

1 0

[largescale-sig] Next meeting: September 23, 8utc
by Thierry Carrez 23 Sep '20

23 Sep '20

Hi everyone, Our next meeting will be a EU-APAC-friendly meeting, this Wednesday, September 23 at 8 UTC[1] in the #openstack-meeting-3 channel on IRC: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200923T08 Feel free to add topics to our agenda at: https://etherpad.openstack.org/p/large-scale-sig-meeting A reminder of the TODOs we had from last meeting, in case you have time to make progress on them: - all to describe briefly how you solved metrics/billing in your deployment in https://etherpad.openstack.org/p/large-scale-sig-documentation - ttx to look into a basic test framework for oslo.metrics - masahito to push latest patches to oslo.metrics - amorin to see if oslo.metrics could be tested at OVH - ttx to file Scaling Stories forum session, with amorin and someone from penick's team to help get it off the ground Talk to you all later, -- Thierry Carrez

1 1

[Kuryr] Stepping down as PTL
by Michał Dulko 23 Sep '20

23 Sep '20

Hi, Given that it's considered healthy to have rotation in the PTL role, after serving 2.5 cycle as Kuryr PTL, I won't be a candidating in Wallaby cycle. I'm not going anywhere and I will continue to work on Kuryr projects. Thanks, Michał

2 1

[kolla] Kolla klub meeting
by Mark Goddard 23 Sep '20

23 Sep '20

Hi, Tomorrow (Thursday) sees the return of the Kolla Klub! As usual, the meeting will be at 15:00 UTC. Lets kick off with the following topics: * Quick upstream update * Improving engagement with the community in non EU/US timezones * Operator feedback Look forward to seeing you there. https://docs.google.com/document/d/1EwQs2GXF-EvJZamEx9vQAOSDB5tCjsDCJyHQN5_… Thanks, Mark

1 0

[kolla] Ussuri -source images now use stable branches tarballs
by Michał Nasiadka 23 Sep '20

23 Sep '20

Hello, Since [1] was merged - Kolla source type images are using stable branch tarballs for OpenStack projects - compared to latest point releases - as previously. There are some projects though, that kolla-build uses point releases for those, the list can be found in version-check tool source [2]. Users that want to build source images using latest point releases - can run tools/version-check.py with --versioned-releases option (-v) - and it will adapt sources list accordingly. [1]: https://review.opendev.org/#/c/750297/ [2]: https://opendev.org/openstack/kolla/src/branch/master/tools/version-check.p… -- Michał Nasiadka mnasiadka(a)gmail.com

1 0

[storlets] Wallaby PTG planning
by Takashi Kajinami 22 Sep '20

22 Sep '20

Hello, After discussion in IRC I booked a slot for Storlets project in the Wallaby vPTG. I created a planning etherpad[1] so please put your name/nick if you are interested to join , and also put any topics you want to discuss there. [1] https://etherpad.opendev.org/p/storlets-ptg-wallaby Currently we have a slot from 13:00 UTC booked, but if we don't see attendance from EMEA/NA, we might reschedule it to "earlier" slots since current active cores are based in APAC. Please let me know if you have any questions. Thank you Takashi

1 1

[all][elections][ptl][tc] Combined PTL/TC Nominations Kickoff
by Jeremy Stanley 22 Sep '20

22 Sep '20

Nominations for OpenStack PTLs (Project Team Leads) and TC (Technical Committee) positions (4 positions) are now open and will remain open until Sep 29, 2020 23:45 UTC. All nominations must be submitted as a text file to the openstack/election repository as explained at https://governance.openstack.org/election/#how-to-submit-a-candidacy Please make sure to follow the candidacy file naming convention: candidates/wallaby/<Project_Name or "TC">/<email_address> (for example, "candidates/wallaby/TC/stacker(a)example.org"). The name of the file should match an email address for your current OpenStack Foundation Individual Membership. Take this opportunity to ensure that your OSF member profile contains current information: https://www.openstack.org/profile/ Any OpenStack Foundation Individual Member can propose their candidacy for an available, directly-elected seat on the Technical Committee. In order to be an eligible candidate for PTL you must be an OpenStack Foundation Individual Member. PTL candidates must also have contributed to the corresponding team during the Ussuri to Victoria timeframe, Sep 27, 2019 00:00 UTC - Sep 29, 2020 00:00 UTC. Your Gerrit account must also have a verified email address matching the one used in your candidacy filename. Both PTL and TC elections will be held from Oct 06, 2020 23:45 UTC through to Oct 13, 2020 23:45 UTC. The electorate for the TC election are the OpenStack Foundation Individual Members who have a code contribution to one of the official teams over the Ussuri to Victoria timeframe, Sep 27, 2019 00:00 UTC - Sep 29, 2020 00:00 UTC, as well as any Extra ATCs who are acknowledged by the TC. The electorate for a PTL election are the OpenStack Foundation Individual Members who have a code contribution over the Ussuri to Victoria timeframe, Sep 27, 2019 00:00 UTC - Sep 29, 2020 00:00 UTC, in a deliverable repository maintained by the team which the PTL would lead, as well as the Extra ATCs who are acknowledged by the TC for that specific team. The list of project teams can be found at https://governance.openstack.org/tc/reference/projects/ and their individual team pages include lists of corresponding Extra ATCs. Please find below the timeline: nomination starts @ Sep 22, 2020 23:45 UTC nomination ends @ Sep 29, 2020 23:45 UTC campaigning starts @ Sep 29, 2020 23:45 UTC campaigning ends @ Oct 06, 2020 23:45 UTC elections start @ Oct 06, 2020 23:45 UTC elections end @ Oct 13, 2020 23:45 UTC Shortly after election officials approve candidates, they will be listed on the https://governance.openstack.org/election/ page. The electorate is requested to confirm their email addresses in Gerrit prior to 2020-09-29 00:00:00+00:00, so that the emailed ballots are sent to the correct email address. This email address should match one which was provided in your foundation member profile as well. Gerrit account information and OSF member profiles can be updated at https://review.openstack.org/#/settings/contact and https://www.openstack.org/profile/ accordingly. If you have any questions please be sure to either ask them on the mailing list or to the elections officials: https://governance.openstack.org/election/#election-officials -- Jeremy Stanley on behalf of the OpenStack Technical Election Officials

1 0

[all][elections][tc] Stepping down from the TC
by Nate Johnston 22 Sep '20

22 Sep '20

All, I have decided not to run for reelection to the TC. Although I remain a part of the OpenStack community my responsibilities have shifted away from engineering, and I strongly believe that the TC should be composed of people who are actively creating or operating OpenStack on a daily basis. I am deeply appreciative for all of the support I have recieved from current and former TC members. I also want to take this chance to tell my story a bit, in hopes that it will encourage others to participate more with the TC. A year ago when I joined the TC I did not have a clear idea what to expect. I had observed a few TC meetings and brought one issue to the TC's attention, but since I did not have background on the workstreams in progress, there was a lot that I did not understand or could not contextualize. So what I did was observe, gathering an understanding of the issues and initiatives and raising my hand to participate when I felt like my efforts could make a difference. I was pleasantly surprised how many times I was able to raise my hand and work on things like community goals or proposals like distributed project leadership. The fact that I have not been around since the beginning - my first significant code contributions were merged in the Mitaka cycle - and I did not already know all the names and histories did not matter much. What mattered was a willingness to actively engage, to participate in thoughtful discernment, and when the opportunity presented itself to put in the work. I feel like I made a difference. And if you don't feel the calling to join the TC, that is fine too. Be a part of the process - join the meetings, discuss the issues that cut across projects, and have your voice heard. If you are a part of creting or using OpenStack then you are a part of the TC's constituency and the meetings are to serve you. You don't have to be a member of the TC to participate in the process. Thanks so much, Nate Johnston

7 6

Re: Ussuri CentOS 8 add mptsas driver to introspection initramfs
by Oliver Weinmann 22 Sep '20

22 Sep '20

Hi, thanks a lot. That did the trick. Now it loads the module automatically. I even added another driver and it works like a charm. :) Best Regards, Oliver Am 15. September 2020 um 0:19 schrieb Donny Davis <donny(a)fortnebula.com>: On Fri, Sep 11, 2020 at 3:25 PM Oliver Weinmann <oliver.weinmann(a)icloud.com> wrote: Hi, I already asked this question on serverfault. But I guess here is a better place. I have a very ancient hardware with a MPTSAS controller. I use this for TripleO deployment testing. With the release of Ussuri which is running CentOS8, I can no longer provision my overcloud nodes as the MPTSAS driver has been removed in CentOS8: https://www.reddit.com/r/CentOS/comments/d93unk/centos8_and_removal_mpt2sas… I managed to include the driver provided from ELrepo in the introspection image but It is not loaded automatically: All commands are run as user "stack". Extract the introspection image: cd ~ mkdir imagesnew cd imagesnew tar xvf ../ironic-python-agent.tar mkdir ~/ipa-tmp cd ~/ipa-tmp /usr/lib/dracut/skipcpio ~/imagesnew/ironic-python-agent.initramfs | zcat | cpio -ivd | pax -r Extract the contents of the mptsas driver rpm: rpm2cpio ~/kmod-mptsas-3.04.20-3.el8_2.elrepo.x86_64.rpm | pax -r Put the kernel module in the right places. To figure out where the module has to reside I installed the rpm on a already deployed node and used find to locate it. xz -c ./usr/lib/modules/4.18.0-193.el8.x86_64/extra/mptsas/mptsas.ko > ./usr/lib/modules/4.18.0-193.6.3.el8_2.x86_64/kernel/drivers/message/fusion/mptsas.ko.xz mkdir ./usr/lib/modules/4.18.0-193.6.3.el8_2.x86_64/weak-updates/mptsas sudo ln -sf /lib/modules/4.18.0-193.el8.x86_64/extra/mptsas/mptsas.ko lib/modules/4.18.0-193.6.3.el8_2.x86_64/weak-updates/mptsas.ko sudo chown root . -R find . 2>/dev/null | sudo cpio --quiet -c -o | gzip -8 > ~/images/ironic-python-agent.initramfs Upload the new image cd ~/images openstack overcloud image upload --update-existing --image-path /home/stack/images/ Now when I start the introspection and ssh into the host I see no disks: [root@localhost ~]# fdisk -l [root@localhost ~]# lsmod | grep mptsas Once i manually load the driver, I can see the disks: [root@localhost ~]# modprobe mptsas [root@localhost ~]# lsmod | grep mptsas mptsas 69632 0 mptscsih 45056 1 mptsas mptbase 98304 2 mptsas,mptscsih scsi_transport_sas 45056 1 mptsas [root@localhost ~]# fdisk -l Disk /dev/sda: 67.1 GiB, 71999422464 bytes, 140623872 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes But how can I make it so that it will automatically load on boot? Best Regards, Oliver I guess you could try using modules-load to load the module at boot. > sudo ln -sf /lib/modules/4.18.0-193.el8.x86_64/extra/mptsas/mptsas.ko lib/modules/4.18.0-193.6.3.el8_2.x86_64/weak-updates/mptsas.ko echo "mptsas" > ./etc/modules-load.d/mptsas.conf > sudo chown root . -R Also I would have a look see at these docs to build an image using ipa builder https://docs.openstack.org/ironic-python-agent-builder/latest/ -- ~/DonnyD C: 805 814 6800 "No mission too difficult. No sacrifice too great. Duty First"

1 0

Re: Ussuri CentOS 8 add mptsas driver to introspection initramfs
by Oliver Weinmann 22 Sep '20

22 Sep '20

Hi, thanks a lot. That did the trick. Now it loads the module automatically. I even added another driver and it works like a charm. :) Best Regards, Oliver Am 15. September 2020 um 0:19 schrieb Donny Davis <donny(a)fortnebula.com>: On Fri, Sep 11, 2020 at 3:25 PM Oliver Weinmann <oliver.weinmann(a)icloud.com> wrote: Hi, I already asked this question on serverfault. But I guess here is a better place. I have a very ancient hardware with a MPTSAS controller. I use this for TripleO deployment testing. With the release of Ussuri which is running CentOS8, I can no longer provision my overcloud nodes as the MPTSAS driver has been removed in CentOS8: https://www.reddit.com/r/CentOS/comments/d93unk/centos8_and_removal_mpt2sas… I managed to include the driver provided from ELrepo in the introspection image but It is not loaded automatically: All commands are run as user "stack". Extract the introspection image: cd ~ mkdir imagesnew cd imagesnew tar xvf ../ironic-python-agent.tar mkdir ~/ipa-tmp cd ~/ipa-tmp /usr/lib/dracut/skipcpio ~/imagesnew/ironic-python-agent.initramfs | zcat | cpio -ivd | pax -r Extract the contents of the mptsas driver rpm: rpm2cpio ~/kmod-mptsas-3.04.20-3.el8_2.elrepo.x86_64.rpm | pax -r Put the kernel module in the right places. To figure out where the module has to reside I installed the rpm on a already deployed node and used find to locate it. xz -c ./usr/lib/modules/4.18.0-193.el8.x86_64/extra/mptsas/mptsas.ko > ./usr/lib/modules/4.18.0-193.6.3.el8_2.x86_64/kernel/drivers/message/fusion/mptsas.ko.xz mkdir ./usr/lib/modules/4.18.0-193.6.3.el8_2.x86_64/weak-updates/mptsas sudo ln -sf /lib/modules/4.18.0-193.el8.x86_64/extra/mptsas/mptsas.ko lib/modules/4.18.0-193.6.3.el8_2.x86_64/weak-updates/mptsas.ko sudo chown root . -R find . 2>/dev/null | sudo cpio --quiet -c -o | gzip -8 > ~/images/ironic-python-agent.initramfs Upload the new image cd ~/images openstack overcloud image upload --update-existing --image-path /home/stack/images/ Now when I start the introspection and ssh into the host I see no disks: [root@localhost ~]# fdisk -l [root@localhost ~]# lsmod | grep mptsas Once i manually load the driver, I can see the disks: [root@localhost ~]# modprobe mptsas [root@localhost ~]# lsmod | grep mptsas mptsas 69632 0 mptscsih 45056 1 mptsas mptbase 98304 2 mptsas,mptscsih scsi_transport_sas 45056 1 mptsas [root@localhost ~]# fdisk -l Disk /dev/sda: 67.1 GiB, 71999422464 bytes, 140623872 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes But how can I make it so that it will automatically load on boot? Best Regards, Oliver I guess you could try using modules-load to load the module at boot. > sudo ln -sf /lib/modules/4.18.0-193.el8.x86_64/extra/mptsas/mptsas.ko lib/modules/4.18.0-193.6.3.el8_2.x86_64/weak-updates/mptsas.ko echo "mptsas" > ./etc/modules-load.d/mptsas.conf > sudo chown root . -R Also I would have a look see at these docs to build an image using ipa builder https://docs.openstack.org/ironic-python-agent-builder/latest/ -- ~/DonnyD C: 805 814 6800 "No mission too difficult. No sacrifice too great. Duty First"

1 0

[openstack][cinder] volume_copy_bps_limit
by Ignazio Cassano 22 Sep '20

22 Sep '20

Hello stackers, I am using cinder netapp nfs driver and I have vm performances problems during the backup of volumes. My backup tool make snapshots of volumes, then, on compute notes, it use virt-convert for creating a volume backup on another nfs backend using a different vlan. But during the virt-convert a lot of read are done on netapp and my virtual machines become very slow. I am asking if volume_copy_bps_limit can help me to mitigate. Please, anyone could help me ? Ignazio

2 2

[Neutron][QoS] Meeting cancelled today
by Rodolfo Alonso Hernandez 22 Sep '20

22 Sep '20

Hello: Due to the lack of agenda, the Neutron QoS meeting will be cancelled today (22/9/2020). Regards.

1 0

[manila][FFE] Request for "User messages panel"
by Victoria Martínez de la Cruz 21 Sep '20

21 Sep '20

Hi, I would like to ask for an FFE for the RFE "User messages panel" [0] This feature adds support for manila's user messages API to the user interface. It's implemented by this single patch [1] that already has reviews. Thanks, Victoria [0] https://blueprints.launchpad.net/manila-ui/+spec/ui-user-messages [1] https://review.opendev.org/#/c/742550/

2 1

[ops][neutron]: Anyone using Calico with neutron in production?
by Imtiaz Chowdhury 21 Sep '20

21 Sep '20

Hi all, I have some Calico related questions and am wondering if any operators in this forum have experience in running Calico with OpenStack in production environment. Thanks and regards, Imtiaz

1 0

[nova] update field cpu_info.features value
by Alexander Usov 21 Sep '20

21 Sep '20

Hi guys, Several servers in the cluster have an older version of Intel microcode. I updated one of the servers and rebooted it. After reboot: root@xxx3:~# cat /proc/cpuinfo | grep flags | tail -1 flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm rdt_a rdseed adx smap intel_pt xsaveopt cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts flush_l1d root@xxx3:~# cat /proc/cpuinfo | grep micro | tail -1 microcode : 0xb000038 But the value on the controller didn't update: ~$ nova hypervisor-show 99 | grep ssbd xxx@admin:~$ I updated the value in the database, but it was immediately reverted If the way to update cpu_info.features value without deleting and adding the hypervisor? Nova version: 2:16.1.0 Thanks

2 1

[all] Forum Schedule is now LIVE!
by Kendall Nelson 21 Sep '20

21 Sep '20

Hello Everyone! The forum schedule is now live: https://www.openstack.org/summit/2020/summit-schedule/global-search?t=forum Please let myself or Jimmy McArthur know as soon as possible if you see any conflicts. Speakers will be contacted shortly (if not already) with more details about the event and your sessions. Thanks! -Kendall Nelson (diablo_rojo)

1 0

[tc] weekly update
by Mohammed Naser 21 Sep '20

21 Sep '20

Hi everyone, Here's an update for what happened in the OpenStack TC this week. You can get more information by checking for changes in openstack/governance repository. # Patches ## Open Reviews - Retire devstack-plugin-pika project https://review.opendev.org/748730 - Clarify impact on releases for SIGs https://review.opendev.org/752699 - Define TC-approved release in a resolution https://review.opendev.org/752256 - Add assert:supports-standalone https://review.opendev.org/722399 - Add election schedule exceptions in charter https://review.opendev.org/751941 - Remove tc:approved-release tag https://review.opendev.org/749363 ## Project Updates - Add openstack/osops to Ops Docs and Tooling SIG https://review.opendev.org/749835 - Add python-dracclient to be owned by Hardware Vendor SIG https://review.opendev.org/745564 - Retire the devstack-plugin-zmq project https://review.opendev.org/748731 - Migrate rpm-packaging to a SIG https://review.opendev.org/752661 ## General Changes - Reinstate weekly meetings https://review.opendev.org/749279 - Resolution to define distributed leadership for projects https://review.opendev.org/744995 - Add exception for Sept 2020 term election https://review.opendev.org/751936 # Other Reminders - PTG Brainstorming: https://etherpad.opendev.org/p/tc-wallaby-ptg Thanks for reading! Mohammed & Kendall -- Mohammed Naser VEXXHOST, Inc.

1 0

[tripleo][ansible-ceph[ussuri][rdo][centos8] fails on ansible-ceph execution.
by Ruslanas Gžibovskis 21 Sep '20

21 Sep '20

Hi all, using tripleo 13.4.0-1.el8 and ceph-ansible 4.0.25-1.el8 on CentOS8 from @centos-openstack-ussuri repo. but get [1] error. I thought it was due to not found python exec, but I saw later, when added verbosity 4, that it is able to find python3. It looks like output in paste.openstack.org is too short, not sure what was an issue, but here is a second place [2] for same full output [1] http://paste.openstack.org/show/i2XpSBiSVjuL69Ahm1sl/ [2] https://proxy.qwq.lt/ceph-ansible.html -- Ruslanas Gžibovskis +370 6030 7030

2 12

Re: Re: [openstack-ansible] OpenStack Ansible deployment fails due to lxc containers not having network connection
by Oliver Wenz 21 Sep '20

21 Sep '20

Hi Jonathan, thank you for your reply! I probably should have specified that I already changed some default values in /etc/ansible/roles/lxc_hosts/defaults/main.yml to prevent a conflict with my storage network. Here's the part that I changed: ``` lxc_net_address: 10.255.255.1 lxc_net_netmask: 255.255.255.0 lxc_net_dhcp_range: 10.255.255.2,10.255.255.253 ``` Could there be some other reference to the original default address range which causes the error? I'm also confused about dnsmasq: Running 'apt-get install dnsmasq' I discovered that it wasn't installed on the infra host yet (though installing it also didn't solve the problem). Moreover, I couldn't find dnsmasq in the prerequisites in the OSA deployment guide. Kind regards, Oliver On 03/09/2020 18:38, openstack-discuss-request(a)lists.openstack.org wrote: > Message: 1 > Date: Thu, 3 Sep 2020 16:51:51 +0100 > From: Jonathan Rosser <jonathan.rosser(a)rd.bbc.co.uk> > To: openstack-discuss(a)lists.openstack.org > Subject: Re: [openstack-ansible] OpenStack Ansible deployment fails > due to lxc containers not having network connection > Message-ID: <e6746294-ada6-0f29-cdfb-59538396a0e0(a)rd.bbc.co.uk> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi Oliver, > > The default route would normally be via eth0 in the container, which I > suspect has some issue. > > This is given an address by dnsmasq/dhcp on the host and attached to > lxcbr0. This is where I would start to look. I am straight seeing that > the default address range used for eth0 is in conflict with your storage > network, so perhaps this is also something to look at. See > https://github.com/openstack/openstack-ansible-lxc_hosts/blob/master/defaul… > <https://github.com/openstack/openstack-ansible-lxc_hosts/blob/master/defaul…> > > You join us on irc at #openstack-ansible for some 'real-time' assistance > if necessary. > > Regards, > Jonathan. > > On 03/09/2020 16:18, Oliver Wenz wrote: >> I'm trying to deploy OpenStack Ansible. When running the first playbook >> ```openstack-ansible setup-hosts.yml```, there are errors for all >> containers during the task ```[openstack_hosts : Remove the blacklisted >> packages]``` (see below) and the playbook fails. >> >> ``` >> fatal: [infra1_repo_container-1f1565cd]: FAILED! => {"changed": false, >> "cmd": "apt-get update", "msg": "E: The repository >> 'http://ubuntu.mirror.lrz.de/ubuntu bionic Release' no longer has a >> Release file. >> E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-updates >> Release' no longer has a Release file. >> E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-backports >> Release' no longer has a Release file. >> E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-security >> Release' no longer has a Release file.", "rc": 100, "stderr": "E: The >> repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic Release' no longer >> has a Release file. >> E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-updates >> Release' no longer has a Release file. >> E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-backports >> Release' no longer has a Release file. >> E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-security >> Release' no longer has a Release file. >> ", "stderr_lines": ["E: The repository >> 'http://ubuntu.mirror.lrz.de/ubuntu bionic Release' no longer has a >> Release file.", "E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu >> bionic-updates Release' no longer has a Release file.", "E: The >> repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-backports Release' >> no longer has a Release file.", "E: The repository >> 'http://ubuntu.mirror.lrz.de/ubuntu bionic-security Release' no longer >> has a Release file."], "stdout": "Ign:1 >> http://ubuntu.mirror.lrz.de/ubuntu bionic InRelease >> Ign:2 http://ubuntu.mirror.lrz.de/ubuntu bionic-updates InRelease >> Ign:3 http://ubuntu.mirror.lrz.de/ubuntu bionic-backports InRelease >> Ign:4 http://ubuntu.mirror.lrz.de/ubuntu bionic-security InRelease >> Err:5 http://ubuntu.mirror.lrz.de/ubuntu bionic Release >> Cannot initiate the connection to 192.168.100.6:8000 (192.168.100.6). >> - connect (101: Network is unreachable) >> Err:6 http://ubuntu.mirror.lrz.de/ubuntu bionic-updates Release >> Cannot initiate the connection to 192.168.100.6:8000 (192.168.100.6). >> - connect (101: Network is unreachable) >> Err:7 http://ubuntu.mirror.lrz.de/ubuntu bionic-backports Release >> Cannot initiate the connection to 192.168.100.6:8000 (192.168.100.6). >> - connect (101: Network is unreachable) >> Err:8 http://ubuntu.mirror.lrz.de/ubuntu bionic-security Release >> Cannot initiate the connection to 192.168.100.6:8000 (192.168.100.6). >> - connect (101: Network is unreachable) >> Reading package lists... >> ", "stdout_lines": ["Ign:1 http://ubuntu.mirror.lrz.de/ubuntu bionic >> InRelease", "Ign:2 http://ubuntu.mirror.lrz.de/ubuntu bionic-updates >> InRelease", "Ign:3 http://ubuntu.mirror.lrz.de/ubuntu bionic-backports >> InRelease", "Ign:4 http://ubuntu.mirror.lrz.de/ubuntu bionic-security >> InRelease", "Err:5 http://ubuntu.mirror.lrz.de/ubuntu bionic Release", >> " Cannot initiate the connection to 192.168.100.6:8000 (192.168.100.6). >> - connect (101: Network is unreachable)", "Err:6 >> http://ubuntu.mirror.lrz.de/ubuntu bionic-updates Release", " Cannot >> initiate the connection to 192.168.100.6:8000 (192.168.100.6). - connect >> (101: Network is unreachable)", "Err:7 >> http://ubuntu.mirror.lrz.de/ubuntu bionic-backports Release", " Cannot >> initiate the connection to 192.168.100.6:8000 (192.168.100.6). - connect >> (101: Network is unreachable)", "Err:8 >> http://ubuntu.mirror.lrz.de/ubuntu bionic-security Release", " Cannot >> initiate the connection to 192.168.100.6:8000 (192.168.100.6). - connect >> (101: Network is unreachable)", "Reading package lists..."]} >> >> ``` >> >> When I attach to any container and run ```ping 192.168.100.6``` (local >> DNS), I get the same error (```connect: Network is unreachable```). >> However, when I specify an interface by running ```ping -I eth1 >> 192.168.100.6``` there is a successful connection. >> Running ```ip r``` on the infra_cinder container yields: >> ``` >> 10.0.3.0/24 dev eth2 proto kernel scope link src 10.0.3.5 >> 192.168.110.0/24 dev eth1 proto kernel scope link src 192.168.110.232 >> ``` >> so there seems to be no default route which is why the connection fails >> (similar for the other infra containers). Shouldn't OSA automatically >> configure this? I didn't find anything regarding a default route on >> containers in the Docs. >> >> Here's my openstack_user_config.yml: >> >> ``` >> cidr_networks: >> container: 192.168.110.0/24 >> tunnel: 192.168.32.0/24 >> storage: 10.0.3.0/24 >> >> used_ips: >> - "192.168.110.1,192.168.110.2" >> - "192.168.110.111" >> - "192.168.110.115" >> - "192.168.110.117,192.168.110.118" >> - "192.168.110.131,192.168.110.140" >> - "192.168.110.201,192.168.110.207" >> - "192.168.32.1,192.168.32.2" >> - "192.168.32.201,192.168.32.207" >> - "10.0.3.1" >> - "10.0.3.11,10.0.3.14" >> - "10.0.3.21,10.0.3.24" >> - "10.0.3.31,10.0.3.42" >> - "10.0.3.201,10.0.3.207" >> >> global_overrides: >> # The internal and external VIP should be different IPs, however they >> # do not need to be on separate networks. >> external_lb_vip_address: 192.168.100.168 >> internal_lb_vip_address: 192.168.110.201 >> management_bridge: "br-mgmt" >> provider_networks: >> - network: >> container_bridge: "br-mgmt" >> container_type: "veth" >> container_interface: "eth1" >> ip_from_q: "container" >> type: "raw" >> group_binds: >> - all_containers >> - hosts >> is_container_address: true >> - network: >> container_bridge: "br-vxlan" >> container_type: "veth" >> container_interface: "eth10" >> ip_from_q: "tunnel" >> type: "vxlan" >> range: "1:1000" >> net_name: "vxlan" >> group_binds: >> - neutron_linuxbridge_agent >> - network: >> container_bridge: "br-ext1" >> container_type: "veth" >> container_interface: "eth12" >> host_bind_override: "eth12" >> type: "flat" >> net_name: "ext_net" >> group_binds: >> - neutron_linuxbridge_agent >> - network: >> container_bridge: "br-storage" >> container_type: "veth" >> container_interface: "eth2" >> ip_from_q: "storage" >> type: "raw" >> group_binds: >> - glance_api >> - cinder_api >> - cinder_volume >> - nova_compute >> - swift-proxy >> >> ### >> ### Infrastructure >> ### >> >> # galera, memcache, rabbitmq, utility >> shared-infra_hosts: >> infra1: >> ip: 192.168.110.201 >> >> # repository (apt cache, python packages, etc) >> repo-infra_hosts: >> infra1: >> ip: 192.168.110.201 >> >> # load balancer >> haproxy_hosts: >> infra1: >> ip: 192.168.110.201 >> >> ### >> ### OpenStack >> ### >> >> os-infra_hosts: >> infra1: >> ip: 192.168.110.201 >> >> identity_hosts: >> infra1: >> ip: 192.168.110.201 >> >> network_hosts: >> infra1: >> ip: 192.168.110.201 >> >> compute_hosts: >> compute1: >> ip: 192.168.110.204 >> compute2: >> ip: 192.168.110.205 >> compute3: >> ip: 192.168.110.206 >> compute4: >> ip: 192.168.110.207 >> >> storage-infra_hosts: >> infra1: >> ip: 192.168.110.201 >> >> storage_hosts: >> lvm-storage1: >> ip: 192.168.110.202 >> container_vars: >> cinder_backends: >> lvm: >> volume_backend_name: LVM_iSCSI >> volume_driver: cinder.volume.drivers.lvm.LVMVolumeDriver >> volume_group: cinder_volumes >> iscsi_ip_address: "{{ cinder_storage_address }}" >> limit_container_types: cinder_volume >> >> ``` >> >> I also asked this question on the server fault stackexchange: >> https://serverfault.com/questions/1032573/openstack-ansible-deployment-fail… >> >> >> Kind regards, >> Oliver >> >> >> >

2 1

Openstack version 18.04
by ops＠clustspace.com 21 Sep '20

21 Sep '20

Hello, We are decided to change Apache CloudStack to OpenStack. Trying to install, but only Stein....As you can see we have repositories ussuri root@ops:~# apt update Hit:1 http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-updates/ussuri InRelease Hit:2 http://us.archive.ubuntu.com/ubuntu bionic InRelease Hit:3 http://security.ubuntu.com/ubuntu bionic-security InRelease Hit:4 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease Hit:5 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. root@ops:~# But after installation we got only Stein root@ops:~# openstack --version openstack 5.2.0 Do'es anyone have idea why we can install only Stein?

3 2

[tripleo][ansible-ceph][ussuri]ceph-ansiible fails at chown stack: /tmp/ceph_ansible_tmp on distributed compute HCI node
by Ruslanas Gžibovskis 21 Sep '20

21 Sep '20

Hi all, using tripleo 13.4.0-1.el8 and ceph-ansible 4.0.25-1.el8 on CentOS8 from @centos-openstack-ussuri repo. I get error [1]. When ansi playbook tries to chown to stack user dir: /tmp/ceph_ansible_tmp, but not able to find user stack. As I understand the deployment process, should it have tripleo-admin user? Also executed ansible.sh file with ansible-playbook -vvvv [2] it also has /home/stack/config-download/v3/ceph-ansible/create_ceph_ansible_remote_tmp.log I see in default file, it has the correct things set: owner: "{{ ansible_user | default('tripleo-admin', true) }}" In undercloud.conf I do not have deployment user set, that option is commented out. I have not set any in overcloud config files... [1] http://paste.openstack.org/show/798126/ [2] http://paste.openstack.org/show/798127 -- Ruslanas Gžibovskis +370 6030 7030

2 3

[tc] weekly meeting time
by Mohammed Naser 21 Sep '20

21 Sep '20

Hi folks: Given that we've landed the change to start having weekly meetings again, it's time to start picking a time: https://doodle.com/poll/xw2wiebm2ayqxvki A few people also mentioned they wouldn't mind taking the current office hours time towards that, I guess we can try and come to an agreement if we want to do that here (or simply by voting that time on the Doodle). Thanks, Mohammed -- Mohammed Naser VEXXHOST, Inc.

2 2

[tc][heat] PTL not available next week
by Rico Lin 19 Sep '20

19 Sep '20

Dear all Due to some personal matters, I'm not available next week 9/21-9/25. for releases, I already propose the patch [1]. And I'm fine with any renew on the patch as long as there's no new feature included (will try to keep update [1] too). [1] https://review.opendev.org/#/c/752809/ -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

1 0

[Neutron] Bug Deputy Report (Sep 14 - Sep 19)
by Hongbin Lu 19 Sep '20

19 Sep '20

Hi all, Below is the bug deputy report: High: * https://bugs.launchpad.net/neutron/+bug/1895671 [OVN] test_add_interface_in_use fail with OVN Midium: * https://bugs.launchpad.net/neutron/+bug/1895933 Admin user can do anything without the control of policy.json * https://bugs.launchpad.net/neutron/+bug/1895950 keepalived can't perform failover if the l3 agent is down * https://bugs.launchpad.net/neutron/+bug/1895972 IPv6 prefix delegation for OVN routers Low: * https://bugs.launchpad.net/neutron/+bug/1896217 [OVS] When "explicitly_egress_direct" is enabled, egress flows are not deleted when the port is removed Undecided: * https://bugs.launchpad.net/neutron/+bug/1895677 [OVS][FW] In some cases, OVS FW tries to set a OF rule when ofport = -1 * https://bugs.launchpad.net/neutron/+bug/1896203 TypeError: Cannot look up record by empty string in check_for_igmp_snoop_support task * https://bugs.launchpad.net/neutron/+bug/1896205 AttributeError: 'NoneType' object has no attribute 'db_find_rows' during neutron-server startup * https://bugs.launchpad.net/neutron/+bug/1896226 The vnics are disappearing in the vm Invalid: * https://bugs.launchpad.net/neutron/+bug/1895636 'NoneType' object has no attribute 'address_scope_id'

1 0

[rpm-packaging][packaging][sigs] Moving to a packaging SIG
by Jean-Philippe Evrard 18 Sep '20

18 Sep '20

Hello folks, It's maybe a little late, as the elections process already have started, but I think it's worth re-opening the conversation about migrating the rpm-packaging project to a SIG. Last time we tried this, we were stopped by bureaucracy and technical details (IIRC?) which shouldn't be there anymore. I don't see a reason why this team couldn't move to a SIG now, which would be a lightweight governance model for you. You would keep your repos, and can still propose releases (if I am not mistaken). Things shouldn't change much. You can decide to change/add chair people when you want, and don't have to sign off a PTL for 6 months at elections, which was the most concerning matter for your projects IIRC (which lead to missed elections deadlines in the past). I hope that this SIG can evolve in the future, to group not only RPM packaging, but also other packaging mechanism that want to follow under that new banner. That's why I proposed the SIG to be named "Packaging" instead. It's up to the community now to gather around the same banner :) So if you're interested with this change, please vote on here: [1] [2]. Regards, Jean-Philippe Evrard (evrardjp) [1]: https://review.opendev.org/752659 [2]: https://review.opendev.org/752661

4 9

[tripleo] patch abandonment, cleaning up gerrit
by Wesley Hayutin 18 Sep '20

18 Sep '20

Greetings, FYI folks I'm going to tear through our projects today and abandon patches older than 365 days. Please read through our policy [1] if you have any questions or concerns. It will be nice to have a little clean up before the next release and PTL take over :) Thanks [1] https://specs.openstack.org/openstack/tripleo-specs/specs/policy/patch-aban…

1 1

[TC][nova] Failing device detachments on Focal
by Balázs Gibizer 18 Sep '20

18 Sep '20

Hi, I want to raise a potential conflict between the fact that OpenStack Victoria officially supports Ubuntu Focal[3] and a high severity regression in Nova [1] caused by a qemu bug [2] in the qemu version that is shipped with Focal. The Nova team documented[4] it as a limitation without a known workaround in Nova. Also as far as I know Canonical does not support downgrading the qemu version so I don't see a viable workaround on Focal side either. Is the Nova reno[4] enough from the TC perspective to go forward with the switch to Focal and with the Victoria release? cheers, gibi [1] https://bugs.launchpad.net/nova/+bug/1882521 [2] https://bugs.launchpad.net/qemu/+bug/1894804 [3] https://governance.openstack.org/tc/reference/runtimes/victoria.html [4] https://review.opendev.org/#/c/752654

5 6

[manila] Bug squash event coming up next Monday (September 21st)
by Victoria Martínez de la Cruz 18 Sep '20

18 Sep '20

Hi all, After the success of our doc-a-thon last month (details to come soon in the original thread) we decided to repeat the experience, this time, with code bugs. We are organizing a bugs squash next Monday, September 21st, with the main goal of closing several bugs in preparation for the RC (that we are cutting next week). We will gather on our Freenode channel #openstack-manila at 3pm UTC and we will use this Jitsi bridge [0] to go over a curated list (thanks Vida!) of opened bugs we have here [1] *Your* participation is truly valued, being you an already Manila contributor or if you are interested in contributing and you didn't know how, so looking forward to seeing you there :) Cheers, Victoria [0] https://meetpad.opendev.org/ManilaV-ReleaseBugSquashRC [1] http://ethercalc.openstack.org/26utlmzuk6cc

1 0

[all][qa][ci][kuryr] Default swap size of gate VMs is 1 GB now
by Michał Dulko 18 Sep '20

18 Sep '20

Hi, Last Friday Kuryr team noticed elevated rate of failures of the kuryr- kubernetes gate jobs. Later on we've tracked it down to oom-killer slaying our Amphora instances. We couldn't find a reason why that only started to happen on Friday, until now. So commit [1] reduced default swap size to 1 GB. If your jobs need more memory - you can try overwriting that in your job configs like we do in [2]. I'm posting this to save people from a week of debugging as it wasn't a fun activity. ;) Thanks, Michał [1] https://opendev.org/openstack/openstack-zuul-jobs/commit/45f555fdf036de786b… [2] https://review.opendev.org/#/c/752233/4/.zuul.d/base.yaml@35

1 0

[neutron][ovn] Logical flow scaling (flow explosion in lr_in_arp_resolve)
by Krzysztof Klimonda 18 Sep '20

18 Sep '20

Hi, We're running some tests of ussuri deployment with ovn ML2 driver and seeing some worrying numbers of logical flows generated for our test deployment. As a test, we create 400 routes, 400 private networks and connect each network to its own routers. We also connect each router to an external network. After doing that a dump of logical flows shows almost 800k logical flows, most of them in lr_in_arp_resolve table: --8<--8<--8<-- # cat lflows.txt |grep -v Datapath |cut -d'(' -f 2 | cut -d ')' -f1 |sort | uniq -c |sort -n | tail -10 3264 lr_in_learn_neighbor 3386 ls_out_port_sec_l2 4112 lr_in_admission 4202 ls_in_port_sec_l2 4898 lr_in_lookup_neighbor 4900 lr_in_ip_routing 9144 ls_in_l2_lkup 9160 ls_in_arp_rsp 22136 lr_in_ip_input 671656 lr_in_arp_resolve # --8<--8<--8<-- ovn: 20.06.2 + patch for SNAT IP ARP reply issue openvswitch: 2.13.0 neutron: 16.1.0 I've seen some discussion about similar issue at OVS mailing lists: https://www.mail-archive.com/ovs-discuss@openvswitch.org/msg07014.html - is this relevant to neutron, and not just kubernetes? -- Krzysztof Klimonda kklimonda(a)syntaxhighlighted.com

3 5

[tripleo][ci] collectd-mysql
by Wesley Hayutin 18 Sep '20

18 Sep '20

Greetings, More fun as usual. Error: Problem: cannot install the best candidate for the job - nothing provides libmysqlclient.so.21()(64bit) needed by collectd-mysql-5.11.0-2.el8.x86_64 - nothing provides libmysqlclient.so.21(libmysqlclient_21.0)(64bit) needed by collectd-mysql-5.11.0-2.el8.x86_64 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) https://bugs.launchpad.net/tripleo/+bug/1896178 https://review.rdoproject.org/r/#/c/29472/ 0/

2 1

[release] Release countdown for week R-3 Sept 21 - 25
by Sean McGinnis 18 Sep '20

18 Sep '20

Development Focus ----------------- The Release Candidate (RC) deadline is next Thursday, September 24. Work should be focused on fixing any release-critical bugs. General Information ------------------- All deliverables released under a cycle-with-rc model should have a first release candidate by the end of the week, from which a stable/victoria branch will be cut. This branch will track the victoria release. Once stable/victoria has been created, master will be ready to switch to wallaby development. While master will no longer be feature-frozen, please prioritize any work necessary for completing victoria plans. Release-critical bugfixes will need to be merged in the master branch first, then backported to the stable/victoria branch before a new release candidate can be proposed. Actions ------- Early in the week, the release team will be proposing RC1 patches for all cycle-with-rc projects, using the latest commit from master. If your team is ready to go for cutting RC1, please let us know by leaving a +1 on these patches. If there are still a few more patches needed before RC1, you can -1 the patch and update it later in the week with the new commit hash you would like to use. Remember, stable/victoria branches will be created with this, so you will want to make sure you have what you need included to avoid needing to backport changes from master (which will technically then be wallaby) to this stable branch for any additional RCs before the final release. The release team will also be proposing releases for any deliverable following a cycle-with-intermediary model that has not produced any victoria release so far. Finally, if you haven't submitted any yet, now is a good time to finalize release highlights. Release highlights help shape the messaging around the release and make sure that your work is properly represented. Upcoming Deadlines & Dates -------------------------- RC1 deadline: September 24 (R-3) Final Victoria release: October 14 Open Infra Summit: October 19-23 Wallaby PTG: October 26-30

1 0

[all][goals] Switch legacy Zuul jobs to native - update #4
by Luigi Toscano 17 Sep '20

17 Sep '20

Hi, another round of updates. The list of the remaining legacy jobs is shortening but the Victoria branching will happen next week, so we need to speed up a bit. Status ====== As usual, the etherpad [3] lists the full status and the links to the patches. Here is a more detailed report for each remaining project. cinder ------ The only legacy job left is a bit unusual, but there is a WIP review now. It needs some more work to fix the reporting. designate --------- The patch for only legacy job has been approved, but there is an unrelated issue which requires input from the designate team. heat ------ Only one legacy job left, the heat cores are aware of it. infra ----- Only one devstack-gate job in the os-loganalyze repository, which should be probably retired. There are 2 other legacy jobs, but not devstack-gate, so less urgent. ironic ------ The port of the remaining legacy job is going to be merged soon (even though it's failing, but the legacy job is failing as well). manila ------ There is only one legacy-base job (not devstack-gate), so less urgent, but there is a patch for it. monasca ------- The monasca-transform contains a devstack-gate legacy job, but the repository is almost retired. There are 3 legacy (non devstack-gate) jobs in other repositories. murano ------ There are two legacy jobs left (murano-apps-refstackclient-unittest and murano-dashboard-sanity-check) which require some input from the team. neutron ------- Only two legacy grenade jobs are left and they are being worked on. nova ---- The work is ongoing on the remaining legacy jobs (a new job which will replace a legacy one, and a grenade job)). zaqar ----- Mostly done, it only requires a python-zaqarclient backport to be merged in Victoria. References ========== [1] the goal: https://governance.openstack.org/tc/goals/selected/victoria/native-zuulv3-j… [2] the up-to-date Zuul v3 porting guide: https://docs.openstack.org/project-team-guide/zuulv3.html [3] the etherpad which tracks the current status: https://etherpad.opendev.org/p/goal-victoria-native-zuulv3-migration [4] the previous reports: http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016058.html http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016561.h… http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016892.h… Ciao -- Luigi

1 0

[policy] Wallaby PTG planning
by Ghanshyam Mann 17 Sep '20

17 Sep '20

Hello Everyone, We have booked 2 hrs slot for the policy popup team in the Wallaby vPTG. Time is Monday 23.00-00 UTC and Tuesday 00.-01:00 UTC Tuesday in Havana room (Both are continuous slots). I have created the etherpad to collect the discussion point. Please add the topic you would like to discuss - https://etherpad.opendev.org/p/policy-popup-wallaby-ptg We request more and more projects to participate in this and discuss the various queries or plan to switch to the new policy. -gmann & raildo

1 0

[neutron] Drivers meeting cancelled
by Slawek Kaplonski 17 Sep '20

17 Sep '20

Hi, I know that it's been already a while since we had our last drivers meeting but recently we don't have any new RFEs to discuss and because of that lets cancel it this week too. If You have any ideas or topics which You would like to discuss on the drivers meeting, please add it to the "On Demand" section at [1]. [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers -- Slawek Kaplonski Senior software engineer Red Hat

1 0

[TC] vPTG Details
by Kendall Nelson 17 Sep '20

17 Sep '20

Hello! As you might or might not have seen, I signed up the TC for two chunks of time (based on poll results). The times are: - 15-17 UTC Tuesday October 27th (2 hours; Grizzly Room) - 13-17 UTC Friday October 30 (4 hours; Grizzly Room Hope to see you all there! Also, please add your discussion topics to our brainstorming etherpad[1]! -Kendall Nelson (diablo_rojo) [1] https://etherpad.opendev.org/p/tc-wallaby-ptg

1 0

[Diversity] Diversity & Inclusion WG Meeting 9/21 - Removing Divisive Language
by Amy Marrich 17 Sep '20

17 Sep '20

The Diversity and Inclusion WG will be holding a meeting to continue drafting the OSF's stance on the removal of Divisive Language within the OSF projects. The WG invites members of all OSF projects to participate in this effort and to join us at our next meeting Monday, September 21, at 17:00 UTC which will be held at https://meetpad.opendev.org/osf-diversity-and-inclusion. <https://meetpad.opendev.org/osf-diversity-and-inclusion> Drafts for the stance can be found at https://etherpad.opendev.org/p/divisivelanguage If you have any questions please let me and the team know here, on #openstack-diversity on IRC, or you can email me directly. Thanks, Amy Marrich (spotz)

1 0

[release][heat][karbor][patrole][requirements][swift][tempest][vitrage] Cycle With Intermediary Unreleased Deliverables
by Kendall Nelson 17 Sep '20

17 Sep '20

Hello! Quick reminder that we'll need a release very soon for a number of deliverables following a cycle-with-intermediary release model but which have not done *any* release yet in the Victoria cycle: heat-agents karbor-dashboard karbor patrole requirements swift tempest vitrage-dashboard vitrage Those should be released ASAP, and in all cases before $rc1-deadline, so that we have a release to include in the final $series release. - Kendall Nelson (diablo_rojo)

2 1

[baremetal-sig][ironic] Future work and regular meetings
by Arne Wiebalck 17 Sep '20

17 Sep '20

Dear all, With the release of the bare metal white paper [0] the bare metal SIG has completed its first target and is now ready to tackle new challenges. A number of potential topics the SIG could work on were raised during the recent opendev events. The suggestions are summarised on the bare metal etherpad [1]. To select and organise the future work, we feel that it may be better to start with regular meetings, though: the current idea is once a month, for one hour, on zoom. Based on the experience with the ad-hoc meetings we had so far I have set up a doodle to pick the exact slot: https://doodle.com/poll/3hpypw73455t2g24 If interested, please respond by the end of this week. Equally, if you have additional suggestions for the next focus of the SIG, do not hesitate to add them to [1]. Thanks! Arne [0] https://www.openstack.org/use-cases/bare-metal/how-ironic-delivers-abstract… [1] https://etherpad.opendev.org/p/bare-metal-sig

1 1

[Neutron][FFE] request for QoS policy update for bound ports feature
by Lajos Katona 17 Sep '20

17 Sep '20

Hi, I would like to ask for FFE for the RFE "allow replacing the QoS policy of bound port", [1]. This feature adds the extra step to port update operation to change the allocation in Placement to the min_kbps values of the new QoS policy, if the port has a QoS policy with minimum_bandwidth rule and is bound and used by a server. In neutron there's one open patch: https://review.opendev.org/747774 There's an open bug report for the neutron-lib side: https://bugs.launchpad.net/neutron/+bug/1894825 (placement story: https://storyboard.openstack.org/#!/story/2008111 ) and a fix for that: https://review.opendev.org/750349 [1] https://bugs.launchpad.net/neutron/+bug/1882804 Thanks and Regards, Lajos Katona (lajoskatona)

4 8

[Neutron][python-openstackclient][openstacksdk][FFE] Add source_ip_prefix and destination_ip_prefix to metering label rules
by Rafael Weingärtner 17 Sep '20

17 Sep '20

Hello guys, I would like to ask for FFE for the RFE "Add source_ip_prefix and destination_ip_prefix to metering label rules", [1]. This feature adds source and destination filtering options to Neutron metering label rules. Most of the patches (PRs) relating to this feature have already been reviewed, and are ready to be merged [2]. Moreover, the feature has already been partially merged into Neutron and Neutron-lib. Therefore, it might be interesting to finish the merging process and get the feature into Victoria. [1] https://bugs.launchpad.net/neutron/+bug/1889431 [2] https://review.opendev.org/#/q/topic:bug/1889431+(status:open+OR+status:mer… Thanks and Regards, -- Rafael Weingärtner

2 1

[tripleo] stepping down as PTL
by Wesley Hayutin 17 Sep '20

17 Sep '20

Greetings, Thank you for the opportunity to be the TripleO PTL. This has been a great learning opportunity to work with a pure upstream community, other projects and the OpenStack leadership. Thank you to the TripleO team for your help and dedication in adding features, fixing bugs, and responding to whatever has come our way upstream. Lastly.. Thank you to Alex and Emilien for all the assistance throughout!! Managing the work required here with Covid-19, home schooling is a little much for me at this time, I would like to encourage others to volunteer for the opportunity in Wallaby. 0/

4 3

[qa] Wallaby PTG planning
by Masayuki Igawa 16 Sep '20

16 Sep '20

Hi, We need to start thinking about the next cycle already. As you probably know, next virtual PTG will be held in October 26-30[0]. I prepared an etherpad[1] to discuss and track our topics. So, please add your name if you are going to attend the PTG session. And also, please add your proposals of the topics which you want to discuss during the PTG. I also made a doodle[2] with possible time slots. Please put your best days and hours so that we can try to schedule and book our sessions in the time slots. [0] https://www.openstack.org/ptg/ [1] https://etherpad.opendev.org/p/qa-wallaby-ptg [2] https://doodle.com/poll/qqd7ayz3i4ubnsbb Best Regards, -- Masayuki Igawa Key fingerprint = C27C 2F00 3A2A 999A 903A 753D 290F 53ED C899 BF89

3 5

[Octavia] Please help with deployment of octavia unbound lb port when creating LB
by Bujack, Stefan 16 Sep '20

16 Sep '20

2 2