February 2022 - openstack-discuss

[all][elections][ptl][tc] Combined PTL/TC Zed cycle Election Nominations End
by Ghanshyam Mann 16 Feb '22

16 Feb '22

Hello Everyone, The PTL and TC Nomination period is now over. The official candidate lists for PTLs [0] and TC seats [1] are available on the election website. -- PTL Election Details -- There are 17 projects without candidates, so according to this resolution[2], the TC will have to decide how the following projects will proceed: Adjutant, Freezer, Heat, Magnum, Masakari, Monasca, Murano, OpenStack_Charms, Openstack_Chef, Senlin, Skyline, Solum, Trove, Venus, Watcher, Zaqar, Zun There are 0 projects that will have elections. -- TC Election Details -- The 5 seats were filled and no runoff is required. Now begins the campaigning period where candidates and electorate may debate their statements. Thank you, [0] https://governance.openstack.org/election/#z-ptl-candidates [1] https://governance.openstack.org/election/#z-tc-candidates [2] https://governance.openstack.org/resolutions/20141128-elections-process-for… -gmann & The OpenStack Technical Election Officials

1 0

Create Image in queue State in XENA Version
by Adivya Singh 16 Feb '22

16 Feb '22

Hi Team, We have lately upgraded to Xena , but when users trying to upload any image, it is always in queue state, i did not see any error regarding any issue with glance configuration file. Any thoughts on this Regards Adivya Singh

2 1

[tooz] [mistral] Tenacity >= 8.0.1 issues (in Debian)
by Thomas Goirand 16 Feb '22

16 Feb '22

Hi, It seems Tenacity has some incompatible changes leading to this: https://bugs.debian.org/1005636 (tooz) https://bugs.debian.org/1005467 (mistral) Note that both Manila and Heat were fixed already for this last version of Tenacity, so these would likely be the only remaining blockers to upgrade to 8.0.1. As Tenacity 8.0.1 is already in Debian Unstable, I'd prefer if we fixed these rather than pinning to a lower version. Can anyone help? Cheers, Thomas Goirand (zigo)

2 2

[cinder] final reviews needed for os-brick yoga release
by Brian Rosmaita 16 Feb '22

16 Feb '22

Hello Argonauts, We are now aiming to release on Tuesday 15 Feb at 20:00 UTC. The list of patches needing review and some comments on their status is here: https://etherpad.opendev.org/p/os-brick-yoga-release We're in mostly good shape, just need a final sprint to close this out. reviewers: please review! patch authors: please keep an eye on your patches and respond quickly and make sure your CI has responded with success thanks, brian

1 1

[election][Requirements] PTL candidacy for Zed
by Matthew Thode 15 Feb '22

15 Feb '22

I would like to announce my candidacy for PTL of the Requirements project for the Zed cycle. The following will be my goals for the cycle, in order of importance: 1. The primary goal is to keep a tight rein on global-requirements and upper-constraints updates. (Keep things working well) 2. Un-cap requirements where possible (stuff like prettytable). 3. Fix some automation of generate contstraints (pkg-resources being added and setuptools being dropped) 4. Audit global-requirements and upper-constraints for redundancies. One of the rules we have for new entrants to global-requirements and/or upper-constraints is that they be non-redundant. Keeping that rule in mind, audit the list of requirements for possible redundancies and if possible, reduce the number of requirements we manage. 5. introduce better python version range support into constraints. I look forward to continue working with you in this cycle, as your PTL or not. Thanks for your time, -- Matthew Thode

1 0

[election][swift] PTL candidacy for Zed
by Timothy Burke 15 Feb '22

15 Feb '22

