- openstack-discuss - lists.openstack.org

[tc][goals] community feedback on 'stabilization' goal
by Mohammed Naser 11 Dec '20

11 Dec '20

Hi there, Over the last TC meeting, we exchanged opinions about the new goal selection. It was discussed that due to the extraordinary situation this year, we could have a loose goal instead. Therefore, we would like to propose having a stabilization cycle this release. Some ideas discussed for this “stabilization” cycle (would be all of those): 1. Use this time to rest and relax, no need to do something. 2. Use this time to finish up this really cool thing you've been trying to find time to, and share with us to recognize. 3. Check out these existing goals/popup teams that might interest you if you want to invest time in something different/new. As a reminder that we don't have to do a community goal for every release, we are leaving this open and would like to know what the community thinks. Feel free to send over your thoughts, Regards, -- Mohammed Naser VEXXHOST, Inc.

4 3

[tc] weekly meeting summary
by Mohammed Naser 11 Dec '20

11 Dec '20

Hi everyone, Here's a summary of what happened in our TC weekly meeting last Thursday, Dec 10. # ATTENDEES (LINES SAID) - mnaser (115) - apevec (60) - gmann (57) - yoctozepto (26) - mugsie (26) - fungi (20) - jungleboyj (14) - noonedeadpunk (9) - diablo_rojo__ (6) - marios|rover (6) - ricolin (6) - zbr (4) - weshay|ruck (2) - jrosser (2) - akahat (1) - gouthamr (1) # MEETING SUMMARY 1. Rollcall 2. Follow up on past action items DONE: mnaser change all reference of meeting time to go towards eavesdrop for single source of truth DONE: mnaser remove openstacksdk discussions for future meetings DONE: mnaser remove project retirement from agenda 3. X cycle goal selection start It was discussed that due to the extraordinary situation this year, perhaps we could have a stabilization goal instead. As a reminder that we don't have to do a community goal for every release, we are leaving this open and will ask folks to update the proposed goal page with something they worked on. Some ideas discussed for this "stabilization" cycle: 1) Use this time to rest and relax, no need to do something. 2) Use this time to finish up this really cool thing you've been trying to find time to, and share with us to recognize. 3) Check out these existing goals/popup teams that might interest you if you want to invest time in something different/new We will keep this as an open discussion item to track the progress and will keep collecting new ideas for goals. 4. Audit and clean-up tags (gmann) For API interoperability tag, patch is merged; gmann will start the ML to encourage projects to start applying for that tag. We will keep this action to discuss the progress of getting projects in, and we will have each tag one by. 5. X cycle release name vote recording (gmann) Because the votes were not recorded, we are asking TC members to list what they voted for on the mailing list http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019337… 6. CentOS 8 releases are discontinued / switch to CentOS 8 Stream (gmann/yoctozepto) Community members from RH were present to help talk through the changes that are occurring with the introduction of CentOS Stream 8. mnaser work to find time for community deployment projects + centos/rdo team to meet to help teams get more information about the upcoming change # ACTION ITEMS 1. mnaser send email to ML to find volunteers to help drive goal selection 2. gmann complete retirement of searchlight & qinling 3. diablo_rojo complete retirement of karbor 4. mnaser work to find time for community deployment projects + centos/rdo team To read the full logs of the meeting, please refer to http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-12-10-15.01.log.html -- Mohammed Naser VEXXHOST, Inc.

1 0

[nova][gate] nova-multi-cell job failing test_*_with_qos_min_bw_allocation
by melanie witt 11 Dec '20

11 Dec '20

