- openstack-discuss - lists.openstack.org

[release] Release countdown for week R-2, March 6-10
by Thierry Carrez 03 Mar '23

03 Mar '23

Development Focus ----------------- At this point we should have release candidates (RC1 or recent intermediary release) for almost all the deliverables. Teams should be working on any release-critical bugs that would require another RC or intermediary release before the final release. Actions ------- Early in the week, the release team will be proposing stable/2023.1 branch creation for all deliverables that have not branched yet, using the latest available 2023.1 Antelope release as the branch point. If your team is ready to go for creating that branch, please let us know by leaving a +1 on these patches. If you would like to wait for another release before branching, you can -1 the patch and update it later in the week with the new release you would like to use. By the end of the week the release team will merge those patches though, unless an exception is granted. Once stable/2023.1 branches are created, if a release-critical bug is detected, you will need to fix the issue in the master branch first, then backport the fix to the stable/2023.1 branch before releasing out of the stable/2023.1 branch. After all of the cycle-with-rc projects have branched we will branch devstack, grenade, and the requirements repos. This will effectively open them up for Bobcat development, though the focus should still be on finishing up Antelope until the final 2023.1 release. For projects with translations, watch for any translation patches coming through and merge them quickly. A new release should be produced so that translations are included in the final 2023.1 Antelope release. Finally, now is a good time to finalize release notes. In particular, consider adding any relevant "prelude" content. Release notes are targeted for the downstream consumers of your project, so it would be great to include any useful information for those that are going to pick up and use or deploy the 2023.1 Antelope version of your project. Upcoming Deadlines & Dates -------------------------- Final RC deadline: March 17 (end of R-1 week) Final 2023.1 Antelope release: March 22 Virtual PTG: March 27-31 -- Thierry Carrez (ttx)

1 0

[neutron] Drivers meeting cancelled
by Rodolfo Alonso Hernandez 03 Mar '23

03 Mar '23

Hello Neutrinos: Due to the lack of agenda [1], today's meeting is cancelled. Have a nice weekend. *PS: do not forget to add your topics to the PTG agenda [2]**. PTG is coming!* [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers [2]https://etherpad.opendev.org/p/neutron-bobcat-ptg

1 0

[kolla] [train] [cinder] Volume multiattach exposed to non-admin users via API
by Albert Braden 03 Mar '23

03 Mar '23

According to this document [1] multiattach volumes can only be setup if explicitly allowed by creating a “multiattach” volume type. “Starting from the Queens release the ability to attach a volume to multiple hosts/servers requires that the volume is of a special type that includes an extra-spec capability setting of multiattach=<is> True… Creating a new volume type is an admin-only operation by default. One of our customers appears to have used TerraForm to create a volume with the multiattach flag set and it worked, and that volume has multiple attachments. When I look here [2] it appears that the default is: #"volume:multiattach": "rule:xena_system_admin_or_project_member" So it looks like, by default, any project member can create a multiattach volume. What am I missing? [1]: https://docs.openstack.org/cinder/latest/admin/volume-multiattach.html [2]: https://docs.openstack.org/cinder/latest/configuration/block-storage/sample…

5 10

[governance][heat][tacker] Moving governance of tosca-parser(and heat-translator ?) to Tacker
by Takashi Kajinami 02 Mar '23

02 Mar '23

Hello, Currently tosca-parser is part of heat's governance, but the core reviewers of this repository does not contain any active heat cores while we see multiple Tacker cores in this group. Considering the fact the project is mainly maintained by Tacker cores, I'm wondering if we can migrate this repository to Tacker's governance. Most of the current heat cores are not quite familiar with the codes in this repository, and if Tacker team is not interested in maintaining this repository then I'd propose retiring this. Similarly, we have heat-translator project which has both heat cores and tacker cores as its core reviewers. IIUC this is tightly related to the work in tosca-parser, I'm wondering it makes more sense to move this project to Tacker, because the requirement is mostly made from Tacker side rather than Heat side. [1] https://review.opendev.org/admin/groups/1f7855baf3cf14fedf72e443eef18d844bc… [2] https://review.opendev.org/admin/groups/66028971dcbb58add6f0e7c17ac72643c48… Thank you, Takashi

3 8

[infra][ironic][tact-sig] Intent to grant control of x/virtualpdu to OpenStack community
by Jeremy Stanley 02 Mar '23

02 Mar '23

