- openstack-discuss - lists.openstack.org

[tripleo][ci] update - CI jobs failures on RDO and Software Factory Project
by Wesley Hayutin 08 Dec '20

08 Dec '20

forwarded from rdo.... Hi, The CI jobs that are running on Vexxhost should be fine now. Regards, Dan

1 0

[all][qa][kolla][ops][tc] CentOS Project shifts focus to CentOS Stream
by Radosław Piliszek 08 Dec '20

08 Dec '20

TL;DR After 2021 there will be no CentOS 8 point releases. The focus is on CentOS 8 Stream. For more information, please read [1]. As the QA team, we have Stream testing proposed already [2]. We actually had Victoria from Manila ask us about it quite a while ago. Ghanshyam promised to coordinate this topic with the TC. As the Kolla team, we made switch to CentOS 8 Stream a priority of Wallaby and we will likely discuss this option for stable branches which will outlive the 2021 deadline. PS: Don't kill me. I'm just passing the information on. :-) [1] https://lists.centos.org/pipermail/centos-devel/2020-December/075451.html [2] https://review.opendev.org/c/openstack/devstack/+/759122 Kind regards, -yoctozepto

2 2

[tripleo][ci] CI jobs failures on RDO project
by Wesley Hayutin 08 Dec '20

08 Dec '20

FYI ---------- Forwarded message --------- From: Daniel Pawlik <dpawlik(a)redhat.com> Date: Mon, Dec 7, 2020 at 6:13 AM Subject: [rdo-users] CI jobs failures on RDO project To: <users(a)lists.rdoproject.org> Hello, We are facing an outage in our cloud providers. That's why from time to time you can have problems validating CI jobs in RDO project. We are doing our best to fix the issues as soon as possible. Kindly regards, Dan _______________________________________________ users mailing list users(a)lists.rdoproject.org http://lists.rdoproject.org/mailman/listinfo/users To unsubscribe: users-unsubscribe(a)lists.rdoproject.org

2 1

[tc] weekly update
by Mohammed Naser 08 Dec '20

08 Dec '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 - Revive os_monasca https://review.opendev.org/c/openstack/governance/+/765800 - Deprecate openstack-ansible-galera_client role https://review.opendev.org/c/openstack/governance/+/765784 - Clarify impact on releases for SIGs https://review.opendev.org/c/openstack/governance/+/752699 - Remove Searchlight project team https://review.opendev.org/c/openstack/governance/+/764530 - Remove Qinling project team https://review.opendev.org/c/openstack/governance/+/764523 - Add Resolution of TC stance on the OpenStackClient https://review.opendev.org/c/openstack/governance/+/759904 ## General Changes - Remove already done use-builtin-mock from goal https://review.opendev.org/c/openstack/governance/+/764262 - Propose Kendall Nelson for vice chair https://review.opendev.org/c/openstack/governance/+/762014 - Add election schedule exceptions in charter https://review.opendev.org/c/openstack/governance/+/751941 - Generate the TC liaisons assignments https://review.opendev.org/c/openstack/governance/+/763810 - Update example and oslo code usage in JSON->YAML goal https://review.opendev.org/c/openstack/governance/+/764261 - Clarify the requirements for supports-api-interoperability https://review.opendev.org/c/openstack/governance/+/760562 - Remove assert_supports-zero-downtime-upgrade tag https://review.opendev.org/c/openstack/governance/+/761975 - Add assert:supports-standalone https://review.opendev.org/c/openstack/governance/+/722399 ## Project Updates - Add Magpie charm to OpenStack charms https://review.opendev.org/c/openstack/governance/+/762820 ## Other Reminders - [TC] Weekly meeting, December 10 at 1500 UTC. If you would like to add topics for discussion, please go to https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting and fill out your suggestions by Wednesday, December 09, at 2100 UTC. Thanks for reading! Mohammed & Kendall -- Mohammed Naser VEXXHOST, Inc.

1 0

[cinder] reminder: virtual mid-cycle wednesday 1400 utc
by Brian Rosmaita 08 Dec '20

08 Dec '20

The Cinder Wallaby R-18 virtual mid-cycle will be held: DATE: WEDNESDAY 9 DECEMBER 2020 TIME: 1400-1600 UTC LOCATION: https://bluejeans.com/3228528973 The meeting will be recorded. Please add topics to the mid-cycle etherpad: https://etherpad.opendev.org/p/cinder-wallaby-mid-cycles cheers, brian

1 0

[development] Installation of Openstack for development using OVS
by Pavlos Basaras 08 Dec '20

08 Dec '20

Hello, I would like to install openstack for testing/development (not production) with OVS, with a controller node and multiple compute nodes, with the option to use ironic. I have followed the documentation https://docs.openstack.org/install-guide/ and i have a successful installation with linux bridges instead of OVS, with all the features working as mentioned in the tutorial. Any directions in how to have an openstack installation with OVS, e.g., a similar manual? Any advice welcome. all the best Pavlos.

1 0

[neutron] Team meeting - Tuesday 08.12.2020
by Slawek Kaplonski 08 Dec '20

08 Dec '20

Hi, It's just quick reminder that today at 1400 UTC on the #openstack-meeting-3 channel there will be neutron team meeting. Agenda is on [1]. If You have any topics which You would like to discuss, please add it to the "On demand section" in the agenda page. Just after that, at 1500 UTC in the same channel there will be also Neutron CI team meeting. [1] https://wiki.openstack.org/wiki/Network/Meetings -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[ironic][masakari] Should masakari rely on Ironic to power fence failing hosts?
by Nicolas Parquet 08 Dec '20

08 Dec '20

Hello Ironic people! I am coming to you with a question from one of the points we discussed during Masakari's PTG [1]. When a host fails and Masakari gets notified, there are some cases in which we would like Masakari to power fence the host before evacuating its instances to other hosts. That way it is safe to start the instances from the failed host on another one. Given that Ironic has the responsability of managing hosts, we would be interested to know how Masakari should do that, in your view? We discussed implementing IPMI power on / off directly in masakari, but maybe an integration where Masakari calls some Ironic API would be better? Or maybe we should implement it relying on the pyghmi library, or any other library? A positive side of relying on Ironic would be that Masakari does not have to store IPMI information about hosts; however that would create a dependency between the 2 projects as some deployments might use masakari without managing their hosts through Ironic. Any insight is welcome! Regards, Nicolas [1] https://etherpad.opendev.org/p/masakari-wallaby-vptg -- Nicolas Parquet Gandi nicolas.parquet(a)gandi.net

2 1

[TripleO] how to make that inspection IP is given only to known hosts
by Ruslanas Gžibovskis 08 Dec '20

08 Dec '20

Hi all, I have a situation, when in my network, I have loads of equipment, which I do not control. and Inspection range gets occupied quite fast. and in TCP dump I get such messages: DHCP-Message Option 53, length 1: NACK Server-ID Option 54, length 4: DHCPD-IP MSG Option 56, length 21: "address not available" I have disabled: enabled_node_discovery = false Anything else? maybe additional environment options for undercloud I could provide? Than kyou in advance, have a good $day_time -- Ruslanas Gžibovskis +370 6030 7030

3 3

[OSSA-2020-008] horizon: Open redirect in workflow forms
by Gage Hugo 07 Dec '20

07 Dec '20

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 ============================================== OSSA-2020-008: Open redirect in workflow forms ============================================== :Date: December 03, 2020 :CVE: CVE-2020-29565 Affects ~~~~~~~ - - Horizon: <15.3.2, >=16.0.0 <16.2.1, >=17.0.0 <18.3.3, >=18.4.0 <18.6.0 Description ~~~~~~~~~~~ Pritam Singh (Red Hat) reported a vulnerability in Horizon's workflow forms. Previously there was a lack of validation on the "next" parameter, which would allow someone to supply a malicious URL in Horizon that can cause an automatic redirect to the provided malicious URL. Patches ~~~~~~~ - - https://review.opendev.org/758843 (Stein) - - https://review.opendev.org/758841 (Train) Credits ~~~~~~~ - - Pritam Singh from Red Hat (CVE-2020-29565) References ~~~~~~~~~~ - - https://launchpad.net/bugs/1865026 - - http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-29565 -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEWa125cLHIuv6ekof56j9K3b+vREFAl/OrjwACgkQ56j9K3b+ vRG/Gg//Tyj5La8eFwIrwhpDbV/tKNFS+t3NzuhJzLS24WNS9cLf5yDronRdBPdT Ow2OegTZ7K5GyoRARpycTjtE66RIizX9I8Kx27FXPc83hLYYOs/MButYpqcp0swM 687RXZGFcZ5HZtPuRuTcclEcyhzvcUX7HXmznOCmVOHchr+RXzmp6cXC7tyCuNkV cGuuMtptDfkFmn2MpGmiTWEiMusMRbV5HqeyY39jg5dwph0kbMCcuzkX6c2WHubE T+rjVKbmqHr+v7og6mkZoK+pVk6Ulta/lGsYh/0NlszdQw3poN4FIt//TIwJZVwx WSlbMt6IwBW5XiPXvjpX9Awis6CT0jxlIV5XBq+klr3Jo+YnDsChElIPQs3CRKoM vqXVextHCk3LK1Evs3FkBns2Taro4tWOlkGYKR6INT4F1TJKNIzIUiF08673uF3B 8zXDfnVEb7tEMqwu6OdVnfQQ4SRu7uyrN1sHhtwIyfK10AAI7gfJL/wbItJy21Om SQahTfDnikEY5gYYU+NH0LBMXkE0I/T+uvPh4LgP7wUxCMR9uI8+iA0711Gp/aPD WUdm3pUfIJYE7Gq6sT7BJQftHyMPcxOBj+MIrmFDFOxyPV70Mub+f34zxdu3Qoda tZNpy/BGL19VqrlRa9R8H65tzzNy7k5GqkaUYEF5/LegfUgZOTo= =jr+k -----END PGP SIGNATURE-----

1 0

[ops] In a compute node, outbound traffic blocked when a VM running
by Hyunwoo KIM 07 Dec '20

07 Dec '20

