- openstack-discuss - lists.openstack.org

[elections][ptl][barbican]
by Douglas Mendizabal 11 Feb '22

11 Feb '22

Hi All, I would like to continue to serve as Barbican PTL for the Z cycle. Barbican is slowly moving forward, and I would like to see improvements continue for the next cycle. Thanks, Douglas Mendizábal OFTC: dmendiza[m]

1 0

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

11 Feb '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week meeting yesterday. Most of the meeting discussions are summarized below (Completed or in-progress activities section). Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-02-10-15.00.log.html * Next week's meeting is on 17th Feb Thursday 15:00 UTC, feel free add the topic on the agenda[1] by 16th Feb. 2. What we completed this week: ========================= * Reverted the neutron-fwaas deprecation and it is maintained under neutron stadium now[2]. * Removed security-specs from security sig[3]. 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[4]. 2 out of 9 items are completed. Open Reviews ----------------- * Four open reviews for ongoing activities[5]. Dropping tags framework ------------------------------ yoctozepto has updated the part1 of dropping the tag framework[6] which is ready for review. He will continue working on part2 which is to update the release scripts and openstack navigation sites to remove the tag usage. Z release cycle name ------------------------- TC selection on proposed names is closed and selected names are under trademark checks by foundation, follow the ML[7] for updates. Z release cycle Technical Election --------------------------------------- Nomination for PTL and TC election are in-progress and will be open until 15th Feb[8]. I would like to encourage project leaders to stand for PTL and community members to run for TC. Please add your nomination before deadline[9]. TC position on release cadence ------------------------------------- We had separate call to discuss the next step and TC position on release cadence[10] and as discussed Dan has proposed the new release model as TC resolution[11]. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[12]. Project updates ------------------- * Retire js-openstack-lib (waiting on Adjutant to have new PTL/maintainer) [13] 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[14]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [15] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/828078 [3] https://review.opendev.org/c/openstack/governance/+/828018 [4] https://etherpad.opendev.org/p/tc-yoga-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] https://review.opendev.org/c/openstack/governance/+/822900 [7] http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026810.… [8] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027117… [9] https://governance.openstack.org/election/ [10] https://meetpad.opendev.org/OpenStackReleasecadence [11] https://review.opendev.org/c/openstack/governance/+/828777 [12] https://etherpad.opendev.org/p/zuul-config-error-openstack [13] https://review.opendev.org/c/openstack/governance/+/798540 [14] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [15] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[Manila] Yoga Collab reviews
by Fernando Ferraz 11 Feb '22

11 Feb '22

Hi Team, Would like to invite you to our collaborative review session occurring next Monday and Thursday (Feb. 14tth and 17th). Following our proposals targeted to the Yoga cycle, all patches partially implement the release independent spec "*Add spec for multiple subnet share servers" *[1]. *February 14th (16:00-17:30 UTC):* - 825110: Add multiple subnets per AZ support https://review.opendev.org/c/openstack/manila/+/825110 *February 17th (16:00-17:30 UTC):* - 825155: NetApp ONTAP: Add support to multiple subnets per AZ https://review.opendev.org/c/openstack/manila/+/825155 - 826462: Container: Multiple subnets per AZ https://review.opendev.org/c/openstack/manila/+/826462 [1] https://review.opendev.org/c/openstack/manila-specs/+/619925 Regards, Fernando

2 2

[release] Release countdown for week R-6, Feb 14-18
by Előd Illés 11 Feb '22

11 Feb '22

