November 2023 - openstack-discuss

RE: openstack-discuss Digest, Vol 61, Issue 61- Nova- Compute Service Issue
by Asma Naz Shariq 16 Nov '23

16 Nov '23

Hello Openstack Team, I have deployed openstack zed release with multinode cluster through kolla-ansible controller with 1x storage, 1x compute node. The nova-compute service failed to register itself on the compute-host as attached; due to which there encounters an error of no availability zone for an instance to launch. Can any one guide me how to resolve this nova service issues. -----Original Message----- From: openstack-discuss-request(a)lists.openstack.org <openstack-discuss-request(a)lists.openstack.org> Sent: Thursday, November 16, 2023 2:15 AM To: openstack-discuss(a)lists.openstack.org Subject: openstack-discuss Digest, Vol 61, Issue 61 Send openstack-discuss mailing list submissions to openstack-discuss(a)lists.openstack.org To subscribe or unsubscribe 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: [kolla-ansible][cinder-schedule] Problem between Ceph and cinder-schedule (Franck VEDEL) 2. Re: Re: [keystone] temporary workaround for deprecated _member_ role? (Michael Knox) 3. openstack: aborted: Failed to allocate the network(s), not rescheduling.]. (kjme001(a)gmail.com) ---------------------------------------------------------------------- Message: 1 Date: Wed, 15 Nov 2023 21:33:15 +0100 From: Franck VEDEL <franck.vedel(a)univ-grenoble-alpes.fr> Subject: Re: [kolla-ansible][cinder-schedule] Problem between Ceph and cinder-schedule To: Alan Bishop <abishop(a)redhat.com> Cc: openstack-discuss(a)lists.openstack.org Message-ID: <63B87539-94A5-4CA5-A6CA-9CB67124EAEF(a)univ-grenoble-alpes.fr> Content-Type: multipart/alternative; boundary="Apple-Mail=_880E21AE-FC09-43C2-8C33-2E2670B2D035" Alan ! Thanks a lot…. I had doubts about the last config because I only wanted to use the Ceph cluster, but cinder-scheduler was looking for a backend which it could not find. But the cluster was functional so: kolla-ansible -i multinode stop …..destroy…. deploy…. post-deploy…. init-runonce…. Et VOILA. This reset all configurations, adds and rollbacks to 0. And it works ! Thanks!! Franck > Le 15 nov. 2023 à 15:43, Alan Bishop <abishop(a)redhat.com> a écrit : > > > > On Wed, Nov 15, 2023 at 6:32 AM Franck VEDEL <franck.vedel(a)univ-grenoble-alpes.fr <mailto:franck.vedel@univ-grenoble-alpes.fr>> wrote: >> Hi Pierre >> Maybe I found something: >> In the container « cinder_volume », there is a file >> /etc/ceph/ceph.conf But, no /etc/ceph/ceph.conf file in « cinder_scheduler » container. >> I think it’s my problem !! > > Sorry, but the scheduler does not require access to /etc/ceph files. I > think you need to review the scheduler logs to see why it concluded > there are no available c-vol backends. Since you are able to create a volume, I assume the ceph backend is "up," but it would also be good to verify it remains up, especially during the time when you're trying to create a volume from an image. > > Alan > >> but why ? >> What is the option in globals.yml ? >> Or maybe there is something to add in /etc/kolla/config/cinder/ >> >> I have this (the last try): >> >> >> enable_cinder: "yes" >> enable_cinder_backup: "no" >> enable_cinder_backend_lvm: "no" >> external_ceph_cephx_enabled: "yes" >> >> # Glance >> ceph_glance_keyring: "ceph.client.glance.keyring" >> ceph_glance_user: "glance" >> ceph_glance_pool_name: "images" >> # Cinder >> ceph_cinder_keyring: "ceph.client.cinder.keyring" >> ceph_cinder_user: "cinder" >> ceph_cinder_pool_name: "volumes" >> >> #ceph_cinder_backup_keyring: "ceph.client.cinder-backup.keyring" >> #ceph_cinder_backup_keyring: "ceph.client.cinder.keyring" >> #ceph_cinder_backup_user: "cinder" >> #ceph_cinder_backup_user: "cinder-backup" >> #ceph_cinder_backup_pool_name: "backups" >> # Nova >> #ceph_nova_keyring: "{{ ceph_cinder_keyring }}" >> ceph_nova_keyring: "ceph.client.nova.keyring" >> ceph_nova_user: "nova" >> ceph_nova_pool_name: "vms" >> >> # Configure image backend. >> glance_backend_ceph: "yes" >> >> # Enable / disable Cinder backends >> cinder_backend_ceph: "yes" >> >> # Nova - Compute Options >> ######################## >> nova_backend_ceph: "yes" >> >> >> Thanks a lot >> >> >> >> Franck >> >> >>> Le 15 nov. 2023 à 09:54, Pierre Riteau <pierre(a)stackhpc.com <mailto:pierre@stackhpc.com>> a écrit : >>> >>> Hi Franck, >>> >>> It would help if you could share more details about the error (check both cinder-scheduler and cinder-volume logs). >>> >>> Do you have capabilities to access the images pool (presumably what is used by Glance) on your client.cinder user? >>> >>> Best wishes, >>> Pierre Riteau (priteau) >>> >>> On Wed, 15 Nov 2023 at 09:50, Franck VEDEL <franck.vedel(a)univ-grenoble-alpes.fr <mailto:franck.vedel@univ-grenoble-alpes.fr>> wrote: >>>> Good morning, >>>> I'll come back for help, thanks in advance. >>>> I am testing an Openstack 2023.1/Ceph Pacific environment. >>>> The cluster works, and from Horizon for example, if I create a simple volume, it works normally, it is placed in the "volumes" pool in the Ceph cluster, exactly as expected. >>>> >>>> if I create a volume from an image, ERROR cinder-schedule. >>>> In the cinder_volume and cinder_scheduler containers, same settings in cinder.conf. >>>> >>>> Before continuing to find out what the error could be, could there be a problem between Antelope (2023.1) and Ceph Pacific? (I'm on Ubuntu 22.04). >>>> >>>> Franck >>>> >>>> >>>> >>

1 0

[kolla-ansible][cinder-schedule] Problem between Ceph and cinder-schedule
by Franck VEDEL 16 Nov '23

16 Nov '23

Good morning, I'll come back for help, thanks in advance. I am testing an Openstack 2023.1/Ceph Pacific environment. The cluster works, and from Horizon for example, if I create a simple volume, it works normally, it is placed in the "volumes" pool in the Ceph cluster, exactly as expected. if I create a volume from an image, ERROR cinder-schedule. In the cinder_volume and cinder_scheduler containers, same settings in cinder.conf. Before continuing to find out what the error could be, could there be a problem between Antelope (2023.1) and Ceph Pacific? (I'm on Ubuntu 22.04). Franck

