August 2023 - openstack-discuss - lists.openstack.org

[elections][venus] PTL Candidacy for 2024.1
by Eric Zhang (张连法)-浪潮信息 31 Aug '23

31 Aug '23

Hello everyone! I would like to announce my candidacy for the role of Venus PTL during the Caracal/2024.1 cycle. I have been in this role for the last 2 cycles and I would like to continue serving as PTL. In the upcoming cycle, I would like to focus on the following: * Continuous improvement in documents, unit tests, clients and dashboard. * Enhance log anomaly detection, such as more matching rules, improving performance. Thank you for your consideration! Lianfa Zhang

1 0

[all][elections][tc] TC Election Campaigning Kickoff
by Ian Y. Choi 31 Aug '23

31 Aug '23

Developers, The TC Election Campaigning Period has now started[1]. During the next couple days, you are all encouraged to ask the candidates questions about their platforms[2], opinions on OpenStack, community governance, and anything else that will help you to better determine how you will vote. This is the time to raise any issues you wish the future TC to consider, and to evaluate the opinions of the nominees prior to their election. Candidates, Each of you has posted a platform[2], and announced your nomination to the developers. From this point, you are encouraged to ask each other questions about the posted platforms, and begin discussion of any points that you feel are particularly important during the next cycle. While you are not yet TC members, your voices and opinions about the issues raised in your platforms and questions raised by the wider community will help ensure that the future TC has the widest possible input on the matters of community concern, and the electorate has the best information to determine the ideal TC composition to address these and other issues that may arise. [1] https://governance.openstack.org/election/ [2] https://opendev.org/openstack/election/src/branch/master/candidates/2024.1/…

1 0

[elections][cyborg] PTL Candidacy for 2024.1
by Alex Song (宋文平) 31 Aug '23

31 Aug '23

Hello everyone! I would like to announce my candidacy for the role of Cyborg PTL during the Caracal/2024.1 cycle. I have been in this role for the last 3 cycles and I would like to continue serving as PTL. During the past cycles, there was a lot of effort on promoting contributor collaboration through different activities and it helped us to make progress on closing gaps between the Cyborg APIs and other clients consuming them, as well as tackling tech debt and getting new features and drivers merged. I feel energized to continue pushing on these areas, but also put some focus on: * Complete the new features such as vgpu and mig management, disable and enable devices, update the device attribute and so on. * Working on the stability of our upstream CI first party jobs and also checking with third party CI maintainers to ensure their CI is healthy and reporting valid results. * Enhancing the review bandwidth and doing more actions to encourage more reviews from people submitting code to the Cyborg code base. * Work on documentation to help new contributors understand what are the requirements when proposing new features, and also continue the effort to cover the lack of documentation we have on third party CI setups for Cyborg, helping potential new vendors to quickly set up their CI systems. Thank you for your consideration! Wenping Song IRC: wenping1

1 0

[all][elections][ptl][tc] Combined PTL/TC 2024.1 cycle Election Nominations End
by Ian Y. Choi 31 Aug '23

31 Aug '23

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 12 projects without candidates, so according to this resolution[2], the TC will have to decide how the following projects will proceed: Cyborg, Ec2_Api, Mistral, Monasca, Openstack_Chef, Rally, Sahara, Senlin, Skyline, Sunbeam, Trove, Venus There are 1 projects that will have elections: OpenStack_Helm. The details for those will be posted around polling start date after we setup the CIVS system. -- TC Election Details -- Now begins the campaigning period where candidates and electorate may debate their statements. Polling will start Sep 06, 2023 23:45 UTC. Thank you, [0] https://governance.openstack.org/election/#ptl-candidates [1] https://governance.openstack.org/election/#tc-candidates [2] https://governance.openstack.org/resolutions/20141128-elections-process-for…

1 0

Cinder Bug Report 2023-08-30
by Jon Bernard 30 Aug '23

30 Aug '23