Development Focus ----------------- Work on libraries should be wrapping up, in preparation for the various library-related deadlines coming up. 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. 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 February 17th, 2022. Only bugfixes releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/yogabranching request with the review (as an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… In the next weeks we will have deadlines for: * Client libraries (think python-*client libraries), which need to have their last feature release before "Client library freeze" (February 24th, 2022) * Deliverables following a cycle-with-rc model (that would be most services), which observe a Feature freeze on that same date, February 24th, 2022. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. As we are getting to the point of creating stable/yogabranches, this would be a good point for teams to review membership in their $project-stable-maint groups. Once the stable/yogabranches are cut for a repo, the ability to approve any necessary backports into those branches for Yogawill 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. Upcoming Deadlines & Dates -------------------------- Non-client library freeze: February 17th, 2022(R-6 week) Client library freeze: February 24th, 2022(R-5 week) Yoga-3 milestone: February 24th, 2022(R-5 week) Cycle Highlights Due: February 24th, 2022(R-5 week) Yogafinal release: March 30th, 2022 Next PTG: April 4 - 8, 2022 (virtual) ElődIllés irc: elodilles

1 0

[election][nova] Sylvain to throw his hat into the Nova PTL ring again
by Sylvain Bauza 11 Feb '22

11 Feb '22

Hello again Nova (and Placement) fellows, This went fast, but it's time for me to run again for the Nova PTL position, this time for the Zen/Zombie/Zeta [1] release cycle, after having been the PTL for the Yoga cycle. Just a quick look at this current cycle. First, it was quick but : - we added a new way to help contributors to say they are reviewing some change - we now have a new nova-core - we have around 25 accepted feature requests and 15 of them are already reviewed. What we had't yet time to discuss and what I'd like us to start to look are : - given some operators want to upgrade at least every year, we should try to start seeing how to support two-cycle-older computes - sometimes we want to do things that we'd like but that we don't have time for. Some of them are actually simple to implement. Maybe then we should organize back ways to share ideas to new contributors and provide them mentoring efforts (eg. with Outreachy or any engineering interns wanting to work on OpenStack and Nova in particular) As you know, I'm also open to any idea. I'm not a leader, I'm just a herder. Thanks, -Sylvain [1] Pick any Z name you want given we don't know yet the result.

1 0

[cinder][nova][ironic][glance][downstream distro] raising requirements minima in yoga os-brick
by Brian Rosmaita 11 Feb '22

11 Feb '22

Hello os-brick consumers, I have a patch up raising the minima in {test-}requirements.txt for the yoga os-brick release. I seem to remember that when I did this without warning last cycle, it caused a few issues (I think mostly a cascade of updates at an inconvenient time for people still maintaining lower-constraints.txt; probably nothing more serious because we're all testing in the gates with the latest versions allowed by upper-constraints anyway). The commit message on the patch explains what changes are made (and some that aren't): https://review.opendev.org/c/openstack/os-brick/+/828802 Please respond before 18:00 UTC on Monday 14 Feb if you see any issues. (Sorry this email is a bit late, but that's how I roll.) cheers, brian

1 0

[election][trove][ptl] PTL non-candidacy
by Lingxian Kong 11 Feb '22

11 Feb '22

Hi all, I'm writing this email to let you know that I'm not going to run for Trove PTL for Z dev cycle. I've been serving Trove PTL since Train, trying the best to revive the project back to production ready, lots of changes have been made since then, and also helped my former employer successfully deploy Trove in production and pass the security review conducted by the 3rd party security company. However, I changed my job recently and shifted the focus, can't guarantee the contribution for this open source project, hopefully someone could pick that up and drive the project. I'm willing to provide help if needed. --- Lingxian Kong

1 0

[neutron] Drivers meeting - Friday 11.2.2022 - cancelled
by Lajos Katona 10 Feb '22

10 Feb '22

Hi Neutron Drivers! Due to the lack of agenda, let's cancel tomorrow's drivers meeting. See You on the meeting next week. Lajos Katona (lajoskatona)

1 0

[kolla][ceilometer][gnocchi] Error in ceilometer_central service
by Mahendra Paipuri 10 Feb '22

10 Feb '22

Hello, I am playing around Openstack using kolla-ansible deployment on a single node. I am facing the same issue as here -> https://bugs.launchpad.net/kolla-ansible/+bug/1920095. I see that there is an PR here -> https://review.opendev.org/c/openstack/kolla-ansible/+/781595 but has not been merged. Is it still a bug or am I missing something in kolla configuration? Cheers Mahendra

1 1

[TaskFlow]
by 黄一心 09 Feb '22

09 Feb '22

Hi, In our project, the taskflow is used to back up and restore data. After the task is submitted or started to run, the task may be suspended. However, the program process still exists. It seems that the thread for executing the task is missing. After the program process is restarted, the task can be resumed. Can you give us some advice. Thank you.

1 0

[TaskFlow]
by 黄一心 09 Feb '22

09 Feb '22

发自我的iPhone

1 0

[all][tc] Technical Committee next weekly meeting on Feb 10th at 1500 UTC
by Ghanshyam Mann 09 Feb '22

09 Feb '22

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

1 1

[election][tc] Non-candidacy
by Belmiro Moreira 09 Feb '22

09 Feb '22

Dear all, I would like to let you know that I won't run for the Technical Committee (TC). After 2 years in this role I believe that it’s time for some rotation. It was a pleasure to work with all of you. Thank you for this amazing experience. cheers, Belmiro

4 3

[openstacksdk] create object (eg. snapshot) on behalf of user as admin
by Benedikt Trefzer 09 Feb '22

09 Feb '22

Hi list I like to connect as an amin user to an openstack cloud and create a snapshot of a volume in the same project as the volume exists. I use the openstacksdk to achive this in python. So far I can connect as admin and create the snapshot but the snapshot is in the admins project, not in the project of the volume. Code so far: from openstack import connect import openstack.config conn=connect() conn.volume.create_snapshot(name='test', description='testing', volume='volumeIDinANYproject') I tried to use conn.connect_as_project('ProjectID') but was not successfull. Please direct me in the correct direction to achive this ! Any help appreciated. Greeting Benedikt

2 2

[Skyline] Project mascot to review
by James Cole 09 Feb '22

09 Feb '22

Greetings everyone, I’m James, a designer with the OpenInfra Foundation. We have a been working on a new project mascot for Skyline and wanted to share a couple of options with you. The reference we were provided alluded to a nine-color-deer, so we created a deer illustration in the style of the other project mascots. The two options are essentially the same, but one is white with spots and the other is yellow with spots. Let me know if you like one or the other—or if we’re totally off on the theme—and we will add the text to the logo and finalize the assets. There is a PDF attached to this message or you can view the document by visiting this link <https://www.dropbox.com/s/d2ikaphzhml7tqb/20220120%20Mascots%20Project.pdf?…>. Thank you! -James

11 20

[ironic] kickstart/iso configuration
by Carol Bouchard 09 Feb '22

09 Feb '22

Ironic folks: I've set-up bifrost which is spawning two VMs to test with. I'm using the xena branch for both bifrost and ironic. Bifrost sets these VMs up as whole-disk-images. I've undeployed one VM and trying to deploy the same VM by using the default kickstart file and a RHEL7 ISO file but I'm not having any success. Could you suggest what configuration changes are expected in this case to get this to work? What would you expect deploy-interface and instance-info to look like? BTW And I've applied portions (changes to cache_ramdisk_kernel() only) of the patch for https://review.opendev.org/c/openstack/ironic/+/827924. Carol

2 1

[Update Process]
by Joshua Crawford 09 Feb '22

09 Feb '22

Hi, I have been given the task of updating our openstack/swift setup. Currently, we are on openstack 2.3.1 with python-swiftclient 3.0.0 on Ubuntu 16.04. My plan is to upgrade Ubuntu to 18.04 and then to 20.04. Then focus on updating openstack and swift. I do not have any previous experience with openstack or swift, but from what I have read so far, our current version is not supported on anything newer than Ubuntu 16.04. Should I revise my plan and look at updating openstack/swift first, or is my plan to update Ubuntu first a good path forward. Thank you, joshua. [cid:d105ac7d-e828-4289-8ff1-70d919cdb057.jpg] [cid:Quadrivium-Logo_Horizontal-OneColor-CyberSecurityServices_456360a7-a556-4b83-b682-08dcceeef14a.jpg] Joshua Crawford | Senior Engineer Quadrivium Inc. | 5537 Bleaux Ave. Springdale, AR 72762 479.419.4600 | quadrivium.com<https://quadrivium.com> [cid:cyber-verify-2021-AAA_2ce098a9-58cb-442b-9293-b75ce40d6ff4.jpg] This message is confidential. It may also be privileged or otherwise protected by work product immunity or other legal rules. If you have received it by mistake, please let us know by e-mail reply and delete it from your system; you may not copy this message or disclose its contents to anyone. The integrity and security of this message cannot be guaranteed on the Internet.

2 3

[election][Neutron]PTL candidacy for Z
by Lajos Katona 09 Feb '22

09 Feb '22

Hello Openstack Community, I write to submit my candidacy for the Neutron PTL position during the Z cycle. I have been PTL for the Yoga cycle, and I would like to serve the community for another cycle. During the last few cycles the team faced a lot of challenges, like: * Lack of review capacity, which on the other hand means that we have a lot to review, and that is good. * Channel in developers from new companies. * Keep Neutron stable while at the same time keep the speed of feature development. * CI instabilities. * Keep coverage and decrease the load Neutron jobs cause in the infra. The team tried to address these, so we have biweekly video meeting for CI issues (on the other week we kept the IRC for CI meeting), we increased the size of the drivers team, we included back some retired stadium project with new developers who would like to maintain them, or worked actively to decrease the amount of jobs we execute for each commit. As a summary I would like to continue with a focus on these items to keep Networking in Openstack stable and inclusive. Thank you for your time and consideration. Lajos Katona (lajoskatona)

1 0

[kolla] [horizon] Custom logos (WAS: [Openstack-operators] Horizon Custom Logos (Queens, 13.0.1))
by Gregory Orange 09 Feb '22

09 Feb '22

We have been using Ubuntu VMs for the control plane until now, so it was a simple matter of inserting our logo-splash.svg and logo.svg into /var/lib/openstack-dashboard/static/dashboard/img/ and then restarting services. Now we're switching to Kolla, and the relevant path isn't mounted as is the case with the likes of /etc/kolla/horizon and /var/log/kolla. We don't (yet?) build our own container images, so I'm wondering what next. Did anyone get any further with this? On 21/8/18 9:28 pm, Nick Jones wrote: > Hi Erich. > > Yeah, I battled against this myself quite recently. Here's what I did > to add a logo to the Horizon splash page and to the header of each page > itself. > > Create a file called _splash.html, containing: > > <div class="text-center"> > <img class="splash-logo" src={% themable_asset "img/logo.png" %}> > </div> > > And a file called _brand.html, containing: > > {% load branding %} > {% load themes %} > > <a class="navbar-brand" href="{% site_branding_link %}" target="_self"> > <img class="openstack-logo" src="{% themable_asset 'img/logo.png' %}" > alt="{% site_branding %}"> > </a> > > I then created a folder > called /usr/share/openstack-dashboard/openstack_dashboard/themes/default/templates/auth/ > and copied _splash.html into there, copied _brand.html > into /usr/share/openstack-dashboard/openstack_dashboard/templates/header/, > and finally my 'logo.png' was copied > into /usr/lib/python2.7/site-packages/openstack_dashboard/static/dashboard/img/ > > Note that this approach might differ slightly from your setup, as in my > case it's a Kolla-based deployment so these changes are applied to the > image I'm using to deploy a Horizon container. But it's the same > release (Queens) and a CentOS base image, so in principle the steps > should work for you. > > Hope that helps. > > -- > > -Nick > > On 20 August 2018 at 17:40, Erich Weiler <weiler(a)soe.ucsc.edu > <mailto:weiler@soe.ucsc.edu>> wrote: > > Hi Y'all, > > I've been banging my head against a wall for days on this item and > can't find anything via google on how to get around it - I am trying > to install a custom logo onto my Horizon Dashboard front page (the > splash page). I have my logo ready to go, logo-splash.png. I have > tried following the instructions here on how to install a custom logo: > > https://docs.openstack.org/horizon/queens/admin/customize-configure.html > <https://docs.openstack.org/horizon/queens/admin/customize-configure.html> > > But it simply doesn't work. It seems this stanza... > > #splash .login { > background: #355796 url(../img/my_cloud_logo_medium.png) no-repeat > center 35px; > } > > ...doesn't actually replace the logo (which is logo-splash.svg), it > only seems to put my file, logo-splash.png as the *background* to > the .svg logo. And since the option there is "no-repeat center", it > appears *behind* the svg logo and I can't see it. I played around > with those options, removing "no-repeat" for example, and it > dutifully shows my logo repeating in the background. But I need the > default logo-splash.svg file to actually be gone and my logo to > exist in it's place. Maybe I'm missing something simple? > > I'm restarting apache and memchached after every change I make when > I was testing. > > And because the images directory is rebuilt every time I restart > apache, I can't even copy in a custom logo-splash.svg file. Which > wouldn't help anyway, as I want my .png file in there instead. I > don't have the means to create a .svg file at this time. ;) > > Help! > > As a side note, I'm using the Queens distribution via RedHat. > > Many thanks in advance, > erich > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators(a)lists.openstack.org > <mailto:OpenStack-operators@lists.openstack.org> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators> > > > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > -- Gregory Orange Cloud System Administrator Scientific Platforms Team building representative Pawsey Supercomputing Centre, CSIRO

3 3

Recently Upgraded to XENA and getting this error
by Adivya Singh 09 Feb '22

09 Feb '22

Hello, We have recently upgraded to XENA release of Openstack, and getting this error while trying to Resize instance using GUI, it is telling "Danger , Please try Later" Same is working properly from CLI without any issue Any thoughts on this Regards Adivya Singh

9 11

[kolla-ansible] custom configuration override issue.
by Satish Patel 09 Feb '22

09 Feb '22

Folks, I have a working kolla-ansible environment and now I want to push out some nova custom changes to specific compute nodes and I am trying the following override but somehow it doesn't work for me. Ansible inventory file multinode [control] 192.168.75.141 ansible_ssh_private_key_file=/root/.ssh/nodes_ssh_key 192.168.75.142 ansible_ssh_private_key_file=/root/.ssh/nodes_ssh_key 192.168.75.143 ansible_ssh_private_key_file=/root/.ssh/nodes_ssh_key [compute] 192.168.75.[144:175] ansible_ssh_private_key_file=/root/.ssh/nodes_ssh_key I want to change some option on 192.168.75.199 compute server, I don't have compute name in inventory so i am using IP address for override but somehow that doesn't work /etc/kolla/config/nova/192.168.75.199/nova.conf I have tried the following to use hypervisor hostname but that doesn't work. What am I doing wrong here? /etc/kolla/config/nova/COMP01.local/nova.conf Following works for me but they are for global not for specific nodes. How do i override specific node file? /etc/kolla/config/nova/nova-compute.conf

2 4

Error: Not authorized for image
by Michael STFC 09 Feb '22

09 Feb '22

Hi All, I have a problem with vm. Its in error state and rebooting won’t fixed it and still no luck. Error: Failed to perform requested operation on instance “xxx-production-db”, the instance has an error status: Please try again later [Error: Not authorized for image 3457dd8a-037a-4360-b77a-059d2782cbbf.].

1 0

[neutron] Bug deputy report for week of January 31
by Lajos Katona 08 Feb '22

08 Feb '22

Hi Neutron Team I was bug deputy in neutron last week. Summary ======= Needs attention ============ * Neutron-dynamic-routing does not work with OVN ( https://bugs.launchpad.net/neutron/+bug/1959666) * [stein][neutron] Static rules losed ( https://bugs.launchpad.net/neutron/+bug/1959884) * VM gets wrong ipv6 address from neutron-dhcp-agent after ipv6 address on port was changed (https://bugs.launchpad.net/neutron/+bug/1959697) Bugs with assignees ================ * Random Tempest test failures(SSH failure) in openvswitch jobs ( https://bugs.launchpad.net/neutron/+bug/1959564) ** https://review.opendev.org/c/openstack/neutron/+/827315 * QoS Ingress bandwidth limit with OVS backend may not work as expected ( https://bugs.launchpad.net/neutron/+bug/1959567) ** WIP: https://review.opendev.org/c/openstack/neutron/+/827112 * test_local_ip_connectivity test failing in stable/xena jobs ( https://bugs.launchpad.net/neutron/+bug/1959573) ** MERGED: https://review.opendev.org/c/openstack/neutron/+/827057 * pip 22 breaks python3.6 jobs (Victoria and older CI jobs) ( https://bugs.launchpad.net/neutron/+bug/1959600) ** MERGED: https://review.opendev.org/q/Iab2c391d5388461fe9e9037cee81884ce8032e72 * minimum_packet_rate qos rule type is not visible in the GET /v2.0/qos/rule-types response ( https://bugs.launchpad.net/neutron/+bug/1959749) ** https://review.opendev.org/q/topic:bug%252F1959749 * "get_rule_type" should not check the context admin status ( https://bugs.launchpad.net/neutron/+bug/1959778) ** https://review.opendev.org/c/openstack/neutron-lib/+/827533 * ovn-octavia loadbalancer not working when VIP is on a dual-stack provider network (https://bugs.launchpad.net/neutron/+bug/1959903 ) ** https://review.opendev.org/c/openstack/ovn-octavia-provider/+/827670 * [ovn] Stale ports in the OVN database at churn ( https://bugs.launchpad.net/neutron/+bug/1960006) ** https://review.opendev.org/c/openstack/neutron/+/827834 * neutron-tempest-with-uwsgi job failing tempest tests with: Floating ip <fip> failed to associate with server <server id> in time ( https://bugs.launchpad.net/neutron/+bug/1960022 ) ** MERGED: https://review.opendev.org/c/openstack/tempest/+/814085 * NullQuota driver returns None that breaks client API ( https://bugs.launchpad.net/neutron/+bug/1960032) ** https://review.opendev.org/c/openstack/neutron/+/827875 Low hanging fruit ============= * potential performance issue when scheduling network segments ( https://bugs.launchpad.net/neutron/+bug/1959750) Need more information ================== * Disallow users to allocate gateway ip of external subnets as floating ip ( https://bugs.launchpad.net/neutron/+bug/1959699 ) Regards Lajos Katona (lajoskatona)

2 1

OpenInfra Summit Berlin- CFP Deadline in 24 Hours!
by Erin Disney 08 Feb '22

08 Feb '22

The deadline for the upcoming OpenInfra Summit’s Call for Presentations is in 24 hours! CFP for the Berlin Summit (June 7-9th) is still open until February 9th at 22:59 UTC (4:59 PM CT). Reminder that Summit attendance fees are waived for all accepted speakers. Submit your talk for the OpenInfra Summit here: https://cfp.openinfra.dev/app/berlin-2022 2022 Summit Tracks: 5G, NFV & Edge AI, Machine Learning & HPC CI/CD Container Infrastructure Getting Started Hands-on Workshops NEW: Hardware Enablement Open Development Private & Hybrid Cloud Public Cloud Security More Summit resources: Registration is live at Early Bird pricing: https://openinfrasummitberlin.eventbrite.com/ Sponsorships are available: https://openinfra.dev/summit-sponsor Apply for the Travel Support Program: https://openinfrafoundation.formstack.com/forms/TSP_Berlin2022 Questions or issues with your submission? Email speakersupport(a)openinfra.dev and we will be happy to help you sort it out. Thanks, Erin Erin Disney Event Marketing Open Infrastructure Foundation Erin Disney Event Marketing Open Infrastructure Foundation

1 0

[all][Neutron][Octavia][Nova][Kuryr] Bump pyroute2 version to 0.6.5 in stable/wallaby
by Lucas Alvares Gomes 08 Feb '22

08 Feb '22

Hi, I currently have a patch up for openstack/requirements [0] bumping the version of the pyroute2 library from 0.5.14 to 0.6.5 as the older version have a memory leak issue [1] in the NDB module which can cause the service using the library to be killed by the OOM killer because of an out-of-memory condition. This email was a suggestion by a core reviewer to raise awareness from the broader community to this change/issue. Please if you have any concerning about this version bump let us know here on in the patch itself [0] [0] https://review.opendev.org/c/openstack/requirements/+/828091 [1] https://github.com/svinota/pyroute2/issues/789 Cheers, Lucas

2 2

[ironic]Anaconda deploy interface config
by Carol Bouchard 08 Feb '22

08 Feb '22

Ironic folks: I'm trying to spawn a RHEL7 image using a kickstart file and having issues with stage2 file. First I used bifrost to initially setup a couple of VMs. (There is no openstack/glance). I'm now using one of those VMs to boot up with RHEL7. I changed the VM config with the following: *| deploy_interface | anaconda* * | instance_info | {'kernel': 'http://myip:8080/RHEL7/vmlinuz <http://myip:8080/RHEL7/vmlinuz>', 'ramdisk': 'http://myip:8080/RHEL7/initrd.img <http://myip:8080/RHEL7/initrd.img>', 'image_source': 'http://myip:8080/RHEL7/initrd.img <http://myip:8080/RHEL7/initrd.img>', 'stage2': 'http://myip:8080/RHEL7/squashfs.img <http://myip:8080/RHEL7/squashfs.img>', 'ks_cfg': 'http://myip:8080/RHEL7/ks.cfg.template <http://myip:8080/RHEL7/ks.cfg.template>', 'ks_template': 'http://myip:8080/RHEL7/ks.cfg.template <http://myip:8080/RHEL7/ks.cfg.template>'}* ironic.conf changes I made are as follows: *enabled_deploy_interfaces = direct,ramdisk,anaconda* *[anaconda]default_ks_template = file:///etc/ironic/ks.cfg.template* The error I'm getting is as follows: *$ baremetal node show testvm1 --field last_error* *| last_error | Deploy step deploy.deploy failed with IsADirectoryError: [Errno 21] Is a directory: '/httpboot/4e41df61-84b1-5856-bfb6-6b5f2cd3dd11/LiveOS/squashfs.img'.* Tail end of traceback is as follows: * ironic-conductor[]: ERROR ironic.conductor.utils File "/opt/stack/bifrost/lib64/python3.9/site-packages/ironic/common/pxe_utils.py", line 1245, in cache_ramdisk_kernel ironic-conductor[]: ERROR ironic.conductor.utils deploy_utils.fetch_images(ctx, TFTPImageCache(), list(t_pxe_info.values()), ironic-conductor[]: ERROR ironic.conductor.utils File "/opt/stack/bifrost/lib64/python3.9/site-packages/ironic/drivers/modules/deploy_utils.py", line 240, in fetch_images ironic-conductor[]: ERROR ironic.conductor.utils cache.fetch_image(href, path, ctx=ctx, force_raw=force_raw) ironic-conductor[]: ERROR ironic.conductor.utils File "/opt/stack/bifrost/lib64/python3.9/site-packages/ironic/drivers/modules/image_cache.py", line 120, in fetch_image ironic-conductor[]: ERROR ironic.conductor.utils dest_up_to_date = _delete_dest_path_if_stale(master_path, ironic-conductor[]: ERROR ironic.conductor.utils File "/opt/stack/bifrost/lib64/python3.9/site-packages/ironic/drivers/modules/image_cache.py", line 460, in _delete_dest_path_if_stale ironic-conductor[]: ERROR ironic.conductor.utils os.unlink(dest_path) ironic-conductor[]: ERROR ironic.conductor.utils IsADirectoryError: [Errno 21] Is a directory: '/httpboot/4e41df61-84b1-5856-bfb6-6b5f2cd3dd11/LiveOS/squashfs.img'* Please advise. Carol

3 5

[election][cinder] PTL Candidacy for Z
by Rajat Dhasmana 08 Feb '22

08 Feb '22

Hi All, I would like to announce my candidacy for PTL of the Cinder project for the Z cycle. Since this is the first time I'm proposing my candidacy, I would like to briefly introduce myself. I started contributing to OpenStack back in the Queens release (although not very actively) and started focusing on the Cinder project in the Rocky release. I became a core reviewer in Cinder in the mid of the Stein release and since then I've been actively contributing to the Cinder project in terms of features, bug fixes, reviews etc. I'm also a part of Cinder's core security group and a stable core and currently serving as release liaison for Cinder for the past 3 releases. Coming to the focus for the Z release, Cinder receives an abundance of commits every cycle in terms of new drivers, driver features, core cinder features, bug fixes, improvements etc and we've always faced a shortage in reviews. It is not due to fewer people working actively but more of a priority issue in their respective roles. I would like to encourage contributors to discuss with their managers about the importance of code review in opensource and how it is helpful for the community and the individuals as well. Apart from that, I would like to revisit the security issues backlog since that hasn't been looked upon in quite some time and if we encounter something that needs attention, we can also hold core security meetings from time to time to address the issues. We are also getting active driver contributions every cycle which is a good thing, but sadly the driver implementation patches seem to have a lot of mistakes which are well documented in the driver contribution docs and something I would like to highlight in the Z PTG (as most of the vendors join it and propose their driver ideas). Again, the documentation is not perfect as we discussed in Yoga PTG. Following up upon this and improving it is another focus I support for Cinder. Lastly, I would like to put more emphasis upon the 3rd Party CI compliance check which we haven't done in a while and it would be good to know how many vendors are actually maintaining their CI consistently. There are some new ideas started by Brian in the past releases which I would like to continue. Some examples include the last cinder meeting being a video+IRC meeting and every third Friday of the month, we have a festival of XS reviews which significantly reduced the backlog of open patches. In the end, I would like to say, I want to continue the good trends set in the Cinder community and improve on certain areas where there is not much attention being given. I will do my best to address the above mentioned items during my time as PTL. Thanks for considering me. Rajat Dhasmana (whoami-rajat)

1 0

[election][tc] My TC non-candidacy
by Radosław Piliszek 08 Feb '22

08 Feb '22

Dears, I am hereby announcing my TC non-candidacy. It was a great pleasure to work with you but my personal and professional life has shifted away from OpenStack enough to make it hard for me to dedicate the time the TC deserves. Kind regards, -yoctozepto

4 3

[all][elections][ptl][tc] Combined PTL/TC z cycle Election Nominations Kickoff
by Ghanshyam Mann 08 Feb '22

08 Feb '22

Hello Everyone, Nominations for OpenStack PTLs (Project Team Leads) and TC (Technical Committee) positions (5 positions) are now open and will remain open until Feb 15, 2022 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 Please make sure to follow the candidacy file naming convention: candidates/z/<Project_Name or "TC">/<email_address> (for example, "candidates/z/TC/stacker(a)example.org"). The name of the file should match an email address for your current OpenStack Foundation Individual Membership. Take this opportunity to ensure that your OSF member profile contains current information: https://www.openstack.org/profile/ Any OpenStack 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 OpenStack Foundation Individual Member. PTL candidates must also have contributed to the corresponding team during the Xena to Yoga timeframe, Mar 26, 2021 00:00 UTC - Feb 15, 2022 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 Feb 22, 2022 23:45 UTC through to Mar 01, 2022 23:45 UTC. The electorate for the TC election are the OpenStack Foundation Individual Members who have a code contribution to one of the official teams over the Xena to Yoga timeframe, Mar 26, 2021 00:00 UTC - Feb 15, 2022 00:00 UTC, as well as any Extra ATCs who are acknowledged by the TC. The electorate for a PTL election are the OpenStack Foundation Individual Members who have a code contribution over the Xena to Yoga timeframe, Mar 26, 2021 00:00 UTC - Feb 15, 2022 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/ and their individual team pages include lists of corresponding Extra ATCs. Please find below the timeline: PTL + TC nomination starts @ Feb 08, 2022 23:45 UTC PTL + TC nomination ends @ Feb 15, 2022 23:45 UTC TC campaigning starts @ Feb 15, 2022 23:45 UTC TC campaigning ends @ Feb 22, 2022 23:45 UTC PTL + TC elections start @ Feb 22, 2022 23:45 UTC PTL + TC elections end @ Mar 01, 2022 23:45 UTC Shortly after election officials approve candidates, they will be listed on the https://governance.openstack.org/election/ page. The electorate is requested to confirm their email addresses in Gerrit prior to 2022-02-15 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 OSF member profiles can be updated at https://review.openstack.org/#/settings/contact and https://www.openstack.org/profile/ accordingly. 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 -gmann & The OpenStack Technical Election Officials

1 0

[stable] sphinx docs jobs fail on old stable branches (no more py2 support)
by Előd Illés 08 Feb '22

08 Feb '22

Hi stable maintainers, This mail is about to get some attention to build-openstack-sphinx-docs job that recently started to fail on old stable branches (Queens and Pike) and block gates for about ~30 repositories. (The failures are also visible in periodic stable jobs). This is because py27 support from sphinx jobs were removed [1] recently. (Python 3 (py35) support was mostly done in Rocky so that branch is not affected) To unblock the gates I see the following options: 1. fix sphinx jobs to work with py35 (most probably requires some patches to backport - in a squashed patch - and maybe some resolution of requirement conflicts) 2. set sphinx jobs to non-voting (even better to remove them to do not use resources unnecessarily) 3. revert the patch [1] that removed the py2 support of sphinx (maybe the easiest thing to do, though i understand that py2 support is something that shouldn't be kept forever) 4. teams examine their old branches and if they are not really maintained, haven't merged patches recently, then probably it is a good time to propose their EOL transition according to the EOL process [1] Some additional thoughts: - When Extended Maintenance was introduced the community agreed that certain CI jobs can be removed, CI coverage can be reduced as time goes. - To keep open an old branch in Extended Maintenance helps the cooperation between vendors / users as instead of maintaining it by themselves it can be done with a common effort, which could be beneficial for everyone. On the other hand, if there are no maintainers or invested efforts to keep the branch and CI alive, then it is a reasonable decision to transition the branch to End of Life. Please consider the above options and act to eliminate the gate failures / periodic stable job failures. [1] https://review.opendev.org/c/zuul/zuul-jobs/+/827588 <https://review.opendev.org/#/q/I98c3da5b02a4ac7fb9d7bd8e00170762e77b9f40>[2] https://docs.openstack.org/project-team-guide/stable-branches.html#end-of-l… Thanks, Előd

2 1

[election][ptl][cinder] PTL non-candidacy
by Brian Rosmaita 08 Feb '22

08 Feb '22

Hello Argonauts, With the election season rapidly approaching [0], I want to communicate my intentions to the team, to wit, I will not be standing for PTL for the Z cycle. I've served as PTL for five cycles, which conflicts with my belief that it's good for open source projects to rotate leadership. I think the Cinder project is fairly healthy, but it will be good to have someone take the Cinder helm who has a fresh perspective and who will be as excited to be PTL as I was way back in Ussuri. We have an excellent project team, and I have no doubt that whoever steps up will have plenty of support from the Cinder community (including me, I don't have any intention of going anywhere in the near term). cheers, brian [0] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027070…

7 6

Floating IP issue regarding Latest upgrade to XENA
by Adivya Singh 08 Feb '22

08 Feb '22

Hi Team, We have the latest upgrade to XENA, and we are facing an issue with XENA release , where a few times, even Floating IP attached to the instance are not reachable. I tried various ways to troubleshoot the issue, Regarding The IP is reachable from the router Namespace, The router IP is reachable, L3 agent is working Fine, as other Floating IP are reachable which are hosted through router on L3 agent, All ports are up, Interfaces are up, SNAT and DNAT are working Fine, But as soon as i dissociate and associate the Floating IP , it started working Fine Any Idea, why this Happening , and later on Fixed when Floating IP is dissociate and associate again, and later again starts happening Regards Adivya Singh

1 0

[ironic] Each deploy overwrites the entire target disk
by Radosław Piliszek 08 Feb '22

08 Feb '22

Dears, I have a question regarding the default behaviour of Ironic Python Agent - it seems that each deploy causes the entire target disk to be overwritten. I have noticed this after replacing disks with larger ones, the deployment process started taking considerably longer and I observed that each sector is rewritten on the target device. Is that expected? Can I somehow avoid it? I am using whole-disk, qcow2 images that are much smaller than the disk size (even in raw form). I am running Ironic Wallaby. The deployment method is direct. Kind regards, -yoctozepto

2 4

[openstack-helm] No Meeting Tomorrow
by Gage Hugo 07 Feb '22

07 Feb '22

Hey team, Since there's nothing on the agenda for tomorrow's meeting, it has been cancelled. We will meet again next week.

1 0

[nova][ops] Problem with nova policies for resume operation
by Massimo Sgaravatto 07 Feb '22

07 Feb '22

Dear all I am running a Xena installation I have modified the nova policy fail so that certain operations can be done only by the user who created the instance, or by the administrator This [*] is my policy.yaml file. While the suspend operation works as intended (I can suspend only my instances and I am not allowed to suspend an instance created by another user) I am not able to resume an instance that I own and that I have previously suspended. I get this error: ERROR (Forbidden): Policy doesn't allow os_compute_api:os-suspend-server:suspend to be performed. (HTTP 403) (Request-ID: req-c57458bc-b1ea-4b40-a1d2-0f67608ef673) Only removing the line: "os_compute_api:os-suspend-server:suspend": "rule:admin_api or user_id:%(user_id)s" from the policy file, I am able to resume the instance. I am not able to understand what is wrong with that policy. Any hints ? Thanks, Massimo [*] # Pause a server # POST /servers/{server_id}/action (pause) # Intended scope(s): system, project "os_compute_api:os-pause-server:pause": "rule:admin_api or user_id:%(user_id)s" # Delete a server # DELETE /servers/{server_id} # Intended scope(s): system, project "os_compute_api:servers:delete": "rule:admin_api or user_id:%(user_id)s" # Resize a server # POST /servers/{server_id}/action (resize) # Intended scope(s): system, project "os_compute_api:servers:resize": "rule:admin_api or user_id:%(user_id)s" # Rebuild a server # POST /servers/{server_id}/action (rebuild) # Intended scope(s): system, project "os_compute_api:servers:rebuild": "rule:admin_api or user_id:%(user_id)s" # Stop a server # POST /servers/{server_id}/action (os-stop) # Intended scope(s): system, project "os_compute_api:servers:stop": "rule:admin_api or user_id:%(user_id)s" # Resume suspended server # POST /servers/{server_id}/action (resume) # Intended scope(s): system, project "os_compute_api:os-suspend-server:resume": "rule:admin_api or user_id:%(user_id)s" # Suspend server # POST /servers/{server_id}/action (suspend) # Intended scope(s): system, project "os_compute_api:os-suspend-server:suspend": "rule:admin_api or user_id:%(user_id)s"

4 8

[kolla-ansible][mariadb]error (galera cluster problem ?)
by Franck VEDEL 07 Feb '22

07 Feb '22

Hello, I am in an emergency situation, quite catastrophic situation because I do not know what to do. I have an Openstack cluster with 3 servers (serv1, serv2, serv3). He was doing so well… A network admin came to me and told me to change an MTU on the cards. I knew it shouldn't be done...I shouldn't have done it. I did it. Of course, it didn't work as expected. I went back to my starting configuration and there I have a big problem with mariadb which is set up on serv1 and serv2. Here are my errors: 2022-02-04 17:40:36 0 [ERROR] WSREP: failed to open gcomm backend connection: 110: failed to reach primary view: 110 (Connection timed out) at gcomm/src/pc.cpp:connect():160 2022-02-04 17:40:36 0 [ERROR] WSREP: gcs/src/gcs_core.cpp:gcs_core_open():209: Failed to open backend connection: -110 (Connection timed out) 2022-02-04 17:40:36 0 [ERROR] WSREP: gcs/src/gcs.cpp:gcs_open():1475: Failed to open channel 'openstack' at 'gcomm://10.0.5.109:4567,10.0.5.110:4567': -110 (Connection timed out) 2022-02-04 17:40:36 0 [ERROR] WSREP: gcs connect failed: Connection timed out 2022-02-04 17:40:36 0 [ERROR] WSREP: wsrep::connect(gcomm://10.0.5.109:4567,10.0.5.110:4567) failed: 7 2022-02-04 17:40:36 0 [ERROR] Aborting I do not know what to do. My installation is done with kolla-ansible, mariadb docker restarts every 30 seconds. Can the "kolla-ansible reconfigure mariadb" command be a solution? Could the command "kolla-ansible mariadb recovery" be a solution? Thanks in advance if you can help me. Franck

3 6

[ops][cinder] resource count survey
by Brian Rosmaita 07 Feb '22

07 Feb '22

Hello operators, The Cinder project is working on the cinder quotas system in an effort to improve its accuracy and remove the necessity for operators to go through and clean it up occasionally when it gets out of sync with reality. One way to do this is to use dynamic database counting (instead of storing the usage info in a table where it can become outdated). Whether this will be a good change depends on how many records the database has to process during a transaction, which in turn depends on how many Cinder resources a project has. So we need to get some information from you. Please take this brief survey: https://rosmaita.wufoo.com/forms/cinder-resource-count-survey/ The survey closes on Wednesday 30 March at 1200 UTC, so that we can have data to discuss during the "Z" PTG. But please don't procrastinate, it's only 6 questions and the answers are all positive integers. It shouldn't take long to fill out! Thanks! brian

1 0

Re: Recently Upgraded to XENA and getting this error
by Mohammed Naser 07 Feb '22

07 Feb '22

The fix hasn’t landed yet since then. On Fri, Feb 4, 2022 at 8:38 AM Adivya Singh <adivya1.singh(a)gmail.com> wrote: > hi Mohammed, > > This is for pike release, I am talking about Xena > > Regards > Adivya Singh > > On Thu, Feb 3, 2022 at 4:37 AM Mohammed Naser <mnaser(a)vexxhost.com> wrote: > >> I think you're running into this which has been broken for a hot minute: >> >> https://review.opendev.org/c/openstack/horizon/+/808102 >> >> that patch works for us locally. >> >> On Wed, Feb 2, 2022 at 10:37 AM Adivya Singh <adivya1.singh(a)gmail.com> >> wrote: >> > >> > Hello, >> > >> > We have recently upgraded to XENA release of Openstack, and getting >> this error while trying to Resize instance using GUI, it is telling "Danger >> , Please try Later" >> > Same is working properly from CLI without any issue >> > >> > Any thoughts on this >> > >> > Regards >> > Adivya Singh >> >> >> >> -- >> Mohammed Naser >> VEXXHOST, Inc. >> > -- Mohammed Naser VEXXHOST, Inc.

2 1

[baremetal-sig][ironic] Tue Feb 8, 2022, 2pm UTC: Scaling Ironic
by Arne Wiebalck 07 Feb '22

07 Feb '22

Dear all, The Bare Metal SIG will meet tomorrow Tue Feb 8, 2022, at 2pm UTC on zoom. The meeting will feature a "topic-of-the-day" presentation by Julia Kreger on "Scaling Ironic" providing details on the massive performance and scaling improvements Ironic has seen in the latest releases. Come along and bring your questions, everyone is welcome! As usual, all details on https://etherpad.opendev.org/p/bare-metal-sig Cheers, Arne

1 0

[all][elections][ptl][tc] Combined PTL/TC Election Feb-Mar 2022 Season
by Ghanshyam Mann 06 Feb '22

06 Feb '22

Hello Everyone! This is time for the Z development cycle Technical elections. Election details: https://governance.openstack.org/election/ The nomination period officially begins Feb 8, 2022 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 five (5) 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… [2] https://governance.openstack.org/tc/reference/charter.html#number-of-seats-… [3] https://governance.openstack.org/election/#election-officials -gmann & The OpenStack Technical Election Officials

1 0

[designate] Tentative PTG time slots for Designate
by Michael Johnson 04 Feb '22

04 Feb '22

Hello Designate community, I have tentatively put Designate down for two time slots for the PTG. Tuesday April 5th 15:00 - 17:00 UTC Wednesday April 6th 15:00-17:00 UTC Please let me know if those times do not work for you and you would like to attend. Michael

1 0

[release] Release countdown for week R-7, Feb 07-11
by Előd Illés 04 Feb '22

04 Feb '22

Development Focus ----------------- We are entering the last weeks of the Yogadevelopment 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. Please plan accordingly to avoid any last minute rushes to get key functionality in. General Information ------------------- Next week is the Extra-ATC freeze, in preparation for elections. All contributions to OpenStack are valuable, but some are not expressed as Gerrit code changes. Please list active contributors to your project team who do not have a code contribution this cycle, and therefore won't automatically be considered an Active Technical Contributor and allowed to vote. This is done by adding extra-atcs to https://opendev.org/openstack/governance/src/branch/master/reference/projec… before the Extra-ATC freeze on February 10th, 2022. 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 (February 17th, 2022). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (February 24th, 2022) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, February 24th, 2022. 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 (March 7th, 2022) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (March 24th, 2022) 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 (February 24th, 2022). Background on cycle-highlights: http://lists.openstack.org/pipermail/openstack-dev/2017-December/125613.html 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 -------------------------- Extra-ATC freeze: February 10th, 2022(R-7 week) Non-client library freeze: February 17th, 2022(R-6 week) Client library freeze: February 24th, 2022(R-5 week) Yoga-3 milestone: February 24th, 2022(R-5 week) Yoga final release: March 30th, 2022 Next PTG: April 4 - 8, 2022 (virtual) ElődIllés irc: elodilles

1 0

[oslo] feature freeze - Feb 07 - Feb 11 (R-7)
by Herve Beraud 04 Feb '22

04 Feb '22

Hello Osloers, Just a friendly reminder that oslo's feature freeze will happen next week (R-7 - Feb 07 - Feb 11). It's earlier than everyone else, and if you're wondering why, we have a policy[1] that discusses it. The main thing is that if you have features you want to get into Oslo libraries this cycle, please make sure they merge by Friday. After that we'll need to go through the FFE process and there's no guarantee we can land them. Feel free to ping us on IRC if you need reviews. Thanks for your attention. [1] http://specs.openstack.org/openstack/oslo-specs/specs/policy/feature- freeze.html -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

1 0

openstack swift and local path filename
by admin＠gibdev.ru 03 Feb '22

03 Feb '22

I have installed openstack swift 2.25.2 object-server writes and serves local files from disk It receives http requests from a proxy-server, for example: http get: /sdb4/525/AUTH_xxxxxxxxxxxxxxxxxxxxxxxx/panda/2c34a941f581d848e2799e7a0956ea14f3cb27b0e516aef99a438fdaebbd7592 reads a file from disk: /srv/node/sdb4/objects/525/346/835ee70dce07217d8e33147e0864f346/1643910916.71556.data how can I calculate the path by which the file will be read by object-server? thanks

2 1

[PTG] April 2022 Team Signup
by Kendall Nelson 03 Feb '22

03 Feb '22

Hello Everyone! Last week, we announced the next virtual PTG will be held virtually from Monday, April 4th to Friday, April 8th, 2022. We will have the same schedule set up available as last time with three windows of time spread across the day to cover all timezones with breaks in between. To signup your team, you must complete BOTH the survey[1] AND reserve time in the ethercalc[2] by end of day March 11th. We ask that the PTL/SIG Chair/Team lead sign up for time to have their discussions with 3 rules/guidelines: 1. Cross project discussions (like SIGs or support project teams) should be scheduled towards the start of the week so that any discussions that might shape those of other teams happen first. 2. No team should sign up for more than 4 hours per UTC day to help keep participants actively engaged. 3. No team should sign up for more than 16 hours across all time slots to avoid burning out our contributors and to enable participation in multiple teams discussions. Again, you need to fill out BOTH the ethercalc AND the survey to complete your team's sign up. If you have any issues with signing up your team, due to conflict or otherwise, please let me know! While we are trying to empower you to make your own decisions as to when you meet and for how long (after all, you know your needs and teams timezones better than we do), we are here to help! Once your team is signed up, please register[3]! And remind your team to register! Registration is free, but it's important that you sign up to let us know you'll be attending because that's how you'll receive event details, passwords, and other relevant information about the PTG. Continue to visit openinfra.dev/ptg for updates. -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/april2022_vptg_survey [2] Ethercalc Signup: https://ethercalc.openstack.org/7yxdas7suqnd [3] PTG Registration: https://openinfra-ptg.eventbrite.com/

1 0

[cinder][drivers] third-party CI compliance check
by Brian Rosmaita 03 Feb '22

03 Feb '22

Hello Argonauts, particularly vendor driver maintainers, This is a reminder that the third-party CI compliance check is imminent [0]. You can prevent any unpleasantness by checking now to verify that your CI is compliant. [0] https://releases.openstack.org/yoga/schedule.html#cinder-3rd-party-ci-compl… [1] https://docs.openstack.org/cinder/latest/drivers-all-about.html#driver-comp…

1 0

[cinder] new driver freeze & exceptions
by Brian Rosmaita 03 Feb '22

03 Feb '22

Hello Argonauts, The new driver merge deadline passed at 20:00 UTC today. I'm extending the new driver merge deadline to Friday 28 January at 20:00 UTC for two drivers: 1. Lightbits: It has both a cinder and os-brick patch, and I want the team to have more time to look at the os-brick patch. I think the driver patch is close to ready; the developers have been quick to respond to comments and make revisions. Also, the third-party CI is functioning and responding on patches. cinder: https://review.opendev.org/c/openstack/cinder/+/821602 os-brick: https://review.opendev.org/c/openstack/os-brick/+/821603 2. NEC Storage V Series: the driver patch has one +2 and the third party CI is functioning and responding on patches; I don't see any reason to make this one wait for the Z release. https://review.opendev.org/c/openstack/cinder/+/815614 Cinder core reviewers: please continue to review the above patches. With respect to the other proposed drivers: - Pure Storage NVMe-RoCE: vendor decided to hold it for Z - Dell EMC PowerStore NFS driver: vendor decided to hold it for Z - HPE XP Storage FC & iSCSI: the code is very straightforward, but the CI is not ready yet, so this will have to wait for Z - YADRO Tatlin.UNIFIED driver: initial patch arrived yesterday (and has a -1 from Zuul); the CI appears to be running, but the cinder team needs to move on to reviewing os-brick and Yoga feature patches, so this will have to wait for Z also cheers, brian

3 4

[neutron] Drivers meeting - Friday 4.2.2022 - cancelled
by Lajos Katona 03 Feb '22

03 Feb '22

Hi Neutron Drivers! Due to the lack of agenda, let's cancel tomorrow's drivers meeting. See You on the meeting next week. Lajos Katona (lajoskatona)

1 0

[nova][gate] test_tagged_attachment failing close to 100% in nova-next
by Artom Lifshitz 03 Feb '22

03 Feb '22

https://bugs.launchpad.net/nova/+bug/1959899 The test times out verifying the tags in the metadata API after attaching a NIC and volume. This is happening almost 100% of the time, but I've seen at least a couple of passing runs as well. We have yet to determine what the exact failure mode is - is the metadata API timing out (unlikely, since every other test passes)? Or are the expected tags just not present (more likely)? I'm trying to figure some things out at [1], but other than that this is very much under investigation with no root cause identified yet. [1] https://review.opendev.org/c/openstack/nova/+/827549

2 1

[nova][tempest] nova-next gate blocker
by Artom Lifshitz 03 Feb '22

03 Feb '22

nova-next (and possibly others) is broken because of https://bugs.launchpad.net/tempest/+bug/1959682 The fix is at https://review.opendev.org/c/openstack/tempest/+/827305, with a Nova DNM patch to exercise it at https://review.opendev.org/c/openstack/nova/+/827306 Please hold your rechecks until this is resolved. Cheers!

2 2