June 2023 - openstack-discuss - lists.openstack.org

[puppet] puppet module improvements
by Benedikt Trefzer 06 Jun '23

06 Jun '23

Hi all I use the openstack puppet modules to deploy openstack. I'd like to suggest some improvements to the modules and like to know what the community thinks about: 1.) use proper types for parameters Parameter validation is done with 'validate_legacy...' instead of defining the class/resource parameter with a proper type all over the code. I cannot imaging of any advantage not using proper type definitions. Instead using typed parameters would be more efficient an code readability would increase. 2.) params.pp This is the legacy way to define parameter defaults for different OS's. In the modern puppet world a module specific hiera structure is used, which eliminates the need of params.pp class (with inheritance and include). The usage of hiera improves readability and flexibility (every parameter can be overwritten on request, eg. change of packages names etc.) This also eliminate the restriction that the modules can only be used by certain OS'es (osfamily 'RedHat' or 'Debian'). 3.) Eliminate "if OS=='bla' {" statements in code These statements make the code very inflexible. It cannot be overruled if necessary (eg. if I use custom packages to install and do not need the code provided in the if statement). Instead a parameter should be used with a default provided in hiera. Since there is lot of code to change I do not expect this to be done in a single commit (per module) but in steps probably in more than one release cycle. But defining this as best practice for openstack puppet modules and start using above in new commits would bring the code forward. Finally: These are suggestions open for discussion. In no way I like to critic the current state of the puppet modules (which is quite good, but a bit legacy) or the people working on the modules. This is just a feedback/suggestion from an operator using the modules on a daily basis. Regards Benedikt Trefzer

4 4

[tc] Technical Committee next weekly meeting on June 6, 2023
by Nikolla, Kristi 06 Jun '23

06 Jun '23

Hi all, This is a reminder that the next weekly Technical Committee meeting is to be held on Tuesday, Jun 6, 2023 at 1800 UTC on Zoom. Meeting link and agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting Please find below the current agenda for the meeting. * Roll call * Follow up on past action items ** knikolla Book timeslots for PTG in Vancouver ** knikolla Prepare PTG agenda for Vancouver ** knikolla To fix link redirect to release from docs ** knikolla Finish TC Tracker 2023.2 * Open Infra Summit and PTG in Vancouver, next week * Gate health check * Broken docs due to inconsistent release naming * Open Discussion and Reviews ** https://review.opendev.org/q/projects:openstack/governance+is:open Thank you, Kristi Nikolla

1 0

[ceph-users] Quuncy release - radosGW integration with Keystone
by fsbiz＠yahoo.com 06 Jun '23

06 Jun '23