Hello Argonauts, Cinder Bug Meeting Etherpad <https://etherpad.opendev.org/p/cinder-bug-squad-meeting> Undecided - [StorPool Storage] Live VM Migration Fails <https://bugs.launchpad.net/cinder/+bug/2033292> - Status: In Progress - Dell PowerMax - Online migration can fail <https://bugs.launchpad.net/cinder/+bug/2033398> - Status: New - Hitachi: send unnecessary request to unlock storage resource group <https://bugs.launchpad.net/cinder/+bug/2033448> - Status: In Progress Thanks -- Jon

1 0

Re: openstack-discuss Digest, Vol 58, Issue 107
by Karera Tony 30 Aug '23

30 Aug '23

Hi Michael, I have realized that the docker version I have on the new compute nodes after running the bootstrap command is 24 while the previous compute and controller nodes have 20. Could that be a problem? Regards Regards Tony Karera On Wed, Aug 30, 2023 at 3:22 PM < openstack-discuss-request(a)lists.openstack.org> wrote: > Send openstack-discuss mailing list submissions to > openstack-discuss(a)lists.openstack.org > > To subscribe or unsubscribe via the World Wide Web, visit > > https://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss > > or, via email, send a message with subject or body 'help' to > openstack-discuss-request(a)lists.openstack.org > > You can reach the person managing the list at > openstack-discuss-owner(a)lists.openstack.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of openstack-discuss digest..." > > > Today's Topics: > > 1. Re: [elections][Cinder] PTL Candidacy for 2024.1 (Caracal) > (Brian Rosmaita) > 2. Re: [kolla] [train] [cinder] Cinder issues during controller > replacement (Danny Webb) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 30 Aug 2023 08:31:32 -0400 > From: Brian Rosmaita <rosmaita.fossdev(a)gmail.com> > To: openstack-discuss(a)lists.openstack.org > Subject: Re: [elections][Cinder] PTL Candidacy for 2024.1 (Caracal) > Message-ID: <fa39fe25-6651-688a-4bfa-39abbdbb7e04(a)gmail.com> > Content-Type: text/plain; charset=UTF-8; format=flowed > > On 8/29/23 10:17 AM, Rajat Dhasmana wrote: > > Hi All, > > > > I would like to nominate myself to be Cinder?PTL during the 2024.1 > (Caracal) > > cycle. > [snip] > > Here are some work items we are planning for the next cycle (2024.1): > > > > * We still lack review bandwidth since one of our active cores, Sofia, > > couldn't contribute to Cinder anymore > > hence we will be looking out for potential core reviewers. > > * Continue working on migrating from cinderclient to OSC (and SDK) > support. > > * Continue with the current cinder events like festival of XS reviews, > > midcycle, video meeting once a month etc > > that provides regular team interaction and helps tracking and discussion > > of ongoing work throughout the cycle. > > All this sounds great to me! Thanks for stepping up once again to take > on the task of herding the Argonauts and keeping the Cinder project on > track. > > > > > [1] https://review.opendev.org/q/topic:cinderclient-sdk-migration > > <https://review.opendev.org/q/topic:cinderclient-sdk-migration> > > [2] https://review.opendev.org/q/topic:cinder-sdk-gap > > <https://review.opendev.org/q/topic:cinder-sdk-gap> > > [3] > > > https://docs.google.com/spreadsheets/d/1yetPti2XImRnOXvvJH48yQogdKDzRWDl-NY… > < > https://docs.google.com/spreadsheets/d/1yetPti2XImRnOXvvJH48yQogdKDzRWDl-NY… > > > > [4] > > > https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branc… > < > https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branc… > > > > > > Thanks > > Rajat Dhasmana > > > > > ------------------------------ > > Message: 2 > Date: Wed, 30 Aug 2023 13:19:49 +0000 > From: Danny Webb <Danny.Webb(a)thehutgroup.com> > To: Eugen Block <eblock(a)nde.ag>, > "openstack-discuss(a)lists.openstack.org" > <openstack-discuss(a)lists.openstack.org> > Subject: Re: [kolla] [train] [cinder] Cinder issues during controller > replacement > Message-ID: > < > LO2P265MB5773FCAFE86B26D1E45E31459AE6A(a)LO2P265MB5773.GBRP265.PROD.OUTLOOK.COM > > > > Content-Type: text/plain; charset="windows-1252" > > Just to add to the cornucopia of configuration methods for cinder > backends. We use a variation of this for active/active controller setup > which seems to work (on pure, ceph rbd and nimble). We use both > backend_host and volume_backend_name so any of our controllers can action a > request for a given volume. We've not had any issues with this setup since > ussuri (we're on Zed / Yoga now). > > eg: > > [rbd] > backend_host = ceph-nvme > volume_backend_name = high-performance > ... > > [pure] > backend_host = pure > volume_backend_name = high-performance > ... > > which leaves us with a set of the following: > > $ openstack volume service list > > +------------------+-------------------------+----------+---------+-------+----------------------------+ > | Binary | Host | Zone | Status | State > | Updated At | > > +------------------+-------------------------+----------+---------+-------+----------------------------+ > | cinder-volume | nimble@nimble-az1 | gb-lon-1 | enabled | up > | 2023-08-30T12:34:18.000000 | > | cinder-volume | nimble@nimble-az2 | gb-lon-2 | enabled | up > | 2023-08-30T12:34:14.000000 | > | cinder-volume | nimble@nimble-az3 | gb-lon-3 | enabled | up > | 2023-08-30T12:34:17.000000 | > | cinder-volume | ceph-nvme@ceph-nvme-az3 | gb-lon-3 | enabled | up > | 2023-08-30T12:34:14.000000 | > | cinder-volume | pure@pure-az1 | gb-lon-1 | enabled | up > | 2023-08-30T12:34:11.000000 | > | cinder-volume | pure@pure-az2 | gb-lon-2 | enabled | up > | 2023-08-30T12:34:11.000000 | > > +------------------+-------------------------+----------+---------+-------+----------------------------+ > > > ________________________________ > From: Eugen Block <eblock(a)nde.ag> > Sent: 30 August 2023 11:36 > To: openstack-discuss(a)lists.openstack.org < > openstack-discuss(a)lists.openstack.org> > Subject: Re: [kolla] [train] [cinder] Cinder issues during controller > replacement > > CAUTION: This email originates from outside THG > > Just to share our config, we don't use "backend_host" but only "host" > on all control nodes. Its value is the hostname (shortname) pointing > to the virtual IP which migrates in case of a failure. We only use > Ceph as storage backend with different volume types. The volume > service list looks like this: > > controller02:~ # openstack volume service list > > +------------------+--------------------+------+---------+-------+----------------------------+ > | Binary | Host | Zone | Status | State | > Updated At | > > +------------------+--------------------+------+---------+-------+----------------------------+ > | cinder-scheduler | controller | nova | enabled | up | > 2023-08-30T10:32:36.000000 | > | cinder-backup | controller | nova | enabled | up | > 2023-08-30T10:32:34.000000 | > | cinder-volume | controller@rbd | nova | enabled | up | > 2023-08-30T10:32:28.000000 | > | cinder-volume | controller@rbd2 | nova | enabled | up | > 2023-08-30T10:32:36.000000 | > | cinder-volume | controller@ceph-ec | nova | enabled | up | > 2023-08-30T10:32:28.000000 | > > +------------------+--------------------+------+---------+-------+----------------------------+ > > We haven't seen any issue with this setup in years during failover. > > Zitat von Gorka Eguileor <geguileo(a)redhat.com>: > > > On 29/08, Albert Braden wrote: > >> What does backend_host look like? Should it match my internal API > >> URL, i.e. api-int.qde4.ourdomain.com? > >> On Tuesday, August 29, 2023 at 10:44:48 AM EDT, Gorka Eguileor > >> <geguileo(a)redhat.com> wrote: > >> > > > > Hi, > > > > If I remember correctly you can set it to anything you want, but for > > convenience I would recommend setting it to the hostname that currently > > has more volumes in your system. > > > > Let's say you have 3 hosts: > > qde4-ctrl1.cloud.ourdomain.com > > qde4-ctrl2.cloud.ourdomain.com > > qde4-ctrl3.cloud.ourdomain.com > > > > And you have 100 volumes on ctrl1, 20 on ctrl2, and 10 on ctrl3. > > > > Then it would be best to set it to ctrl1: > > [rbd-1] > > backend_host = qde4-ctrl1.cloud.ourdomain.com > > > > And then use the cinder-manage command to modify the other 2. > > > > For your information the value you see as "os-vol-host-attr:host" when > > seeing the detailed information of a volume is in the form of: > > <HostName>@<BackendName>#<PoolName> > > > > In your case: > > <HostName> = qde4-ctrl1.cloud.ourdomain.com > > <BackendName> = rbd-1 > > <PoolName> = rbd-1 > > > > In the RBD case the poolname will always be the same as the backendname. > > > > Cheers, > > Gorka. > > > >> On 29/08, Albert Braden wrote: > >> > We?re replacing controllers, and it takes a few hours to build > >> the new controller. We?re following this procedure to remove the > >> old controller: > >> > https://docs.openstack.org/kolla-ansible/train/user/adding-and-removing-hos… > < > https://docs.openstack.org/kolla-ansible/train/user/adding-and-removing-hos… > > > >> > > >> > After that the cluster seems to run fine on 2 controllers, but > >> approximately 1/3 of our volumes can?t be attached to a VM. When we > >> look at those volumes, we see this: > >> > > >> > | os-vol-host-attr:host | > >> qde4-ctrl1.cloud.ourdomain.com@rbd-1#rbd-1 > >> | > >> > > >> > Ctrl1 is the controller that is being replaced. Is it possible to > >> change the os-vol-host-attr on a volume? How can we work around > >> this issue while we are replacing controllers? Do we need to > >> disable the API for the duration of the replacement process, or is > >> there a better way? > >> > > >> > >> Hi, > >> > >> Assuming you are running cinder volume in Active-Passive mode (which I > >> believe was the only way back in Train) then you should be hardcoding > >> the host name in the cinder.conf file to avoid losing access to your > >> volumes when the volume service starts in another host. > >> > >> This is done with the "backend_host" configuration option within the > >> specific driver section in cinder.conf. > >> > >> As for how to change the value of all the volumes to the same host > >> value, you can use the "cinder-manage" command: > >> > >> cinder-manage volume update_host \ > >> --currenthost <current host> \ > >> --newhost <new host> > >> > >> Cheers, > >> Gorka. > >> > >> > >> > > > >