Howdy all, FYI we have gate failures of the recently added test_*_with_qos_min_bw_allocation tests [1] in the nova-multi-cell job on the master, stable/victoria, and stable/ussuri branches. The failures occur during cross cell migrations. I have opened a bug for the failure on the master branch: * https://bugs.launchpad.net/nova/+bug/1907522 The issue here is that we fail to create port bindings in neutron during a cross cell migration in the superconductor: nova.exception.PortBindingFailed: Binding failed for port <port uuid> and that corresponds to a failure in the neutron server log where it fails the port binding with: neutron_lib.exceptions.placement.UnknownResourceProvider: No such resource provider known by Neutron I don't yet know what is going on here ^. For the bug on stable/victoria and stable/ussuri I have opened this bug: * https://bugs.launchpad.net/nova/+bug/1907511 and have a WIP stable-only patch proposed that needs tests: https://review.opendev.org/c/openstack/nova/+/766364 I just wanted to see ASAP if the nova-multi-cell job will pass on it. The issue here ^ is that during a cross cell migration, we aren't targeting the cell database for the target host when we attempt to lookup the service record of the target host. For the stable branch failures I think the failure rate is 100% and it looks like it might also be 100% for the master branch failures. Cheers, -melanie [1] https://review.opendev.org/c/openstack/tempest/+/694539

2 3

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

11 Dec '20

Friendly reminder that submission deadline for Virtualization & IaaS dev room at Fosdem is on 20th of December.

1 0

[TC][all] X Release name polling
by Sean McGinnis 11 Dec '20

11 Dec '20

