December 2024 - openstack-discuss

Fwd: Regarding Trove-Openstack error
by skumari 13 Dec '24

13 Dec '24

---------- Original Message ---------- From: skumari <skumari(a)cdac.in> To: jimmy(a)openstack.org, communitymngr(a)openstack.org Date: December 9, 2024 at 10:03 AM Subject: Regarding Trove-Openstack error Hi Sir, In trove-openstack while iam trying to create a database instance iam getting this error: Polling request timed out. | | fault_date | 2024-12-06T10:45:59 | | fault_details | Traceback (most recent call last): | | | File "/var/lib/kolla/venv/lib/python3.11/site-packages/trove/common/utils.py", line 208, in wait_for_task | | | return polling_task.wait() | | | ^^^^^^^^^^^^^^^^^^^ | | | File "/var/lib/kolla/venv/lib/python3.11/site-packages/eventlet/event.py", line 124, in wait | | | result = hub.switch() | | | ^^^^^^^^^^^^ | | | File "/var/lib/kolla/venv/lib/python3.11/site-packages/eventlet/hubs/hub.py", line 310, in switch | | | return self.greenlet.switch() | | | ^^^^^^^^^^^^^^^^^^^^^^ | | | File "/var/lib/kolla/venv/lib/python3.11/site-packages/oslo_service/loopingcall.py", line 154, in _run_loop | | | idle = idle_for_func(result, self._elapsed(watch)) | | | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | | | File "/var/lib/kolla/venv/lib/python3.11/site-packages/oslo_service/loopingcall.py", line 349, in _idle_for | | | raise LoopingCallTimeOut( | | | oslo_service.loopingcall.LoopingCallTimeOut: | | | Looping call timed out after 1808.67 seconds | | | | | | During handling of the above exception, another exception occurred: | | | | | | Traceback (most recent call last): | | | File "/var/lib/kolla/venv/lib/python3.11/site-packages/trove/taskmanager/models.py", line 447, in wait_for_instance | | | utils.poll_until(self._service_is_active, | | | File "/var/lib/kolla/venv/lib/python3.11/site-packages/trove/common/utils.py", line 224, in poll_until | | | return wait_for_task(task) | | | ^^^^^^^^^^^^^^^^^^^ | | | File "/var/lib/kolla/venv/lib/python3.11/site-packages/trove/common/utils.py", line 210, in wait_for_task | | | raise exception.PollTimeOut | | | trove.common.exception.PollTimeOut: Polling request timed out. I even increased poll request timeout also . can you please help me to solve the error Thankyou Kumari. ------------------------------------------------------------------------------------------------------------ [ C-DAC is on Social-Media too. Kindly follow us at: Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ] This e-mail is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email is strictly prohibited and appropriate legal action will be taken. ------------------------------------------------------------------------------------------------------------

4 4

[nova][tc] Removing md5 in password injection
by Thomas Goirand 12 Dec '24

12 Dec '24

Hi, I didn't feel it would be controversial, though it seems removing md5 password injection is still up to debate: https://review.opendev.org/c/openstack/nova/+/935512 Of course, I'd like the TC to agree with me that injecting md5-hashed passwords is, in 2024, to be considered a security problem that should be fixed (and backported) ASAP. BTW, IMO this patch could be using the new feature from oslo_utils.secretutils that Takashi managed to get in: https://review.opendev.org/c/openstack/oslo.utils/+/931899 https://review.opendev.org/c/openstack/oslo.utils/+/935525 These, IMO, should also be backported to earlier oslo.utils releases, so we can fix earlier OpenStack releases in a nicer way. Cheers, Thomas Goirand (zigo)

6 14

[blazar] Next IRC meeting cancelled
by Pierre Riteau 12 Dec '24

12 Dec '24

Hello, Due to the holiday season, the next IRC meeting scheduled for December 26 is cancelled. We will meet again on January 9. I wish you all happy holidays. Cheers, Pierre Riteau (priteau)

1 0

[watcher] Canceling Dec 26th and Jan 2nd weekly meetings
by Douglas Viroel 12 Dec '24

12 Dec '24

Hi all o/ Since most of us will be out during the holidays, we agreed[1] on canceling watcher's weekly meetings[2] on Dec 26th and Jan 2nd. The last meeting of 2024 will be next week, on Dec 19th, and the first one of 2025 will be on Jan 9th. BR, [1] https://meetings.opendev.org/meetings/watcher/2024/watcher.2024-12-12-12.00… -- Douglas Viroel - dviroel

1 0

[cinder][ceph rbd] change volume type
by Tony Liu 12 Dec '24

12 Dec '24

Hi, With Antelope, old volume type is on replicated pool and new volume type is on EC pool. Change volume type doesn't work, volume type remains and no error returns. Is such change supported? I also tried change volume type from one replicated pool to another replicated pool. Doesn't work either. Am I missing anything? Thanks! Tony

2 1

[Openstack-ansible][Rabbitmq] Rabbitmq role is installing latest version of rabbitmq even after setting package version in variable file
by Danish Khan 12 Dec '24

12 Dec '24

Dear All, I have upgraded few of my openstack clusters from Ussuri to Wallaby successfully. But it seems rabbitmq repo is changed and now rabbitmq is getting its packages from: https://dl.cloudsmith.io/public/rabbitmq/rabbitmq-server/deb/ubuntu Everything was working fine until I face below issue while running rabbitmq playbook: TASK [rabbitmq_server : Apply rabbitmq policies] ******************************************************************************************************* failed: [rabbit_mq_container] (item={'name': 'HA', 'pattern': '^(?!(amq\\.)|(.*_fanout_)|(reply_)).*', 'priority': 0, 'tags': 'ha-mode=all'}) => {"ansible_loop_var": "item", "changed": false, "cmd": "/usr/sbin/rabbitmqctl -q -n '' set_policy -p / HA '^(?!(amq\\.)|(.*_fanout_)|(reply_)).*' '{\"ha-mode\": \"all\"}' --priority 0", "item": {"name": "HA", "pattern": "^(?!(amq\\.)|(.*_fanout_)|(reply_)).*", "priority": 0, "tags": "ha-mode=all"}, "msg": "Error:\nValidation failed\n\n[{<<\"ha-mode\">>,<<\"all\">>}] are not recognised policy settings", "rc": 69, "stderr": "Error:\nValidation failed\n\n[{<<\"ha-mode\">>,<<\"all\">>}] are not recognised policy settings\n\n", "stderr_lines": ["Error:", "Validation failed", "", "[{<<\"ha-mode\">>,<<\"all\">>}] are not recognised policy settings", ""], "stdout": "", "stdout_lines": []} It seems ha-mode=all is deprecated in latest version of Rabbitmq (4.0.4). I tried to install 3.8 or some other compatible version of rabbitmq but anyway the latest version of rabbitmq is getting installed. I have updated below entries of file /etc/ansible/roles/rabbitmq_server/vars/debian.yml : _rabbitmq_package_version: "3.8.14-1" and _rabbitmq_erlang_version_spec: "{{ (rabbitmq_install_method == 'external_repo') | ternary('1:23.3.4.15-1', '1:22.*') }}" Can someone please help me with this? I guess either I need to find a away to install specific version of rabbitmq to fox rabbitmq policy issue or I need to update parameters of command while applying policy. Regards, Danish Khan

2 2

[KOLLA-Ansible] default values for cpu_allocation_ratio
by Oliver Weinmann 12 Dec '24

12 Dec '24

Hi all, what are the default values for: cpu_allocation_ratio ram_allocation_ratio disk_allocation_ratio when using kolla-ansible? I can't seem to find any clear statement about it. Currently I assume they are 1.0 for each. Cheers, Oliver

2 2

[magnum] Cluster type (vm, ubuntu, kubernetes) not supported
by Satish Patel 11 Dec '24

11 Dec '24

Folks, I am trying to create a template for magnum but getting the following error. I am running the 2024.1 release. Anything changed or missing here? openstack image create ${IMAGE_NAME} --disk-format=qcow2 --container-format=bare --property os_distro=${OS_DISTRO} --file=${IMAGE_NAME}.qcow2; \ openstack coe cluster template create \ --image $(openstack image show ${IMAGE_NAME} -c id -f value) \ --external-network public \ --dns-nameserver 8.8.8.8 \ --master-lb-enabled \ --master-flavor gen.c4-m8-d30 \ --flavor gen.c4-m8-d30 \ --network-driver calico \ --docker-storage-driver overlay2 \ --coe kubernetes \ --label kube_tag=${version} \ k8s-${version}; Cluster type (vm, ubuntu, kubernetes) not supported (HTTP 400) (Request-ID: req-7c7f27b2-d67c-4f5b-aacf-01754b35bba8)

4 7

Re: [nova][security-sig] Communicating SSH host keys on
by Jeremy Stanley 11 Dec '24

11 Dec '24

first boot (was: Removing md5 in password injection) Reply-To: In-Reply-To: <8a163fa2-f071-4744-aae3-2182c048351c(a)redhat.com> On 2024-12-11 16:30:40 +0000 (+0000), Sean Mooney wrote: [...] > > Tangential, sorry, but could this sort of mechanism also be used to > > provide an out-of-band verification of SSH hostkeys generated on > > first boot for *nix type guests? We used to splat them to the > > primary terminal and then try to scrape them from the console log, > > but having a structured API response would be a lot cleaner (or did > > something similar already get added and I missed it?). [...] > i see the merrit in supprot some kind of reporting for limited > trusted boot type use cases such as providing the ssh host key > fingerprint so you can validate that the vm is the one you expect > it to be. > > im not sure how i would feel about allowing arbiarty metadata to > be store this way. > > is there something beyond the host key that would be useful for > you to record on boot? Nothing else comes to mind. Basically it's the desire to avoid ToFU style finger-crossing that the SSH host key you get on initially connecting to a newly booted server instance is really coming from that instance and not a MitM or honeypot. It's possible in most providers to create an authenticated backchannel by abusing the console log, as I described, but that has its own challenges. I suppose there might be alternative management protocols similar to SSH which rely on asymmetric key algorithms to authenticate hosts, but I'm not personally familiar with any (none with the near ubiquity of SSH at any rate). > perhaps we can try and capture this is a spec or separate thread > and work out what an mvp would look like. there would basically be > two part, one extednign the metadata api to support recording the > host key fingerprint somewhere, and then making that discoverable > via the main api perhaps in server show. That would make sense, and it would probably also be a good idea to try to involve e.g. a cloud-init maintainer in any such design discussion, as this would need client-side integration eventually anyway in whatever's going to communicate the key back to nova. > is we allowed read write access to all instance metadata we would > would not actually need to modify the main api as you can already > list metadata on an instance but im worried that could be abused > so i don't know if that is a good idea. Yes, that sounds like a security nightmare. > the nova metadata api is not intended a a high performance key > value store so i dont necessarily think it would be a good idea to > extned this to a generic crud api but we certainly could provide > limited support for targeted uscease liek the one you raise. Agreed, I suppose the field could be given a more generic name in case certain kinds of guests wanted to store functionally similar things in it, but as I said I don't know what else that would end up being anyway. -- Jeremy Stanley

1 1

Some questions about ironic
by Johnny Hao 11 Dec '24

11 Dec '24

Hi Buddies, I am new to ironic, after some study, I have several questions about it, could anyone help to answer? Thanks a lot. 1. According to the workflow chart below, what's the communication method between nova-compute and Ironic API? HTTP API call or RPC call through mq like rabbitmq? So are the communications between Ironic Conductor and other components of Neutron, Glance and Cinder/Swift etc? 2. Where do Ironic services run (Ironic API/Conductor/Drivers and DB)? In the controller node? Or a separate node is also supported? ** -- Best regards QingFeng Hao

2 1

[nova] riscv64 emulation support
by James Page 11 Dec '24

11 Dec '24

Hi Nova Team We've had some initial support for enabling RISCV64 support in Nova in a review for sometime which I refreshed this week: https://review.opendev.org/c/openstack/nova/+/889137 Sean suggested that this really needs a blueprint and discussion at the next Nova meeting (which I can't make) so proposing discussion via ML instead: https://blueprints.launchpad.net/nova/+spec/riscv64-emulation-support I'm also going to look at the nova-emulation job to see if that can be extended to cover RISCV64 as well - there are a few nuances with dependent packages (opensbi) in Ubuntu 24.04 but I think we can come up with something workable for testing. Review and comments are appreciated. Thanks James

2 1

OpenStack metrics and logs
by Timothé Bauge 11 Dec '24

11 Dec '24

Hello Stackers, I would like to know what are you all using to monitor and supervise your Openstack clusters ? We are in the process of setting up our own private cloud based on RedHat OpenStack Platform 17.1, we choose not to go with the RedHat Service Telemetry Platform, and were strongly advise against Ceilometer and aodh. At the moment, we built our own stack based on Prometheus (with the plenty of exporters) for the metrics, Graylog + OpenSearch for the logs, and Grafana for the visualisation. For now, we are only looking to retrieve basic information in order to know if a dysfunction occurs, but the end goal might be to go as far as to be able to count the cpu/mem/disk usage per hour per vm per project, etc. So, what are you all using and how did you implement it ? Best regards, [cid:659cb34d-63ad-4c5a-94e4-734ef252c20b] Timothé BAUGÉ timothe.bauge(a)covage.com<mailto:pr%C3%A9nom.nom@covage.com> COVAGE I Wholesale B2B du Groupe Altitude

3 3

Re: [openstack-helm] [Cinder] Cinder-Scheduler oslo_privsep.daemon.FailedToDropPrivileges: Privsep daemon failed to start
by daniel890723＠gmail.com 11 Dec '24

11 Dec '24

Hello Daniel here I have been test and trying to solve the oslo_privsep.daemon.FailedToDropPrivileges: Privsep daemon failed to start Error on openstack-helm deployed Cinder After the test with kolla-ansible i can confirm the problem is from kubernetes So i perform the test with all Cinder Service with Priviliged true setting in Value.yaml: pod: security_context: volume_usage_audit: pod: runAsUser: 42424 container: cinder_volume_usage_audit: readOnlyRootFilesystem: true privileged: true allowPrivilegeEscalation: true cinder_api: pod: runAsUser: 42424 container: ceph_coordination_volume_perms: runAsUser: 0 readOnlyRootFilesystem: true cinder_api: readOnlyRootFilesystem: true allowPrivilegeEscalation: true privileged: true cinder_scheduler: pod: runAsUser: 42424 container: ceph_coordination_volume_perms: runAsUser: 0 readOnlyRootFilesystem: true cinder_scheduler: capabilities: add: - SYS_ADMIN privileged: true readOnlyRootFilesystem: true allowPrivilegeEscalation: true Also Glance-api container too: pod: security_context: glance: pod: runAsUser: 42424 container: glance_perms: readOnlyRootFilesystem: true runAsUser: 0 ceph_keyring_placement: readOnlyRootFilesystem: true runAsUser: 0 glance_api: privileged: true readOnlyRootFilesystem: true allowPrivilegeEscalation: true nginx: readOnlyRootFilesystem: false runAsUser: 0 With Cinder and Glance container set as priviliged container the problem is gone and i can create volume with image normally So it is confirmed that the ERROR is because the pod permission Also my System Setup: | OS | Ubuntu:22.04 | | Kubernetes | 1.30.4 | | Openstack-helm | 2024.1 | P.S. i haven't test with a complete clean enviroment with only Ceph and Openstack component installed Daniel Lu

3 3

[nova] Specs review day is TODAY and Spec soft freeze is TOMORROW
by Sylvain Bauza 11 Dec '24

11 Dec '24

Hi folks, As we discussed on yesterday's nova meeting, today is our second specs review day and tomorrow (Dec 12th) will be the last day for providing a new spec to be reviewed. Please see our schedule here: https://releases.openstack.org/epoxy/schedule.html Thanks, -Sylvain

1 0

[tc][all][monasca ] Retiring the Monasca project
by Ghanshyam Mann 10 Dec '24

10 Dec '24

Hello everyone, As you might know, the Monasca project is not active and was marked 'inactive' since 2024.1 cycle[1]. In this cycle also, this project is leaderless[2] and no maintainer stepped up to maintain it. As discussed in the Leaderless project etherpad[2], the next step is to retire the project. I'm sending this email to propose the Monasca retirement and based on the response, I will proceed next. [1] https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [2] https://etherpad.opendev.org/p/2024.2-leaderless#L72 -gmann

6 15

Open Stack APIs
by foram.thakkar＠crestdata.ai 10 Dec '24

10 Dec '24

Hello, We want to fetch all the servers present in all the projects a user has access to. Currently we have to provide any one project name in the body of the authentication call. Is there a way we can fetch all the projects without providing any project name?

3 3

[all][tc][ptl][qa] Migrating upstream CI/CD jobs to Ubuntu Noble (24.04)
by Ghanshyam Mann 10 Dec '24

10 Dec '24

Hello Everyone, As per the 2025.2 cycle testing runtime, we need to run upstream CI/CD jobs on Ubuntu Noble (24.04) [1]. For better tracking and speeding up this work, it is the community-wide goal for this cycle[2]. This is the etherpad which has the migration plan and will be used for the tracking: - https://etherpad.opendev.org/p/migrate-to-noble I have prepared the change(WIP) for base jobs migration on Noble (openstack tox jobs, devstack, and tempest) which will migrate most of the projects jobs. Tempest change[3] include dependency on openstack tox, devstack base jobs changes so testing project gate using the the tempest change will test the complete set. Refer to the etherpad for the complete migration plan/steps. * Deadline: Nov 29th 2024 (R18) is the deadline to test/fix the projects jobs and to merge the base jobs running on Noble (openstck tox, devstack, and tempest). [1] https://governance.openstack.org/tc/reference/runtimes/2025.1.html [2] https://governance.openstack.org/tc/goals/selected/migrate-ci-jobs-to-ubunt… [3] https://review.opendev.org/c/openstack/tempest/+/932156 -gmann

2 8

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.1/R-16)
by Goutham Pacha Ravi 10 Dec '24

