- openstack-discuss - lists.openstack.org

[release] Release countdown for week R-19, Nov 20-24
by Herve Beraud 17 Nov '23

17 Nov '23

Development Focus ----------------- We are now past the Caracal-1 milestone. Teams should now be focused on feature development. General Information ------------------- Our next milestone in this development cycle will be Caracal-2, on January 11, 2024. This milestone is when we freeze the list of deliverables that will be included in the 2024.1 Caracal final release, so if you plan to introduce new deliverables in this release, please propose a change to add an empty deliverable file in the deliverables/caracal directory of the openstack/releases repository. Now is also generally a good time to look at bugfixes that were introduced in the master branch that might make sense to be backported and released in a stable release. If you have any question around the OpenStack release process, feel free to ask on this mailing-list or on the #openstack-release channel on IRC. Upcoming Deadlines & Dates -------------------------- Caracal-2 Milestone: January 11, 2024 -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

1 0

[kolla-ansible][cinder]Backend problems
by Franck VEDEL 17 Nov '23

17 Nov '23

Hi, I come back to a point that caused me a big problem, because I would like to understand something that I did not do correctly. I have a lab with an Openstack (2023.1, kolla-ansible, ubuntu 22-04, 2 nodes) and to show that it works, I start with an LVM backend. Everything is working. I'm adding a Ceph (Pacific) cluster and want to switch from LVM backend to CEPH. If we edit the globals.yml file and make the changes, then the "deploy" command, the LVM backend is still in the list of backends. If we restart the cinder containers, same thing. If we do "stop" then "deploy": same thing. I had to do "stop", "destroy", "deploy" to no longer have the LVM backend but only the CEPH backend. My question is therefore the following: what should we do in this situation? Is there a solution to easily no longer take into account a backend? Thansk for your help Franck

2 2

[kolla][masakari] Deprecating Masakari Support in Kolla-Ansible
by Michał Nasiadka 17 Nov '23

17 Nov '23

Hello, Since the Kolla-Ansible CI jobs for Masakari using 2023.2 have been failing [1] due to some time - we are deprecating Masakari support in Kolla/Kolla-Ansible. As I can see - even the OpenStack bot patches have not been merged in 2023.2 branch [2]. If there is anybody willing to go the extra mile of reviving Masakari stable/2023.2 branch - please reach out - ideally by commenting on the deprecation patch in Gerrit [3]. [1]: https://zuul.opendev.org/t/openstack/builds?job_name=kolla-ansible-ubuntu-m… [2]: https://review.opendev.org/q/project:openstack/masakari+is:open+branch:stab… [3]: https://review.opendev.org/c/openstack/kolla-ansible/+/901193

1 0

[neutron] Drivers meeting cancelled next two weeks
by Brian Haley 16 Nov '23

16 Nov '23

Hello Neutrinos: Due to the lack of agenda, Friday's drivers meeting is cancelled. Have a nice weekend! Also canceling next week's since with the US Thanksgiving holiday we will likely not have quorum. -Brian

1 0

openstack: how can you remove volumen from postgres database on openstack controller?
by kjme001＠gmail.com 16 Nov '23

16 Nov '23

Hello, I have a problem with the volume, I can't delete it, it's still in the deleting state how can you remove volumen from postgres database on openstack controller? Thank you for your help

1 0

[neutron] How to divide a provider network into address segments for different projects to use
by 韩光宇 16 Nov '23

16 Nov '23

Hi, I have a victoria cluster. And all node have two nic. Same to neutron doc[1], one nic is management interface, other is provider interface. Assuming provider network is same as the example in the Neutron deployment doc, which is the 203.0.113.0/24 with gateway 203.0.113.1. I hope use different address segment for different project. For example: project_A: 203.0.113.11,203.0.113.30 project_B: 203.0.113.31,203.0.113.60 project_C: 203.0.113.61,203.0.113.90 I am currently considering one method: Creating different VLAN networks for different projects, but it requires configuring the physical switch ports as trunks. Is there any other way to achieve this? I would prefer to use a flat network. I will appreciate for any help. Best regards, Han Guangyu [1]: https://docs.openstack.org/neutron/latest/install/environment-networking-ob…

1 0

[Glance] Cancelling Weekly Meeting - 16th Nov
by Mridula Joshi 16 Nov '23

16 Nov '23

Hello All, Cancelling today's weekly meeting as most of the team members are not around for the meeting. See you next week ! Thanks, Mridula Joshi

1 0

[cinder] Festival of XS reviews (17 Nov)
by Rajat Dhasmana 16 Nov '23

16 Nov '23

Hello Argonauts, We will be having our monthly festival of reviews tomorrow i.e. 17th November (Friday) from 1400-1600 UTC. Following are the details: Date: 17th November, 2023 Time: 1400-1600 UTC Meeting link: https://meet.google.com/jqg-eigw-rku etherpad: https://etherpad.opendev.org/p/cinder-festival-of-reviews Thanks Rajat Dhasmana

1 0

openstack: aborted: Failed to allocate the network(s), not rescheduling.].
by kjme001＠gmail.com 16 Nov '23

16 Nov '23

when creating a new instance I get an error: aborted: Failed to allocate the network(s), not rescheduling.]. Can anyone tell me where to look for the problem? Regards

3 2

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