Hey everyone, We recently collected naming suggestions for the X release name. A lot of great suggestions by the community! Much more than I had expected for this letter. As a reminder, starting with the W release we had changed the process for selecting the name [1]. We collected suggestions from the community, then the members of the TC voted in a poll [2] to select which name(s) out of the suggestions to go with. The vetting of the top choices from that process is happening now, and we should have a official result soon. This is a bit of a mea culpa from me about an issue with how this was conducted though. The naming process specifically states: "the poll should be run in a manner that allows members of the community to see what each TC member voted for." When I set up the CIVS poll, I failed to check the box that would allow seeing the detailed results of the poll. So while we do have the winning names, we are not able to see which TC members voted and how. I apologize for missing this step (and I've noted that we really should add some detailed process for future coordinators to follow!). I believe the intent with that part of the process was to allow the community to see how your elected TC members voted as one factor to consider when reelecting anyone. Also transparency to show that no one is pushing through their own choices, circumventing any process. The two options I see at this point would be to either redo the entire naming poll, or just try to capture what TC members voted for somewhere so we have a record of that. It's been long enough now since taking the poll that I don't expect TC members to remember exactly how they ranked things. But we've also started the vetting process through the Foundation (lawyers engaged, etc) so I'd really rather not start over if we can avoid it. If TC members could respond here with what they remember voting for, I hope that is enough to satisfy the spirit of the defined process. If there are any members of the community that have a strong objection to this, please say so. I leave it up to the TC then to decide how to proceed. Again, apologies for missing this step. Otherwise, I think the process has worked well, and I hope we can declare an official X name shortly. Thanks! Sean [1] https://governance.openstack.org/tc/reference/release-naming.html#release-n… [2] https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_7e6e96070af39fe7

8 9

[nova] weekly meeting is canceled during the holidays
by Balázs Gibizer 11 Dec '20

11 Dec '20

Hi, As we agreed on the weekly meeting the nova meeting schedule will look like the following during the next weeks: Dec 17 2020 16:00 UTC, #openstack-meeting-3 Dec 24 2020 16:00 UTC, Cancelled Dec 31 2020 16:00 UTC, Cancelled Jan 7 2021 16:00 UTC, #openstack-meeting-3 Cheers, gibi

1 0

About fuel
by sunkai 11 Dec '20

11 Dec '20

Hello, I have a question to ask you。How do I modify the disk configuration of fuel for the node? I need to add some configuration items。How can I fulfill this requirement？Looking forward to your reply，Thankyou very much!!!

1 0

[all][policy] Canceling policy-popup's 24th Dec meeting
by Ghanshyam Mann 10 Dec '20

10 Dec '20

Hello Everyone, Due to new year vacations, we decided to cancel the policy popup 24th Dec meeting and will resume meeting from 7th Jan onwards. -gmann

1 0

[all][tc][policy] Progress report of consistent and secure default policies pop-up team
by Ghanshyam Mann 10 Dec '20

10 Dec '20

Hello Everyone, Please find this month's progress on 'Consistent and Secure Default Policies Popup Team'. Meeting notes: ============ * We discussed progress on policy format migration from JSON->YAML and updates required in oslo.upgradecheck is merged now. * As you saw in another email thread by Lance[1], he has started the work on many projects. We will be adding the test coverage also in those, I will be able to help lance on some of them in next month. * We will define the common personas in oslo.policy for reusing it on the service side[2] * Below are the 'Action items, by person': ** gmann to check with abhishekk on glance point in meeting agenda ** gmann to push common persona on oslo policy and release 3.6.1 and lbragstad to review that ** lbragstad/gmann to push common persona on Oslo policy and release 3.6.1 and lbragstad to review that ** lbragstad to finish placement as first ** raildo to update https://review.opendev.org/#/c/743318/ Progress so far: ============ * Popup team meet twice in a month and discuss and work on progress and pre-work to do. - https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popu… * Pre-work to provide a smooth migration path to the new policy <here we will add any pre-work we need to do before more project start moving towards new policy> ** Migrate Default Policy Format from JSON to YAML - This is now a community-wide goal, refer my separate ML thread for progress - https://review.opendev.org/q/topic:%22policy-json-to-yaml%22+(status:open%2… ** Improving documentation about target resources (oslo.policy) - https://bugs.launchpad.net/oslo.policy/+bug/1886857 - raildo pushed the patch which is under review: https://review.opendev.org/#/c/743318/ * Team Progress: (list of a team interested or have volunteer to work) ** Keystone (COMPLETED; use as a reference) ** Nova (COMPLETED; use as a reference) ** Cyborg (COMPLETED) ** Work started in other projects *** https://review.opendev.org/q/topic:%22secure-rbac%22+(status:open%20OR%20st… [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019313… [2] https://review.opendev.org/c/openstack/oslo.policy/+/766536 -gmann

1 0

Multiple VM ports on provider networks / dhcp fails
by Eric K. Miller 10 Dec '20

10 Dec '20

Hi, We ran into an issue recently that I haven't been able to figure out (this environment is on Stein which uses DVR). It involves an environment with many provider networks that connect to a legacy environment as well as many tenant networks. We create a server on a tenant network and add ports to this afterwards with each port attached to its respective provider network. The provider networks have "None" for the "gateway" property, so we don't have multiple default routes added to the routing table. We have a single subnet which has DHCP enabled and a proper allocation pool on its subnet. Note that this is a CentOS 8 server we are testing with, which has "no" ifcfg files for the additional ports, and so we rely on CentOS using DHCP by default. After adding the first port, the DHCP client does its job and requests an IP, which succeeds - so the DHCP server in the respective network namespace is responding fine. However, after adding the second port, it appears the DHCP client is sending requests out the network (we can see this traffic when tcpdump'ing the respective tap interface on the host), but the DHCP server is not replying. After looking at OpenVSwitch flows, it appears that DHCP broadcast traffic is being dropped for the second network. This does NOT happen with tenant networks. I can add multiple ports, each connected to its respective tenant network, and an IP is assigned to each interface that appears in CentOS immediately after the port has been added. Is there something special that is blocking the creation of the DHCP flow for subsequent provider network ports? NOTE that non-DHCP traffic flows fine if we create an ifcfg file with a static IP set to the address that DHCP should have set the interface to - it just appears that DHCP traffic is not flowing to the DHCP namespace for second and subsequent ports/networks. Thanks! Eric

1 0

[all][stable] bandit 1.6.3 drops py2 support
by Lee Yarwood 10 Dec '20

10 Dec '20

Hello all, $subject [1][2] is breaking various <= stable/train jobs where we attempt to pull bandit in while still using py2. This has been reported upstream and it looks like the 1.6.3 release may end up being yanked. If it isn't I've proposed the following requirements change to try to cap bandit to the 1.6.2 release, assuming this is safe to do on stable: Cap bandit at 1.6.2 when using py2 https://review.opendev.org/c/openstack/requirements/+/766170 Cheers, [1] https://github.com/PyCQA/bandit/releases/tag/1.6.3 [2] https://github.com/PyCQA/bandit/pull/615 [3] https://github.com/PyCQA/bandit/issues/663 -- Lee Yarwood A5D1 9385 88CB 7E5F BE64 6618 BCA6 6E33 F672 2D76

5 12

Fwd: [SAVE THE DATE] End of Year Contributor Celebration Event
by Kendall Nelson 10 Dec '20

10 Dec '20

Hello Everyone! Wanted to take a moment to extend this invite to the k8s end of year celebration to the OpenStack community :) Their TOC asked me to invite our TC, but since they call out wanting both friends and family to attend, mnaser and I thought to invite all of you as well :) Hope to see you there! -Kendall Nelson (diablo_rojo) ---------- Forwarded message --------- From: Alison Dowdney <alison(a)alisondowdney.com> Date: Fri, Nov 13, 2020 at 1:53 PM Subject: [SAVE THE DATE] End of Year Contributor Celebration Event To: <kubernetes-dev(a)googlegroups.com>, <leads(a)kubernetes.io> Hey there everyone, Thanks for your feedback! When we asked what you wanted to do for a “contributor summit”, most of you overwhelmingly chose to do something social to bring the community together. With that, we’d like to announce that this year’s “summit” will be a Contributor Celebration. There will be 🎂 TL;DR - “Hallway track” event after 1.20 release, December 10-13th - Event will use Discord <https://discord.com>[1] - Games and other social activities (taking suggestions) - Hangouts and hackathons - Friends and family are invited - Event website <https://k8s.dev/celebration>[2] - Registration form <https://forms.gle/51tqQgxuHxLaeU1P8>[3] It's been a rough year, and without any in person events we've lost the best part of the Contributor Summits - the Hallway Track. The Kubernetes Contributor Celebration is an attempt to reclaim that and celebrate our accomplishments. It's a time for us to relax, chat, and do something fun with your fellow contributors! 🏖 We realize that some of you may not be into games/trivia, so this year we’re going full casual. This isn’t meant to be stressful or yet-another-virtual event. If you just want to come and hang out in chat, or listen in on the trivia, then that’s ok. We’re also leaving enough open options to do fun things, for example someone wanted to play a saxophone for the community, that’s totally an option 🎷. The event website <https://k8s.dev/celebration>[2] will be the source of truth for all event information with updates being sent to the list. [1]: https://discord.com [2]: https://k8s.dev/celebration [3]: https://forms.gle/51tqQgxuHxLaeU1P8 Many Thanks, Alison on behalf of the Contributor Celebration Team -- You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe(a)googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/CALLkKiDfDah-YykTkyxKsC-nO… <https://groups.google.com/d/msgid/kubernetes-dev/CALLkKiDfDah-YykTkyxKsC-nO…> .