Summary of the problem This problem is in a compute node, not in a VM. Once a VM is running in a compute node, all outbound connections in a compute node (not VM) are blocked. For example: # telnet www.google.com 80 Trying 172.217.5.4... Technical Details: We only use provider network. These 4 services are running in each compute node: - neutron-linuxbridge-agent.service - neutron-dhcp-agent.service - neutron-metadata-agent.service - openstack-nova-compute.service Detailed description of the problem: In a compute node, the following is the result of iptables -L when no VM is running: <begin> Chain INPUT (policy ACCEPT) target prot opt source destination neutron-linuxbri-INPUT all -- anywhere anywhere And our usual rules Chain FORWARD (policy ACCEPT) target prot opt source destination neutron-filter-top all -- anywhere anywhere neutron-linuxbri-FORWARD all -- anywhere anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination neutron-filter-top all -- anywhere anywhere neutron-linuxbri-OUTPUT all -- anywhere anywhere Chain neutron-filter-top (2 references) target prot opt source destination neutron-linuxbri-local all -- anywhere anywhere Chain neutron-linuxbri-FORWARD (1 references) target prot opt source destination ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out tapb --physdev-is-bridged ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-in tapb --physdev-is-bridged ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out tap9 --physdev-is-bridged ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-in tap9 --physdev-is-bridged Chain neutron-linuxbri-INPUT (1 references) target prot opt source destination Chain neutron-linuxbri-OUTPUT (1 references) target prot opt source destination Chain neutron-linuxbri-local (1 references) target prot opt source destination Chain neutron-linuxbri-sg-chain (0 references) target prot opt source destination ACCEPT all -- anywhere anywhere Chain neutron-linuxbri-sg-fallback (0 references) target prot opt source destination DROP all -- anywhere anywhere </end> In the same compute node, when a VM is running, the following is the result of iptables -L: <begin> Chain INPUT (policy ACCEPT) target prot opt source destination neutron-linuxbri-INPUT all -- anywhere anywhere And our usual rules Chain FORWARD (policy ACCEPT) target prot opt source destination neutron-filter-top all -- anywhere anywhere neutron-linuxbri-FORWARD all -- anywhere anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination neutron-filter-top all -- anywhere anywhere neutron-linuxbri-OUTPUT all -- anywhere anywhere Chain neutron-filter-top (2 references) target prot opt source destination neutron-linuxbri-local all -- anywhere anywhere Chain neutron-linuxbri-FORWARD (1 references) target prot opt source destination neutron-linuxbri-sg-chain all -- anywhere anywhere PHYSDEV match --physdev-out tap8 --physdev-is-bridged neutron-linuxbri-sg-chain all -- anywhere anywhere PHYSDEV match --physdev-in tap8 --physdev-is-bridged ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out tapb --physdev-is-bridged ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-in tapb --physdev-is-bridged ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out tap9 --physdev-is-bridged ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-in tap9 --physdev-is-bridged Chain neutron-linuxbri-INPUT (1 references) target prot opt source destination neutron-linuxbri-o8 all -- anywhere anywhere PHYSDEV match --physdev-in tap8 --physdev-is-bridged Chain neutron-linuxbri-OUTPUT (1 references) target prot opt source destination Chain neutron-linuxbri-i8 (1 references) target prot opt source destination RETURN all -- anywhere anywhere state RELATED,ESTABLISHED RETURN udp -- anywhere fermicloud248.fnal.gov udp spt:bootps dpt:bootpc RETURN udp -- anywhere 255.255.255.255 udp spt:bootps dpt:bootpc RETURN icmp -- anywhere anywhere RETURN tcp -- fermilab-net.fnal.gov/16 anywhere tcp dpt:ssh RETURN all -- anywhere anywhere match-set NIPv41d69ba3c-68e3-414f-8f1b- src DROP all -- anywhere anywhere state INVALID neutron-linuxbri-sg-fallback all -- anywhere anywhere Chain neutron-linuxbri-local (1 references) target prot opt source destination Chain neutron-linuxbri-o8 (2 references) target prot opt source destination RETURN udp -- default 255.255.255.255 udp spt:bootpc dpt:bootps neutron-linuxbri-s8 all -- anywhere anywhere RETURN udp -- anywhere anywhere udp spt:bootpc dpt:bootps DROP udp -- anywhere anywhere udp spt:bootps dpt:bootpc RETURN all -- anywhere anywhere state RELATED,ESTABLISHED RETURN tcp -- anywhere anywhere tcp dpt:https RETURN all -- anywhere anywhere RETURN tcp -- anywhere anywhere tcp dpt:http DROP all -- anywhere anywhere state INVALID neutron-linuxbri-sg-fallback all -- anywhere anywhere Chain neutron-linuxbri-s8 (1 references) target prot opt source destination RETURN all -- fermicloud248.fnal.gov anywhere MAC FA:16: DROP all -- anywhere anywhere Chain neutron-linuxbri-sg-chain (2 references) target prot opt source destination neutron-linuxbri-i8 all -- anywhere anywhere PHYSDEV match --physdev-out tap8 --physdev-is-bridged neutron-linuxbri-o8 all -- anywhere anywhere PHYSDEV match --physdev-in tap8 --physdev-is-bridged ACCEPT all -- anywhere anywhere Chain neutron-linuxbri-sg-fallback (2 references) target prot opt source destination DROP all -- anywhere anywhere </end> Let me summarize the differences from when no VM running: Chain INPUT : no change Chain FORWARD: no change Chain OUTPUT : no change Chain neutron-filter-top: no change Chain neutron-linuxbri-FORWARD: Two new rules are added neutron-linuxbri-sg-chain neutron-linuxbri-sg-chain Chain neutron-linuxbri-INPUT: One new rule is added neutron-linuxbri-o8ae816b0-f Chain neutron-linuxbri-sg-chain: Two new rules are added neutron-linuxbri-i8 neutron-linuxbri-o8 Chain neutron-linuxbri-OUTPUT: no change Chain neutron-linuxbri-local: no change Chain neutron-linuxbri-sg-fallback: no change Chain neutron-linuxbri-i8: A new chain with multiple rules Chain neutron-linuxbri-o8: A new chain with multiple rules Chain neutron-linuxbri-s8: A new chain with multiple rules But now a problem arises here: All outbound connections are blocked (remember this is in a compute node, not VM): For example: # telnet www.google.com 80 Trying 172.217.5.4... When there isn't any VM running, We don't see this problem. I was wondering if I needed to create a new security group rule for the port 80 (for example) but that didn't solve the issue. Any technical advice will be appreciated, Thanks, Hyunwoo

2 2

openstack read only user
by dhanesh1212121212 07 Dec '20

07 Dec '20

Hi Team, Please let me know the steps to create a read only user in openstack. (My version is Rocky) Regards, Dhanesh M.

4 3

[interop][refstack] Revival/Maintenance proposal
by Goutham Pacha Ravi 07 Dec '20

07 Dec '20

Hi, As many of you are aware, the interop working group defines test advisories for evaluating implementations of OpenStack for interoperability. The implementers themselves - whether they are OpenStack cloud operators, distributions or vendors of specific products aligning with OpenStack use refstack-client [1] to submit their results. Refstack client is a bunch of helpful scripts to stand up tempest, run the tests and compile results. The results compiled from refstack-client are posted to https://refstack.openstack.org - code for which exists in the "refstack" repository [2] For a few releases now, gmann has pointed out to the Interop WG that refstack needs maintainers. In our last meeting, Martin Kopec (mkopec) volunteered to maintain refstack-client, and help coordinate changes to adopt the latest advisories published by the interop working group. Martin's been running interop testing for Red Hat OpenStack, and he has contributed ansible automation for installing, running tests and submitting results [3]. So he'll bring valuable interop perspective to this project and maintain it effectively. The interop WG also suggested that Martin's ansible scripts [3] be moved under the "osf/" organization on opendev.org, and he's currently pursuing that [4]. I see a number of names on the refstack-core group on Gerrit [5]. Is it possible there's anyone in the team that's still involved in the maintenance of this project, and can add Martin? Thanks, Goutham [1] https://opendev.org/osf/refstack-client [2] https://opendev.org/osf/refstack [3] https://opendev.org/x/ansible-role-refstack-client [4] https://review.opendev.org/c/openstack/project-config/+/765787 [5] https://review.opendev.org/admin/groups/8cd7203820004ccdb67c999ca3b811534bf…

2 1

[tc][all][searchlight ] Retiring the Searchlight project
by Ghanshyam Mann 07 Dec '20

07 Dec '20

Hello Everyone, As you know, Searchlight is a leaderless project for the Wallaby cycle, which means there is no PTL candidate to lead it in the Wallaby cycle. 'No PTL' and no liaisons for DPL model is one of the criteria which triggers TC to start checking the health, maintainers of the project for dropping the project from OpenStack Governance[1]. TC discussed the leaderless project in PTG[2] and checked if the project has maintainers and what activities are done in the Victoria development cycle. It seems no functional changes in Searchlight repos except few gate fixes or community goal commits[3]. Based on all these checks and no maintainer for Searchlight, TC decided to drop this project from OpenStack governance in the Wallaby cycle. Ref: Mandatory Repository Retirement resolution [4] and the detailed process is in the project guide docs [5]. If your organization product/customer use/rely on this project then this is the right time to step forward to maintain it otherwise from the Wallaby cycle, Searchlight will move out of OpenStack governance by keeping their repo under OpenStack namespace with an empty master branch with 'Not Maintained' message in README. If someone from old or new maintainers shows interest to continue its development then it can be re-added to OpenStack governance. With that thanks to Searchlight contributors and PTLs for maintaining this project. [1] https://governance.openstack.org/tc/reference/dropping-projects.html [2] https://etherpad.opendev.org/p/tc-wallaby-ptg [3] https://www.stackalytics.com/?release=victoria&module=searchlight-group&met… [4] https://governance.openstack.org/tc/resolutions/20190711-mandatory-reposito… [5] https://docs.openstack.org/project-team-guide/repository.html#retiring-a-re… -gmann

5 8