Hi folks, My ceph cluster with Quincy and Rocky9 is up and running.But I'm having issues with radosGW authenticating with keystone. Was wondering if I'm missed anything in the configuration. From the debug logs below, it appears that radosgw is still trying to authenticate withSwift instead of Keystone.Any pointers will be appreciated. thanks, Fred Here is my configuration. # ceph config dump | grep rgw client advanced debug_rgw 20/20 client advanced rgw_keystone_accepted_roles admin,user * client advanced rgw_keystone_admin_domain Default * client advanced rgw_keystone_admin_password <secret> * client advanced rgw_keystone_admin_project service * client advanced rgw_keystone_admin_user ceph-ks-svc * client advanced rgw_keystone_api_version 3 client advanced rgw_keystone_implicit_tenants false * client advanced rgw_keystone_token_cache_size 0 client basic rgw_keystone_url <Identity URL> * client advanced rgw_s3_auth_use_keystone true client advanced rgw_swift_account_in_url true client basic rgw_thread_pool_size 512 client.rgw.s_rgw.dev-ipp1-u1-control01.ojmddc basic rgw_frontends beast port=7480 * client.rgw.s_rgw.dev-ipp1-u1-control02.adnjrx basic rgw_frontends beast port=7480 Here's the debug log. If I interpret it correctly, it is trying to do a swift authentication and failing.Am I missing any configuration for Keystone based authentication ? Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: beast: 0x7fddeb8e7710:10.117.53.10 - - [03/Jun/2023:18:47:03.060 +0000] "GET/swift/v1/AUTH_c668ed224e434c88a9e0fce125056112?format=json HTTP/1.1" 401 119 -"openstacksdk/0.52.0 keystoneauth1/4.0.0 python-requests/2.22.0 CPython/3.8.10"- latency=0.000000000s Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: HTTP_ACCEPT=*/*Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: HTTP_ACCEPT_ENCODING=gzip,deflateJun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: HTTP_CONNECTION=closeJun 03 11:47:03 dev-ipp1-u1-control02.radosgw[2802861]:HTTP_HOST=dev-ipp1-u1-object-storeJun 03 11:47:03 dev-ipp1-u1-control02radosgw[2802861]: HTTP_USER_AGENT=openstacksdk/0.52.0keystoneauth1/4.0.0 python-requests/2.22.0 CPython/3.8.10Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: HTTP_VERSION=1.1 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]:HTTP_X_AUTH_TOKEN=gAAAAABke4qn779UQ_XMz0EDL3P3TgjBQsGG6p-MNhviJxLZTuMTnTDmpT5Yfi9UpgO_T3LOOsPjQAw6zoMUIaC22wPeryp5x-UumB3XwXOWp-qSXLbuN3b9oj_Qg5kCZWA0waWNRHzQ1mwtlEmmpTgvTXbU5V1ym6hEBOn6Q3RWhn34Hj3cF9oJun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: HTTP_X_FORWARDED_FOR=10.117.148.3Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: QUERY_STRING=format=jsonJun 03 11:47:03 dev-ipp1-u1-control02.radosgw[2802861]: REMOTE_ADDR=10.117.53.10 Jun 03 11:47:03 dev-ipp1-u1-control02.radosgw[2802861]: REQUEST_METHOD=GETJun 03 11:47:03 dev-ipp1-u1-control02.radosgw[2802861]:REQUEST_URI=/swift/v1/AUTH_c668ed224e434c88a9e0fce125056112?format=jsonJun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]:SCRIPT_URI=/swift/v1/AUTH_c668ed224e434c88a9e0fce125056112 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: SERVER_PORT=7480Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: ====== starting new requestreq=0x7fddeb8e7710 ===== Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s initializing for trans_id = tx000003991cfc5c1791f95-00647b8aa7-30c56-default Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s rgw api priority: s3=8 s3website=7Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s host=dev-ipp1-u1-object-store Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s subdomain= domain= in_hosted_domain=0 in_hosted_domain_s3website=0 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s final domain/bucket subdomain= domain= in_hosted_domain=0in_hosted_domain_s3website=0 s->info.domain=s->info.request_uri=/swift/v1/AUTH_c668ed224e434c88a9e0fce125056112 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s name: format val: jsonJun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s ver=v1 first= req= Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s handler=29RGWHandler_REST_Service_SWIFT Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s getting op 0 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s get_system_obj_state: rctx=0x7fddeb8e6790obj=default.rgw.log:script.prerequest. state=0x55f743b97720 s->prefetch_data=0 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s cache get: name=default.rgw.log++script.prerequest. : hit (negative entry) Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets scheduling with throttler client=3 cost=1Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets op=29RGWListBuckets_ObjStore_SWIFTJun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets verifying requester Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets rgw::auth::swift::DefaultStrategy: tryingrgw::auth::swift::TempURLEngine Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets rgw::auth::swift::TempURLEngine denied with reason=-13 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets rgw::auth::swift::DefaultStrategy: tryingrgw::auth::swift::SignedTokenEngine Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets rgw::auth::swift::SignedTokenEngine denied with reason=-1 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets rgw::auth::swift::DefaultStrategy: tryingrgw::auth::swift::SwiftAnonymousEngine Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets rgw::auth::swift::SwiftAnonymousEngine denied withreason=-1 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets Failed the auth strategy, reason=-1 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: failed to authorize requestJun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s op->ERRORHANDLER: err_no=-1 new_err_no=-1Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s get_system_obj_state: rctx=0x7fddeb8e6790obj=default.rgw.log:script.postrequest. state=0x55f743b97960 s->prefetch_data=0 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s cache get: name=default.rgw.log++script.postrequest. : hit (negative entry) Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets op status=0 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets http status=401

1 0

[publiccloud-sig] Reminder - next meeting June 7th - 0700 UTC
by Felix Kronlage-Dammers 06 Jun '23

06 Jun '23

Hi everyone, on Wednesday the next meeting of the public cloud sig is going to happen. We meet on IRC in #openstack-operators at 0700 UTC. A preliminary agenda can be found in the pad: https://etherpad.opendev.org/p/publiccloud-sig-meeting See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG read you on Wednesday! 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

swift container retention
by Geert Geurts 06 Jun '23

06 Jun '23