1 0

[manila] No IRC meeting on 24th and 31st Dec 2020
by Goutham Pacha Ravi 10 Dec '20

10 Dec '20

Hi there zorillas, As discussed during the weekly IRC meeting today, we're not going to meet on 24th and 31st December due to these dates coinciding with holidays in many parts of the world where our contributors live. If you have concerns in the meantime, please let us know on this mailing list, or on the #openstack-manila IRC channel on freenode. We're meeting on IRC as usual at 1500 UTC next Thursday, 17th Dec 2020 on #openstack-meeting-alt. [1] Since we'll be in a holiday mood, we'd love to see you all in ugly sweaters and mismatched socks during this meeting. Thanks, Goutham [1] https://wiki.openstack.org/wiki/Manila/Meetings

1 0

[nova-compute] Failed to publish message to topic 'scheduler_fanout'
by Tony Liu 10 Dec '20

10 Dec '20

Hi, With Ussuri, failed to launch VM and saw such error from nova-compute. Didn't see any error in nova-api, nova-conductor and nova-scheduler. Did some search and not found any similar cases. Wondering anyone has ever hit this issue? ================================================= 2020-12-09 13:24:29.333 8 ERROR oslo.messaging._drivers.impl_rabbit [req-4226ac03-a5b7-446a-a74b-2785f9818927 - - - - -] [3830bc00-1541-4951-b4ed-e73faafaa78c] AMQP server on 10.6.20.21:5672 is unreachable: connection already closed. Trying again in 1 seconds.: amqp.exceptions.RecoverableConnectionError: connection already closed 2020-12-09 13:24:30.361 8 INFO oslo.messaging._drivers.impl_rabbit [req-4226ac03-a5b7-446a-a74b-2785f9818927 - - - - -] [3830bc00-1541-4951-b4ed-e73faafaa78c] Reconnected to AMQP server on 10.6.20.21:5672 via [amqp] client with port 55524. 2020-12-09 13:26:28.377 8 ERROR oslo.messaging._drivers.impl_rabbit [req-4226ac03-a5b7-446a-a74b-2785f9818927 - - - - -] Failed to publish message to topic 'scheduler_fanout': : amqp.exceptions.MessageNacked 2020-12-09 13:26:28.377 8 ERROR oslo.messaging._drivers.impl_rabbit [req-4226ac03-a5b7-446a-a74b-2785f9818927 - - - - -] Unable to connect to AMQP server on 10.6.20.21:5672 after inf tries: : amqp.exceptions.MessageNacked 2020-12-09 13:26:28.378 8 ERROR oslo_service.periodic_task [req-4226ac03-a5b7-446a-a74b-2785f9818927 - - - - -] Error during ComputeManager._sync_scheduler_instance_info: oslo_messaging.exceptions.MessageDeliveryFailure: Unable to connect to AMQP server on 10.6.20.21:5672 after inf tries: ================================================= Thanks! Tony