4 8

[cinder][ops] Deprecating vmdk volume driver
by Takashi Kajinami 15 Nov '23

15 Nov '23

Hello, # This is similar to my previous email[1] but this one is for a different component. Cinder has provided the following two volume drivers to manage volumes in VMWare product. VMwareVcVmdkDriver for VMWare vCenter server VMwareVStorageObjectDriver for VMWare VStorageObject These drivers may be useful for OpenStack deployments using VMWare hypervisors. However the vmware api virt driver is being removed during this cycle, and this use case is no longer supported. I'm sending this email to hear if anyone is using these volume drivers WITHOUT the vmware api virt driver. If no, then I'll propose deprecating these drivers in 2024.1 release, and remove these in 2024.2. In case you have any concerns (or agree with the plan) then please reply to this thread (or to me directly if needed). Thank you, Takashi [1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack…

1 0

Cinder Bug Report 2023-11-15
by Jon Bernard 15 Nov '23

15 Nov '23

Hello Argonauts, Cinder Bug Meeting Etherpad <https://etherpad.opendev.org/p/cinder-bug-squad-meeting> There are exactly 0 new bugs this week, so no bug meeting today! Thanks, -- Jon

1 0

[largescale-sig] Next meeting: Nov 15, 8utc
by Thierry Carrez 15 Nov '23

