- openstack-discuss - lists.openstack.org

[neutron][elections] PTL non candidacy for Y cycle
by Slawek Kaplonski 19 Aug '21

19 Aug '21

Hi, It's been great 2 years for me when I had an honor to serve as Neutron PTL - yeah, time flies :) It has been pleasure to work with all of You on the Neutron project. We did a lot of great things during that time. But now, as I said in my last nomination [1], I'm not going to candidate for being PTL in the Yoga cycle. I think it's good for the project to have new leader every few cycles. That brings fresh ideas and new energy to the project. If You would be interested in that, to which I encourage anyone, and maybe have any questions, feel free to reach out to me in any way (irc, email, etc.). I will be more than happy to answer all Your questions. As for me, I'm not going anywhere. I'm still going to work on Neutron as I did so far. I will be of course very happy to help new PTL if that will be needed :) Once again thank You all for all Your help and supporting me in that role in the last 2 years and good luck to our new PTL! [1] http://lists.openstack.org/pipermail/openstack-discuss/2021-March/ 020901.html -- Slawek Kaplonski Principal Software Engineer Red Hat

6 5

[masakari] Compute service with name XXXXX not found.
by at 19 Aug '21

19 Aug '21

Hi, I have some problem with masakari. I can create segment (from CLI and Horizon), but can't create host (the same result from Horizon and CLI). openstack segment host create XXXXX COMPUTE SSH segment_id returns BadRequest: Compute service with name XXXXX could not be found. XXXXX is the name which Horizon suggest, and it's a name of compute host. openstack compute service list returns proper list with state up/enabled on compute hosts (zone nova) Maybe I misunderstood some parameters of host create? As "type" I use COMPUTE, what value should it be? From "Binary" column of openstack compute service list? What is "control_attributes" field, because documentation lacks preceise information what value should be there and what is it use for. Tried to found some info on this error but I haven't found anything... Thanks in advance for any help. Best regards Adam Tomas

4 7

[tripleo] Help wanted to fix CI!
by Cédric Jeanneret 18 Aug '21

18 Aug '21

Hello Community! We're hitting a blocking issue in the CI: due to some changes in tox, the tox-py36 job is failing due to some bad encoding settings, preventing some package installation. More details: https://bugs.launchpad.net/tripleo/+bug/1940313 We'd need help in a massive tox.ini edition throughout all the projects, at least for master and stable/wallaby branches. Here's a couple of examples: https://review.opendev.org/q/topic:%22encodingfix%22+(status:open%20OR%20st… If anyone has a spare minute to propose such a patch, please do - and, please, be sure to use the same topic, "encodingfix", so that anyone will be able to follow the work! Thank you for your support! Have a great one! Cheers, C. -- Cédric Jeanneret (He/Him/His) Sr. Software Engineer - OpenStack Platform Deployment Framework TC Red Hat EMEA https://www.redhat.com/

2 2

list admins: my mails are not yet publishing to the list members ?
by KK CHN 18 Aug '21

18 Aug '21

List admins/ Members, I am new to openstack, so I subscribed to the openstack-discuss mailing list in my best belief that this is the right place for a newbe to ask doubts and post errors which occurs during my learning stage with Openstack. If this is not the right place to seek help/ ask about doubts regarding openstack kindly direct me to the right place. What ever mails I am sending to openstack-discuss(a)lists.openstack.org not even publishing to the mailing lists. last two weeks I have sent 5 to 6 emails with various errors I got while importing VMs from other hypervisors to OpenStack. I posted to openstack-discuss(a)lists.openstack.org but none of them got response from list members. Iam afraid that my emails are going to Spam or am I not in the right place sending those emails? kindly correct me if I am wrong. Best regards, Kris

3 2

[blazar][ptg] Yoga PTG meeting
by Pierre Riteau 18 Aug '21

18 Aug '21

Hello, As part of the Yoga PTG, the Blazar team project will meet on Thursday October 21 from 15:00 to 17:00 UTC in the Bexar room. I have created an Etherpad to define the agenda: https://etherpad.opendev.org/p/yoga-ptg-blazar Feel free to add topics you would like to see discussed. Thanks, Pierre Riteau

1 1

[barbican] No weekly meeting next week
by Douglas Mendizabal 18 Aug '21

18 Aug '21

Hi All, I'll be out on PTO for a few days, so I won't be available to chair the next Barbican weekly meeting. I should be back the following week for the August 31 meeting. Thanks, - Douglas Mendizábal (redrobot) https://etherpad.opendev.org/p/barbican-weekly-meeting

1 0

[cinder] Bug deputy report for week of 2021-18-08
by Sofia Enriquez 18 Aug '21

18 Aug '21

Hello, This is a bug report from 2021-11-08 to 2021-18-08. This ^ isn't completely accurate. I apologize because my launchpad link failed or something and I've missed a couple of bugs that I've included in today's report. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- High - https://bugs.launchpad.net/cinder/+bug/1939972 "Original volume size is lost when uploading a volume to a qcow2 image". Assigned to Takashi Kajinam. - https://bugs.launchpad.net/cinder/+bug/1937084 "Nova thinks deleted volume is still attached". Assigned to Gorka Eguileor. Medium - https://bugs.launchpad.net/cinder/+bug/1939241 "StorPool: encrypted volumes cannot be attached". Assigned to Peter Penchev. - https://bugs.launchpad.net/cinder/+bug/1940069 "HPE 3PAR: SSH Connection rejected - max number of connections reached". Assigned to Raghavendra Tila. - https://bugs.launchpad.net/cinder/+bug/1938870 "KumoScale Driver replicated volume missing portals attached without raid". Assigned to Zohar Mamedov. - https://bugs.launchpad.net/cinder/+bug/1936848 "PowerMax - Group rename error". Assigned to Helen Walsh. - https://bugs.launchpad.net/cinder/+bug/1940436 "[LVM] lvextend command crashes with code 139". Assigned to Eric Harney. Low - https://bugs.launchpad.net/cinder/+bug/1939956 "Driver-specific options should not be added to [DEFAULT]". Assigned to Takashi Kajinami. - https://bugs.launchpad.net/cinder/+bug/1938572 "PowerMax - legacy PowerMax issue with generations". Assigned to Helen Walsh. - https://bugs.launchpad.net/cinder/+bug/1940437 "Removing a volume in wrong state doesn't report its state". Assigned to Emilien Macchi. Incomplete - https://bugs.launchpad.net/cinder/+bug/1939842 "[CEPH] cinder-backup service blocked by creating volume from backup". Assigned to Jeremy Li. - https://bugs.launchpad.net/cinder/+bug/1939139 "PowerMax - PowerMaxOS 5978.711 snapshot exception". Assigned to Helen Walsh. - https://bugs.launchpad.net/cinder/+bug/1936474 "Create instance from volume fails on reschedule". Unassigned. Wishlist - https://bugs.launchpad.net/cinder/+bug/1938457 "[Storwize] Fix rccg_name based on group display_name". Assigned to Venkata krishna Thumu. Cheers, -- L. Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

[neutron] Drivers meeting agenda for 20.08.2021
by Slawek Kaplonski 18 Aug '21

18 Aug '21

Hi, I will not be available this Thursday and Friday but we have 2 RFEs to discuss during drivers meeting and Miguel volunteered that he will chair the meeting on Friday. RFEs to discuss: * https://bugs.launchpad.net/neutron/+bug/1936408 It's again raised by ralonsoh as he added some new clarifications to it, let's discuss it in the drivers team again. * https://bugs.launchpad.net/neutron/+bug/1939602 New RFE proposed by ralonsoh -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[cyborg] Y cycle PTL nomination from 17th August
by Wang, Xin-ran 18 Aug '21

18 Aug '21