2 2

[openstack-helm] No meetings for the rest of 2020
by Gage Hugo 10 Dec '20

10 Dec '20

Hello everyone, With holidays approaching and people being out, we are going to cancel the openstack-helm meetings for the remainder of the year. We will meet again in 2021 on Jan 5th. Have a Happy Holidays and Happy New Year! Stay Safe!

1 0

[security] Security SIG meetings cancelled until 2021
by Gage Hugo 10 Dec '20

10 Dec '20

Hello everyone, With holidays approaching and people being out, we are going to cancel the security sig meetings for the remainder of the year. We will meet again in 2021 on Jan 7th. Have a Happy Holidays and Happy New Year! Stay Safe!

1 0

[neutron] Drivers meeting agenda - Friday 11.12.2020
by Slawek Kaplonski 10 Dec '20

10 Dec '20

Hi, For tomorrow drivers meeting we have 3 RFEs to discuss: * https://bugs.launchpad.net/neutron/+bug/1905295 * https://bugs.launchpad.net/neutron/+bug/1905391 * https://bugs.launchpad.net/neutron/+bug/1907089 If You have anything else to discuss with the drivers team, please add it to the "On Demand" agenda at https://wiki.openstack.org/wiki/Meetings/NeutronDrivers Please read them and see You tomorrow on the meeting :) -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[release] weekly meeting skip
by Herve Beraud 10 Dec '20

10 Dec '20

Hello everyone, Since we don't have specific actions to manage for this week and nothing took place in our corresponding agenda, we will be skipping week's meeting. Also notice that the meeting of the next 3 weeks will be skipped too as we haven't specific actions to manage. If an emergency happens I'll let you know and I'll trigger a meeting next week. It's a good opportunity for us to take a look to see what action items defined during our PTG session remains to be done. At first glance more or less everything seems already done. If you plan to take PTO during the next few weeks then please let us know by updating the 'Team availability notes' that correspond to the given weeks, it could help us to avoid the "Bystander effect". Thanks for reading, Regards, -- 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