1 0

[keystone][election] Self-nomination for Keystone PTL for 2024.1 cycle
by Dave Wilde 30 Aug '23

30 Aug '23

Hey folks, It's Dave here, your current OpenStack Keystone PTL. I'd like to submit my candidacy to again act as the PTL for the 2024.1 cycle. We're making great progress with Keystone, and I would like to continue with that excellent work. As PTL in this cycle here are some of the things I'd like to focus on: - Finish the manager role and ensure that the SRBAC implied roles are correct for manager and member - Continue the OAuth 2.0 Implementation - Start a known issues section in the Keystone documentation - Start a documentation audit to ensure that our documentation is of the highest quality Of course we will continue the weekly meetings and the reviewathons. I think the reviewathons have been very successful and I'm keen on keeping them going. I'm looking forward to another successful cycle and working with everyone again! Thank you! /Dave

1 0

[elections][Cinder] PTL Candidacy for 2024.1 (Caracal)
by Rajat Dhasmana 30 Aug '23

30 Aug '23

Hi All, I would like to nominate myself to be Cinder PTL during the 2024.1 (Caracal) cycle. I have been the Cinder PTL for the last 3 cycles namely Zed, 2023.1 (Antelope) and 2023.2 (Bobcat). Few of the notable things we achieved in the past cycle are: ** OpenStack Client and SDK work: *We started two efforts in parallel: ** Migrate OSC commands to SDK[1] ** Add support of missing operations in SDK[2] We are making good progress in this area but looking at the work items[3], this effort will span across the next couple of cycles to be completed. ** Security Vulnerabilities:* We were able to address a major security vulnerability CVE-2023-2088 that prevents end users to delete volume attachments directly leaving left over devices on compute hosts resulting in data leaks. ** Transition from EM to Unmaintained: *We noticed the inactive contribution in extended maintenance branches and the need to fix gate issues from time to time. Also the project team is responsible to merge changes into these EM branches. After the recent CVE-2023-2088 wasn't proposed to EM branches, it was clear that the efforts were not worth the outcome so the Cinder team initiated a discussion regarding EOLing the current EM branches. There is a resolution from TC to migrate EM to unmaintained branches[4]. ** Outreachy Mentorship: *We had a successful quarter of outreachy internship from May-August 2023 with 2 interns, Desire and Toheeb. They were able to get a good amount of work done on the project "Automating generation of api-ref samples". ** Review bandwidth and quality:* We have been able to maintain good quantity and quality of reviews from contributors contributing from different organizations. Here are some work items we are planning for the next cycle (2024.1): * We still lack review bandwidth since one of our active cores, Sofia, couldn't contribute to Cinder anymore hence we will be looking out for potential core reviewers. * Continue working on migrating from cinderclient to OSC (and SDK) support. * Continue with the current cinder events like festival of XS reviews, midcycle, video meeting once a month etc that provides regular team interaction and helps tracking and discussion of ongoing work throughout the cycle. [1] https://review.opendev.org/q/topic:cinderclient-sdk-migration [2] https://review.opendev.org/q/topic:cinder-sdk-gap [3] https://docs.google.com/spreadsheets/d/1yetPti2XImRnOXvvJH48yQogdKDzRWDl-NY… [4] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branc… Thanks Rajat Dhasmana