Hi all, The Y cycle PTL nomination will start on 17th August. Firstly, I want to give a big thanks to all of you, thank you for the continuously support and contribution for Cyborg. As I have been this role for almost 2 cycles, I think it is better to have someone else to take this role which can bring us new ideas. Please refer to this guide[1] if you want submit your candidacy. If you have any question, please feel free to contact me. [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy Thanks, Xin-Ran

4 3

[neutron][stable] Nominate Lajos Katona to the neutron-stable-maint team
by Slawek Kaplonski 18 Aug '21

18 Aug '21

Hi, I would like to nominate Lajos Katona as a Neutron stable core reviewer. Lajos is core in Neutron since long time. He is maintaining many stadium projects as well as he is very active in the main Neutron project. He helps us a lot with keeping stable branches healthy (especially for stadium projects, but not only). During that time he has proven already his knowledge about Neutron and Neutron stadium projects as well as knowledge of the stable branches rules. I will keep this nomination open for about 1 week. After that if there will be no votes agains, I will ask stable-maint-core team to add Lajos to the neutron-stable-maint team. -- Slawek Kaplonski Principal Software Engineer Red Hat

7 8

[election][Neutron]PTL candidacy for Yoga
by Lajos Katona 18 Aug '21

18 Aug '21

Hello Openstack Community, I write to submit my candidacy for the Neutron PTL position during the Yoga cycle. I have worked with Openstack since Grizzly in downstream projects, and as a fulltime upstream developer from Rocky. I mostly focused on Neutron, but worked with testing, CI and even added some networking features to Horizon. I work for Ericsson, who brings in interesting TelCo needs and experiences, like trunks or bandwidth aware scheduling. In Ericsson I worked not only as developer, but as team lead and team coach, that gave me opportunity to view things from different perspectives and help teams to solve issues together. I tried to keep Neutron stadium projects alive and maintained, actively participated in Neutron meetings and in activities like the scheduled bug deputy weeks. In the last cycles the Neutron community was stable, and worked together as a real team, and was the best experience of my professional life to work with them and learn every day new things. As I see the team was able to create a kind of gravitation that encouraged developers from around the world to report their bugs, propose their fixes and new ideas to networking projects. My priorities as PTL are the following: * Keep Neutron's stadium ecosystem alive and healthy. In Xena we moved tap-as-a-service back to stadium, and there's even new features arriving to make some of them work with OVN. Continue this effort to keep Neutron as a natural API and code base for many projects. * The team has strong tradition to focus on CI with dedicated weekly meeting, eyes on jobs' results and increasing test coverage. Continue these efforts to make Neutron CI more stable and capable of giving fast and reliable feedback to developers. * In the last cycles OVN became one of Neutron's in-tree backends, and now it is used as default backend in Openstack CI. There's a continuous effort to remove the gaps between ML2/OVS and OVN (see: https://docs.openstack.org/neutron/latest/ovn/gaps.html) some of these already have owner (like QoS Minimum Bandwidth allocation with Placement, or BGP), this effort should be continued. * Neutron team is quite healthy, but I want to onboard developers from other companies to keep the influx of people and ideas. * In the last cycles the performance improvements were always on the written or unconscious TODO list of the team (like enginefacade-switch, or this cycle's efforts from Oleg and other Huawei developers). Like CI, performance improvements and monitoring should be a continuous effort. * Continue the ongoing implementation for feautres like new QoS rules (pps limit and minimum pps), and new l3 related features. Thank you for your time and consideration. Lajos Katona (lajoskatona)

1 0

[ironic] Departure from full-time work on the project
by Jay Faulkner 17 Aug '21

17 Aug '21

Hello everyone, As mentioned in the Ironic IRC meeting, I will no longer be working full time on OpenStack Ironic after this week. It is my intention to continue reviewing code for a small amount of time on the weekends until my context around the project becomes too stale. Working on OpenStack Ironic has been the greatest adventure of my career so far, but I'll mostly remember all the nice people I met along the way. Thanks, Jay Faulkner

5 4

[all][elections][ptl][tc] Combined PTL/TC Nominations Kickoff
by helena＠openstack.org 17 Aug '21

17 Aug '21