I intend to continue serving as Swift PTL for the Zed cycle. We have seen Swift scale in spectacular ways. Hard drives have grown from 2-4 terabytes when Swift was started to 10-20T. The idea of a "large cluster" has gone from dozens of petabytes across hundreds of nodes to hundreds of petabytes across thousands of nodes. We will continue to see (and address) new challenges in scaling Swift. We anticipate hitting the bounds of our current ring format. We see operators struggle to balance the prioritization of cluster expansion and data durability. We see the need to improve sharding, so that clients are less impacted by what's going on in the backend. All of these have seen progress in the last cycle, and will continue to be advanced in the next. Just as important as scaling the core storage platform, however, is building up the ecosystem of ancillary services that users have come to expect out of their object storage. When a container grows to have billions of objects, it is impractical to perform thousands of listing requests to analyze its contents; instead, users expect a periodic inventory that's easy to pull into their existing data pipelines. Users should be able to examine their own access logs rather than needing to involve operators. Users want to manage their data movement and retention en masse rather than object-by-object. I look forward to seeing the balance we strike between enhancing the core storage platform and building out the data services surrounding it over the coming years. Tim Burke

1 0

[election][Release_Management] PTL candidacy for Z cycle
by Előd Illés 15 Feb '22

15 Feb '22

Hello OpenStack Community, I would like to announce my candidacy for the PTL role of the Release Management team for the Z cycle. I am core member in the Release Management team since Wallaby, but I followed the team's work even before that, and I also have been the PTL of the team for Yoga cycle for some months now. (Though, from release management perspective this is not a long period, since the most laborous part will only start in the coming weeks ;)) Furthermore, as in the past, beside release management duties, my focus is still on stable maintenance as well, since I am stable-maint-core member, too. The next cycle's challenges will be to prepare our tooling to alphabet roll-over after the Z cycle and to adjust to any other changes in our processes. And of course, parallel to this, to release OpenStack Z :) Thanks for your consideration, Előd Illés (elodilles)

1 0

[nova][placement] Implementation review day on Thursday Fev 17
by Sylvain Bauza 15 Feb '22

15 Feb '22

Hey folks, Last minute item, but we agreed during today's meeting to run a feature review day on Thursday February the 17th. If you're one of the owners of the blueprints that are marked in [1], you're eligible to ensure that this etherpad is up to date based on your last efforts and that you're somehow around either on IRC or asynchronously through Gerrit on that day to answer comments and questions about your patches. Cores, I'd appreciate if you can dedicate this Thursday to feature reviews as we still have a large set of blueprints that aren't merged yet. Thanks, -Sylvain [1] https://etherpad.opendev.org/p/nova-yoga-blueprint-status

1 0

[all][tc] OpenStack next release name is final- "OpenStack Zed"
by Ghanshyam Mann 15 Feb '22

15 Feb '22

Hello Everyone, We have the final name selected for the OpenStack next release name. Its "OpenStack Zed". As per the release name criteria[1], selection of release name has gone through three steps: Step1: Name nomination from community members[2]. Step2: TC voted on the nominated names[3]. Step3: Trademark checks by Foundation on winners from TC votes. In trademark check, “Zed” is finalized as the best bet for this release. Thanks community members for participating in name nomination, TC to vote and Foundation for performing the trademark checks. [1] https://governance.openstack.org/tc/reference/release-naming.html#release-n… [2] https://wiki.openstack.org/wiki/Release_Naming/Z_Proposals [3] https://civs1.civs.us/cgi-bin/results.pl?id=E_693bd8bbe63ca52f -gmann

4 6

[election][Kuryr] PTL candidacy for the Z cycle
by Maysa De Macedo Souza 15 Feb '22

15 Feb '22

Hello OpenStack community, I would like to announce my candidacy for the Z cycle. I have been serving as Kuryr PTL since the Wallaby and I would like to continue doing that. In the Yoga cycle we have achieved the following: * Extended features and improvements: addition of events to Kubernetes resources, reduction on the workload Kuryr puts on Neutron, limiting the number of Neutron Ports creation happening in parallel, continuation on the load-balancer resources reconciliation with k8s Services, and many more. * CI improvements: Made Devstack installations to use CRI-O and improved some tempest tests. For the next cycle, I propose the following goals to Kuryr: * Continue improvements for Kuryr scalability with Neutron, OpenStack resources reconciliation with Kubernetes and Kuryr controller health checks. Thanks for your consideration. Best regards, Maysa Macedo. IRC: maysams

1 0