December 2020 - openstack-discuss

[neutron] Bug deputy - 7.12 - 14.12.2020
by Slawek Kaplonski 14 Dec '20

14 Dec '20

1 0

port Groups (Bonds) Configuration in Openstack Baremetal Provisioning.
by Lokendra Rathour 13 Dec '20

13 Dec '20

Hello, I am trying to install a baremetal on existing openstack setup. During the time of installation, is it possible to have bonds already setup when the baremetal nodes comes up. I was trying to work on the : Port groups configuration in the Bare Metal service *Documents referred :* 1. https://docs.openstack.org/ironic/pike/admin/portgroups.html#:~:text=A%20po… . 2. https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/14… *Setup used:* Baremetal on StarlingX Setup : https://docs.starlingx.io/deploy_install_guides/r4_release/bare_metal/ironi… ¶ <https://docs.openstack.org/ironic/queens/admin/portgroups.html#port-groups-…> -- ~ Lokendra

2 5

[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