February 2022 - openstack-discuss

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 07 Feb '22

07 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 05 Feb '22

05 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