[tc][all][qinling] Retiring the Qinling project
by Ghanshyam Mann 07 Dec '20

07 Dec '20

Hello Everyone, As you know, Qinling is a leaderless project for the Wallaby cycle, which means there is no PTL candidate to lead it in the Wallaby cycle. 'No PTL' and no liaisons for DPL model is one of the criteria which triggers TC to start checking the health, maintainers of the project for dropping the project from OpenStack Governance[1]. TC discussed the leaderless project in PTG[2] and checked if the project has maintainers and what activities are done in the Victoria development cycle. It seems no functional changes in Qinling repos except few gate fixes or community goal commits[3]. Based on all these checks and no maintainer for Qinling, TC decided to drop this project from OpenStack governance in the Wallaby cycle. Ref: Mandatory Repository Retirement resolution [4] and the detailed process is in the project guide docs [5]. If your organization product/customer use/rely on this project then this is the right time to step forward to maintain it otherwise from the Wallaby cycle, Qinling will move out of OpenStack governance by keeping their repo under OpenStack namespace with an empty master branch with 'Not Maintained' message in README. If someone from old or new maintainers shows interest to continue its development then it can be re-added to OpenStack governance. With that thanks to Qinling contributors and PTLs (especially lxkong ) for maintaining this project. [1] https://governance.openstack.org/tc/reference/dropping-projects.html [2] https://etherpad.opendev.org/p/tc-wallaby-ptg [3] https://www.stackalytics.com/?release=victoria&module=qinling-group&metric=… [4] https://governance.openstack.org/tc/resolutions/20190711-mandatory-reposito… [5] https://docs.openstack.org/project-team-guide/repository.html#retiring-a-re… -gmann

4 6

[Neutron] How to enable the SCTP protal support in security-groups for Openstack-Rocky release
by Velugubantla Praveen 07 Dec '20

07 Dec '20

Hi Team, In OPENSTACK security groups how to add the SMTP protocol rules, can some-one please point me to the right documentation of how to add those required configurations to enable SMTP and other protocols to my openstack-rocky release neutron setup. Can we add some additional protocol's above the default provided security rules? Any help or suggestion is highly appreciated. Thanks in advance. Regards, ________________________________________________________ Velugubantla Praveen Engineer - Non-Media Solutions Communications & Media L&T TECHNOLOGY SERVICES LIMITED L3 Building, Manyata Embassy Business Park, Nagawara Hobli, Bengaluru-560045 ________________________________________________________ Mobile: +91 9154111420 www.LTTS.com<http://www.ltts.com/> [cid:e997ce03-4d35-4f33-ad56-ad4facc1f804] L&T Technology Services Ltd www.LTTS.com L&T Technology Services Limited (LTTS) is committed to safeguard your data privacy. For more information to view our commitment towards data privacy under GDPR, please visit the privacy policy on our website www.Ltts.com. This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.

2 1

[ptl] Victoria Release Community Meeting Videos
by helena＠openstack.org 07 Dec '20

07 Dec '20