2 1

Adding compute nodes to openstack cluster running wallaby
by Karera Tony 30 Aug '23

30 Aug '23

Hello Team, I am running openstack wallaby deployed using kolla-ansible and I am trying to add two compute node but I am getting this error. failed: [compute3] (item={'key': 'cron', 'value': {'container_name': 'cron', 'group': 'cron', 'enabled': True, 'image': 'kolla/ubuntu-source-cron:wallaby', 'environment': {'DUMMY_ENVIRONMENT': 'kolla_useless_env'}, 'volumes': ['/etc/kolla/cron/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}}}) => {"ansible_loop_var": "item", "changed": true, "item": {"key": "cron", "value": {"container_name": "cron", "dimensions": {}, "enabled": true, "environment": {"DUMMY_ENVIRONMENT": "kolla_useless_env"}, "group": "cron", "image": "kolla/ubuntu-source-cron:wallaby", "volumes": ["/etc/kolla/cron/:/var/lib/kolla/config_files/:ro", "/etc/localtime:/etc/localtime:ro", "/etc/timezone:/etc/timezone:ro", "kolla_logs:/var/log/kolla/"]}}, "msg": "'Traceback (most recent call last):\\n File \"/tmp/ansible_kolla_docker_payload_e49mzp45/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 1241, in main\\n File \"/tmp/ansible_kolla_docker_payload_e49mzp45/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 355, in compare_container\\n File \"/tmp/ansible_kolla_docker_payload_e49mzp45/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 376, in check_container_differs\\n File \"/tmp/ansible_kolla_docker_payload_e49mzp45/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 571, in compare_dimensions\\nKeyError: \\'KernelMemory\\'\\n'"} Please advise Tony Regards Tony Karera

2 1

[release][ironic][OpenStackSDK][swift] cycle-with-intermediary deliverables without any release
by Herve Beraud 30 Aug '23

30 Aug '23

Hi everyone, Quick reminder that we'll need a release very soon for a number of deliverables following a cycle-with-intermediary release model but which have not done *any* release yet in the 2023.2 Bobcat cycle: The following deliverables have done a bobcat release, but it was not refreshed in the last two months: [ironic] bifrost ironic-prometheus-exporter ironic-python-agent-builder ironic-ui networking-baremetal networking-generic-switch [OpenStackSDK] python-openstackclient [swift] swift Those should be released ASAP, and in all cases before September 15, so that we have a release to include in the final 2023.2 Bobcat release. Thanks in advance, -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

1 0