- openstack-discuss - lists.openstack.org

[manila] Cancelling Nov 23rd weekly meeting
by Carlos Silva 22 Nov '23

22 Nov '23

Hello Zorillas! As a lot of people from our regular audience have holidays during this week, we are cancelling the Nov 23rd Manila weekly meeting. In the Nov 30th meeting, we would like to use most of the time to review backports, so please join us to help getting some fixes landing in the stable branches. Thanks and regards, carloss

1 0

[publiccloud-sig] Summary meeting CW 47
by Felix Kronlage-Dammers 22 Nov '23

22 Nov '23

Hi, in today’s publiccloud-sig meeting we’ve continued the topic of “flavor discoverability”, a topic that has been part of our discussion for a while. Before I dive into that, a quick heads-up: So far we’ve been meeting in the odd weeks. We’ll be switching that to the even weeks. This means, we’ll be meeting again next week (Nov. 29th). For today’s meeting: The minutes for the meeting are here: https://etherpad.opendev.org/p/publiccloud-sig-meeting Since this was a videocall (and as such no meetingbot logs), here a quick summary (thanks @joek-office). ======= 0. Discussion on flavor/image/volume "search engine" aka flavor-discovery - (gtema) The most informations that can be interessting for clients to search resources are at the respective services (nova/glance/cinder) in place - nova has traits but this is not searchable (possible extension - nova mentioned this as a tricky development), especially for clients - the traits has the ability to give out internal informations about the infrastructure, so cloud provider's possibly not happy with this solution - (gtema) problems with finding the right flavor/image in a openstack cloud - The flavor definitions are more or less a range in that nova scheduler will do its best to meet the criteria, no guarantee to get what you want @gtema pls update/delete this - The architecture of the instance is more defined by the image than from the flavor - thats because in the image are the appropriate sources for a cpu architecture - at the moment two possible ideas idea 1: extend the services with the appropriate features to meet the requirements cons: - long development pros: - no moderation/weighting of results possible idea 2: build up a new service with required metadata based on the .wellknown concept supported by sdk right now (or discoverable via service catalogue - that's not in scope of the service catalog, but the new "discovery" service may be added into the catalog) cons: pros: - the service can moderate/weight results to meet criterias from cloud provider AND client side - available for older OpenStack versions ========= For people interested in this subject, we (at least gtema and me) are going to continue this discussion tomorrow at 1400 CET here: https://conf.scs.koeln:8443/OIF-public-cloud-sig felix -- Felix Kronlage-Dammers Product Owner IaaS & Operations Sovereign Cloud Stack Sovereign Cloud Stack — standardized, built and operated by many Ein Projekt der Open Source Business Alliance - Bundesverband für digitale Souveränität e.V. Tel.: +49-30-206539-205 | Matrix: @fkronlage:matrix.org | fkr(a)osb-alliance.com

1 0

[kolla] Weekly meeting cancelled today (22nd Nov 2023)
by Michał Nasiadka 22 Nov '23

22 Nov '23

Hello, Due to key participants absence - the weekly Kolla meeting is cancelled today. Let’s meet next week Thanks, Michal

1 0

[cinder][backup] backup_max_operations configuration is not working
by Pureewat Kaewpoi 22 Nov '23

22 Nov '23