[OpenStack-discuss] doc-build-failures
by Stone, Ronald 10 Dec '20

10 Dec '20

Hi, Starting Tuesday several contributors to StarlingX docs can no longer successfully perform local doc builds: $ tox -e docs docs installed: alabaster==0.7.12,Babel==2.9.0,certifi==2020.11.8,chardet==3.0.4,colorama==0.4.4,docutils==0.15.2,dulwich==0.20.14,idna==2.10,imagesize==1.2.0,Jinja2==2.11.2,MarkupSafe==1.1.1,openstackdocstheme==2.2.7,os-api-ref==2.1.0,packaging==20.7,pbr==5.5.1,Pygments==2.7.2,pyparsing==2.4.7,pytz==2020.4,PyYAML==5.3.1,requests==2.25.0,six==1.15.0,snowballstemmer==2.0.0,Sphinx==3.3.1,sphinxcontrib-applehelp==1.0.2,sphinxcontrib-devhelp==1.0.2,sphinxcontrib-htmlhelp==1.0.3,sphinxcontrib-jsmath==1.0.1,sphinxcontrib-qthelp==1.0.3,sphinxcontrib-serializinghtml==1.1.4,urllib3==1.26.2 docs run-test-pre: PYTHONHASHSEED='662' docs run-test: commands[0] | sphinx-build -a -E -W -d doc/build/doctrees -b html doc/source doc/build/html ERROR: InvocationError for command could not find executable sphinx-build ___________________________________ summary ___________________________________ ERROR: docs: commands failed The executable sphinx-build.exe is missing from docs/.tox/docs/Scripts/ If manually restored, it is deleted the next time tox -e docs is run. Deleting .tox before rerunning does not help. Wondering if anyone is seeing this behavior with OpenStack docs and if it might be related to recent pip and virtualenv changes. Ron

1 0

[puppet] Broken CI because of missing powertools repo
by Takashi Kajinami 10 Dec '20

10 Dec '20

Hello, Some of you might have noticed this, but currently integration jobs and litmus jobs for puppet projects are failing because of missing powertools repo, which was caused by recent change in delorean-deps.repo provided by RDO (IIUC). I filed a bug[1] to track this issue and submitted a short-term fix which looks promising as per results in CIs. [1] https://bugs.launchpad.net/puppet-openstack-integration/+bug/1907323 [2] https://review.opendev.org/c/openstack/puppet-openstack-integration/+/766213 Please refrain from rechecking any puppet patches (I guess it also affects Victoria and Ussuri), until we land the fix. Thank you for your understanding and patience. Thank you, Takashi Kajinami

1 0

[cinder] wallaby R-18 mid-cycle summary available
by Brian Rosmaita 09 Dec '20

09 Dec '20

In case you missed the exciting cinder R-18 virtual mid-cycle session, I've posted a summary: https://wiki.openstack.org/wiki/CinderWallabyMidCycleSummary It includes a link to the recording (in case you want to see what you missed or if you want to re-live the excitement). We're planning to have another mid-cycle session the week of R-9. cheers, brian

1 0

[cyborg] No weekly meeting - December 10
by yumeng bao 09 Dec '20

09 Dec '20

Hello guys! As this week, cores of the team are either out of office, or busy with their company’s internal things before the new year holiday. As such, we are cancelling the December 10th meeting. If no other cancelling ML shows up, you can expect that meeting will be resumed next week on December 17th. Regards， Yumeng

1 0

[all]OpenStack + CentOS
by DHilsbos＠performair.com 09 Dec '20

09 Dec '20