10 Dec '24

Hello Stackers, We're 16 weeks away from the 2025.1 ("Epoxy") release date (2024-04-02) [1]. OpenStack project teams are planning bug squashes and review jams in the next couple of weeks before contribution activity slows due to end-of-the-year holidays around the world. The OpenStack Technical Committee did not merge any new governance changes this week; however, a few proposals are iterating with community and TC review. === Weekly Meeting === The OpenStack Technical Committee held its monthly video conference last week, which was simultaneously recorded via text on IRC [2][3]. The discussion tracked several TC initiatives for this release cycle [4]. Most notably, the recent migration of base integration jobs to Ubuntu 24.04 LTS and Python 3.12 has caused CI jobs to break for several code repos [5]. I’d like to reiterate that project teams must resolve these issues or temporarily pin the nodeset of their test jobs to "ubuntu-jammy" to buy some time for fixes. We then checked on the status of "unmaintained" branches. The release team wanted the TC to solidify processes for two specific issues: nominating "unmaintained" liaisons and establishing guidelines for retiring these branches. The lack of such processes has resulted in the proliferation of "unmaintained" code branches across the community and failure to implement the TC resolution that created these branches [6]. The oldest unmaintained branch is "unmaintained/victoria", and it’s unclear if anyone benefits from keeping it around. Discussion on cleanup has been delayed due to uncertainty about what to do [7]. Meanwhile, branches like Yoga may still have high usage and active contributors, emphasizing the need for a clear process to decide their fate. The technical committee may consider advising the release team to eliminate branches with low usage, but this doesn’t solve the problem of finding volunteers to maintain high-usage branches. The idea is that projects can opt to maintain more branches if there is sufficient user interest and support, but there is currently no process for this, nor is it clear how to recruit volunteers. We agreed to continue this discussion at the next meeting. However, in the meantime, there were no objections to EOL-ing the Victoria, Wallaby, and Xena branches. Clark Boylan (clarkb) noted an issue with building CentOS Stream 10 images using Disk Image Builder, as they cannot boot on several clouds due to the x86_64 v3 CPU instruction set requirement. Only a few provider clouds, including OpenMetal and Rackspace Flex, meet the CPU requirements to boot CentOS 10. This limitation may affect options for regular test nodes, and project teams are advised to take notice. Until all Zuul/Nodepool cloud providers meet the CPU requirements, teams may need to adjust their testing strategies. Jeremy Stanley (fungi) reminded us that nominations for individual member representatives for the OpenInfra Foundation Board of Directors are still open [8]. Ten nominations from members are required to make it onto the ballot. The OpenStack TC's next weekly meeting is today, 2024-12-10. This will be an IRC meeting hosted on #openstack-tc at 1800 UTC. Please find the agenda on the meeting wiki [9]. I look forward to seeing you there. === Governance Proposals === ==== Open for Review ==== Add ansible-role-httpd repo to OSA-owned projects | https://review.opendev.org/c/openstack/governance/+/935694 Retire Murano/Senlin/Sahara OpenStack-Ansible roles | https://review.opendev.org/c/openstack/governance/+/935677 Rework the initial goal proposal as suggested by people | https://review.opendev.org/c/openstack/governance/+/931254 Resolve to adhere to non-biased language | https://review.opendev.org/c/openstack/governance/+/934907 Propose to select the eventlet-removal community goal | https://review.opendev.org/c/openstack/governance/+/934936 Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2025.1 "Epoxy" Release Schedule: https://releases.openstack.org/epoxy/schedule.html [2] TC Meeting Video Recording, 2024-12-03: https://youtu.be/KlYbFxjhACs [3] TC Meeting IRC Log 2024-12-03: https://meetings.opendev.org/meetings/tc/2024/tc.2024-12-03-18.00.log.html [4] TC Tracker for 2025.1: https://etherpad.opendev.org/p/tc-2025.1-tracker [5] Runtime update to Ubuntu 24.04/Python3.12: https://etherpad.opendev.org/p/migrate-to-noble [6] TC Resolution to create "unmaintained" code branches: https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branc… [7] Transition "victoria" code branch to EOL: https://review.opendev.org/c/openstack/releases/+/935373 [8] Nominations for OpenInfra Individual Board Member Elections: https://lists.openinfra.dev/archives/list/foundation@lists.openinfra.dev/th… [9] TC Meeting Agenda, 2024-12-10: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee

1 0

Kolla-Ansible: Why is handling kolla_*_fqdn in /etc/hosts out of scope?
by Matthias Tinnemeier 09 Dec '24

09 Dec '24

Dear Community, According to the documentation (https://docs.openstack.org/kolla-ansible/2024.2/admin/advanced-configuratio…) the provisioning of kolla_*_fqdn Name Resolution via /etc/hosts must be managed outside of the scope of Kolla. The question, therefore, is why :-) Given the existence of "customize_etc_hosts", there should be at least some logic to implement this behaviour in an automatic way. Is there a particular reason why this is not being implemented via Kolla? Alternatively, would it be worth proposing a patch for this? With kind regards Matthias

1 0

a suggestion: use LDAP to manage all openstack components configuration
by Shi Wei 09 Dec '24

09 Dec '24

Hi, everyone, I have a suggestion. we can use LDAP service to mange all openstak components and nodes(including physical nodes and vm nodes).  Because ldap is easy to read and ldap can support DNS and DHCP service. if a node get ip address by DHCP server with ldap. You and get the Mac address information from the LDAP server. and if all components are communicated by domain name. all records are on the LDAP server. if the one node will change IP address, you can just modify on the ldap server.  The ldap server can easy to backup and extend. use ldap command to export as a ldf file.   you can easy to backup before update configuration. if a new component will join, you can extend the schema by .sch file.  

2 1

[ops][largescale-sig] Join the Large Scale OpenStack virtual meetup with Rackspace !
by Thierry Carrez 09 Dec '24

09 Dec '24

Hi everyone, This cycle the Large Scale SIG is organizing virtual meetups, where operators of large-scale OpenStack deployments come to discuss their experiences, challenges and solutions with fellow operators. On Thursday, December 5, at 16 UTC (10am CT, 5pm Paris), we'll have our first one. The special guest for this meetup will be Kevin Carter, operator of the Rackspace Cloud. It will last one hour and will happen through a video meeting. To join us, please fill this form and we'll send you the link for the event the day before! https://forms.gle/92o1DTavHwivN8tn6 Hoping to see you there. -- Thierry Carrez (ttx)

4 6

OpenStack API Ports
by darsh.mehta＠crestdata.ai 09 Dec '24

09 Dec '24

I’m working with OpenStack APIs and noticed that the following endpoints use specific ports: Port 5000: - /auth/tokens?nocatalog - /auth/projects Port 8774: - /servers/detail - /flavors/detail - /images/detail - /os-hypervisors/detail I would like to know: Are these default port assignments (5000 for authentication and 8774 for compute services) configurable? Under what circumstances might these ports change? For example, would they differ in custom deployments or under certain OpenStack configurations?

3 2

[upgrades][openstack-ansible][upgrade from Wallaby to Antelope or Caracal]
by mmunther＠creativeadvtech.com 09 Dec '24

09 Dec '24

Hi Everyone, Kindly we would like to upgrade from Wallaby to something more recent such as Antelope or Caracal. We also have Ubuntu 20.04 and would like to upgrade the OS to Ubuntu 22.04. What would be the correct upgrade path for such a scenario using openstack ansible. Thanks Best Regards Monis

3 2

[neutron] Bug deputy report for week of December 2nd
by Miguel Lavalle 08 Dec '24

08 Dec '24

I was the Neutron bug deputy last week. Following is a brief summary of the reported bugs: Critical bugs ----------------- https://bugs.launchpad.net/neutron/+bug/2091021 Fullstack ha failover tests from neutron.tests.fullstack.test_l3_agent.TestHAL3Agent failing due to "destination ip 42.0.0.15 is replying to ping from namespace test-3dc5c664-ddba-4c2e-a9a9-48bbda478506, but it shouldn't". Assignee Slawek Kaplonski. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/937097 High bugs -------------- https://bugs.launchpad.net/neutron/+bug/2091071 ovn-agent: exception when deleing agent. Assignee Kien Nguyen. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/936988 Medium bugs ------------------ https://bugs.launchpad.net/neutron/+bug/2090825 AAP arp entry has incorrect mac address. Assignee Vasyl Saienko. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/936807 https://bugs.launchpad.net/neutron/+bug/2090913 [ovn]Allow multiple IPv6 ports on router from same network on ovn_l3. Assigned to Liu Xie. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/936931 Low bugs ------------- https://bugs.launchpad.net/neutron/+bug/2091106 OVN information in networking-ovn, Assignee: Brian Haley. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/937296 Under investigation -------------------------- https://bugs.launchpad.net/neutron/+bug/2090921 The OVN database is missing 6 ACL for security group default after each redeployment. Assignee Brian Haley https://bugs.launchpad.net/neutron/+bug/2091211 network leakage for flat network. Marked as incomplete for now pending more information from submitter

1 0

about accelerating database initialization
by Jiatong Shen 07 Dec '24

07 Dec '24

Hello all, I am trying to find out if there are ways to accelerate the database initialization process. We are using openstack-helm for deployment victoria OpenStack cluster and internally openstack-helm uses nova-manage db sync command to bootstrap the database. It works but a little bit slower than expected. Right now, I am measuring this bootstrap command could took around 2 minutes to complete. I'd like to get some advices on accelerating the process as well as what is the reasonable time to have. Thank you very much for your insights. -- Best Regards, Jiatong Shen

2 1