Hallo, I've gotten the assignment to implement a backup solution using openstack swift containers. What we want is that the files of customers are kept in the customers own container and for those files to retain their versions on updates of the file. So far so good, this is all possible, and extensively documented online. Now, the second part is more complicated it appears where I thougth this would be a quite common usage example of object storage. I cannot find how I can automagically delete versions of files that are older then X days. There is the X-delete-after header, but this header needs to be added for each transaction. What I want is for all objects in a container to get deleted after X days without having to add a header once the object is uploaded. Does anyone have suggestions on how I could implement this requirement? Please find below a grafical repesentation of what I want Versioning disabled Automated add headers delete-after Versioning enabled Usage on the account of LF Usage on the account of client │ │ │ │ │ │ ▼ ▼ ┌────────────────────────┐ ┌────────────────────────┐ │ │ │ │ │ Versions-container │ │ Current-container │ │ │ │ │ ├────────────────────────┤ ├────────────────────────┤ │ │ │ │ │File1 v123456 │ │ File1 │ │File1 v567899 │ │ File2 │ │ │ │ File3 │ │File3 v234567 │ │ ... │ │ │ │ FileN │ └────────────────────────┘ └─────────────┬──────────┘ ▲ │ │ │ └────────────────────────────────────────┘ Modifications cause current to be moved to Versioned-container Best regards, Geert

2 1

Kubernetes Conformance 1.24 + 1.25
by Kendall Nelson 06 Jun '23

06 Jun '23