The OpenStack Ironic project relies on VirtualPDU, which is no longer actively developed. Ironic contributors reached out to the VirtualPDU maintainers with an offer to officially assume maintenance responsibilities in order to avoid forking it, and received a response from one (Mathieu Mitchell) who indicated support for that plan. Unfortunately, communication died off shortly thereafter, and the Ironic team has been unable to raise any of the current maintainers to actually add their access to the x/virtualpdu project in OpenDev's Gerrit. We don't have a documented process since this is the first time it's really come up, but I'm officially announcing that I intend to use my administrative permissions as an OpenDev sysadmin to add membership of an OpenStack Ironic team representative to the following Gerrit groups if no objections are raised before Wednesday, March 8: * virtualpdu-core * virtualpdu-release This will effectively grant full control of the x/virtualpdu repository to OpenStack Ironic contributors. Please follow up to the service-discuss(a)lists.opendev.org or openstack-discuss(a)lists.openstack.org mailing list with any concerns as soon as possible, or you can feel free to reach out to me directly by email or in IRC (fungi in the #opendev channel on the OFTC network). -- Jeremy Stanley

3 3

(OpenStack-Upgrade)
by Adivya Singh 02 Mar '23

02 Mar '23

Hi Team, I am planning to upgrade my Current Environment, The Upgrade procedure is available in OpenStack Site and Forums. But i am looking fwd to roll back Plan , Other then have a Local backup copy of galera Database Regards Adivya Singh

5 9

[OPENSTACKSDK] - Missing feature or bad reader?
by Gaël THEROND 02 Mar '23

02 Mar '23

> Hi everyone, > > I'm currently adding a new module on ansible-collections-openstack, > however, I'm having a hard time finding the appropriate function for my > module. > > Within ansible-collections-openstack, we have a compute_services_info > module that list services using the conn.compute.services() function that, > to my knowledge, come from the openstacksdk.compute.v2.service.py module. > > Our ansible module replicate what you get with: > openstack --os-cloud compute service list command. > or > openstack --os-cloud volume service list command. > (If I'm not wrong, it seems, openstack client is leveraging osc-lib for > that and not the SDK). > > My problem is, I want to add another similar module on our collection, > (volume_services_info) that would do the same but for volumes services: > > Unfortunately, either I'm not looking at the right place, or any volume > endpoint (v2/v3) within the openstack sdk is implementing the appropriate > service module. >From what I see block_storage in SDK is currently missing implementation for >service management (it is an admin-only and such APIs tend to be of lower prio >in SDK). >Artem All right, thanks a lot for the confirmation Artem, gonna see it we could add that pretty quickly on SDK as cinder already provide the appropriate /os-service API endpoint.

1 0

[OPENSTACKSDK] - Missing feature or bad reader?
by Gaël THEROND 02 Mar '23

02 Mar '23

Hi everyone, I'm currently adding a new module on ansible-collections-openstack, however, I'm having a hard time finding the appropriate function for my module. Within ansible-collections-openstack, we have a compute_services_info module that list services using the conn.compute.services() function that, to my knowledge, come from the openstacksdk.compute.v2.service.py module. Our ansible module replicate what you get with: openstack --os-cloud compute service list command. or openstack --os-cloud volume service list command. (If I'm not wrong, it seems, openstack client is leveraging osc-lib for that and not the SDK). My problem is, I want to add another similar module on our collection, (volume_services_info) that would do the same but for volumes services: Unfortunately, either I'm not looking at the right place, or any volume endpoint (v2/v3) within the openstack sdk is implementing the appropriate service module. Did I miss something or is that class simply missing? Thanks everyone!

2 1

[security-sig] Polls in preparation to revive our meetings
by Jeremy Stanley 01 Mar '23

01 Mar '23

As discussed at the last PTG, the present meeting time (15:00 UTC on the first Thursday of each month) is inconvenient for some attendees, and that combined with year-end holidays and general busy weeks recently have led to skipping them entirely. In order to start narrowing down the potential meeting schedule, I have two initial polls. The first is to determine what frequency we should meet. If you have an opinion on that, please fill out this poll before Thursday, February 9 (two weeks from today): https://framadate.org/wz7GioqmgyWeILkr The second poll is to hopefully determine what day of the week is optimal for potential attendees. If you have a preference for which day of the week to meet, please complete this one by the same date as the first: https://framadate.org/CyxKgZPT8PWxcCnJ Once I can analyze the results, I'll put together a more specific poll for choosing a time of day as well as possibly choosing which week(s) of the month (if we don't settle on weekly frequency). In the meantime, let's plan to hold February's meeting on Thursday the 2nd at 15:00-16:00 UTC as usual[*] for anyone who is able to attend, and I'll get an agenda together in preparation for that. [*] https://meetings.opendev.org/#OpenStack_Security_SIG_meeting -- Jeremy Stanley

1 1

June 2023 PTG Team Signup Kickoff
by Kendall Nelson 01 Mar '23

01 Mar '23

Hello Everyone, As you may have seen, we are hosting an abbreviated PTG in conjunction with the Vancouver OpenInfra Summit[0]! To sign your team up, you must complete the survey[1] by April 2nd at 7:00 UTC. We NEED accurate contact information for the moderator of your team’s sessions. This is because the survey information will be used to organize the schedule signups which will be done via the PTGBot. If you are not on IRC, please get setup[2] on the OFTC network and join #openinfra-events. You are also encouraged to familiarize yourself with the PTGBot documentation[3] as well. If you have any questions, please reach out! Information about signing up for timeslots will be sent to moderators shortly after the team signup deadline. Registration is open[4] and prices will increase May 5th! Continue to visit openinfra.dev/ptg for updates. -Kendall (diablo_rojo) [0] OpenInfra Summit Site: [1] Team Survey: https://openinfra.dev/summit/vancouver-2023 https://openinfrafoundation.formstack.com/forms/june2023_ptg_survey [2] Setup IRC: https://docs.openstack.org/contributors/common/irc.html [3] PTGBot README: https://opendev.org/openstack/ptgbot/src/branch/master/README.rst [4] OpenInfra Summit Registration: https://vancouver2023.openinfra.dev/

1 0