15 Nov '23

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 8UTC, our EU+APAC-friendly time. Note that in some parts of the world, DST means that that meeting will be one hour earlier than usual. You can doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20231115T08 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Thanks, -- Thierry Carrez (ttx)

1 1

[tc][releases][ptl][all] 'Unmaintained' branch update
by Brian Rosmaita 15 Nov '23

15 Nov '23

Hello Stackers, I'm sure you saw Elod's email eariler this week [0] calling for final releases from stable/yoga in preparation for its transition to 'Unmaintained' status. In addition to stable/yoga, the TC resolution [1] specified that the three most recent Extended Maintenance branches would also transition to 'Unmaintained', and branches older than that can be deleted. The TC and the release team have had some discussions over the past two weeks [2,3,4,5], and we are closing in on a consensus on how the proposal described in the 2023-07024 resolution should work. This is how it's looking: (1) branches ineligible for Unmaintained status These are stable/ussuri and stable/train. The release team will use the current tooling to generate the patches proposing the ussuri-eol and train-eol tags; teams will have a grace period to get any final changes merged; after the -eol tags are made, the branches will be deleted. (2) transitioning a branch out of Maintained status This is stable/yoga. Elod has already sent the reminder email [0] for project teams to propose a release patch if there's a reason to do a final release. The release team is working on tooling that will mark the HEAD of stable/yoga with yoga-eom (for "end of maintenance"), delete the stable/yoga branch, and then cut the unmaintained/yoga branch based on the yoga-eom tag. There will be a grace period for the community to decide whether the branch should be kept in Unmaintained status or deleted, as described in [1]. Eventually (either when the grace period expires, or later, when there is no longer interest in keeping unmaintained/yoga around), the HEAD will be tagged yoga-eol and the branch deleted. (3) transitioning current eligible Extended Maintenance branches to Unmaintained status These are stable/xena, stable/wallaby, and stable/victoria. Ericsson has expressed interest in keeping victoria in Unmaintained status. Subject to the guidelines in [1], wallaby, xena, and yoga will therefore be kept in Unmaintained status as well. Eventually, consistent with [1], these branches will be tagged $series-eol and deleted. For more details about (1)-(3) above, see the discussion in [6]. The current patch to the Project Team Guide [7] will be updated shortly to reflect the discussion in [6]. (4) amendment to the Unmaintained branch resolution The original plan in [1] was for there to be a $project-unmaintained-core Gerrit group for each OpenStack project that would have +2/+W powers on the unmaintained/$series branches. This would entail changes in the Gerrit ACL config files for all projects plus populating all the Gerrit groups. I've put up an amendment [8] to the resolution that would instead establish a single openstack-unmaintained-core Gerrit group that would have +2/+W powers over all the unmaintained/* branches in the openstack namespace. Projects that would prefer to stick with the original proposal and have tighter control over their unmaintained/* branches can still do so; they'll have to patch the appropriate Gerrit ACL config file(s) for their project and populate the $project-unmaintained-core group. Note that except for the Amendment mentioned in (4), this email only provides details about how [1] is to be implemented; it does not change the nature of the Unmaintained branch proposal that was adopted by the TC back in July 2023. If you have questions or comments, please reply to the openstack-discuss mailing list, or leave comments on [7] and [8]. [0] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [1] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branc… [2] https://meetings.opendev.org/meetings/tc/2023/tc.2023-10-31-18.00.log.html#… [3] https://meetings.opendev.org/meetings/tc/2023/tc.2023-11-07-18.00.log.html#… video meeting recording: https://www.youtube.com/watch?v=qv6nSRhfV_M [4] https://meetings.opendev.org/meetings/releaseteam/2023/releaseteam.2023-11-… [5] https://meetings.opendev.org/meetings/tc/2023/tc.2023-11-14-18.00.log.html#… [6] https://etherpad.opendev.org/p/early-caracal-unmaintained-transition [7] https://review.opendev.org/c/openstack/project-team-guide/+/897505 [8] https://review.opendev.org/c/openstack/governance/+/900940