Hi communities I have set cinder backup with these configurations backup_max_operations = 4 backup_workers = 4 When I create 20 backups simultaneously According to logs It still creating backups at the same time. 2023-11-07 06:17:42.029 555360 INFO cinder.backup.manager [] Create backup started, backup: <BACKUP-ID> volume: <VOLUME-ID> 2023-11-07 06:17:42.038 555360 INFO cinder.backup.manager [] Call Volume Manager to get_backup_device for Backup(*TRUNCRATED*) 2023-11-07 06:17:44.328 555360 INFO cinder.backup.manager [] Create backup started, backup: <BACKUP-ID> volume: <VOLUME-ID> 2023-11-07 06:17:44.334 555360 INFO cinder.backup.manager [] Call Volume Manager to get_backup_device for Backup(*TRUNCRATED*) 2023-11-07 06:17:46.665 555360 INFO cinder.backup.manager [] Create backup started, backup: <BACKUP-ID> volume: <VOLUME-ID> 2023-11-07 06:17:46.672 555360 INFO cinder.backup.manager [] Call Volume Manager to get_backup_device for Backup(*TRUNCRATED*) 2023-11-07 06:17:49.005 555360 INFO cinder.backup.manager [] Create backup started, backup: <BACKUP-ID> volume: <VOLUME-ID> 2023-11-07 06:17:49.018 555360 INFO cinder.backup.manager [] Call Volume Manager to get_backup_device for Backup(*TRUNCRATED*) 2023-11-07 06:17:51.378 555360 INFO cinder.backup.manager [] Create backup started, backup: <BACKUP-ID> volume: <VOLUME-ID> 2023-11-07 06:17:51.389 555360 INFO cinder.backup.manager [] Call Volume Manager to get_backup_device for Backup(*TRUNCRATED*) 2023-11-07 06:17:54.004 555360 INFO cinder.backup.manager [] Create backup started, backup: <BACKUP-ID> volume: <VOLUME-ID> 2023-11-07 06:17:54.017 555360 INFO cinder.backup.manager [] Call Volume Manager to get_backup_device for Backup(*TRUNCRATED*) 2023-11-07 06:17:56.094 555360 INFO cinder.backup.manager [] Create backup started, backup: <BACKUP-ID> volume: <VOLUME-ID> 2023-11-07 06:17:56.113 555360 INFO cinder.backup.manager [] Call Volume Manager to get_backup_device for Backup(*TRUNCRATED*) 2023-11-07 06:17:58.523 555360 INFO cinder.backup.manager [] Create backup started, backup: <BACKUP-ID> volume: <VOLUME-ID> 2023-11-07 06:17:58.536 555360 INFO cinder.backup.manager [] Call Volume Manager to get_backup_device for Backup(*TRUNCRATED*) 2023-11-07 06:18:01.017 555360 INFO cinder.backup.manager [] Create backup started, backup: <BACKUP-ID> volume: <VOLUME-ID> 2023-11-07 06:18:01.027 555360 INFO cinder.backup.manager [] Call Volume Manager to get_backup_device for Backup(*TRUNCRATED*) 2023-11-07 06:18:03.146 555360 INFO cinder.backup.manager [] Create backup started, backup: <BACKUP-ID> volume: <VOLUME-ID> 2023-11-07 06:18:03.162 555360 INFO cinder.backup.manager [] Call Volume Manager to get_backup_device for Backup(*TRUNCRATED*) 2023-11-07 06:18:05.622 555360 INFO cinder.backup.manager [] Create backup started, backup: <BACKUP-ID> volume: <VOLUME-ID> 2023-11-07 06:18:05.649 555360 INFO cinder.backup.manager [] Call Volume Manager to get_backup_device for Backup(*TRUNCRATED*) 2023-11-07 06:18:07.800 555360 INFO cinder.backup.manager [] Create backup started, backup: <BACKUP-ID> volume: <VOLUME-ID> 2023-11-07 06:18:07.818 555360 INFO cinder.backup.manager [] Call Volume Manager to get_backup_device for Backup(*TRUNCRATED*) 2023-11-07 06:18:10.129 555360 INFO cinder.backup.manager [] Create backup started, backup: <BACKUP-ID> volume: <VOLUME-ID> 2023-11-07 06:18:10.148 555360 INFO cinder.backup.manager [] Call Volume Manager to get_backup_device for Backup(*TRUNCRATED*) 2023-11-07 06:18:12.684 555360 INFO cinder.backup.manager [] Create backup started, backup: <BACKUP-ID> volume: <VOLUME-ID> 2023-11-07 06:18:12.775 555360 INFO cinder.backup.manager [] Call Volume Manager to get_backup_device for Backup(*TRUNCRATED*) 2023-11-07 06:18:16.356 555360 INFO cinder.backup.manager [] Create backup started, backup: <BACKUP-ID> volume: <VOLUME-ID> 2023-11-07 06:18:16.400 555360 INFO cinder.backup.manager [] Call Volume Manager to get_backup_device for Backup(*TRUNCRATED*) 2023-11-07 06:18:17.480 555360 INFO cinder.backup.manager [] Create backup started, backup: <BACKUP-ID> volume: <VOLUME-ID> 2023-11-07 06:18:17.575 555360 INFO cinder.backup.manager [] Call Volume Manager to get_backup_device for Backup(*TRUNCRATED*) 2023-11-07 06:18:20.227 555360 INFO cinder.backup.manager [] Create backup started, backup: <BACKUP-ID> volume: <VOLUME-ID> 2023-11-07 06:18:20.249 555360 INFO cinder.backup.manager [] Call Volume Manager to get_backup_device for Backup(*TRUNCRATED*) 2023-11-07 06:18:22.115 555360 INFO cinder.backup.manager [] Create backup started, backup: <BACKUP-ID> volume: <VOLUME-ID> 2023-11-07 06:18:22.165 555360 INFO cinder.backup.manager [] Call Volume Manager to get_backup_device for Backup(*TRUNCRATED*) 2023-11-07 06:18:24.379 555360 INFO cinder.backup.manager [] Create backup started, backup: <BACKUP-ID> volume: <VOLUME-ID> 2023-11-07 06:18:24.435 555360 INFO cinder.backup.manager [] Call Volume Manager to get_backup_device for Backup(*TRUNCRATED*) 2023-11-07 06:18:27.681 555360 INFO cinder.backup.manager [] Create backup started, backup: <BACKUP-ID> volume: <VOLUME-ID> 2023-11-07 06:18:28.074 555360 INFO cinder.backup.manager [] Call Volume Manager to get_backup_device for Backup(*TRUNCRATED*) 2023-11-07 06:18:29.440 555360 INFO cinder.backup.manager [] Create backup started, backup: <BACKUP-ID> volume: <VOLUME-ID> 2023-11-07 06:18:30.324 555360 INFO cinder.backup.manager [] Call Volume Manager to get_backup_device for Backup(*TRUNCRATED*) 2023-11-07 06:18:31.846 555360 INFO cinder.backup.manager [] Create backup started, backup: <BACKUP-ID> volume: <VOLUME-ID> 2023-11-07 06:18:31.874 555360 INFO cinder.backup.manager [] Call Volume Manager to get_backup_device for Backup(*TRUNCRATED*) The expected result is creating 4 backups simultaneously Have anyone face this issue ? or Do I config a wrong configuration ? Thanks Pureewat Kaewpoi

