December 2020 - openstack-discuss

[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