1 0

Discuss i18n IRC Meeting date
by Seongsoo Cho 15 Nov '23

15 Nov '23

Hi i18n Team. It's time to update our regular meeting date. This is the current meeting date in the doc, but actually, there are no meeting. [1] Every odd week: 16:00 UTC, Thursday Every even week: 07:00 UTC, Thursday So I want to set a new meeting date. For now, I'd like to have a monthly IRC meeting. Please let me know what days and times work best for you. Survey form: https://forms.gle/SZUFmwJS6QTs4akNA Best Regards Seongsoo [1] https://docs.openstack.org/i18n/latest/i18n_team_meeting.html -- Seongsoo Cho OpenStack Korea User Group / Community Leader IRC #seongsoocho

1 0

[ptls][PTG] OpenInfra Live: PTG Recap
by Kristin Barrientos 15 Nov '23

15 Nov '23

Hi Everyone, I wanted to reach out to see if any PTLs were interested in providing their highlights from last month’s PTG in an OpenInfra Live[1] episode on Thursday, December 7 at 1500 UTC. Ideally, we would like to have 4-6 projects represented (OpenStack, Kata, and/or StarlingX). A previous example of a PTG recap episode can be found here[2]. Please let me know if you’re interested and I can provide the next steps. If you would like to provide an update but that time doesn’t work for you, please share a recording with me and I can get it added. Thanks, Kristin Barrientos Marketing Coordinator OpenInfra Foundation [1] openinfra.dev/live [2] https://www.youtube.com/watch?v=yIt4dJvTQVg&t=231s

7 11

[swift]: Swiftstack Zone/DC decommission
by Muralikrishna Gutha 15 Nov '23

15 Nov '23

Hello Team, We currently utilize SwiftStack Object Storage to meet our object storage requirements, and our cluster has a Primary Zone/Secondary Zone topology. Recently, we attempted to remove/disable the Secondary Zone. However, upon doing so, we observed a concerning trend: the storage utilization in the Primary Zone rapidly increased, reaching approximately 90%. This surge was particularly notable due to the use of the 'tworeplicaperregion' policy. In an attempt to address this, we brought the Secondary Zone nodes back online, expecting Swift to redistribute the data back to these nodes and alleviate the storage strain on the Primary Zone. Despite reintegrating the Secondary Zone nodes into the cluster, we continue to witness a persistent rise in storage utilization within the Primary Zone. Interestingly, two out of the three nodes in the Primary Zone seem to bear the brunt of the data and tokens, while the third node is not receiving a proportional distribution of data. At this juncture, we are seeking guidance on potential configurations or adjustments, such as specific knobs, that could expedite the rebalance process. Our objective is to efficiently distribute the data across nodes, particularly in the Primary Zone, and optimize the overall storage utilization in our SwiftStack Object Storage cluster. Any insights or recommendations on tuning parameters for a swifter rebalance would be highly appreciated. Thanks, Murali -- This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this on behalf of the addressee you must not use, copy, disclose or take action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply email and delete this message. Thank you.

3 7

[tc] Next TC Meeting will be Nov 28 (2023-11-21 meeting cancelled)
by Jay Faulkner 14 Nov '23

14 Nov '23

Hi all, The Technical Committee will not be meeting next week. The meeting was cancelled due to American Thanksgiving. Our next meeting will be November 28, 2023. Thanks, Jay Faulkner OpenStack TC Chair

1 0