All; As you may or may not know; yesterday morning RedHat announced the end of CentOS as a rebuild distribution[1]. "CentOS" will be retired in favor of the recently announced "CentOS Stream." Can OpenStack be installed on CentOS Stream? Since CentOS Stream is currently at 8, the question really is: Can OpenStack Victoria be installed on CentOS Stream 8? How about Ussuri? Thank you, Dominic L. Hilsbos, MBA Director - Information Technology Perform Air International Inc. DHilsbos(a)PerformAir.com<mailto:DHilsbos@PerformAir.com> www.PerformAir.com<http://www.PerformAir.com> [1: https://blog.centos.org/2020/12/future-is-centos-stream/] Dominic L. Hilsbos, MBA Director - Information Technology [Perform Air International, Inc.] DHilsbos(a)PerformAir.com<mailto:DHilsbos@PerformAir.com> 300 S. Hamilton Pl. Gilbert, AZ 85233 Phone: (480) 610-3500 Fax: (480) 610-3501 www.PerformAir.com<http://www.performair.com/>

4 5

[tc] weekly meeting
by Mohammed Naser 09 Dec '20

09 Dec '20

Hi everyone, Here’s the agenda for our weekly TC meeting. It will happen tomorrow (Thursday the 10th) at 1500 UTC in #openstack-tc, and I will be your chair. If you can’t attend, please put your name in the “Apologies for Absence” section. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting # ACTIVE INITIATIVES * Follow up on past action items * W cycle goal selection start * Audit and clean-up tags (gmann) * X cycle release name vote recording (gmann) * CentOS 8 releases are discontinued / switch to CentOS 8 Stream (gmann/yoctozepto) * Open Reviews Thank you, Mohammed -- Mohammed Naser VEXXHOST, Inc.

1 0

[kolla] Ussuri Horizon containers fail after Centos 8.3 release
by Braden, Albert 09 Dec '20

09 Dec '20

We are running Train on Centos 7, but I'm experimenting with Adjutant under Ussuri on Centos 8. Until yesterday my Ussuri Horizon containers were ok, but after the Centos 8.3 release they started failing with "{"log":"CommandError: An error occurred during rendering /var/lib/kolla/venv/lib/python3.6/site-packages/openstack_dashboard/templates/horizon/_scripts.html: Couldn't find any precompiler in COMPRESS_PRECOMPILERS setting for mimetype '\\'text/javascript\\''.\n","stream":"stderr","time":"2020-12-08T20:08:03.267208752Z"}" I dug through the Centos release notes and didn't find anything there. [1] I already have the "lowercasing" issue fixed [2]. I see the javascript reference in _scripts.html [3] but it's not obvious what is going wrong. How can I work around this? Is there a variable I can set to build the container on Centos 8.2? Or is there a better way? More logs at [4] [1] https://wiki.centos.org/Manuals/ReleaseNotes/CentOS8.2011 [2] https://review.opendev.org/c/openstack/kolla/+/765854 [3] http://paste.openstack.org/show/800896/ [4] http://paste.openstack.org/show/800897/ I apologize for the nonsense below. So far I have not been able to stop it from being attached to my external emails. I'm working on it. E-MAIL CONFIDENTIALITY NOTICE: The contents of this e-mail message and any attachments are intended solely for the addressee(s) and may contain confidential and/or legally privileged information. If you are not the intended recipient of this message or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and any attachments. If you are not the intended recipient, you are notified that any use, dissemination, distribution, copying, or storage of this message or any attachment is strictly prohibited.

2 2

[tripleo] Deployment update (node addition) after changing aggregate groups/zones
by Ruslanas Gžibovskis 09 Dec '20

09 Dec '20

Hi all. After changing the host aggregate group and zone, I cannot run OpenStack deploy command successfully again, even after updating deployment environment files according to my setup. I receive error bigger one in [0]: 2020-12-02 10:16:18.532419 | 52540000-0001-cf95-492f-0000000003ca | FATAL | Nova: Manage aggregate and availability zone and add hosts to the zone | undercloud | error={"changed": false, "msg": "ConflictException: 409: Client Error for url: http://10.120.129.199:8774/v2.1/os-aggregates/1/action, Cannot add host to aggregate 1. Reason: One or more hosts already in availability zone(s) ['Alpha01']."} I was following this link [1] instructions for "Configuring Availability Zones (AZ)" steps to modify with OpenStack commands. And zone was created successfully, but when I needed to add additional nodes, executed deployment again with increased numbers it was complaining about an incorrect aggregate zone, and now it is complaining about not empty zone with error [0] mentioned above. I have added aggregate zones into deployment files even role file... any ideas? Also, I think, this should be mentioned, that added it after install, you lose the possibility to update using tripleo tool and you will need to modify environment files with. [0] http://paste.openstack.org/show/800622/ [1] https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/feature… -- Ruslanas Gžibovskis +370 6030 7030