Hi Everyone, Thank you to all the PTLs who presented and all the community members who attended the Victoria Release Community Meeting last November! As mentioned before we uploaded the presentations from the community meeting to the project navigator for each project that was presented on ([ Glance ]( https://www.openstack.org/software/releases/victoria/components/glance ), [ Cinder ]( https://www.openstack.org/software/releases/victoria/components/cinder ), [ Manila ]( https://www.openstack.org/software/releases/victoria/components/manila ), [ Nova ]( https://www.openstack.org/software/releases/victoria/components/nova ), [ Masakri ]( https://www.openstack.org/software/releases/victoria/components/masakari ), [ Neutron ]( https://www.openstack.org/software/releases/victoria/components/neutron )). You can also find the full community meeting and all the individual videos on the “[ Community Meetings ]( https://www.youtube.com/playlist?list=PLKqaoAnDyfgpYADSiOfIVwgKb5zbL0GJE )” playlist on YouTube. If you are a PTL interested in still creating a video to add to YouTube and the Project Navigator, you may do so and email it to me. Cheers, Helena

2 2

[Diversity] Diversity and Inclusion WG Meeting Change for January
by Amy Marrich 07 Dec '20

07 Dec '20

Due to the end of year holidays and the fact some people may still be out we will be moving our January meeting. As our backup meeting date is on Martin Luther King Day, the WG has selected January 11 to meet in IRC. As always I'll send out a reminder in the days leading up to the meeting. Thanks, Amy (spotz)

1 0

[ci] Kernel panics in the guest vm
by Slawek Kaplonski 07 Dec '20

07 Dec '20

Hi, Since some time I noticed that quite often some scenario jobs are failing due to issue with SSH to the guest vm and when I was checking the reason of this SSH failure, it seems that it's due to Kernel panic in the guest vm, like e.g. [1]: [ 0.000000] Console: colour VGA+ 80x25 [ 0.000000] printk: console [tty1] enabled [ 0.000000] printk: console [ttyS0] enabled [ 0.000000] ACPI: Core revision 20190703 [ 0.000000] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604467 ns [ 0.000000] APIC: Switch to symmetric I/O mode setup [ 0.000000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [ 0.000000] ..MP-BIOS bug: 8254 timer not connected to IO-APIC [ 0.000000] ...trying to set up timer (IRQ0) through the 8259A ... [ 0.000000] ..... (found apic 0 pin 2) ... [ 0.000000] ....... failed. [ 0.000000] ...trying to set up timer as Virtual Wire IRQ... [ 0.000000] ..... failed. [ 0.000000] ...trying to set up timer as ExtINT IRQ... [ 0.000000] ..... failed :(. [ 0.000000] Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic=debug and send a report. Then try booting with the 'noapic' option. [ 0.000000] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.3.0-26-generic #28~18.04.1-Ubuntu [ 0.000000] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 1.13.0-1ubuntu1 04/01/2014 [ 0.000000] Call Trace: [ 0.000000] dump_stack+0x6d/0x95 [ 0.000000] panic+0xfe/0x2d4 [ 0.000000] check_timer+0x5e8/0x685 [ 0.000000] ? radix_tree_lookup+0xd/0x10 [ 0.000000] setup_IO_APIC+0x182/0x1ca [ 0.000000] apic_intr_mode_init+0x1f5/0x1f8 [ 0.000000] x86_late_time_init+0x1b/0x22 [ 0.000000] start_kernel+0x4cb/0x58b [ 0.000000] x86_64_start_reservations+0x24/0x26 [ 0.000000] x86_64_start_kernel+0x74/0x77 [ 0.000000] secondary_startup_64+0xa4/0xb0 [ 0.000000] ---[ end Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic=debug and send a report. Then try booting with the 'noapic' option. ]--- Logstash [2] is telling me that it is problem not only in neutron related jobs. Maybe someone of You was already trying to investigate such issue and maybe You have some ideas what we can do with it? In this specific example above [1], it was Cirros 0.5.1 image used. But I didn't check if that is the case in all other cases TBH. [1] https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/… [2] http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3…'t%20work!%20%20Boot%20with%20apic%3Ddebug%20and%20send%20a%20report.%20%20Then%20try%20booting%20with%20the%20'noapic'%20option.%5C%22 -- Slawek Kaplonski Principal Software Engineer Red Hat

3 3

[tripleo] CI jobs failures on RDO project
by Daniel Pawlik 07 Dec '20

07 Dec '20

Hello, We are facing an outage in our cloud providers. That's why from time to time you can have problems validating CI jobs in RDO project. We are doing our best to fix the issues as soon as possible. Kindly regards, Dan

1 0

[networking-ovs-dpdk]
by Elanchezian Settu 07 Dec '20

07 Dec '20

Hi, Tried ovs-dpdk installation in below setup and noticing it fails with OVS-DPDK initialization timeout problem. Herewith I had attached the local.conf file, which I had used for my setup bring up. Server: Ubuntu 18.04 latest OpenStack: Stein OVS-DPDK: Master byte-compiling /usr/local/lib/python3.6/dist-packages/networking_ovs_dpdk/agent/ovs_dpdk_firewall.py to ovs_dpdk_firewall.cpython-36.pyc running install_egg_info Copying networking_ovs_dpdk.egg-info to /usr/local/lib/python3.6/dist-packages/networking_ovs_dpdk-2015.1.1.dev275-py3.6.egg-info running install_scripts /usr/local/lib/python3.6/dist-packages/pbr/packaging.py:410: EasyInstallDeprecationWarning: Use get_header header = easy_install.get_script_header("", executable, is_wininst) ++/opt/stack/networking-ovs-dpdk/devstack/plugin.sh:source:35 popd /opt/stack/ovs ++/opt/stack/networking-ovs-dpdk/devstack/plugin.sh:source:36 start_ovs_dpdk ++/opt/stack/networking-ovs-dpdk/devstack/libs/ovs-dpdk:start_ovs_dpdk:19 '[' -e /etc/init.d/ovs-dpdk ']' ++/opt/stack/networking-ovs-dpdk/devstack/libs/ovs-dpdk:start_ovs_dpdk:20 sudo service ovs-dpdk start Job for ovs-dpdk.service failed because a timeout was exceeded. See "systemctl status ovs-dpdk.service" and "journalctl -xe" for details. +/opt/stack/networking-ovs-dpdk/devstack/libs/ovs-dpdk:start_ovs_dpdk:1 exit_trap +./stack.sh:exit_trap:528 local r=1 ++./stack.sh:exit_trap:529 jobs -p +./stack.sh:exit_trap:529 jobs= +./stack.sh:exit_trap:532 [[ -n '' ]] +./stack.sh:exit_trap:538 '[' -f '' ']' +./stack.sh:exit_trap:543 kill_spinner +./stack.sh:kill_spinner:438 '[' '!' -z '' ']' +./stack.sh:exit_trap:545 [[ 1 -ne 0 ]] +./stack.sh:exit_trap:546 echo 'Error on exit' Error on exit +./stack.sh:exit_trap:548 type -p generate-subunit +./stack.sh:exit_trap:549 generate-subunit 1607341696 1042 fail +./stack.sh:exit_trap:551 [[ -z /opt/stack/logs/screen ]] +./stack.sh:exit_trap:554 /home/ubuntu/devstack/tools/worlddump.py -d /opt/stack/logs/screen Traceback (most recent call last): File "/home/ubuntu/devstack/tools/worlddump.py", line 255, in <module> sys.exit(main()) File "/home/ubuntu/devstack/tools/worlddump.py", line 239, in main sys.stdout = os.fdopen(sys.stdout.fileno(), 'w', 0) File "/usr/lib/python3.6/os.py", line 1017, in fdopen return io.open(fd, *args, **kwargs) ValueError: can't have unbuffered text I/O Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='UTF-8'> OSError: [Errno 9] Bad file descriptor ubuntu@ubuntu:~/devstack$ ubuntu@ubuntu:~/devstack$ systemctl status ovs-dpdk.service ● ovs-dpdk.service - LSB: Open vSwitch DPDK Loaded: loaded (/etc/init.d/ovs-dpdk; generated) Active: failed (Result: timeout) since Mon 2020-12-07 12:05:38 UTC; 15s ago Docs: man:systemd-sysv-generator(8) Process: 21377 ExecStart=/etc/init.d/ovs-dpdk start (code=killed, signal=TERM) Tasks: 2 (limit: 9830) CGroup: /system.slice/ovs-dpdk.service ├─21984 sudo ovs-vsctl --may-exist add-port br-enp24s0f1 enp24s0f1 -- set Interface enp24s0f1 type=dpdk options:dpdk-devargs=0000:18:00.1 other_config:pci_address=0000:18:00.1 other_config:driver=igb_uio other_config:p └─21985 ovs-vsctl --may-exist add-port br-enp24s0f1 enp24s0f1 -- set Interface enp24s0f1 type=dpdk options:dpdk-devargs=0000:18:00.1 other_config:pci_address=0000:18:00.1 other_config:driver=igb_uio other_config:previo Dec 07 12:00:41 ubuntu sudo[21775]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/opt/stack/DPDK-v18.11/usertools/dpdk-devbind.py -b igb_uio 0000:5e:00.1 Dec 07 12:00:41 ubuntu sudo[21775]: pam_unix(sudo:session): session opened for user root by (uid=0) Dec 07 12:00:42 ubuntu sudo[21775]: pam_unix(sudo:session): session closed for user root Dec 07 12:00:42 ubuntu ovs-dpdk[21377]: add-port command: ovs-vsctl --may-exist add-port br-enp24s0f1 enp24s0f1 -- set Interface enp24s0f1 type=dpdk options:dpdk-devargs=0000:18:00.1 other_config:pci_address=0000:18:00.1 Dec 07 12:00:42 ubuntu sudo[21984]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/ovs-vsctl --may-exist add-port br-enp24s0f1 enp24s0f1 -- set Interface enp24s0f1 type=dpdk options:dpdk-devargs=0000:18:00.1 other_ Dec 07 12:00:42 ubuntu sudo[21984]: pam_unix(sudo:session): session opened for user root by (uid=0) Dec 07 12:00:42 ubuntu ovs-vsctl[21985]: ovs|00001|vsctl|INFO|Called as ovs-vsctl --may-exist add-port br-enp24s0f1 enp24s0f1 -- set Interface enp24s0f1 type=dpdk options:dpdk-devargs=0000:18:00.1 other_config:pci_address=0000:18 Dec 07 12:05:38 ubuntu systemd[1]: ovs-dpdk.service: Start operation timed out. Terminating. Dec 07 12:05:38 ubuntu systemd[1]: ovs-dpdk.service: Failed with result 'timeout'. Dec 07 12:05:38 ubuntu systemd[1]: Failed to start LSB: Open vSwitch DPDK. ubuntu@ubuntu:~/devstack$ Thanks & Regards, Elan This message may contain confidential and privileged information. If it has been sent to you in error, please reply to advise the sender of the error and then immediately delete it. If you are not the intended recipient, do not read, copy, disclose or otherwise use this message. The sender disclaims any liability for such unauthorized use. NOTE that all incoming emails sent to Gigamon email accounts will be archived and may be scanned by us and/or by external service providers to detect and prevent threats to our systems, investigate illegal or inappropriate behavior, and/or eliminate unsolicited promotional emails (“spam”).

1 0

[neutron] Bug deputy report (week starting on 2020-11-30)
by Bernard Cafarelli 07 Dec '20

07 Dec '20

Hi neutrinos, time to start last bug deputy rotation for 2020, here are the bugs reported in week 49. A pretty normal range of bugs from CI fixes to scaling enhancements, most in progress. Two are unassigned right now: OVN tempest failure ( https://bugs.launchpad.net/neutron/+bug/1906490) and DHCP agent leases fix with segments (https://bugs.launchpad.net/neutron/+bug/1906406) New RFE: * [RFE] add new extension "device-profile" for port - https://bugs.launchpad.net/neutron/+bug/1906602 New extension for device_profile notion of Cyborg project - already discussed and approved Critical * oom killer kills mysqld process on the node running fullstack tests - https://bugs.launchpad.net/neutron/+bug/1906366 Patch to limit resources used in FT tests: https://review.opendev.org/c/openstack/neutron/+/764907 * SSH failures in the neutron-ovn-tempest-ovs-release-ipv6-only job - https://bugs.launchpad.net/neutron/+bug/1906490 Unassigned * neutron_tempest_plugin.api.admin.test_dhcp_agent_scheduler.DHCPAgentSchedulersTestJSON.test_dhcp_port_status_active is failing often - https://bugs.launchpad.net/neutron/+bug/1906654 https://review.opendev.org/c/openstack/neutron/+/755313 may help here, to confirm High * [ovn] Tempest tests failing while creating security group driver with KeyError: 'remote_address_group_id' - https://bugs.launchpad.net/neutron/+bug/1906500 Broke after a recent merge (and not tested in gates), fix at https://review.opendev.org/c/openstack/neutron/+/765101 * [OVN Octavia Provider] OVN provider not setting member offline correctly on create when admin_state_up=False - https://bugs.launchpad.net/neutron/+bug/1906568 Fix for tempest test in https://review.opendev.org/c/openstack/ovn-octavia-provider/+/765213 Medium * [segments] dnsmasq can't delete lease for instance due to mismatch between client ip and local addr - https://bugs.launchpad.net/neutron/+bug/1906406 With routed provider networks, DHCP agent at startup receives all leases, not only those from its segment Unassigned * MTU for networks with enabled vlan transparency should be 4 bytes lower - https://bugs.launchpad.net/neutron/+bug/1906318 Assigned to slaweq * [L2][scale] add a trunk size config option for bundle flow install - https://bugs.launchpad.net/neutron/+bug/1906487 New option to help with large set of flows installation: https://review.opendev.org/c/openstack/neutron/+/765072 Low * dns-integration api extension shouldn't be enabled by ovn_l3 plugin if there is no corresponding ML2 extension driver enabled - https://bugs.launchpad.net/neutron/+bug/1906311 Patch https://review.opendev.org/c/openstack/neutron/+/764831 * [L3] router HA port concurrently deleting - https://bugs.launchpad.net/neutron/+bug/1906375 Happened on rocky but code did not change since, patch in progress https://review.opendev.org/c/openstack/neutron/+/764913 * [L2] current binding port get type errors - https://bugs.launchpad.net/neutron/+bug/1906381 Patch in progress at https://review.opendev.org/c/openstack/neutron/+/764917 * Wrong error message when removing interface from router - https://bugs.launchpad.net/neutron/+bug/1906508 Suggested fix https://review.opendev.org/c/openstack/neutron/+/765129 -- Bernard Cafarelli

1 0

[security] Auto-renewing trusted user certificates for Openstack services using the ACME protocol
by Stanislav Dimov 07 Dec '20

07 Dec '20

Hello all, I have recently started exploring Openstack with the goal of using it to replace my current private cloud infrastructure. I have been reading the docs about security and I noticed that there isn't really a (straight forward) way of securing Openstack services communication with user provided, trusted, SSL certificates. I believe this should not be the case. My current infrastructure uses a privately hosted CA, that supports the ACME protocol. All my hosts submit CSRs to it, and respond to the ACME challenges in order to get it signed. All certificates are short-lived (1h), but never expire thanks to the ACME automation. I have achieved this through an open source project called Smallstep Step CA and Smallstep Step CLI tools. It is dead easy to set up. All of the tools needed to achieve this can also be containerized, for simplicity. Thus, I propose the following solution (keep in mind I am not an Openstack developer): Addition of an ACME client, with a configurable ACME URL, to all (or as many as possible) Openstack services, that can submit CSRs to an ACME server (basically almost identical to the already implemented Openstack Let's Encrypt functionality for public endpoints). Also, optionally, the creation of a new Openstack service, using the Smallstep Step CA, which can sign the CSRs, and thus eliminate the need for a manual setup of a separate Smallstep CA host. I am providing some links to the Smallstep repositories and documentation for easier access: https://github.com/smallstep/certificates https://github.com/smallstep/cli https://github.com/smallstep/hello-mtls https://smallstep.com/docs/ Thank you for your time and consideration. Kind regards, Stanislav

1 0

octavia flavor question
by Satish Patel 06 Dec '20

06 Dec '20

Folks, I am deployed Octavia and now trying to understand how does flavor play there role using this guide https://docs.openstack.org/octavia/latest/admin/flavors.html In my octavia.conf i have statically defined nova flavor so when i spin up LB it always use m1.amphora (UUID: 8651951f-e478-4efb-b298-cf3150d38472) which has 1vCPU/2GB memory. # grep amp_flavor_id /etc/octavia/octavia.conf amp_flavor_id = 8651951f-e478-4efb-b298-cf3150d38472 Question: how do I create or tell octavia to use multiple nova flavors for example, I want 3 flavors m1.amphora - 1vCPU/2GB/20GB disk m2.amphora - 4vCPU/4GB/20GB disk m3.amphora - 8vCPU/8GB/40GB disk (with HugePage and CPUpinning support) I want my users to have the option to select whatever flavor they like. how does that fit here? I didn't find any document explaining that feature to select your desired nova flavor. Did I miss something?

3 3

[tripleo][ussuri] overcloud deploy increase timeout/wai time to load initramfs to deploy os
by Ruslanas Gžibovskis 06 Dec '20

06 Dec '20

Hi all, To deploy initramfs takes longer time (around 17 min). And while it is loading, overcloud deploy sais: ' Went to status ERROR due to "Message: No valid host was found. , Code: 500" '. the remote compute is in a different continent, so speed is quite slow. is it possible to increase wait time? Thank you. Regards. -- Ruslanas Gžibovskis +370 6030 7030

1 0

[rdo][centos8][repos] CentOS8 RDO-USSURI repo missing openvswitch2.13
by Ruslanas Gžibovskis 05 Dec '20

05 Dec '20

Hi all, I have an issue, in CentOS8 repos for RDO. It is refering to openvswitch2.13 name, but in the repos I can see openvswitch packages with version in version field, looks like in dependency field it is missing dash (-) or smth... here is a paste of repos and error message [0]. Or any other way how this could be fixed? thanks. and packages I can see [1] here. [0] http://paste.openstack.org/show/xEalilL1rRJSDTzNCGt1/ [1] http://paste.openstack.org/show/VLWrNFpRLatwq5qXP2kD/ -- Ruslanas Gžibovskis +370 6030 7030

3 3

[tripleo] TripleO CI Summary: Unified Sprint 36
by Rafael Folco 04 Dec '20

04 Dec '20

Greetings, The TripleO CI team has just completed **Unified Sprint 36** (Nov 13 thru Dec 03). The following is a summary of completed work during this sprint cycle: - Added Tempest cleanup support: https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/76240… - Ported jobs running against tripleo-ansible stable/train to centos-8 - ansible-role-collect-logs role is packaged now and available for train onwards - All the jobs are migrated to vexxhost and rdo-cloud nodeset is - removed - Continued merging changes to wire-up content provider jobs across TripleO related projects to remove docker.io dependencies: https://review.opendev.org/#/q/topic:new-ci-job - Designed a dependency pipeline to early detect breakages in the base OS: https://hackmd.io/14KFQiyWSBCRsfJmBZNARw?both - component standalone-upgrade - Enable the component-ci-testing repo if it is installed: https://review.opendev.org/c/openstack/tripleo-quickstart-extras/+/764767 - https://review.rdoproject.org/r/#/c/31200/ Adds tripleo component standalone-upgrade-master/victoria/ussuri - Redundant content providers for the upgrade jobs to reduce resource usage: https://review.opendev.org/761188 - Tempest scenario manager improvements: 1. https://review.opendev.org/c/openstack/tempest/+/753689 2. https://review.opendev.org/c/openstack/tempest/+/754081 3. https://review.opendev.org/c/openstack/tempest/+/755072 - Promoter configuration fix: https://review.rdoproject.org/r/#/c/28014/ - Created a new job in downstream for 16.2 component pipeline which deploys multiple overcloud stack using a single undercloud node: - https://review.opendev.org/c/openstack/tripleo-quickstart-extras/+/763786 - https://review.opendev.org/c/openstack/tripleo-quickstart/+/761061 - Added OSP 13 ansible openstack collection tests job - Wrote test cases for cockpit (telegraf container bump to python3): https://review.rdoproject.org/r/#/c/30492/ - Removed ubi-8 based jobs: https://review.opendev.org/760426 - Ansible-collections-openstack improvements: 1. ttps://review.opendev.org/c/openstack/ansible-collections-openstack/+/764379 <https://review.opendev.org/c/openstack/ansible-collections-openstack/+/7643…> 2. https://review.opendev.org/c/openstack/ansible-collections-openstack/+/7643… 3. https://review.opendev.org/c/openstack/ansible-collections-openstack/+/7644… 4. https://review.opendev.org/c/openstack/ansible-collections-openstack/+/7640… Upstream promotions [1] Ruck/Rover recorded notes [2]. NEXT SPRINT =========== The planned work for the next sprint is to continue work started in the previous sprint: The Ruck and Rover shifts for the upcoming weeks are scheduled as follows: Dec 7: Sorin Sbarnea (zbr), Marios Andreou (marios) Dec 14: Chandan Kumar (chandankumar), Amol Kahat (akahat) Dec 21: Bhagyashri Shewale (bhagyashris), Soniya Vyas (soniya29) Dec 28: Sandeep Yadav (ysandeep), Sagi Shnaidman (sshnaidm) Jan 4: Wesley Hayutin (weshay), Poja Jadhav (pojadhav) Please direct questions or queries to them regarding CI status or issues in #tripleo, ideally to whomever has the ‘|ruck’ suffix on their nick. Ruck/rover notes to be tracked in hackmd [2]. Thanks, --rfolco [1] http://dashboard-ci.tripleo.org/d/HkOLImOMk/upstream-and-rdo-promotions?org… [2] https://hackmd.io/R0kCgz_7SHSix_cNgoC9pg -- Folco

1 0

[Diversity] Diversity & Inclusion Meeting 12/7
by Amy Marrich 04 Dec '20

04 Dec '20

The Diversity & Inclusion WG invites members of all OSF projects to our next meeting Monday, December 7th, at 17:00 UTC in the #openstack-diversity channel. The agenda can be found at https://etherpad.openstack.org/p/diversity -wg-agenda. Please feel free to add any other topics you wish to discuss at the meeting. Thanks, Amy (spotz)

1 0

[baremetal-sig][ironic] Tue Dec 8, 2pm UTC: Ironic and Redfish Interop Profiles
by Arne Wiebalck 04 Dec '20

04 Dec '20

Dear all, The Bare Metal SIG will meet on Tue Dec 8 at 2pm UTC. This time there will be a 10 minute "topic-of-the-day" presentation by Richard Pioso: 'An Introduction to Ironic Redfish Interoperability Profiles' So, if you would like to learn how to validate if hardware is fit for use with Redfish and Ironic, find all the details for this meeting on the SIG's etherpad: https://etherpad.opendev.org/p/bare-metal-sig Everyone is welcome, don't miss out! Cheers, Arne

2 1

[rdo][centos8] OVS and OVN packages
by Tony Liu 04 Dec '20

04 Dec '20

Hi, I see OVN package ovn2.13-central-20.09.0-2.el8.x86_64.rpm and OVS in openvswitch2.13-2.13.0-60.el8.x86_64.rpm [1]. But I can't find them in [2]. Where are they built? Which source package is it based, [3] and [4]? [1] http://mirror.centos.org/centos/8/nfv/x86_64/openvswitch-2/Packages/o/ [2] https://cbs.centos.org/koji/packages [3] https://github.com/ovn-org/ovn/archive/v20.09.0.tar.gz [4] https://github.com/openvswitch/ovs/archive/v2.13.1.tar.gz Thanks! Tony

2 2

[ironic] : Third-party ML2 plugins for Openstack ironic with virtual networks
by fsbiz＠yahoo.com 04 Dec '20

04 Dec '20

Is anyone using virtual networks for their Openstack Ironic installations? Our flat network is now past 3000 nodes and I am investigating Arista's ML2 plugin and / or Mellanox's NEO as the ML2 plugin. In addition to scaling we also have additional requirements like provisioning a bare-metal serverin a conference room away from the DC for demo purposes. I have general questions on whether anyone is actually using the above two (or any other ML2 plugins)with their Openstack ironic installations ? Thanks,Fred.

2 1

devstack multinode: MTU tag not sent in Libvirt XML created from Nova
by Shashi, Yatindra 04 Dec '20

04 Dec '20

Hi All, I am using devstack-train version. Can you guys tell me which source file or function should I look when I get mtu size in the network-info but not in the libvirtxml parsed like below log Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: DEBUG nova.network.os_vif_util [None req-31d5b683-9e85-455e-95fd-b110de636fe4 admin admin] Converting VIF {"id": "d0358b23-d96b-4394-969d-32858b60e261", "addre ss": "fa:16:3e:46:97:e0", "network": {"id": "991289bb-6794-4673-b32c-e0f2296a8949", "bridge": "br-int", "label": "shared", "subnets": [{"cidr": "192.168.233.0/24", "dns": [], "gateway": {"address": "192.168.233.1 ", "type": "gateway", "version": 4, "meta": {}}, "ips": [{"address": "192.168.233.237", "type": "fixed", "version": 4, "meta": {}, "floating_ips": []}], "routes": [], "version": 4, "meta": {"dhcp_server": "192.16 8.233.2"}}], "meta": {"injected": false, "tenant_id": "ac158184024043faba836ec3d347d0d7", "mtu": 1450, "physical_network": null, "tunneled": true}}, "type": "ovs", "details": {"connectivity": "l2", "port_filter": true, "ovs_hybrid_plug": false, "datapath_type": "system", "bridge_name": "br-int"}, "devname": "tapd0358b23-d9", "ovs_interfaceid": "d0358b23-d96b-4394-969d-32858b60e261", "qbh_params": null, "qbg_params": null , "active": false, "vnic_type": "normal", "profile": {}, "preserve_on_delete": false, "meta": {}} {{(pid=8579) nova_to_osvif_vif /opt/stack/nova/nova/network/os_vif_util.py:516}} Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: DEBUG nova.network.os_vif_util [None req-31d5b683-9e85-455e-95fd-b110de636fe4 admin admin] Converted object VIFOpenVSwitch(active=False,address=fa:16:3e:46:97: e0,bridge_name='br-int',has_traffic_filtering=True,id=d0358b23-d96b-4394-969d-32858b60e261,network=Network(991289bb-6794-4673-b32c-e0f2296a8949),plugin='ovs',port_profile=VIFPortProfileOpenVSwitch,preserve_on_del ete=False,vif_name='tapd0358b23-d9') {{(pid=8579) nova_to_osvif_vif /opt/stack/nova/nova/network/os_vif_util.py:553}} Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: DEBUG nova.objects.instance [None req-31d5b683-9e85-455e-95fd-b110de636fe4 admin admin] Lazy-loading 'pci_devices' on Instance uuid 997103d3-0a60-4ce2-a85d-c42 eb24cfd8b {{(pid=8579) obj_load_attr /opt/stack/nova/nova/objects/instance.py:1090}} Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: DEBUG nova.virt.libvirt.driver [None req-31d5b683-9e85-455e-95fd-b110de636fe4 admin admin] [instance: 997103d3-0a60-4ce2-a85d-c42eb24cfd8b] End _get_guest_xml xml=<domain type="acrn"> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <uuid>997103d3-0a60-4ce2-a85d-c42eb24cfd8b</uuid> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <name>instance-00000001</name> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <memory>1048576</memory> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <vcpu>1</vcpu> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <metadata> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <nova:instance xmlns:nova="http://openstack.org/xmlns/libvirt/nova/1.0"> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <nova:package version="20.1.2"/> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <nova:name>cl_acrn</nova:name> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <nova:creationTime>2020-12-04 09:11:22</nova:creationTime> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <nova:flavor name="ds1G"> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <nova:memory>1024</nova:memory> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <nova:disk>10</nova:disk> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <nova:swap>0</nova:swap> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <nova:ephemeral>0</nova:ephemeral> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <nova:vcpus>1</nova:vcpus> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: </nova:flavor> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <nova:owner> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <nova:user uuid="b4646b0d513645c8ab6d0656b2e699ed">admin</nova:user> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <nova:project uuid="ac158184024043faba836ec3d347d0d7">admin</nova:project> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: </nova:owner> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <nova:root type="image" uuid="b3464729-fdb5-435e-9eff-3525760afa5b"/> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: </nova:instance> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: </metadata> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <os> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <type>hvm</type> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <loader>/usr/share/acrn/bios/OVMF.fd</loader> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <boot dev="hd"/> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: </os> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <features> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <acpi/> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <apic/> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: </features> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <clock offset="utc"/> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <devices> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <disk type="file" device="disk"> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <driver type="raw" cache="none"/> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <source file="/opt/stack/data/nova/instances/997103d3-0a60-4ce2-a85d-c42eb24cfd8b/disk"/> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <target dev="vda" bus="virtio"/> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: </disk> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <interface type="bridge"> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <mac address="fa:16:3e:46:97:e0"/> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <model type="virtio"/> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <source bridge="br-int"/> --> Why no mtu set in xml Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <target dev="tapd0358b23-d9"/> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <virtualport type="openvswitch"> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: <parameters interfaceid="d0358b23-d96b-4394-969d-32858b60e261"/> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: </virtualport> Dez 04 10:11:22 acrn1-NUC7i7DNHE nova-compute[8579]: </interface> : I checked the solution mentioned in [ https://bugs.launchpad.net/nova/+bug/1747496] and the source code which it said to add is already in my nova code. Anyone have any suggestions? Mit freundlichen Grüßen/ with best regards, Yatindra Shashi IoTG DE- Intel Corporation Munich, Germany Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928

1 0

[release] Release countdown for week R-19, Nov 30 - Dec 04
by Herve Beraud 04 Dec '20

04 Dec '20

Greetings Everyone! Development Focus ----------------- We are now past the Wallaby-1 milestone. Teams should now be focused on feature development and completion of release cycle goals [0]. [0] https://governance.openstack.org/tc/goals/selected/wallaby/index.html General Information ------------------- Our next milestone in this development cycle will be Wallaby-2, on 21 January, 2021. This milestone is when we freeze the list of deliverables that will be included in the Wallaby final release, so if you plan to introduce new deliverables in this release, please propose a change to add an empty deliverable file in the deliverables/wallaby directory of the openstack/releases repository. Now is also generally a good time to look at bugfixes that were introduced in the master branch that might make sense to be backported and released in a stable release. If you have any question around the OpenStack release process, feel free to ask on this mailing-list or on the #openstack-release channel on IRC. Upcoming Deadlines & Dates -------------------------- Cinder Spec Freeze: 18 December, 2020 Manila Spec Freeze: 25 December, 2020 Wallaby-2 Milestone: 21 January, 2021 Hervé Beraud (hberaud) and the Release Management Team -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----

1 0

[Interop]
by Kanevsky, Arkady 03 Dec '20

03 Dec '20

Team, I looked at https://www.openstack.org/brand/interop/. Looks like it had not been touched for a while. It does not list any add-on powered program. But it does list latest approved 2020.06 guidelines. Should we add it a verbiage for orchestration and DNS add-ons? And shortly about file system. Thanks, Arkady Kanevsky, Ph.D. SP Chief Technologist & DE Dell EMC office of CTO Dell Inc. One Dell Way, MS PS2-91 Round Rock, TX 78682, USA Phone: 512 7204955

2 4

[tripleo] wallaby-1 milestone and open specs
by Marios Andreou 03 Dec '20

03 Dec '20

Hi TripleO a reminder that this week is the Wallaby-1 milestone. As discussed at the last tripleo irc meeting [1] we should merge all specs by wallaby-1 if we are going to realistically deliver those things during W. Some specs have now merged and if you didn't already do so you can read them at [2]. There are still a few that are in review [3]. Call to all core reviewers please try and find time to review those over the next few days, in particular: network ports v2 @ [4], frrouter/bgp @ [5] and ephemeral heat [6]. Proposers of those specs please try respond quickly to reviewer comments so we can merge asap. thank you marios [1] http://eavesdrop.openstack.org/meetings/tripleo/2020/tripleo.2020-11-24-14.… [2] https://opendev.org/openstack/tripleo-specs/src/branch/master/specs/wallaby [3] https://review.opendev.org/q/project:openstack/tripleo-specs+status:open [4] https://review.opendev.org/c/openstack/tripleo-specs/+/760536 [5] https://review.opendev.org/c/openstack/tripleo-specs/+/758249 [6] https://review.opendev.org/c/openstack/tripleo-specs/+/765000

2 1

[neutron][stable] Backport of the patch which bumps RPC version
by Slawek Kaplonski 03 Dec '20

03 Dec '20

Hi, Some time ago we backported in Neutron patch [1] which caused bug [2]. Patch [1] was merged in the Ussuri development cycle so it is already in Ussuri and Victoria. Our mistake was that we merged it then without bump of the RPC version and without code which would provide backward compatybility between old agent and new neutron-server and that's why [2] happens. Now, as we know that, we have proposed patch [3] to fix it in master branch. And my question is - can we backport fix [3] to the stable/victoria and stable/ ussuri to fix the original issue caused by [1] there? In general I know that we shouldn't do that but here are the reasons why we would like to do it in this specific case: - rpc version which we want to change now wasn't changed since Train at least so there will be no any conflict with that, - bump rpc version now and provide backward compatybility on neutron-server will make upgrades Train->Ussuri and minor updates in Ussuri easier as there will be no similar issue like is described in [2] anymore, - patch [1] was already included in Ussuri and Victoria from master branch, it wasn't really cherry-picked there so it actually should be there since the beginning. Based on those reasons mentioned about and also becuase in general it is forbiden by stable policy to backport changes like that to stable branches I would like to know opinion from wider community, especially stable-core-maint team, about what would be the best approach to fix that issue: backport of [3] to stable/{ussuri,victoria} or revert [1] in stable/{ussuri,victoria}. [1] https://review.opendev.org/c/openstack/neutron/+/712632 [2] https://bugs.launchpad.net/neutron/+bug/1903531 [3] https://review.opendev.org/c/openstack/neutron/+/764108 -- Slawek Kaplonski Principal Software Engineer Red Hat

2 2

[neutron] default(ish) firewall rules
by Vladimir Prokofev 03 Dec '20

03 Dec '20

Hello. I'm running Queens private cloud with few separate projects inside. Guests in those projects have 2 networks - public, which is a provider network with public IP addresses, and private which is a VXLAN overlay network specific to the project. That's the setup, now here's the issue. They're mostly Windows guests there, and they tend to have browser service enabled on both public and private networks. This leads to situations where guests from one project can see guests in other projects over a public network via NetBIOS/SMB protocols, which is undesirable. I have two partial solutions in mind. Create some default firewall rule, similar to that exists by default for DHCP protocol that prohibit guests to act as DHCP server, but for UDP 137-139 port range. But not only I completely forgot how to do this(I think I saw some documentation about it ~2 years ago), but this will also block said protocol over private networks too, which is not an ideal solution. I would still love it if someone could point me to a proper documentation here. Second option is to add similar entries to security group rules. This will allow public/private interface differentiation by applying different security group to different interfaces, but introduces the possibility for cloud operator to delete those entries(either by mistake, or explicitly) which will lead to protocol being allowed once again. Anyone has any idea of a better solution here?

2 3

[tripleo] next meeting Tuesday Dec 08 @ 1400 UTC in #tripleo
by Marios Andreou 03 Dec '20

03 Dec '20

The next scheduled TripleO irc meeting is ** Tuesday 08th December at 1400 UTC in #tripleo. ** ** https://etherpad.opendev.org/p/tripleo-meeting-items ** Please add anything you want to raise at https://etherpad.opendev.org/p/tripleo-meeting-items This could be anything including review requests, blocking issues or to socialise ongoing or planned work. Our last meeting was held on Nov 24th - you can find the logs there http://eavesdrop.openstack.org/meetings/tripleo/2020/tripleo.2020-11-24-14.… thanks, marios

1 0

[ussuri] [neutron] deploy an additional compute node that resides in a different network
by Pavlos Basaras 03 Dec '20

03 Dec '20

1 1

[neutron] Drivers meeting agenda for 04.12.2020
by Slawek Kaplonski 03 Dec '20

03 Dec '20

Hi, Agenda for drivers meeting [1] this week have to new RFEs to discuss: * https://bugs.launchpad.net/neutron/+bug/1905115 * https://bugs.launchpad.net/neutron/+bug/1905295 And there is also "on demand" topic added by Rodolfo: "Smart-Nic Management Overall Design" (Nova spec). Neutron needs to add a new extension to provide to Nova the device profile information. This is a new string parameter added to the port blob and should be included when the port is created. Reference: https://review.opendev.org/c/openstack/nova-specs/+/742785/12/specs/wallaby… Rodolfo - is Your topic related to the RFE https://bugs.launchpad.net/neutron/+bug/1906602 ? See You tomorrow on the meeting :) [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda -- Slawek Kaplonski Principal Software Engineer Red Hat

2 1

Re: [all] Dynamic Zuul results table in Gerrit 3
by Radosław Piliszek 03 Dec '20

03 Dec '20

On Thu, Dec 3, 2020 at 10:33 AM Marcin Juszkiewicz <marcin.juszkiewicz(a)linaro.org> wrote: > > W dniu 03.12.2020 o 10:22, Radosław Piliszek pisze: > > Hello Fellow OpenStack and OpenDev Folks! > > > > TL;DR click on [3] and enjoy. > > Rename to *.user.js so Tampermonkey will recognize it as userscript and > add window around with Install button. > I, personally, hate this "feature" of Tampermonkey but sure - if it makes it easier for you. ;-) Done. Anyone - just click on "Raw" and you will be pestered by Tampermonkey to install the script. > > However, inspired by gibi's work, I decided to finally sit down and > > fix it to work with Gerrit 3 and here it comes: [3]. > > Works well on Chrome with Tampermonkey. Not tested others. > > Firefox with Tampermonkey - script works. > Yay, thanks for confirming! > > I hope you will enjoy this little helper (I do). > > Nice job! > Well, thank you! :-) > It does not catch all Zuul jobs. For Kolla patches AArch64 jobs are not > listed. I have already replied on IRC but will repeat here for others. The dynamic part includes all the running queues. However, the static part parses only a single comment and AArch64 is in a different one. I am obviously biased (being x86-only folk) but I find it more problematic than worth it to hack it any further. I hope a proper solution arrives sooner. :-) > > I know the script looks super fugly but it generally boils down to a > > mix of styles of 3 people and Gerrit having funky UI rendering. > > > Finally, I'd also like to thank hrw (Marcin Juszkiewicz) for linking > > me to the original Michel's script in 2019. > > YW. > -yoctozepto

1 0

[CLOUDKITTY] - Prometheus metrics.yml sample?
by Gaël THEROND 02 Dec '20

02 Dec '20

Hi everyone, I'm currently finishing our cloudkitty implementation, but I'm facing an issue. For now, our cloudkitty-processor process raise a traceback like this: http://paste.openstack.org/show/Y2ZiYPtZSKzvZk93yNWC/ I can't find any reliable documentation describing how to use prometheus with cloudkitty, so I'm kind of using the guess/read the code way to integrate it, but I'm a bit confused so far. My current metric.yml look like this: http://paste.openstack.org/show/6X23ZfVm1iDMruGy3Gpp/ I've created the appropriate group/service/threshold etc but it still continues to raise the same error. I'm using this openstack_exporter: https://github.com/openstack-exporter/openstack-exporter/releases/tag/v1.1.0 I'm running a Train release Openstack platform if it can help. So, if anyone is having a successful cloudkitty/prometheus integration willing to give a hand, I'll be more than happy ;-) Thanks!

1 0

[largescale-sig] Next meeting: December 2, 15utc
by Thierry Carrez 02 Dec '20

02 Dec '20

Hi everyone, We'll have a Large Scale SIG meeting this Wednesday in #openstack-meeting-3 on IRC, at 15UTC. You can doublecheck how it translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20201202T15 Our main topic will be to discuss how to best collect operator scaling experiences. Feel free to add other topics to our agenda at: https://etherpad.openstack.org/p/large-scale-sig-meeting Talk to you all later, -- Thierry Carrez

1 1

IRONIC BAREMETAL partitioned image not spawning.
by Akshay 346 02 Dec '20

02 Dec '20

Hello Team, I hope you all are keeping safe and doing good. I have a OpenStack setup up and running with ironic enabled. I am able to spawn a bare metal node with centos8.2 whole-disk image but when I spawn bare metal with partitioned image, it fails to spawn it stating the following trace ( Full trace back attached in the email): "2020-12-01 12:35:34.603 1 ERROR ironic.conductor.utils [req-0d3a375e-90a3-485d-a7c3-895c97c88006 - - - - -] Deploy failed for instance 463bd844-7f80-4c57-98dd-6ca8cfdb6121. Error: [Errno 2] No such file or directory: 'sgdisk': 'sgdisk': FileNotFoundError: [Errno 2] No such file or directory: 'sgdisk': 'sgdisk'". I have also installed sgdisk (yum install gdisk) on the qcow2 from which I build the partitioned image. Can anyone please guide how to debug it? Regards Akshay DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.

2 4

[kolla] cannot pull docker public hub images
by Adrian Andreias 02 Dec '20

02 Dec '20

Hi, None of the Kolla images on the Docker public registry are tagged. E.g. https://hub.docker.com/r/kolla/centos-source-nova-api Images don't even have the "latest" tag, though they were updated 15 hours ago. And therefore they can't be pulled: $ docker pull kolla/centos-source-nova-api Using default tag: latest Error response from daemon: manifest for kolla/centos-source-nova-api:latest not found: manifest unknown: manifest unknown Is there another public registry where ready-built Kolla images are available? Thanks Regards, Adrian Andreias https://fleio.com

4 6

Re: [neutron][openstack-ansible] Instances can only connect to provider-net via tenant-net but not directly
by Oliver Wenz 02 Dec '20

02 Dec '20

> Neutron sends this notification to the nova-api so You should check in nova-api > logs. > Whole workflow for that process of spawning vm is more or less like below: > 1. nova-compute asks neutron for port, > 2. neutron creates port and binds it with some mechanism driver - so it has > vif_type e.g. "ovs" or "linuxbridge" or some other, > 3. nova, based on that vif details plugs port to the proper bridge on host and > pauses instance until neutron will not do its job, > 4. neutron-l2-agent (linuxbrige or ovs) starts provisioning port and reports > to neutron-server when it is done, > 5. if there is no any provisioning blocks for that port in neutron db (can be > also one from the dhcp agent), neutron sends notification to nova-api that port > is ready, > 6. nova unpauses vm. > > In Your case it seems that on step 5 nova reports some error and that You > should IMO check. > Hi Slawek, thanks for the information and suggestion! I checked the nova-api-os-compute logs and it seems like there are network problems and an issue with wrong token scope: Dec 02 11:15:49 infra1-nova-api-container-83af52a6 nova-api-wsgi[84]: 2020-12-02 11:15:49.074 84 INFO nova.api.openstack.requestlog [req-1d56ad1c-03ea-4dcc-b9da-e4f6e73ccc52 920e739127a14018a55fb4422b0885e7 0f14905dab5546e0adec2b56c0f6be88 - default default] 192.168.110.201 "GET /v2.1/servers/2a1f6fbf-48f8-4e7f-bc36-7162bdaf7e20" status: 200 len: 1358 microversion: 2.1 time: 0.500669 Dec 02 11:15:49 infra1-nova-api-container-83af52a6 nova-api-wsgi[86]: 2020-12-02 11:15:49.256 86 INFO oslo.messaging._drivers.impl_rabbit [-] A recoverable connection/channel error occurred, trying to reconnect: [Errno 104] Connection reset by peer Dec 02 11:15:49 infra1-nova-api-container-83af52a6 uwsgi[48]: Wed Dec 2 11:15:49 2020 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request /v2.1/flavors/7c20746e-f6db-4344-9aa1-be926696ecf4 (ip 192.168.110.201) !!! Dec 02 11:15:49 infra1-nova-api-container-83af52a6 nova-api-wsgi[86]: 2020-12-02 11:15:49.318 86 INFO nova.api.openstack.requestlog [req-832f794d-db9b-4690-bb0c-8320e7beed47 920e739127a14018a55fb4422b0885e7 0f14905dab5546e0adec2b56c0f6be88 - default default] 192.168.110.201 "GET /v2.1/flavors/7c20746e-f6db-4344-9aa1-be926696ecf4" status: 200 len: 473 microversion: 2.1 time: 0.095833 Dec 02 11:15:57 infra1-nova-api-container-83af52a6 nova-api-wsgi[79]: 2020-12-02 11:15:57.000 79 INFO nova.api.openstack.requestlog [req-2c061260-88f4-4183-a74a-ea59d1ff1ae0 b044fe42a4644837a3bd40beec378876 226e9c9f1fb94c8ab271490ad79c6873 - default default] 192.168.110.201 "HEAD /" status: 200 len: 417 microversion: - time: 0.001837 Dec 02 11:15:57 infra1-nova-api-container-83af52a6 nova-api-wsgi[88]: 2020-12-02 11:15:57.214 88 INFO oslo.messaging._drivers.impl_rabbit [-] A recoverable connection/channel error occurred, trying to reconnect: [Errno 104] Connection reset by peer Dec 02 11:15:57 infra1-nova-api-container-83af52a6 uwsgi[48]: Wed Dec 2 11:15:57 2020 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request /v2.1/os-server-external-events (ip 192.168.110.201) !!! Dec 02 11:15:57 infra1-nova-api-container-83af52a6 uwsgi[48]: /openstack/venvs/nova-21.1.0/lib/python3.6/site-packages/oslo_policy/policy.py:1007: UserWarning: Policy os_compute_api:os-server-external-events:create failed scope check. The token used to make the request was project scoped but the policy requires ['system'] scope. This behavior may change in the future where using the intended scope is required Dec 02 11:15:57 infra1-nova-api-container-83af52a6 uwsgi[48]: warnings.warn(msg) Dec 02 11:15:57 infra1-nova-api-container-83af52a6 nova-api-wsgi[88]: 2020-12-02 11:15:57.715 88 INFO nova.api.openstack.compute.server_external_events [req-759c5752-c80b-46f2-b3df-0fa126605895 d9a2e96567ec4670bc60dbcc8f66305f 474b7aa9b7894d6782402135c6ef4c2a - default default] Creating event network-changed:ed4a9455-a33c-454c-b74f-b314751cce3d for instance 2a1f6fbf-48f8-4e7f-bc36-7162bdaf7e20 on bc1blade15 Dec 02 11:15:57 infra1-nova-api-container-83af52a6 nova-api-wsgi[88]: 2020-12-02 11:15:57.734 88 INFO nova.api.openstack.requestlog [req-759c5752-c80b-46f2-b3df-0fa126605895 d9a2e96567ec4670bc60dbcc8f66305f 474b7aa9b7894d6782402135c6ef4c2a - default default] 192.168.110.201 "POST /v2.1/os-server-external-events" status: 200 len: 179 microversion: 2.1 time: 0.533910 Dec 02 11:16:09 infra1-nova-api-container-83af52a6 nova-api-wsgi[82]: 2020-12-02 11:16:09.007 82 INFO nova.api.openstack.requestlog [req-064600c9-196e-4388-978c-00b0f5560b2e 745ecbee83d041c6ba92f9e07ba744d5 a2fd11a3bfdd47c8893e18a6f3b7dfa3 - default default] 192.168.110.201 "HEAD /" status: 200 len: 417 microversion: - time: 0.001638 Dec 02 11:16:16 infra1-nova-api-container-83af52a6 nova-api-wsgi[77]: 2020-12-02 11:16:16.432 77 INFO oslo.messaging._drivers.impl_rabbit [-] A recoverable connection/channel error occurred, trying to reconnect: [Errno 104] Connection reset by peer Dec 02 11:16:16 infra1-nova-api-container-83af52a6 uwsgi[48]: Wed Dec 2 11:16:16 2020 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request /v2.1/os-server-external-events (ip 192.168.110.201) !!! Dec 02 11:16:16 infra1-nova-api-container-83af52a6 uwsgi[48]: /openstack/venvs/nova-21.1.0/lib/python3.6/site-packages/oslo_policy/policy.py:1007: UserWarning: Policy os_compute_api:os-server-external-events:create failed scope check. The token used to make the request was project scoped but the policy requires ['system'] scope. This behavior may change in the future where using the intended scope is required Dec 02 11:16:16 infra1-nova-api-container-83af52a6 uwsgi[48]: warnings.warn(msg) Dec 02 11:16:16 infra1-nova-api-container-83af52a6 nova-api-wsgi[77]: 2020-12-02 11:16:16.939 77 INFO nova.api.openstack.compute.server_external_events [req-71a40ea1-cf64-46d5-9675-d00d539f1922 d9a2e96567ec4670bc60dbcc8f66305f 474b7aa9b7894d6782402135c6ef4c2a - default default] Creating event network-vif-plugged:5cbc8608-8545-4eb3-a745-23ca912347ec for instance ea72988b-83eb-4640-adaa-e24e0c3d018d on bc1blade15 Dec 02 11:16:16 infra1-nova-api-container-83af52a6 nova-api-wsgi[77]: 2020-12-02 11:16:16.958 77 INFO nova.api.openstack.requestlog [req-71a40ea1-cf64-46d5-9675-d00d539f1922 d9a2e96567ec4670bc60dbcc8f66305f 474b7aa9b7894d6782402135c6ef4c2a - default default] 192.168.110.201 "POST /v2.1/os-server-external-events" status: 200 len: 183 microversion: 2.1 time: 0.526920 Dec 02 11:16:17 infra1-nova-api-container-83af52a6 nova-api-wsgi[71]: 2020-12-02 11:16:17.422 71 INFO oslo.messaging._drivers.impl_rabbit [-] A recoverable connection/channel error occurred, trying to reconnect: [Errno 104] Connection reset by peer Kind regards, Oliver

2 1

[Openstack][CFP] Virtualization & IaaS Devroom
by Piotr Kliczewski 02 Dec '20

02 Dec '20

We are excited to announce that the call for proposals is now open for the Virtualization & IaaS devroom at the upcoming FOSDEM 2021, to be hosted virtually on February 6th 2021. This year will mark FOSDEM’s 21th anniversary as one of the longest-running free and open source software developer events, attracting thousands of developers and users from all over the world. Due to Covid-19, FOSDEM will be held virtually this year on February 6th & 7th, 2021. About the Devroom The Virtualization & IaaS devroom will feature session topics such as open source hypervisors and virtual machine managers such as Xen Project, KVM, bhyve, and VirtualBox, and Infrastructure-as-a-Service projects such as KubeVirt, Apache CloudStack, Foreman, OpenStack, oVirt, QEMU and OpenNebula. This devroom will host presentations that focus on topics of shared interest, such as KVM; libvirt; shared storage; virtualized networking; cloud security; clustering and high availability; interfacing with multiple hypervisors; hyperconverged deployments; and scaling across hundreds or thousands of servers. Presentations in this devroom will be aimed at users or developers working on these platforms who are looking to collaborate and improve shared infrastructure or solve common problems. We seek topics that encourage dialog between projects and continued work post-FOSDEM. Important Dates Submission deadline: 20th of December Acceptance notifications: 25th of December Final schedule announcement: 31st of December Recorded presentations upload deadline: 15th of January Devroom: 6th February 2021 Submit Your Proposal All submissions must be made via the Pentabarf event planning site[1]. If you have not used Pentabarf before, you will need to create an account. If you submitted proposals for FOSDEM in previous years, you can use your existing account. After creating the account, select Create Event to start the submission process. Make sure to select Virtualization and IaaS devroom from the Track list. Please fill out all the required fields, and provide a meaningful abstract and description of your proposed session. Submission Guidelines We expect more proposals than we can possibly accept, so it is vitally important that you submit your proposal on or before the deadline. Late submissions are unlikely to be considered. All presentation slots are 30 minutes, with 20 minutes planned for presentations, and 10 minutes for Q&A. All presentations will need to be pre-recorded and put into our system at least a couple of weeks before the event. The presentations should be uploaded by 15th of January and made available under Creative Commons licenses. In the Submission notes field, please indicate that you agree that your presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 license and that you agree to have your presentation recorded. For example: "If my presentation is accepted for FOSDEM, I hereby agree to license all recordings, slides, and other associated materials under the Creative Commons Attribution Share-Alike 4.0 International License. Sincerely, <NAME>." In the Submission notes field, please also confirm that if your talk is accepted, you will be able to attend the virtual FOSDEM event for the Q&A. We will not consider proposals from prospective speakers who are unsure whether they will be able to attend the FOSDEM virtual event. If you are experiencing problems with Pentabarf, the proposal submission interface, or have other questions, you can email our devroom mailing list[2] and we will try to help you. Code of Conduct Following the release of the updated code of conduct for FOSDEM, we'd like to remind all speakers and attendees that all of the presentations and discussions in our devroom are held under the guidelines set in the CoC and we expect attendees, speakers, and volunteers to follow the CoC at all times. If you submit a proposal and it is accepted, you will be required to confirm that you accept the FOSDEM CoC. If you have any questions about the CoC or wish to have one of the devroom organizers review your presentation slides or any other content for CoC compliance, please email us and we will do our best to assist you. Call for Volunteers We are also looking for volunteers to help run the devroom. We need assistance with helping speakers to record the presentation as well as helping with streaming and chat moderation for the devroom. Please contact devroom mailing list [2] for more information. Questions? If you have any questions about this devroom, please send your questions to our devroom mailing list. You can also subscribe to the list to receive updates about important dates, session announcements, and to connect with other attendees. See you all at FOSDEM! [1] <https://penta.fosdem.org/submission/FOSDEM17>https://penta.fosdem .org/submission/FOSDEM21 [2] iaas-virt-devroom at lists.fosdem.org

2 1

[tacker] Please check my slide for the discussion with ETSI-NFV
by Yoshito Ito 02 Dec '20

02 Dec '20

Hi tacker team, As I mentioned in the previous IRC meeting, I uploaded my slide [1] for the discussion with ETSI NFV members. The meeting will be held on 4th Dec so I hope you to put your comments or questions on the etherpad [2] soon. [1] https://www2.slideshare.net/secret/zQLlzi7wwJ5FGQ [2] https://etherpad.opendev.org/p/tacker-meeting Thanks, Yoshito Ito

1 0

[tc] weekly update + meeting
by Mohammed Naser 01 Dec '20

01 Dec '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 - Remove Qinling project team https://review.opendev.org/c/openstack/governance/+/764523 - Clarify the requirements for supports-api-interoperability https://review.opendev.org/c/openstack/governance/+/760562 - Add Resolution of TC stance on the OpenStackClient https://review.opendev.org/c/openstack/governance/+/759904 - Remove Searchlight project team https://review.opendev.org/c/openstack/governance/+/764530 - Update example and oslo code usage in JSON->YAML goal https://review.opendev.org/c/openstack/governance/+/764261 - Remove already done use-builtin-mock from goal https://review.opendev.org/c/openstack/governance/+/764262 - Generate the TC liaisons assignments https://review.opendev.org/c/openstack/governance/+/763810 - Add assert:supports-standalone https://review.opendev.org/c/openstack/governance/+/722399 - Remove assert_supports-zero-downtime-upgrade tag https://review.opendev.org/c/openstack/governance/+/761975 - Clarify impact on releases for SIGs https://review.opendev.org/c/openstack/governance/+/752699## General Changes - Correct Dan Smith IRC nick in TC liaisons https://review.opendev.org/c/openstack/governance/+/763809 - Propose Kendall Nelson for vice chair https://review.opendev.org/c/openstack/governance/+/762014 - Add election schedule exceptions in charter https://review.opendev.org/c/openstack/governance/+/751941 ## Project Updates - Add Magpie charm to OpenStack charms https://review.opendev.org/c/openstack/governance/+/762820 ## Other Reminders - [TC] Weekly meeting December 03. If you would like to add topics for discussion, please go to https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting and fill out your suggestions by Wednesday, December 02, at 2100 UTC. Thanks for reading! Mohammed & Kendall -- Mohammed Naser VEXXHOST, Inc.

1 0

[neutron] Team meeting agenda
by Slawek Kaplonski 01 Dec '20

01 Dec '20

Hi neutrinos, Just quick reminder that today at 2pm UTC we will have out weekly team meeting. Agenda is available at [1]. If You have anything to discuss there, please add it to the "On demand" section there. [1] https://wiki.openstack.org/wiki/Network/Meetings -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0