3 3

[openstack][octavia] octavia scale
by Nguyễn Hữu Khôi 22 Nov '23

22 Nov '23

Hello everyone, I would like to know how can we scale octavia. For example, if octavia is full ram or cpu, how we can resize them. I just google and I cannot see docs about it. Thank you.

2 4

[openstack][magnum] cinder AZ for magmum
by Nguyễn Hữu Khôi 22 Nov '23

22 Nov '23

Hello guys. When I create k8s cluster with magnum, I can choose AZ for nodes but if I want to put my cluster to a specified cinder AZ. How can we do it? Thank you. Nguyen Huu Khoi

2 2

Nominate Nicolas Bock for charms-stable-maint
by Corey Bryant 21 Nov '23

21 Nov '23

I would like to nominate Nicolas Bock for charms-stable-maint. Nicolas has a solid history of contributions and reviews for various OpenStack projects, he is a previous PTL for the Designate project, and over the past 3+ years, he has been contributing to charm reviews [1]. I trust that Nicolas will continue to provide value and quality reviews for the OpenStack charms project. [1] https://review.opendev.org/q/reviewer:nicolas.bock%2540canonical.com+projec… Corey

5 5

[charms] Nominate Brian Haley for charms-stable-maint
by Corey Bryant 21 Nov '23

21 Nov '23