2 8

review.opendev.org issue?
by Chris Morgan 09 Dec '20

09 Dec '20

Seems down for me? -- Chris Morgan <mihalis68(a)gmail.com>

4 5

[manila] Graduation of share migration APIs
by Carlos Silva 09 Dec '20

09 Dec '20

Hello, fellow Zorillas and stackers! During the Wallaby PTG, the Manila team discussed the need to remove the experimental flags from the share migration feature APIs. Then, we have realized that there aren't many third party drivers that have implemented "driver-assisted/optimized share migration", so we wanted to get some input from vendors community members on this. Do you want/have plans to implement the driver optimized migration? It'd also be helpful to know if you have tested this feature (even using host assisted migration) or intend to test host assisted migration and can give us some feedback/thoughts on this? In order to graduate the share migration APIs, we must make sure that they are stable. We haven't had bugs opened against it but gathering feedback from the wider community would be helpful to us. Cheers, Carlos

1 0

[neutron] Status on BGP support when using OVN in Neutron
by Tim Sæterøy 09 Dec '20

09 Dec '20

Hi, I'm trying to explore BGP support when using OVN in Neutron, but haven't been able to find much info on the topic. According to [1] committed in march 2020, OVN seems to lack similar functionality as is seen in ML2/OVS, but there's no further references: > Currently ML2/OVS supports making a tenant subnet routable via BGP, > and can announce host routes for both floating and fixed IP > addresses. I've tried searching for 'bgp' on Neutrons launchpad for issues tagged with 'ovn', in the 'ovn-org/ovn' repo or on docs.ovn.org, but I'm getting blanks. Does anyone happen to know where OVN stands on this, and especially in the context of Neutron? Or perhaps able to point me in the right direction where I can find out more? Thanks. [1]: https://docs.openstack.org/neutron/victoria/ovn/gaps.html -- Tim

3 3

[Keystone]Question about access rules for identity API
by Rikimaru Honjo 09 Dec '20

09 Dec '20

Hi, Are the access rules not applied for identity API? I created an application credential with a access rule that allows only project list API. But the application credential allows all identity APIs. Is this correct? Are there any documents that explains about this? By the way, the application credential denied all other service's APIs. I think this behavior is correct. I use OpenStack Ubuntu. Best regards, -- _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ Rikimaru Honjo E-mail:honjo.rikimaru@ntt-tx.co.jp

1 1

[ironic] No Weekly Meeting - December 21st, 28th, and January 4th.
by Julia Kreger 08 Dec '20

08 Dec '20

Greetings fellow humans! As we have in years past, we are approaching the end of year holiday season where people begin to disappear to use time off, rest, and relax their brains. As such, we're cancelling[0] our December 21st, 28th, and January 4th weekly meetings. As in past years, contributors tend to remain connected to IRC, but expect people to be heads-down if they are working, so replies will be sporadic. This also means December 14th will be our last weekly meeting of 2020. In accordance with the prophecy of end of year time off, we'll be in auto-pilot of sorts during the weeks we do not meet. Contributors should feel free to update the review priorities section on the etherpad[1] and look to it for what is going on or what needs additional reviews/feedback. One bit of warning, CI breakages during this time of year are common. Single core approvals to fix CI issues are encouraged in this case. Have a wonderful remainder of the year everyone! -Julia [0]: http://eavesdrop.openstack.org/meetings/ironic/2020/ironic.2020-12-07-15.00… [1]: https://etherpad.opendev.org/p/IronicWhiteBoard

1 0

[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 07 Dec '20

07 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