Hello Everyone! Nominations for OpenStack PTLs (Project Team Leads) and TC (Technical Committee) positions (4 positions) are now open and will remain open until August 24, 2021 23:45 UTC. All nominations must be submitted as a text file to the openstack/election repository as explained at [ https://governance.openstack.org/election/#how-to-submit-a-candidacy ]( https://governance.openstack.org/election/#how-to-submit-a-candidacy )[ ]( https://governance.openstack.org/election/#how-to-submit-a-candidacy ) Please make sure to follow the candidacy file naming convention: candidates/yoga/<Project_Name or "TC">/<email_address> (for example, "candidates/yoga/TC/stacker(a)example.org"). The name of the file should match an email address for your current OpenInfra Foundation Individual Membership. Take this opportunity to ensure that your Openinfra Foundation member profile contains current information: [ https://www.openstack.org/profile/ ]( https://www.openstack.org/profile/ ) Any OpenInfra Foundation Individual Member can propose their candidacy for an available, directly-elected seat on the Technical Committee. In order to be an eligible candidate for PTL you must be an OpenInfra Foundation Individual Member. PTL candidates must also have contributed to the corresponding team during the Wallaby to Xena timeframe, September 25, 2020 00:00 UTC - August 24, 2021 00:00 UTC. Your Gerrit account must also have a verified email address matching the one used in your candidacy filename. Both PTL and TC elections will be held from August 31, 2021 23:45 UTC through to September 7, 2021 23:45 UTC. The electorate for the TC election are the OpenInfra Foundation Individual Members who have a code contribution to one of the official teams over the Wallaby to Xena timeframe, September 25, 2020 00:00 UTC - August 24, 2021 00:00 UTC, as well as any Extra ATCs who are acknowledged by the TC. The electorate for a PTL election are the OpenInfra Foundation Individual Members who have a code contribution over the Wallaby to Xena timeframe, September 25, 2020 00:00 UTC - August 24, 2021 00:00 UTC, in a deliverable repository maintained by the team which the PTL would lead, as well as the Extra ATCs who are acknowledged by the TC for that specific team. The list of project teams can be found at [ https://governance.openstack.org/tc/reference/projects/ ]( https://governance.openstack.org/tc/reference/projects/ ) and their individual team pages include lists of corresponding Extra ATCs. Please find below the timeline: Nominations Start @ August 17, 2021 23:45 UTC Nominations End @ August 24, 2021 23:45 UTC Campaigning Start @ August 24, 2021 23:45 UTC Campaigning End @ August 31, 2021 23:45 UTC Election Start @ August 31, 2021 23:45 UTC Election End @ September 7, 2021 23:45 UTC Shortly after election officials approve candidates, they will be listed on the [ https://governance.openstack.org/election/ ]( https://governance.openstack.org/election/ ) page. The electorate is requested to confirm their email addresses in Gerrit prior to 2020-08-24 00:00:00+00:00, so that the emailed ballots are sent to the correct email address. This email address should match one which was provided in your foundation member profile as well. Gerrit account information and OpenInfra Foundation member profiles can be updated at [ https://review.openstack.org/#/settings/contact ]( https://review.openstack.org/#/settings/contact ) and [ https://www.openstack.org/profile/ ]( https://www.openstack.org/profile/ ) accordingly. As a reminder, be sure you mark civs as authorized to send e-mails to that address (this is new, due to a civs service policy change since the last round of elections). If you have any questions please be sure to either ask them on the mailing list or to the elections officials: [ https://governance.openstack.org/election/#election-officials ]( https://governance.openstack.org/election/#election-officials ) Cheers, Helena on behalf of the OpenStack Technical Election Officials

3 3

[release] Y cycle PTL nominations from 17th August
by Herve Beraud 17 Aug '21

17 Aug '21

Hello, in case you missed in, the OpenStack Y cycle election season is soon upon us starting 17th August [1]. I do not intend to run for a third cycle as ptl. I think it is healthy for the project to have new energy and ideas brought by a new ptl. I'd like to encourage anyone who is considering this to read the info from [1] and in particular prepare a nomination [2]. Feel free to reach out to me if you have any questions or concerns. If you *are* thinking about it bear in mind there are many experienced people around that can and will help you. Thanks for your attention, [1] http://lists.openstack.org/pipermail/openstack-discuss/2021-August/024093.h… [2] https://governance.openstack.org/election/#how-to-submit-a-candidacy -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

3 2

[OSSA-2021-004] Neutron: Linuxbridge ARP filter bypass on Netfilter platforms (CVE-2021-38598)
by Jeremy Stanley 17 Aug '21

17 Aug '21

=================================================================== OSSA-2021-004: Linuxbridge ARP filter bypass on Netfilter platforms =================================================================== :Date: August 17, 2021 :CVE: CVE-2021-38598 Affects ~~~~~~~ - Neutron: <16.4.1, >=17.0.0 <17.1.3, ==18.0.0 Description ~~~~~~~~~~~ Jake Yip with ARDC and Justin Mammarella with the University of Melbourne reported a vulnerability in Neutron's linuxbridge driver on newer Netfilter-based platforms (the successor to IPTables). By sending carefully crafted packets, anyone in control of a server instance connected to the virtual switch can impersonate the hardware addresses of other systems on the network, resulting in denial of service or in some cases possibly interception of traffic intended for other destinations. Only deployments using the linuxbridge driver with ebtables-nft are affected. Patches ~~~~~~~ - https://review.opendev.org/804058 (Train) - https://review.opendev.org/804057 (Ussuri) - https://review.opendev.org/804056 (Victoria) - https://review.opendev.org/785917 (Wallaby) - https://review.opendev.org/785177 (Xena) Credits ~~~~~~~ - Jake Yip from ARDC (CVE-2021-38598) - Justin Mammarella from University of Melbourne (CVE-2021-38598) References ~~~~~~~~~~ - https://launchpad.net/bugs/1938670 - http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-38598 Notes ~~~~~ - The stable/train branch is under extended maintenance and will receive no new point releases, but a patch for it is provided as a courtesy. -- Jeremy Stanley

1 0

[juju][wallaby] no obvious space for container
by toky0 17 Aug '21

17 Aug '21

Hi, I'm running into error [1] while trying to create lxd containers in the maas+juju deployment guide. This is the output for juju spaces: Name Space ID Subnets alpha 0 default 2 192.168.220.0/24 2001:db8:0:220::/64 public 1 2001:db8::/64 Any pointers are appreciated. Let me know if you need more info. Regards, Sami [1] 3 started 2001:db8:0:220::40 controller0 focal default Deployed 3/lxd/0 down pending focal no obvious space for container "3/lxd/0", host machine has spaces: "default", "public"

1 0

[tripleo] Y cycle PTL nominations from 17th August
by Marios Andreou 17 Aug '21

17 Aug '21

Hello tripleo o/ in case you missed in, the OpenStack Y cycle election season is soon upon us starting 17th August [1] As previously mentioned in tripleo irc meetings I do not intend to run for a third cycle as ptl. I think it is healthy for the project to have new energy and ideas brought by a new ptl and we are very fortunate to have many capable candidates in our community who have not previously occupied that role. I'd like to encourage anyone who is considering this to read the info from [1] and in particular prepare a nomination [2]. Feel free to reach out to me if you have any questions or concerns. If you *are* thinking about it bear in mind there are many experienced people around that can and will help so ... how badly can it go ! ;) regards, marios [1] http://lists.openstack.org/pipermail/openstack-discuss/2021-August/024093.h… [2] https://governance.openstack.org/election/#how-to-submit-a-candidacy

4 4

[neutron] bug deputy report August 9th to 15th
by Miguel Lavalle 16 Aug '21

16 Aug '21

Hi, Here's this week's bugs deputy report: High ==== https://bugs.launchpad.net/neutron/+bug/1939924 [ovn] NeutronNetworks.create_and_delete_subnets failing in concurrent scenario. Needs owner Medium ====== https://bugs.launchpad.net/neutron/+bug/1939403 [ovn] Tag on localnet port is not changed when proivder segment is updated. Assigned to Jakub Libosvar https://bugs.launchpad.net/neutron/+bug/1939429 [periodic] "neutron-ovn-tempest-ovs-master-fedora" failing with Fedora 34. Assigned to Rodolfo Alonso https://bugs.launchpad.net/neutron/+bug/1939432 Concurrent DHCP agent updates can result in a DB lock. Assigned to Rodolfo Alonso. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/804218 https://bugs.launchpad.net/neutron/+bug/1939558 Security group log entry remains in the database after its security group is deleted. Assigned to Slawek Kaplonski. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/804237 https://bugs.launchpad.net/neutron/+bug/1939704 db-sync script may fail when migrating from ovs to ovn. Assigned to Jakub Libosvar. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/804405 https://bugs.launchpad.net/neutron/+bug/1940009 Some options are missing from neutron.conf generated by "tox -e genconfig". Owner assigned Incomplete ======== https://bugs.launchpad.net/neutron/+bug/1939723 neutron-ovn-db-sync generates insufficient flow https://bugs.launchpad.net/neutron/+bug/1939726 neutron-ovn-db-sync error during generate OVN DB RFEs ==== https://bugs.launchpad.net/neutron/+bug/1939602 [RFE] Add a memory profiler. Proposed implementation: https://review.opendev.org/c/openstack/neutron/+/803034 (Rodolfo Alonso) Invalid ===== https://bugs.launchpad.net/neutron/+bug/1939374 [OVN] Support baremetal type vnic https://bugs.launchpad.net/neutron/+bug/1939514 test_dvr_fip_and_router_namespace_rules_with_address_scopes_match iptables failure

1 0

OpenInfra Live - August 19 at 9am CT
by Ashlee Ferguson 16 Aug '21

16 Aug '21

Hi everyone, This week’s OpenInfra Live episode is brought to you by the OpenStack community. For the uninitiated, OpenStack's role in programmable infrastructure can be a little hard to understand unless you know its capabilities and how it works. Furthermore, to some people, OpenStack looks very similar to virtualization or simply like existing public cloud offerings. To fully understand this cloud platform, we will start at the origins of cloud technology and end at how today's OpenStack works. Episode: OpenStack Basics Date and time: August 19 at 9am CT (1400 UTC) You can watch us live on: YouTube: https://www.youtube.com/watch?v=hGRkdYu6I5k <https://www.youtube.com/watch?v=hGRkdYu6I5k> LinkedIn: https://www.linkedin.com/feed/update/urn:li:ugcPost:6831694874451042304/ <https://www.linkedin.com/feed/update/urn:li:ugcPost:6831694874451042304/> Facebook: https://www.facebook.com/104139126308032/posts/4235953959793174/ <https://www.facebook.com/104139126308032/posts/4235953959793174/> WeChat: recording will be posted on OpenStack WeChat after the live stream Speakers: Ben Silverman, CBTS Ildiko Vancsa, Open Infrastructure Foundation Have an idea for a future episode? Share it now at ideas.openinfra.live <https://openinfrafoundation.formstack.com/forms/openinfralive>. Thanks, Ashlee

1 0

[manila] We're having an OSC Hack-a-thon - Aug 18-20th 2021
by Goutham Pacha Ravi 16 Aug '21

16 Aug '21

Hi Zorillas and other interested stackers, tl;dr: - We're swarming to add missing OSC commands to python-manilaclient between 18th-20th Aug 2021, join us. - Kick-off Aug 18th at 1400 UTC, Mid-point check Aug 19th, 1500 UTC, Close-out Aug 20th, 1500 UTC on https://meetpad.opendev.org/manila-xena-hackathon Now for the longer version: As discussed at our IRC meeting today [1], I'm excited to share the nitty gritties of the upcoming OSC hack-a-thon. We'd be delighted to welcome existing and new contributors to come join us in the quest to achieve CLI parity in the OpenStackClient plugin within python-manilaclient. The work is being tracked here: https://tree.taiga.io/project/gouthampacha-openstack-manila-osc-integration… The commands we're targeting are also featured in a specification: https://specs.openstack.org/openstack/manila-specs/specs/release_independen… The fine print for the hack-a-thon: - Maari Tamm has been the force behind this effort so far, and she's put up a very helpful "Getting Started" wiki [2] that we intend to expand through the hack-a-thon and finally add to the project's Contributor Docs. There are also several examples of recent additions [3][4][5] that could serve as inspiration. - You're free to create, claim and edit Taiga cards for the implementation you're chasing, we highly recommend picking only one card, and not claiming something someone else already has. Please reach out to gouthamr/maaritamm if you have to be added to the taiga board. - Also, Add yourself as a "watcher" to two other Taiga cards that someone else is implementing, this will mean that you will be a code reviewer on these implementations! - You can work in teams - min size: 1, max size: 3 - You can submit code between Aug 18th 1200 UTC and Aug 21st 1200 UTC to count towards this hack-a-thon - A day before the hack-a-thon, a few of us will gather to prep taiga.io cards, communicate with owners if there are conflicts, pre-reqs, etc. - During the hack-a-thon, we'll use #openstack-manila on OFTC to chat, and hop onto a meetpad room: https://meetpad.opendev.org/manila-xena-hackathon when required. - We'll have a half-hour kick-off session on Aug 18th at 1400 UTC - We'll use the manila community meeting hour as a mid-point status check (Aug 19th, 1500 UTC) - We'll have a half-hour close out meeting to discuss reviews, AIs and futures (grab your beers) (Aug 20th, 1500 UTC) I'm quite excited to participate in this, and I hope you are too. Please feel free to reach out here or on OFTC's #openstack-manila if you have any questions! Thanks, Goutham [1] https://meetings.opendev.org/meetings/manila/2021/manila.2021-08-12-15.00.l… [2] https://docs.google.com/document/d/1Kc02fO_ei-6NxPm_b6mnFbf-6MVdjMk71mFqX1a… [3] https://review.opendev.org/c/openstack/python-manilaclient/+/772393 [4] https://review.opendev.org/c/openstack/python-manilaclient/+/762754 [5] https://review.opendev.org/c/openstack/python-manilaclient/+/701229

2 1

[victoria][ops][horizon][neutron] Network not available to use by Members in Horizon
by DHilsbos＠performair.com 16 Aug '21

16 Aug '21

All; We just discovered, this morning, that Members of one of our projects can't see the project's network, in order to use it in Instance creation. If an Administrator creates a Port, the Member user can then use it to create an Instance. Most of our activity to this point has been by Administrators, this is the first time we've opened a project up to users with the Member level. Is this expected behavior? Thank you, Dominic L. Hilsbos, MBA Vice President - Information Technology Perform Air International Inc. DHilsbos(a)PerformAir.com www.PerformAir.com

2 2

[ops][security-sig] KVM AMD vulnerabilities (CVE-2021-3653, CVE-2021-3656)
by Jeremy Stanley 16 Aug '21

16 Aug '21

I usually don't do this, but as it is likely to be a widespread concern across many OpenStack deployments I thought it would be a good idea to bring the situation to everyone's attention and help spread the word. Today, two new vulnerabilities were announced in the Linux KVM implementation for AMD processors (CVE-2021-3653 and CVE-2021-3656): https://www.openwall.com/lists/oss-security/2021/08/16/1 The impact described there indicates that these could be leveraged by guest virtual machines to gain access to their underlying hypervisor host servers. If you run a KVM-based deployment on AMD processors, please be on the lookout for updates from your Linux distribution and apply them at the earliest opportunity. Also consider temporarily enacting the mitigations listed in the advisory (e.g. disabling nested virtualization in the kvm_amd module). -- Jeremy Stanley

1 0

答复: [venus] Project Progress
by Brin Zhang(张百林) 16 Aug '21

16 Aug '21

Thanks for working for this job. As we discussed support for log retrieval of Cyborg in Hackthon in China at <http://www.baidu.com/link?url=Rn4my7xbuu7WVmRPPPyFPS0xLUb79O18GxMO5ANBxlO0o wZZMhOInqarCLBY3_IM4kOytWff8QIfUZ2RC9Q_5agl4w2-w1kZ2hbjdXYIy9C> April 2021, which improves our efficiency in locating and solving problems. And there are many companies have expressed interest in the Venus project, and we have already begun to cooperate. Thanks. brinzhang Inspur Electronic Information Industry Co.,Ltd. 发件人: Liye Pang(逄立业) 发送时间: 2021年8月14日 15:38 收件人: openstack-discuss(a)lists.openstack.org 抄送: Brin Zhang(张百林) <zhangbailin(a)inspur.com> 主题: [venus] Project Progress Hi Team: Thanks to everyone for months of hard work, we have made great progress of venus, mainly as follows: 1. Add the retrieval of vitrage, cyborg and other modules to venus. 2.Developed the deployment based on kolla-ansible of venus,the location is: https://review.opendev.org/c/openstack/kolla-ansible/+/793897 https://review.opendev.org/c/openstack/kolla/+/793795 3.The configuration, Search,analysis of Venus are integrated into horizon in the form of plugin as the attached picture. Hope everyone will make persistent efforts to make venus easier and more practical. Regards, pangliye

4 5

[tc][all] Please Help On Collecting Pain Points
by Rico Lin 16 Aug '21

16 Aug '21

Dear all As a proposal for pre-select goals for Yoga [1]. We need to figure out the possibility. *I would like to ask each project team, SIG, and pop-up if you can kindly provide the major pain point you have (and better to be fixable by bugs/features).* *What you can help with is added in pain point information in [2].* *Information like pain point topic, description, and ideas on how to targeting them.* *Why this is important?* I think this data allows us to see clearly if we can have goals like `eliminate pain points`. *What's after this?* If we can make sure this can be a goal material, we might be able to have this as a goal and allow project teams to focus on one of their most important issues. As an alternative, we might be able to collect from user side with a user survey, but that's more like a really long-term plan for this. [1] https://etherpad.opendev.org/p/y-series-goals [2] https://etherpad.opendev.org/p/pain-point-elimination *Rico Lin* OIF Board director, OpenStack TC, Multi-arch SIG chair, Heat PTL, Senior Software Engineer@EasyStack

3 4

[all] SQLAlchemy 2.0 and coming ORM apocalypse
by Stephen Finucane 16 Aug '21

16 Aug '21

tl;dr: If you haven't already started looking at SQLAlchemy 2.0 compatibility and/or are still using sqlalchemy-migrate, you probably have work to do. As you can guess from $subject, there's a new major version of SQLAlchemy in the pipeline. The good news: it cleans up a lot of cruft and makes a lot of things such as session management more explicit and verbose, with the idea being that this should avoid a lot of gotchas and foot-gun moments. The bad news: the changes are pretty extensive, and virtually anyone that uses SQLAlchemy, which is to say every (?) OpenStack service out there, will likely have to make changes. This change will likely have a couple of impacts for users: # Breaking changes in oslo.db The oslo devs have been steadily working through the many errors that oslo.db is currently emitting when SQLAlchemy 2.0 deprecation warnings are turned on. The patches (which is not yet complete) to address these can be found here [1]. As a result of these changes, a number of oslo.db APIs are likely to start performing slightly differently, and many more may be deprecated and eventually removed. An example of the kind of change you can expect to see can be found in this glance patch [2]. We will work to minimize these changes but some will be unavoidable once sqlalchemy 2.0 actually arrives. # Breaking changes in your own project If oslo.db seeing breaking changes because of SQLAlchemy 2.0, you can be sure that you're going to see some too. Fortunately, there are ways you can get ahead of this. Turning SADeprecationWarning warnings into errors for your own module, as we've done for oslo.db [3][4] seems a sensible pattern to weed out these issues. As an aside, enabling warnings as errors seems to be a generally good idea in a unit test environment. It's usually a lot easier to address these things as they pop up that when things are finally removed and stuff explodes. To each their own though, of course. # The long prophesied death of sqlalchemy-migrate The lack of maintenance on sqlalchemy-migrate has already been well documented [5], however, SQLAlchemy 2.0 is likely to be the thing that finally puts the nail in sqlalchemy-migrate's coffin. I've been working on migrating the last few laggards still using sqlalchemy-migrate and have successfully removed all traces of it from glance (thanks, glance-core!), while the nova and cinder patches are making reasonable progress (though I do wish it was faster). The only remaining "core" project to be migrated is keystone. This proved a little too complicated for me to do in the limited time I have to work on these things, and I'm in the middle of a role change in my day job so my time to work on upstream OpenStack will be decreasing much further going forward (though not to zero, I'm hoping). Fortunately, there's quite a bit of prior art available now that people can follow when migrating stuff [6]. Related to the oslo.db changes: everything related to sqlalchemy-migrate in oslo.db should be deprecated by the next oslo.db release, and I suspect we'll be pretty aggressive in pruning these. Based on codesearch.o.o, this will have impacts for at least keystone and cinder. # A chance to evaluate all things DB One positive out of this is that the changes necessary may be broad enough to take the opportunity to re-evaluate decisions made regarding your DB layer. We've been doing this in nova, moving lots of things about to clear up the distinction between the main and API DBs and to reduce lots of tech debt that had built up in 'nova.db'. Consider using the opportunity to do the if possible. --- Hopefully this has been useful. If you have questions about any of the above, please reach out and I'll do my best to answer them. Cheers, Stephen [1] https://review.opendev.org/q/topic:%2522sqlalchemy-20%2522+(status:open+OR+… [2] https://review.opendev.org/c/openstack/glance/+/804406 [3] https://github.com/openstack/oslo.db/commit/40bce5a2baf75dc87dd591e0f71a00f… [4] https://github.com/openstack/oslo.db/commit/4c1eb966c08d29214c1905e74965f41… [5] http://lists.openstack.org/pipermail/openstack-discuss/2021-February/020672… [6] https://review.opendev.org/q/topic:%22bp%252Fremove-sqlalchemy-migrate%22+(…

4 4

[wallaby][neutron] OVN Geneve multiple tunnels
by Ammad Syed 16 Aug '21

16 Aug '21

Hi, I am using neutron with ovn geneve. Currently I have two nic ports and I have bonded them in active passive bond in linux and assigned an IP address on vlan tagged interface for overlay network. Is it possible that I can use two or more IP addresses for overlay tunnels between compute hosts ? I am planning to assign an IP on each NIC so that I can have redundancy as well as a pair of tunnel with more throughput between compute hosts ? Ammad

2 1

[release] Release countdown for week R-7, Aug 16 - Aug 20
by Herve Beraud 16 Aug '21

16 Aug '21

Development Focus ----------------- We are entering the last weeks of the Xena development cycle. From now until the final release, we'll send a countdown email like this every week. It's probably a good time for teams to take stock of their library and client work that needs to be completed yet. The non-client library freeze is coming up, followed closely by the client lib freeze. Now is a good time to make decisions on deferring feature work to the next development cycle in order to be able to focus on finishing already-started feature work. Please plan accordingly to avoid any last minute rushes to get key functionality in. General Information ------------------- We are now getting close to the end of the cycle, and will be gradually freezing feature work on the various deliverables that make up the OpenStack release. This coming week is the deadline for general libraries (except client libraries): their last feature release needs to happen before "Non-client library freeze" on September 19. Only bugfixes releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/xena branching request with the review (as an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… A quick reminder of the upcoming freeze dates. Those vary depending on deliverable type: * General libraries (except client libraries) need to have their last feature release before Non-client library freeze (August 19th). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (September 2nd) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, September 2nd. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. After feature freeze, cycle-with-rc deliverables need to produce a first release candidate (and a stable branch) before RC1 deadline (Sep 13 - Sep 17). * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (Sep 27 - Oct 01). As we are getting to the point of creating stable/xena branches, this would be a good point for teams to review membership in their xena-stable-maint groups. Once the stable/xena branches are cut for a repo, the ability to approve any necessary backports into those branches for xena will be limited to the members of that stable team. If there are any questions about stable policy or stable team membership, please reach out in the #openstack-stable channel. Finally, now is also a good time to start planning what highlights you want for your deliverables in the cycle highlights. The deadline to submit an initial version for those is set to Feature freeze (September 2nd). Background on cycle-highlights: http://lists.openstack.org/pipermail/openstack-discuss/2021-August/024105.h… Project Team Guide, Cycle-Highlights: https://docs.openstack.org/project-team-guide/release-management.html#cycle… knelson [at] openstack.org/diablo_rojo on IRC is available if you need help selecting or writing your highlights Upcoming Deadlines & Dates -------------------------- Non-client library freeze: Aug 19 (R-7 week) Client library freeze: Sep 02 (R-5 week) Xena-3 milestone: Sep 02 (R-5 week) -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

1 0

[rocky][cinder][lvm] VM LVM leakage to packstack host OS
by Alan Davis 16 Aug '21

16 Aug '21

All, I have an issue with LVM on a rocky packstack installation where the LVM constructs inside the VMs running on the server "leak" into the host OS LVM configuration. Here's the listing of the errors from the OS: [root@stack2 log(keystone_apg-project)]# pvs WARNING: Device for PV ILdbcY-VFCm-fnH6-Y3jc-pdWZ-fnl8-PH3TPe not found or rejected by a filter. WARNING: Device for PV yZy8Xk-foKT-ovjV-0EZv-VxEM-GqiP-WH7k53 not found or rejected by a filter. Couldn't find device with uuid ILdbcY-VFCm-fnH6-Y3jc-pdWZ-fnl8-PH3TPe. Couldn't find device with uuid yZy8Xk-foKT-ovjV-0EZv-VxEM-GqiP-WH7k53. PV VG Fmt Attr PSize PFree /dev/md0 cinder-volumes lvm2 a-- <9.10t 4.87t /dev/sdaa pub_vg lvm2 a-- <250.00g 0 /dev/sdac apg-git-encrypted_vg lvm2 a-- <30.00g 0 /dev/sdah encrypted_vg lvm2 a-- <60.00g <60.00g /dev/sdb2 centos_stack2 lvm2 a-- 74.00g 0 [unknown] encrypted_vg lvm2 a-m <60.00g 0 [unknown] encrypted_vg lvm2 a-m <100.00g <100.00g Here are the current cinder.conf lines that seem relevant: # Type of LVM volumes to deploy; (default, thin, or auto). Auto defaults to # thin if thin is supported. (string value) # Possible values: # default - <No description provided> # thin - <No description provided> # auto - <No description provided> lvm_type = default # LVM conf file to use for the LVM driver in Cinder; this setting is ignored if # the specified file does not exist (You can also specify 'None' to not use a # conf file even if one exists). (string value) #lvm_conf_file = /etc/cinder/lvm.conf # Suppress leaked file descriptor warnings in LVM commands. (boolean value) #lvm_suppress_fd_warnings = false I think there are several things going on here : duplicate VG names causing LVM to see UUID/name conflicts and "leakage" of LVM data that cinder should be managing to the OS level. What do I need to change in my configuration to fix this and avoid problems in the future? Thanks -- Alan Davis Principal System Administrator Apogee Research LLC Office : 571.384.8941 x26 Cell : 410.701.0518

2 1

Need a help to recover Openstack
by open infra 15 Aug '21

15 Aug '21

Hi, Openstack was failed and noticed that mariadb-server-1 pod is failing. openstack mariadb-server-0 0/1 Running openstack mariadb-server-1 0/1 CrashLoopBackOff I managed to get logs of each pod. mariadb-server-0 log: https://paste.opendev.org/show/808070/ and https://paste.opendev.org/show/808071/ mariadb-server-1 log: https://paste.opendev.org/show/808067/ I highly appreciate if I can get a hint or steps to resolve this issue. OpenStack is deployed on STX. Regards, Danishka

3 4

Pls help newbie :) bare metal new Ansible deployment
by Nicola Ferrari (#554252) 14 Aug '21

14 Aug '21

Dears, I'm new to the list. We're just trying to introduce a demo install of openstack in our network. Our intention was to use 5 machine, already installed with ubuntu-mini 20.04. ostack1 as control node ostack2 -| ostack3 -| AS COMPUTE NODE ostack4 -| ostack5 -| ostack4 - ostack5 also as block storage node, they are connected on a direct storage (sas) where we deployed lvm with a vg named "cinder_volumes". All nodes both are on a /24 network (192.168.32.0/24) behind a router (32.254) and also on a "private" network (10.255.255.0/24) which just interconnect nodes themselves. We inteded to deploy openstack using openstack-ansible, available on github, last stable release. You can see our user_config as attachment. setup-hosts playbook runs with no errors. setup-infrastructure playbook hangs on RUNNING HANDLER [repo_server : reload nginx] **************************************************************************************** FAILED - RETRYING: reload nginx (1 retries left). fatal: [ostack1_repo_container-aabb6a12]: FAILED! => {"attempts": 5, "changed": false, "msg": "Unable to start service nginx: Job for nginx.service failed because the control process exited with error code.\nSee \"systemctl status nginx.service\" and \"journalctl -xe\" for details.\n"} Looking at log I can see that nginx coudn't start due to "Cannot assign requested address: 99" error. I suppose that must be a mistake in the deploy file? Many thanks for your suggestion, and pls, be sorry for my poor english :) Nick

2 2

[cyborg]Cyborg weekly meeting time slot
by 陈克 14 Aug '21

14 Aug '21

Thanks xinran's advice. So that we can have more time to discuss problems at night~ Thanks, Ke Chen

1 0

[all][tc] What's happening in Technical Committee: summary 13th Aug, 21: Reading: 5 min
by Ghanshyam Mann 13 Aug '21

13 Aug '21

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. What we completed this week: ========================= * Project Skyline(dashboard) pre-proposal discussion. ** TC discussed the pre-proposal required things for the skyline team need to prepare before the project proposal. Kendall sent it on ML[1]. We will wait for the proposal which will have more implementation details. 2. TC Meetings: ============ * TC held this week meeting on Thursday; you can find the full meeting logs in the below link: - https://meetings.opendev.org/meetings/tc/2021/tc.2021-08-12-15.00.log.html * We will have next week's meeting on Aug 19th, Thursday 15:00 UTC[2]. 3. Activities In progress: ================== TC Tracker for Xena cycle ------------------------------ TC is using the etherpad[3] for Xena cycle working item. We will be checking and updating the status biweekly in the same etherpad. Open Reviews ----------------- * Two open reviews for ongoing activities[4]. Combined PTL/TC Election Season for Yoga ---------------------------------------------------- * Yoga cycle election for PTL and TC will be held combined. * The nomination period officially begins August 17, 2021 23:45. * Please read Helena email for more details[5] Murano Project retirement proposal ------------------------------------------ * During a check on project health, we found that Murano is not active anymore. * No code change in Xena cycle last patch merged 4 months ago: https://review.opendev.org/c/openstack/murano/+/783446 * Core team or PTL are not reachable. * In the TC meeting, we decided to start the proposal for its retirement. If you are using it or interested in maintaining it, please respond to mnaser email on openstack-discuss ML[6] Wallaby testing runtime for centos8 vs centos8-stream ----------------------------------------------------------------- * We continue to discuss it in the TC meeting and we agreed: ** Devstack centos8-stream support can be backported to stable/wallaby with the centos8-stream job. ** We will discuss in PTG whether we should update the TC documentation on testing runtime for stable branch or what to do when centos8 is EOL (in Dec 2021). Project updates ------------------- * Retiring js-openstack-lib [7] Yoga release community-wide goal ----------------------------------------- * Please add the possible candidates in this etherpad [8]. * Current status: Proposed "Secure RBAC" to select for Yoga cycle[9]. PTG planning ---------------- * We are collecting the PTG topics in etherpad[10], feel free to add any topic you would like to discuss. Test support for TLS default: ---------------------------------- * Rico has started a separate email thread over testing with tls-proxy enabled[11], we encourage projects to participate in that testing and help to enable the tls-proxy in gate testing. 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[12]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [13] 3. Office hours: The Technical Committee offers a weekly office hour every Tuesday at 0100 UTC [14] 4. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] http://lists.openstack.org/pipermail/openstack-discuss/2021-August/024088.h… [2] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [3] https://etherpad.opendev.org/p/tc-xena-tracker [4] https://review.opendev.org/q/project:openstack/governance+status:open [5] http://lists.openstack.org/pipermail/openstack-discuss/2021-August/024093.h… [6] http://lists.openstack.org/pipermail/openstack-discuss/2021-August/024120.h… [7] https://review.opendev.org/c/openstack/governance/+/798540 [8] https://etherpad.opendev.org/p/y-series-goals [9] https://review.opendev.org/c/openstack/governance/+/803783 [10] https://etherpad.opendev.org/p/tc-yoga-ptg [11] http://lists.openstack.org/pipermail/openstack-discuss/2021-June/023000.html [12] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [13] http://eavesdrop.openstack.org/#Technical_Committee_Meeting [14] http://eavesdrop.openstack.org/#Technical_Committee_Office_hours -gmann

1 0

Octavia
by Chris Lyons 13 Aug '21

13 Aug '21

Octavia group, I created this story to see if I could get some assistance on an Octavia issue I am having with my infra. I did a vanilla install of Openstack Wallaby using the Kolla project with Octavia enabled and auto-configure set. Everything appeared to install fine. When I try to create a load balancer using the horizon console or the cli or through further installs such as cloudfoundry that require a loadbalancer, I get an error from glance about “No image found with tag amphora” even though the image does exist. I hope it is something simple or an oversight on my part. Could I get some ideas or places to look? Story: https://storyboard.openstack.org/#!/story/2009103 Kolla install followed: https://docs.openstack.org/kolla-ansible/latest/reference/networking/octavi… cli output : [root@kolla ~]# openstack image list --tag amphora +--------------------------------------+---------------------+--------+ | ID | Name | Status | +--------------------------------------+---------------------+--------+ | 8f7398e7-7912-43b8-8131-e90f21c91ab4 | amphora | active | | 9bf14389-8521-4fb7-a7db-925f4dea1bf3 | amphora-x64-haproxy | active | +--------------------------------------+---------------------+--------+ [root@kolla ~]# My Infra scripts (relevant): https://github.com/mephmanx/openstack-scripts/blob/32363ef5753fdec381f713c7… I am admin of said infra so if anyone has time or availability (or interest) to log in and take a look I would be happy to provide creds. Thank you for any time that you could provide or offer!

4 11

Backup controller node
by Midhunlal Nb 13 Aug '21

13 Aug '21

Hi team, I have a rocky installed openstack environment and it is working fine.In my set up I have; 1 controller node,2 compute nodes and 1 storage node. Now we are planning to add 1 more controller node as backup.Is it possible to add 1 more controller node in existing set up? if it is possible ,anyone please share the procedure. Thanks & Regards Midhunlal N B +918921245637

1 0

[TripleO] next irc meeting Tuesday 17 August @ 1400 UTC in OFTC #tripleo
by Marios Andreou 12 Aug '21

12 Aug '21

Reminder the next TripleO irc meeting is this coming Tuesday agenda: https://wiki.openstack.org/wiki/Meetings/TripleO one-off items: https://etherpad.opendev.org/p/tripleo-meeting-items (please add any tripleo status/ongoing work etc to the etherpad). Our last meeting was on Aug 03 - you can find logs @ https://meetings.opendev.org/meetings/tripleo/2021/tripleo.2021-08-03-14.00… Hope you can make it, regards, marios

1 0

Horizon problem when configure 2 regions
by Chu Ha Khanh 12 Aug '21

12 Aug '21

I lab configuring 2 region RegionOne, RegionTwo. 2 install 2 controllers node. RegionOne: control3: Horizon, Keystone, Glance. RegionTwo: control4: Glance. I can list image when I use CLI to each regions. However when I login to RegionTwo on Horizon. It show problem. I stuck for several weeks . Hope can be helped. Thank and Regards

1 0

[nova] Removal of legacy block_device_info format
by Lee Yarwood 12 Aug '21

12 Aug '21

Hello all, This is advance notice of $subject [1] for out of tree virt driver maintainers. While working on a bugfix [2] I noticed that the original legacy block_device_info dict format [3] hasn't been used by any in-tree drivers since xenapi was dropped in Victoria [4]. As a result I will be looking to remove support for the format during Xena unless any out of tree drivers come forward with issues. Cheers, Lee [1] https://review.opendev.org/c/openstack/nova/+/804286 [2] https://review.opendev.org/c/openstack/nova/+/804230 [3] https://docs.openstack.org/nova/latest/reference/block-device-structs.html#… [4] https://review.opendev.org/c/openstack/nova/+/749304 -- Lee Yarwood A5D1 9385 88CB 7E5F BE64 6618 BCA6 6E33 F672 2D76

1 0

[networking-bgpvpn][networking-bagpipe] Propose to EOL stable/pike and stable/queens
by Slawek Kaplonski 11 Aug '21

11 Aug '21

Hi, Regarding recent email from Elod [1] CI of the stable/pike and stable/queens branches in networking-bgpvpn is broken now. I checked that it's due to Horizon which is already EOL in those branches. I proposed patch [2] to hopefully fix it quickly by using eol tag of Horizon. But even with that there are some other problems in the openstack-tox-pep8 and networking-bgpvpn-dsvm-functional jobs. Last merged patches in networking-bgpvpn were in 2019: [3] and [4]. Giving all that I propose to make networking-bgpvpn stable/pike and stable/ queens branches to be EOL now. Networking-bagpipe project is tightly coupled with networking-bgpvpn. Last patches merged in that project were also in 2019: [5] and [6]. Because of the above, I propose also to make branches stable/pike and stable/ queens in the networking-bagpipe to be EOL. I will wait until end of next week for anyone who would like to maybe step up as maintainer of those branches. If there will be no volunteers for that, I will EOL those branches in networking-bgpvpn and networking-bagpipe. [1] http://lists.openstack.org/pipermail/openstack-discuss/2021-July/ 023944.html [2] https://review.opendev.org/c/openstack/networking-bgpvpn/+/803545 [3] https://review.opendev.org/q/project:openstack/networking-bgpvpn+branch:sta… [4] https://review.opendev.org/q/project:openstack/networking-bgpvpn+branch:sta… [5] https://review.opendev.org/q/project:openstack/networking-bagpipe+branch:st… [6] https://review.opendev.org/q/project:openstack/networking-bagpipe+branch:st… -- Slawek Kaplonski Principal Software Engineer Red Hat

1 1

[neutron] Drivers meeting 13.08 cancelled
by Slawek Kaplonski 11 Aug '21

11 Aug '21

Hi, I'm cancelling tomorrow drivers meeting. I know that Miguel and all Red Hat people will not be there so we will not have quorum on the meeting. See You all online. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

Unable to retrieve flavor details and unable to retrieve instance details
by cloud learner 11 Aug '21

11 Aug '21

Dear Experts, I have deployed victoria with controller+compute, and 2 extra compute using packstack. Everything is working fine but many times it shows the error as mentioned in the subject line. The log files of nova are attached herewith. Kindly help

2 1

[neutron] Status of networking-mlnx: Is it still maintained ?
by Takashi Kajinami 11 Aug '21

11 Aug '21

Hello, I noticed the networking-mlnx repo[1] is not updated for a while and looks unmaintained. The repo doesn't have a stable/wallaby release created, and its setup.cfg doesn't include python 3.8 as a supported platform. https://opendev.org/x/networking-mlnx Is anybody still maintaining this repo ? If the repo is no longer maintained, I'll propose deprecating support for the plugin from puppet-neutron. Please let me know if you have any concern with that deprecation. I appreciate any input about this $topic. Thank you, Takashi Kajinami

1 2

[all][tc] Technical Committee next weekly meeting on Aug 12th at 1500 UTC
by Ghanshyam Mann 11 Aug '21

11 Aug '21

Hello Everyone, Technical Committee's next weekly meeting is scheduled for Aug 12th at 1500 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Wednesday, Aug 11th, at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

Automating import of large numbers of VMs to OpenStack from other hypervisor environment
by KK CHN 11 Aug '21

11 Aug '21

Hi list, I am in the process of migrating 150+ VMs running on Rhevm4.1 to KVM based OpenStack installation ( Ussuri with KVm and glance as image storage.) What I am doing now, manually shutdown each VM through RHVM GUI and export to export domain and scp those image files of each VM to our OpenStack controller node and uploading to glance and creating each VM manually. query 1. Is there a better way to automate this migration by any utility or scripts ? Any one done this kind of automatic migration before what was your approach? Or whats the better approach instead of doing manual migration ? Or only manually I have to repeat the process for all 150+ Virtual machines? ( guest VMs are CentOS7 and Redhat Linux 7 with LVM data partitions attached) Kindly share your thoughts.. Query 2. other than this 150+ VMs Redhat Linux 7 and Centos VMs on Rhevm 4.1, I have to migrate 50+ VMs which hosted on hyperV. What the method / approach for exporting from HyperV and importing to OpenStack Ussuri version with glance with KVM hpervisor ? ( This is the ffirst time I am going to use hyperV, no much idea about export from hyperv and Import to KVM) Will the images exported form HyperV(vhdx image disks with single disk and multiple disk(max 3 disk) VMs) can be directly imported to KVM ? does KVM support this or need to modify vhdx disk images to any other format ? What is the best approach should be in case of HyperV hosted VMs( Windows 2012 guest machines and Linux guest machines ) to be imported to KVM based OpenStack(Ussuri version with glance as image storage ). Thanks in advance Kris

1 0

[PTLs][release] Xena Cycle Highlights
by helena＠openstack.org 11 Aug '21

11 Aug '21

Hello Everyone!It's that time of the year once again! It's time to start thinking about calling out 'cycle-highlights' in your deliverables! As PTLs, you probably get many pings towards the end of every release cycle by various parties (marketing, management, journalists, etc) asking for highlights of what is new and what significant changes are coming in the new release. By putting them all in the same place it makes them easy to reference because they get compiled into a pretty website like this from the last few releases: Ussuri[1], Victoria[2]. We don't need a fully fledged marketing message, just a few highlights (3-4 ideally), from each project team. Looking through your release notes might be a good place to start. The deadline for cycle highlights is the end of the R-5 week [3] on September 3.How To Reminder: -------------------------Simply add them to the deliverables/$RELEASE/$PROJECT.yaml in the openstack/releases repo like this: cycle-highlights: - Introduced new service to use unused host to mine bitcoin.The formatting options for this tag are the same as what you are probably used to with Reno release notes.Also, you can check on the formatting of the output by either running locally: tox -e docsAnd then checking the resulting doc/build/html/$RELEASE/highlights.html file or the output of the build-openstack-sphinx-docs job under html/$RELEASE/highlights.html. Feel free to add Kendall Nelson (diablo_rojo) as a reviewer on your patches. Can't wait to see you all have accomplished this release! Thanks :) -Helena Spease (hspease) [1] [ https://releases.openstack.org/ussuri/highlights.html ]( https://releases.openstack.org/ussuri/highlights.html ) [2] https://releases.openstack.org/victoria/highlights.html [3] https://releases.openstack.org/xena/schedule.html

1 1

OpenInfra Live - August 12th at 9am CT
by Erin Disney 11 Aug '21

11 Aug '21

Hi everyone, This week’s OpenInfra Live episode is brought to you by the Bare Metal SIG. Join us as members from the Bare Metal SIG join us to discuss how Ironic works to simplify many of the hardships physical bare metal operators deal with on a daily basis, including an overview of the project, project roadmap, and use cases of Ironic in production. Episode: Bare Metal: Ironic In Production Date and time: August 12th at 9am CT (1400 UTC) You can watch us live on: YouTube: https://www.youtube.com/watch?v=m81Q2bU9bGU <https://www.youtube.com/watch?v=m81Q2bU9bGU> LinkedIn: https://www.linkedin.com/feed/update/urn:li:ugcPost:6830910904905940992/ <https://www.linkedin.com/feed/update/urn:li:ugcPost:6830910904905940992/> Facebook: https://www.facebook.com/104139126308032/posts/4229345477120689/ <https://www.facebook.com/104139126308032/posts/4229345477120689/> WeChat: recording will be posted on OpenStack WeChat after the live stream Speakers: Julia Kreger (Red Hat) Mohammed Naser (Vexxhost) Mark Goddard (Stack HPC) Chris Krelle (NVIDIA) Have an idea for a future episode? Share it now at ideas.openinfra.live <https://openinfrafoundation.formstack.com/forms/openinfralive>. Thanks, Erin Erin Disney Event Marketing Open Infrastructure Foundation

1 0

[cinder] Bug deputy report for week of 2021-11-08
by Sofia Enriquez 11 Aug '21

11 Aug '21

Hello, This is a bug report from 2021-04-08 to 2021-11-08. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Incomplete - https://bugs.launchpad.net/cinder/+bug/1939145 "[IBM Storwize SVC]: use system_id in mkrelationship". Unassigned. Wishlist - https://bugs.launchpad.net/cinder-tempest-plugin/+bug/1939325 "Add placement service to README". Unassigned. - https://bugs.launchpad.net/cinder-tempest-plugin/+bug/1939322 " glance registry was deprecated in Queens and should be removed from README". Unassigned. Cheers, -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

[cyborg]Cyborg weekly meeting time slot
by Wang, Xin-ran 11 Aug '21

11 Aug '21

Hi all, I would like to let you know that the now time slot of Cyborg Weekly meeting is 12:00-13:00 UTC. Welcome to join us on https://www.irccloud.com/irc/oftc/channel/openstack-cyborg. Thanks, Xin-Ran Wang

1 0

[all][elections][ptl][tc] Combined PTL/TC Election Season
by helena＠openstack.org 10 Aug '21

10 Aug '21

Election details: [ https://governance.openstack.org/election/ ]( https://governance.openstack.org/election/ ) Hello everyone! The nomination period officially begins August 17, 2021 23:45. Please read the stipulations and timelines for candidates and electorate contained in this governance documentation. The PTL and TC elections for the coming cycle will run concurrently; deadlines for their nomination and voting activities are synchronized but will still use separate ballots. Please note, if only one candidate is nominated as PTL for a project team during the PTL nomination period, that candidate will win by acclaim, and there will be no poll. There will only be a poll if there is more than one candidate stepping forward for a project team's PTL position. If teams do not produce any PTL candidate during the nomination period, or are interested in considering alternatives prior to nominations, the TC may consider requests to switch to the new distributed leadership model they recently documented[1]. In keeping with the established plan[1 ] to gradually reduce the size of the Technical Committee, we will only fill four (4) seats in this coming election. There will be further announcements posted to the mailing list as action is required from the electorate or candidates. This email is for information purposes only. If you have any questions which you feel affect others please reply to this email thread. If you have any questions that you which to discuss in private please email any of the election officials[3] so that we may address your concerns. [1] [ https://governance.openstack.org/tc/resolutions/20200803-distributed-projec… ]( https://governance.openstack.org/tc/resolutions/20200803-distributed-projec… ) [2] [ https://governance.openstack.org/tc/reference/charter.html#number-of-seats-… ]( https://governance.openstack.org/tc/reference/charter.html#number-of-seats-… ) [3] [ https://governance.openstack.org/election/#election-officials ]( https://governance.openstack.org/election/#election-officials ) Cheers, Helena on behalf of the OpenStack Technical Election Officials

1 0

[OSSA-2021-003] Keystone: Account name and UUID oracles in account locking (CVE-2021-38155)
by Jeremy Stanley 10 Aug '21

10 Aug '21

=============================================================== OSSA-2021-003: Account name and UUID oracles in account locking =============================================================== :Date: August 10, 2021 :CVE: CVE-2021-38155 Affects ~~~~~~~ - Keystone: >=10.0.0 <16.0.2, >=17.0.0 <17.0.1, >=18.0.0 <18.0.1, >=19.0.0 <19.0.1 Description ~~~~~~~~~~~ Samuel de Medeiros Queiroz with Oi Cloud reported a vulnerability affecting Keystone account locking. By guessing the name of an account and failing to authenticate multiple times, any unauthenticated actor could both confirm the account exists and obtain that account's corresponding UUID, which might be leveraged for other unrelated attacks. All Keystone deployments enabling security_compliance.lockout_failure_attempts are affected. Patches ~~~~~~~ - https://review.opendev.org/790444 (Train) - https://review.opendev.org/790443 (Ussuri) - https://review.opendev.org/790442 (Victoria) - https://review.opendev.org/790440 (Wallaby) - https://review.opendev.org/759940 (Xena) Credits ~~~~~~~ - Samuel de Medeiros Queiroz from Oi Cloud (CVE-2021-38155) References ~~~~~~~~~~ - https://launchpad.net/bugs/1688137 - http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-38155 -- Jeremy Stanley

1 0

[TC] [horizon] Project Skyline Timeline
by Kendall Nelson 10 Aug '21

10 Aug '21

Hello All! I would like to introduce you to project Skyline[1]! The team has been hard at work getting it ready for the project proposal stage. While they are not quite ready yet (still working on Zuul testing and devstack integration), I wanted to take a moment and give a little history on conversations in this space and see if there was anything else they needed to do before we actually draft the project proposal. There was a mailing list thread[2] a while back that discussed updating Horizon and what that would look like. I would encourage you to read it if you're interested in the complete history, but it all boils down to a few summaries- Mohammed's[3]: ".... 1. Distributions are happy in the way that Horizon is deployed today 2. Distributions don't want to have a front-end JS based thingamajig 3. Users, operators and deployers want to improve the UI experience of Horizon 4. There is so much _historic_ stuff stuffed into Horizon that rewriting something from scratch is easier than refactoring Horizon 5. The path to improving UI inside OpenStack is "starting from scratch". ...." Adrian's [4]: "...As corny as it sounds, I think the first step is admitting we have a problem, and getting a group of interested parties involved to actually "design/build something better by broadcasting a call to arms of sorts. Radomir's [5]: "The current Horizon developers are not going to do it. We are too busy maintaining the released versions of Horizon and trying to keep up with new features being added to OpenStack, and that situation is unlikely to change for at least several years from now, even if a replacement for Horizon with full feature parity was released tomorrow — we will still need to support the released versions of Horizon. We are happy to help with advice and explanations of how current Horizon implementation works — but we won't write the code. You have to start that project yourself or find other developers willing to work on it, who won't mind you telling them which framework to use." Thierry's[6]: " From the outside of this hypothetical team, the Horizon team says that it will continue to maintain the distro-friendly Django-based Horizon code, and that as a team it has no interest/bandwidth in driving a rewrite internally. That means a new team needs to form up (even if obviously some people can be member of both teams). Now from the outside of this hypothetical new team, the TC can say if it supports the idea of a more-JS-native harder-to-package framework and would gladly add it the list of official OpenStack project teams as an alternative solution to Horizon. That may encourage some to step up." And Akihiro[7] "The current state of horizon is almost in the maintenance mode. We have less contributors release by release. The current horizon team is very small (and horizon cores except one are part-time with other projects or outside of OpenStack upstream), so I don't think the horizon team can lead the effort properly. I think it is better that folks interested in this start an effort to implement OpenStack dashboard in modern technologies for better UX as a separate project (or a separate branch)." Cut to the last PTG[8] when the Skyline folks attended the Horizon sessions to work with the team which you can also catch up. And now, we have the Skyline team working on the last few things (I think) before they are ready to propose it as an OpenStack project. I, for one, am excited to have this infusion of new contributors that can help bring a new OpenStack dashboard into reality. If you have any feedback on other things that need to happen before they can be proposed as a project, please reply! -Kendall Nelson (diablo_rojo) [1] Repos: https://opendev.org/skyline/ [2] Original thread: http://lists.openstack.org/pipermail/openstack-discuss/2020-June/015551.html [3] Mohammed's summary http://lists.openstack.org/pipermail/openstack-discuss/2020-June/015654.html [4] Adrian's summary http://lists.openstack.org/pipermail/openstack-discuss/2020-June/015659.html [5] Radomir's summary http://lists.openstack.org/pipermail/openstack-discuss/2020-June/015667.html [6] Thierry's summary http://lists.openstack.org/pipermail/openstack-discuss/2020-June/015674.html [7] Akihiro's summary http://lists.openstack.org/pipermail/openstack-discuss/2020-June/015575.htm… [8] PTG Discussion: https://etherpad.opendev.org/p/xena-ptg-horizon-planning

1 0