I would like to nominate Brian Haley for charms-stable-maint. Brian has a long history of contributions to OpenStack, is the currentl PTL for the Neutron project, and over the past year, Brian has also been contributing to charm reviews [1]. I have no doubt that Brian will continue providing quality reviews to the OpenStack charms project and will be a great asset in helping the project move forward. [1] https://review.opendev.org/q/reviewer:haleyb.dev%2540gmail.com+project:%255… Thanks, Corey

4 4

Isolating OpenStack Project
by open infra 21 Nov '23

21 Nov '23

Hi, Sorry for cross posting. I need to create a new project and expect to isolate all VMs and underline resources from other projects. I have a default 'admin' project with 20+ workers with a bunch of VMs which are already occupied. Is there a guide for this? My intention is to create a new project and all VMs are only scheduled on reserved workers where no other project is able to schedule workloads on those machines. My Openstack deployment is on top of StarlingX 7.0 We say isolation of complete projects, is it possible to count storage (ceph) as well? Regards, Danishka

2 1

RE: openstack-discuss - Openstack Kolla-ansible Nova Compute - Error | Urgent
by Asma Naz Shariq 21 Nov '23

21 Nov '23

Hi Berndbausch, Thankyou for your reply. I tried to resolve the compute node host in /etc/hosts file through (ip : computenode-virtual-machine). I can check that logs have been changed for nova-compute log on compute node as attached. I am unable to find the solution. Can you check this for me and guide me how to resolve these issues. I would appreciate if you schedule a session for it. T -----Original Message----- From: berndbausch(a)gmail.com <berndbausch(a)gmail.com> Sent: Monday, November 20, 2023 2:24 PM To: 'Asma Naz Shariq' <asma.naz(a)techavenue.biz>; openstack-discuss(a)lists.openstack.org Subject: RE: openstack-discuss -Nova Compute - Error | Urgent The compute node tries to register with Nova on the controller but can't communicate with it. The problem appears to be at RabbitMQ, which says it can't reach the controller. First things you should check: Unsynchronized clocks and incorrect configuration of name resolution on the compute node. -----Original Message----- From: Asma Naz Shariq <asma.naz(a)techavenue.biz> Sent: Monday, November 20, 2023 3:50 PM To: openstack-discuss(a)lists.openstack.org Subject: RE: openstack-discuss -Nova Compute - Error | Urgent Hi Openstack Community, I am deploying Openstack zed release Multinode cluster with 1x Controller and 1x compute and 1x storage. At the time of deployment, I encountered a below error for failed to register the compute service: TASK [nova-cell: Fail if nova-compute service failed to register] *********************************** fatal: [X.X.X.X]: FAILED! => {"changed": false, "msg": "The Nova compute service failed to register itself on the following hosts: computenode-virtual-machine"} fatal: [X.X.X.X]: FAILED! => {"changed": false, "msg": "The Nova compute service failed to register itself on the following hosts: computenode-virtual-machine"} The logs in nova-compute.log at compute node state the ERROR: 2023-11-20 11:54:32.008 7 ERROR oslo. messaging._drivers.impl_rabbit [None req-f8176572-75bf-4c27-a9be-e096cb43e2e3 - - - - - -] Connection failed: [Errno 113] EHOSTUNREACH (retrying in 31.0 seconds): OSError: [Errno 113] EHOSTUNREACH. Can anyone guide me how to resolve this issue? Thanks -----Original Message----- From: openstack-discuss-request(a)lists.openstack.org <openstack-discuss-request(a)lists.openstack.org> Sent: Monday, November 20, 2023 10:16 AM To: openstack-discuss(a)lists.openstack.org Subject: openstack-discuss Digest, Vol 61, Issue 70 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: about magnum capi for production (Nguyễn Hữu Khôi) ---------------------------------------------------------------------- Message: 1 Date: Mon, 20 Nov 2023 12:16:11 +0700 From: Nguyễn Hữu Khôi <nguyenhuukhoinw(a)gmail.com> Subject: Re: about magnum capi for production To: Satish Patel <satish.txt(a)gmail.com> Cc: OpenStack Discuss <openstack-discuss(a)lists.openstack.org> Message-ID: <CABAODRfcEA38QRLCpr_DtC5Dbxmr2x=G9nD8hENptAdh0Z0QXg(a)mail.gmail.com> Content-Type: multipart/alternative; boundary="000000000000068859060a8e96ec" Hello guys. This is a doc which is about how to make Magnum CAPI to work with Openstack deployed by Kolla Ansible.. https://github.com/ngyenhuukhoi/openstack-note/blob/main/Magnum%20Cluster%2… Feel free to ask. If I can help, I will. Nguyen Huu Khoi On Mon, Nov 20, 2023 at 12:09 PM Nguyễn Hữu Khôi <nguyenhuukhoinw(a)gmail.com> wrote: > Hello. > It uses prebuild Ubuntu to provision k8s cluster, > > On Mon, Nov 20, 2023 at 11:47 AM Satish Patel <satish.txt(a)gmail.com> > wrote: > >> Hi Folks, >> >> Tell me if I am wrong. CAPI is just kubernetes images to build k8s >> clusters instead using coreOS and install a bunch of stuff via heat. >> In documentation all I can see are imported images. Reference doc: >> https://vexxhost.github.io/magnum-cluster-api/user/getting-started/ >> >> Do I need to install anything else to make it work? >> >> On Fri, Nov 17, 2023 at 11:30 AM Mohammed Naser <mnaser(a)vexxhost.com> >> wrote: >> >>> Thanks! Happy to see that it is working smoothly 😊 >>> >>> >>> >>> Appreciate any docs, comments or issues. >>> >>> >>> >>> *From: *Nguyễn Hữu Khôi <nguyenhuukhoinw(a)gmail.com> >>> *Date: *Friday, November 17, 2023 at 8:57 AM >>> *To: *Mohammed Naser <mnaser(a)vexxhost.com> >>> *Cc: *OpenStack Discuss <openstack-discuss(a)lists.openstack.org> >>> *Subject: *Re: about magnum capi for production >>> >>> Hello guys. >>> >>> >>> >>> I have successfully implemented Magnum CAPI on my openstack system. >>> My deployment tool for Openstack is Kolla-Ansible. It worked >>> greatly, I am testing with create, delete and resize k8s cluster. It >>> is smooth when compared with Heat Driver. I will make some docs for new users to use it. >>> >>> >>> >>> Thank you vexxhost.com and contributors for very nice production. >>> >>> >>> >>> I will keep testing and reporting to help it be much better in the >>> future. >>> >>> >>> Nguyen Huu Khoi >>> >>> >>> >>> >>> >>> On Tue, Nov 14, 2023 at 5:50 AM Nguyễn Hữu Khôi < >>> nguyenhuukhoinw(a)gmail.com> wrote: >>> >>> Hello. >>> >>> I get it now; >>> >>> Thank you very much. >>> >>> Nguyen Huu Khoi >>> >>> >>> >>> >>> >>> On Mon, Nov 13, 2023 at 11:20 PM Mohammed Naser >>> <mnaser(a)vexxhost.com> >>> wrote: >>> >>> Hi there, >>> >>> >>> Nope – it is simply a different driver, so if you try to create >>> Fedora CoreOS clusters – it’ll use the old heat driver. Otherwise, >>> it will use the Cluster API if the image is marked as Ubuntu >>> >>> >>> >>> Thanks! >>> >>> Mohammed >>> >>> >>> >>> *From: *Nguyễn Hữu Khôi <nguyenhuukhoinw(a)gmail.com> >>> *Date: *Monday, November 13, 2023 at 1:58 AM >>> *To: *Mohammed Naser <mnaser(a)vexxhost.com> >>> *Cc: *OpenStack Discuss <openstack-discuss(a)lists.openstack.org> >>> *Subject: *Re: about magnum capi for production >>> >>> Hello Mohammed, >>> >>> >>> >>> I found that >>> >>> >>> >>> >>> https://vexxhost.github.io/magnum-cluster-api/user/getting-started/# >>> creating >>> >>> >>> >>> I would like to know that if we use cluster api, does it overwrite >>> heat when deploying new k8s cluster from horizon? >>> >>> >>> Nguyen Huu Khoi >>> >>> >>> >>> >>> >>> On Mon, Oct 30, 2023 at 7:49 PM Nguyễn Hữu Khôi < >>> nguyenhuukhoinw(a)gmail.com> wrote: >>> >>> Awesome, thank you so much! >>> >>> Nguyen Huu Khoi >>> >>> >>> >>> >>> >>> On Mon, Oct 30, 2023 at 7:31 PM Mohammed Naser <mnaser(a)vexxhost.com> >>> wrote: >>> >>> Sounds good, thank you. >>> >>> >>> >>> We also have a channel on the Kubernetes Slack that is relatively >>> active if you need help — it’s in the README :) >>> >>> >>> >>> Thanks! >>> >>> Mohammed >>> >>> >>> >>> Get Outlook for iOS <https://aka.ms/o0ukef> >>> ------------------------------ >>> >>> *From:* Nguyễn Hữu Khôi <nguyenhuukhoinw(a)gmail.com> >>> *Sent:* Monday, October 30, 2023 8:23:07 AM >>> *To:* Mohammed Naser <mnaser(a)vexxhost.com> >>> *Cc:* OpenStack Discuss <openstack-discuss(a)lists.openstack.org> >>> *Subject:* Re: about magnum capi for production >>> >>> >>> >>> Hello. >>> >>> Thank you very much. I am planning to use Magnum CAPI for my system. >>> I will feedback later. >>> >>> Nguyen Huu Khoi >>> >>> >>> >>> >>> >>> On Mon, Oct 30, 2023 at 7:03 PM Mohammed Naser <mnaser(a)vexxhost.com> >>> wrote: >>> >>> Hi there! >>> >>> >>> >>> It works out of the box since the goal is to have an API that is >>> compatible so that all the ecosystem tools such as Terraform, >>> Ansible, CLI, Horizon all continue to work just fine! >>> >>> >>> >>> We’ve even made some quality of life improvements to the Magnum >>> plugin like letting you download KUBECONFIG from it. >>> >>> >>> >>> Thanks >>> >>> Mohammed >>> >>> >>> >>> Get Outlook for iOS <https://aka.ms/o0ukef> >>> ------------------------------ >>> >>> *From:* Nguyễn Hữu Khôi <nguyenhuukhoinw(a)gmail.com> >>> *Sent:* Monday, October 30, 2023 1:09:10 AM >>> *To:* Mohammed Naser <mnaser(a)vexxhost.com> >>> *Cc:* OpenStack Discuss <openstack-discuss(a)lists.openstack.org> >>> *Subject:* Re: about magnum capi for production >>> >>> >>> >>> Hello, >>> >>> >>> >>> Thank you for your sharing, Could you tell me how we use it with >>> Horizon or we need custom Horizon to use Magnum CAPI. >>> >>> >>> >>> Nguyen Huu Khoi >>> >>> >>> >>> >>> >>> On Mon, Oct 30, 2023 at 11:10 AM Mohammed Naser >>> <mnaser(a)vexxhost.com> >>> wrote: >>> >>> Hi there. >>> >>> >>> >>> We deploy this driver in production in our public cloud as well as >>> many private clouds and as part of Atmosphere and we’ve been fully >>> maintaining it on our side here. >>> >>> >>> >>> Let me know if you have any questions >>> >>> >>> >>> Thanks >>> >>> Mohammed >>> >>> >>> >>> Get Outlook for iOS <https://aka.ms/o0ukef> >>> ------------------------------ >>> >>> *From:* Nguyễn Hữu Khôi <nguyenhuukhoinw(a)gmail.com> >>> *Sent:* Sunday, October 29, 2023 10:22:22 PM >>> *To:* OpenStack Discuss <openstack-discuss(a)lists.openstack.org> >>> *Subject:* about magnum capi for production >>> >>> >>> >>> Hello guys. >>> >>> Could you share with me some experience about using Magnum CAPI in >>> production? >>> >>> >>> >>> https://github.com/vexxhost/magnum-cluster-api >>> >>> >>> >>> Thank you so much. >>> >>> >>> Nguyen Huu Khoi >>> >>>

2 2