Hello All! First of all, I want to say a huge thanks to Guilherme Steinmuller for all his help ensuring that OpenStack Magnum remains Kubernetes Certified [1]! We are certified for v1.24! However, in digging into the set of conformance tests this round, it appears that we will not be able to get 1.25 certified with the current Magnum. This means that in May when we have to re-cert (every 3 months they reach an EOL because that's k8s release cadence) we will not be able to maintain this which is the other part of why I wanted to write this email - to raise awareness and ask for help digging into what needs to happen to make sure we can retain this. Tangentially related, Guilherme has posted a patch with documentation for how to run the conformance tests for yourself and it could use some reviews [2]. And one last thing, I have begun conversation with the opendev folks about what it might take to setup jobs to run the conformance tests periodically so that we don't have to manually run them when it's time to recert. I am planning on submitting a forum topic for this for those interested :) Long live LOKI! - Kendall Nelson [1] https://github.com/cncf/k8s-conformance/pull/2446 [2] https://review.opendev.org/c/openstack/magnum/+/849156

5 10

[neutron] Bug Deputy May 29 - June 4
by Miro Tomaska 06 Jun '23

06 Jun '23

Hello All! Here is bug report from May 29nd to June 4th, Undecided bugs needs further triage: *Critical:-* *High:-* - https://bugs.launchpad.net/neutron/+bug/2021457 The firewall group without any port in active status Assigned to ZhouHeng - https://bugs.launchpad.net/neutron/+bug/2022059 Trunk can be deleted when the parent port is bound to a VM Assigned to Rodolfo Alonso *Medium:-* - https://bugs.launchpad.net/neutron/+bug/2021968 [OVN-BGP-AGENT] Expose subnet CIDR information on NB DB Assigned to Lucas Alvares Gomez - https://bugs.launchpad.net/neutron/+bug/2022070 "neutron-ovn-rally-task" timing out randomly Assigned to Rodolfo Alonso *Low:-* *- *https://bugs.launchpad.net/neutron/+bug/2022043 APIs for resources which don't have project_id still requires it in the API definition Assigned Slawek Kaplonski *Wishlist:-* *Undecided:-* https://bugs.launchpad.net/neutron/+bug/2022058 - l3ha and distributed router extra attributes do not reflect OVN state https://bugs.launchpad.net/neutron/+bug/2022360 - SecurityGroup deletion causes bulk_pull of SG rules by all the agents - requested more info Thank you Miro Tomaska

1 0

[ironic] No Meeting June 12th
by Jay Faulkner 06 Jun '23

06 Jun '23

Hi all, Due to proximity to OpenInfra Summit/Forum/PTG events, the Ironic meeting for June 12th will be cancelled. The next Ironic meeting will be Monday, June 19th. See many of you in Vancouver! Thanks, Jay Faulkner Ironic PTL

1 0

[forum] [k8s] Kubernetes on OpenStack
by Michał Dulko 05 Jun '23

05 Jun '23

Hi folks, With Matt we're holding a Forum session to discuss Kubernetes on OpenStack in Vancouver. We'd like the users, admins and developers of the projects to connect and talk about challenges, pain points and best practices. The agenda is being gathered in the etherpad [1], please do not hesitate to add any topics that you would like to discuss during the meeting. See you in Vancouver! Thanks, Michał [1] https://etherpad.opendev.org/p/openinfra-2023-kubernetes-on-openstack

1 0

Openstack Ansible
by Gk Gk 05 Jun '23

05 Jun '23

Hi All, We have an OSA setup. When I check the usage of filesystem of any container using "df" command, it shows the lvm partitions of the underlying host as well as shown below: -- Filesystem Size Used Avail Use% Mounted on /dev/mapper/lxc1-lv_root 86G 60G 22G 74% / none 492K 4.0K 488K 1% /dev /dev/mapper/lxc-openstack 493G 136G 334G 29% /var/log tmpfs 252G 0 252G 0% /dev/shm tmpfs 51G 88K 51G 1% /run tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 252G 0 252G 0% /sys/fs/cgroup example:gfs-repo 86G 67G 16G 82% /var/www/repo --- How to exclude the host partitions such that df only reports the container usage only ? Thanks Kumar

2 3

[heat] Plan for upcoming June 2023 PTG
by Takashi Kajinami 05 Jun '23

05 Jun '23

Hello, I'm attending the upcoming OpenInfra Summit @ Vancouver, so would like to moderate some Heat sessions in PTG. Unfortunately we have limited number of core reviewers attending this time. We discussed most of the important items during the previous vPTG. So I'm planning to have open discussion slots mainly to hear feedback from users/operators/etc. If you are interested, please add your name and topics to the etherpad . https://etherpad.opendev.org/p/vancouver-june2023-heat I've reserved slots from 11:00 to 12:50 on Wednesday, but we can be flexible. Please let me know if anyone is interested but that slot does not work. Thank you, Takashi Kajinami

1 0

[horizon] Cancelling next weekly meeting on 7th June
by vishal manchanda 05 Jun '23

05 Jun '23

Hello Team, As agreed, during the last weekly meeting, we are canceling our next weekly meeting on 7th June. I am on vacation for next complete week with limited or no access to internet. Please reach out to horizon core team if need any help. Thanks & regards, Vishal Manchanda

1 0

[charms] OpenStack Charms 2023.1 (Antelope) release is now available
by Peter Matulis 03 Jun '23

03 Jun '23

The 2023.1 (Antelope) release of the OpenStack Charms is now available. Please see the release notes for full details: https://docs.openstack.org/charm-guide/latest/release-notes/2023.1-antelope… == Highlights == * OpenStack Antelope OpenStack Antelope is now supported on Ubuntu 22.04 LTS (via UCA) and Ubuntu 23.04 natively. * New charm: ironic-dashboard This new charm integrates the Ironic Dashboard into the OpenStack Dashboard. * Service user password rotation The keystone, mysql-innodb-cluster, and rabbitmq-server charms have gained actions to assist with rotating the passwords of OpenStack service users. Two actions are provided for each of these charms (to list usernames and rotate their passwords). * New features for the ironic-conductor charm The ironic-conductor charm has acquired a few new abilities. It can now enable hardware specific options in the Ironic Conductor service. It also now supports custom timeouts for when requests are made to download install images. * Documentation updates Regular improvements and bug fixes. A new page on Network spaces was landed. == OpenStack Charms team == The OpenStack Charms team can be contacted via real time chat: https://chat.charmhub.io/charmhub/channels/openstack-charms The Juju user forum is also popular for diagnosing technical issues: https://discourse.charmhub.io/c/juju/ == Thank you == Lots of thanks to the 24 contributors below who squashed bugs, enabled new features, and improved the documentation! Alex Kavanagh Arif Ali Bas de Bruijne Billy Olsen Chris MacNaughton Corey Bryant Dmitrii Shcherbakov Edward Hope-Morley Felipe Reyes Frode Nordahl Gabriel Cocenza Guillaume Boutry Hemanth Nakkina James Page Jorge Merlino Liam Young Marcus Boden Martin Kalcok Neil Campbell Olivier Dufour-Cuvillier Peter Matulis Simon Dodsley Tiago Pasqualini Trent Lloyd -- OpenStack Charms Team

1 0

[nova] hw:numa_nodes question
by hai wu 03 Jun '23

03 Jun '23

Is there any concern to enable 'hw:numa_nodes=1' on all flavors, as long as that flavor can fit into one numa node?

4 18

RDO Ice Cream Social at OpenInfra Summit
by Amy Marrich 03 Jun '23

03 Jun '23

Join members of the community for ice cream after the Marketplace Mixer on Wednesday at Soft Peaks in Gastown! Soft Peaks is known for using organic milk and their unique topics! For those with dairy related dietary needs who register we will have an alternative for you so don't feel left out! https://eventyay.com/events/231a963f

1 1

[neutron] Neutron drivers meeting
by Rodolfo Alonso Hernandez 02 Jun '23

02 Jun '23

Hello Neutrinos: Please remember we have the Neutron drivers meeting today at 14:00 UTC. The agenda [1] has one topic: * https://bugs.launchpad.net/neutron/+bug/2020823: [RFE] Add flavor/service provider support to routers in the L3 OVN plugin See you later. [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

1 0

[Nova] How to (live-) migrate instances in a server-group with affinity to another host?
by Christian Rohmann 02 Jun '23

02 Jun '23

Hello OpenStack-Discuss, I was wondering how I as an admin can (live-)migrate instances for which the user applied a server-group with affinity. Looking at the API ([1]), there is no (obvious) way to migrate multiple instances or a server-group "en bloc". But migrating a single instance out of a group does result in: > [...] > 2023-06-01 12:20:00.489 6910 INFO nova.scheduler.host_manager > [req-01d9 83eb5 9c8353142098 - default default] Host filter ignoring > hosts: > 2023-06-01 12:20:00.490 6910 INFO nova.filters [req-01d9 83eb5 > 9c8353142098 - default default] Filter ServerGroupAffinityFilter > returned 0 hosts > 2023-06-01 12:20:00.491 6910 INFO nova.filters [req-01d9 83eb5 > 9c8353142098 - default default] Filtering removed all hosts for the > request with instance ID '2476cfdd-9315-4bff-ba3e-d3be5874593f'. > Filter results: ['AvailabilityZoneFilter: (start: 10, end: 10)', > 'ComputeFilter: (start: 10, end: 10)', 'ComputeCapabilitiesFilter: > (start: 10, end: 9)', 'ImagePropertiesFilter: (start: 9, end: 9)', > 'ServerGroupAntiAffinityFilter: (start: 9, end: 9)', > 'ServerGroupAffinityFilter: (start: 9, end: 0)'] > [...] Am I missing something here? Or am I just holding this wrong? Regards Christian [1] https://docs.openstack.org/api-ref/compute/?expanded=force-migration-comple…

4 4

openstack/devstack issue
by syed 02 Jun '23

02 Jun '23

Hi, I was building a system i.e. an orchestrator that includes resources like an ubuntu virtual machine, firecracker micro virtual machine, unikraft unikernel and a storage. It seems that openstack/devstack is capable of orchestration of such a heterogeneous system and could be customized according to the specific needs. I, however, am experiencing a lot of issues when including the resources e.g. when i try to create an ubuntu image and launch it, it results in errors that are quite complex to resolve and so i intend to reach out to the experts so as to resolve these issues at hand. Regards

2 1

[ironic][stable] Proposing EOL of ironic project branches older than Wallaby
by Jay Faulkner 02 Jun '23

02 Jun '23

Hi all, Ironic has a large amount of stable branches still in EM. We need to take action to ensure those branches are either retired or have CI repaired to the point of being usable. Specifically, I'm looking at these branches across all Ironic projects: - stable/queens - stable/rocky - stable/stein - stable/train - stable/ussuri - stable/victoria In lieu of any volunteers to maintain the CI, my recommendation for all the branches listed above is that they be marked EOL. If someone wants to volunteer to maintain CI for those branches, they can propose one of the below paths be taken instead: 1 - Someone volunteers to maintain these branches, and also report the status of CI of these older branches periodically on the Ironic whiteboard and in Ironic meetings. If you feel strongly that one of these branches needs to continue to be in service; volunteering in this way is how to save them. 2 - We seriously reduce CI. Basically removing all tempest tests to ensure that CI remains reliable and able to merge emergency or security fixes when needed. In some cases; this still requires CI fixes as some older inspector branches are failing *installing packages* in unit tests. I would still like, in this case, that someone volunteers to ensure the minimalist CI remains happy. My intention is to let this message serve as notice and a waiting period; and if I've not heard any response here or in Monday's Ironic meeting (in 6 days), I will begin taking action on retiring these branches. This is simply a start; other branches (including bugfix branches) are also in bad shape in CI, but getting these retired will significantly reduce the surface area of projects and branches to evaluate. I know it's painful to drop support for these branches; but we've provided good EM support for these branches for a long time and by pruning them away, we'll be able to save time to dedicate to other items. Thanks, Jay Faulkner

3 5

Add netapp storage in edge site | Wallaby | DCN
by Swogat Pradhan 02 Jun '23

02 Jun '23

Hi, I have a DCN setup and there is a requirement to use a netapp storage device in one of the edge sites. Can someone please confirm if it is possible? And if so then should i add the parameters in the edge deployment script or the central deployment script. Any suggestions? With regards, Swogat Pradhan

2 10

[blazar] Meeting cancelled today
by Pierre Riteau 01 Jun '23

01 Jun '23

Hello, I am unable to run the IRC meeting today, let's cancel. Best wishes, Pierre Riteau (priteau)

1 0

problem with zun not available console in horizon
by МАКАРОВ МАКС 01 Jun '23

01 Jun '23

1 0

CRITICAL! RabbitMQ PackageCloud repos will be not more available from today - affected Openstack-ansible
by Maroš Varchola 01 Jun '23

01 Jun '23

From today, the PackageCloud repos will be not more available from today. Official information: https://github.com/rabbitmq/rabbitmq-server/discussions/8386 BUG on launchpad: https://bugs.launchpad.net/openstack-ansible/+bug/2021410 -- S pozdravom/Yours Sincerely, Maroš Varchola +421 950 401 060 Astrová 6116/2, 071 01 Michalovce, Slovakia marosvarchola(a)sunray.sk ---- Táto správa bola digitálne podpísaná PGP certifikátom/ This message was digitally signed by PGP certificate

5 7

[neutron] New Yoga, Zed and 2023.1 releases
by Rodolfo Alonso Hernandez 01 Jun '23

01 Jun '23

Hello Neutrinos: Please check the new releases proposals for Yoga, Zed and 2023.1: * https://review.opendev.org/c/openstack/releases/+/885030 * https://review.opendev.org/c/openstack/releases/+/885031 * https://review.opendev.org/c/openstack/releases/+/885033 If you find something wrong please comment on the patch. Regards.

1 0

[horizon][stable] [release] Proposal to make stable/stein as EOL
by vishal manchanda 01 Jun '23

01 Jun '23

Hi all, As discussed in yesterday's Horizon weekly meeting[1] on 2023-05-31, I want to announce that the Horizon team decided to move the stable/stein branch as EOL. Consider this mail as an official announcement of that. The gate for horizon stable/stein is failing for the last few months [2]. I would like to know if anyone still wants to keep this branch to be open otherwise, I will propose an EOL patch for this branch. Thanks & Regards, Vishal Manchanda [1] https://meetings.opendev.org/irclogs/%23openstack-horizon/%23openstack-hori… [2] https://review.opendev.org/q/project:openstack%252Fhorizon+branch:stable%25…

1 0

Question About BGP Dynamic Routing, Floating IP, and SNAT
by Alex 01 Jun '23

01 Jun '23

Hi Everyone, Hope you are all doing well. I'm a beginner to Openstack and Neutron and now run into an issue about SNAT and shared floating IP. I've already deployed a neutron network which use BGP to announce floating IP to PE (Provider Edge router), and everything works as expected when I assigned the public floating IP (e.g., 123.0.0.10/24) to VMs. But when I tried to use floating IP port-forwarding function with floating IP 123.0.0.20/24 and rule (internal_ip 10.10.10.10, internal_port 5555, external_port 64000), and assign a private IP (10.10.10.10/24) to a VM. The floating IP 123.0.0.20 won't be advertised through BGP. May I have some suggestions about how could I get this fixed, or the neutron just won't work this way? FYI, 1. Per my understanding, the port_forwardings rule will make the port acts like a SNAT role and forward any packets that reached to it with destination 123.0.0.20:64000 to the private IP 10.10.10.10/24. 2. The IP address could be reached in the neutron network. 3. PE IP address, CE IP address, and floating IP gateway are using the same subnet A and subnet pool (192.168.123.0/24), while floating IP belongs to subnet B and subnet pool (123.0.0.0/24), both subnets belong to provider network. 4. Only floating IP that assigned to the specific VM will be advertised to PE through BGP 5. Floating IP that assigned to port of a router in the neutron network won't be advertised, even the IP is activated and is reachable internally. Sincerely, Alex

1 0