February 2024 - openstack-discuss

[neutron] Drivers meeting cancelled tomorrow
by Brian Haley 08 Feb '24

08 Feb '24

Hello Neutrinos: Due to the lack of agenda, Friday's drivers meeting is cancelled. Have a nice weekend! -Brian

1 0

[kolla] [Ironic] Is ironic_cleaning_network is tenant network?
by Jayesh Chaudhari 08 Feb '24

08 Feb '24

Hi, I am trying to implement Ironic in my kolla-ansible yoga setup. I am following below document https://docs.openstack.org/kolla-ansible/yoga/reference/bare-metal/ironic-g… Here in ironic_cleaning_network and dnsmasq_dhcp_range is from tenant network?

2 1

[manila] share replication still experimental?
by garcetto 08 Feb '24

08 Feb '24

good evening, is still experimental even in zed or later? https://docs.openstack.org/manila/latest/admin/shared-file-systems-share-re… thank you.

2 1

[magnum] Is magnum support region_name in keystone auth config?
by Seongsoo Cho 08 Feb '24

08 Feb '24

Hi magnum team. It seems that a magnum does not support region_name which is in the keystone_auth and keystone_authtoken section in magnum conf. The internal keystone client of keystoneauth1 only uses the lowest UUID of endpoints for keystone url. [1] And also KeystoneClientV3 's get_auth[2] and get_legacy_auth[3] also don't support region_name as an argument. So, My question is how can I make magnum only use the keystone URL written in the config? Best regards Seongsoo Cho [1] https://github.com/openstack/keystoneauth/blob/master/keystoneauth1/access/… [2] https://github.com/openstack/magnum/blob/master/magnum/common/keystone.py#L… [3] https://github.com/openstack/magnum/blob/master/magnum/common/keystone.py#L… -- Seongsoo Cho OpenStack Korea User Group / Community Leader IRC #seongsoocho

2 2

about magnum capi for production
by Nguyễn Hữu Khôi 07 Feb '24

07 Feb '24

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

6 44

Cinder Bug Report 2024-02-07
by Jon Bernard 07 Feb '24

07 Feb '24

Hello Argonauts, Cinder Bug Meeting Etherpad <https://etherpad.opendev.org/p/cinder-bug-squad-meeting> Undecided - Service cinder-backup failed when Swift with TLS enabled <https://bugs.launchpad.net/cinder/+bug/2051985> - Status: In Progress - hpe xp: wrong copyrights in test scripts <https://bugs.launchpad.net/cinder/+bug/2052409> - Status: In Progress - GRUB menu format error <https://bugs.launchpad.net/cinder/+bug/2052414> - Status: New Thanks, -- Jon

1 0

[cinder][vendors] Third party CI compliance check
by Rajat Dhasmana 07 Feb '24

07 Feb '24

Hello Vendors, This is related to the original discussion on the ML thread[1]. We have noticed that a lot of the drivers don't have their CI reported on a patch in 2024. Based on the last CI report that I checked[2], the number comes out to be 32 though it's not an accurate measure of the inactivity in the project. The following cases are possible: 1. The driver that doesn't have active CI reporting is already marked unsupported 2. The driver is supported but CI is not actively maintained 3. The CI information is not accurate in the wiki page If it's case 2, vendors should look into their CI and fix it else the driver will be marked unsupported in the current or upcoming release. If it's case 3, make sure to have updated CI info in the wiki page. Let's take an example of the HPE driver. The last seen status is shown as: last seen: 2016-08-09 but the driver is actively reporting on patches. The issue here is either: 1. The CI name in the volume driver is not pointing to the correct wiki page[3] 2. The wiki page does not have correct information about CI[4] Vendors should look into updating their CI related information before the midcycle-2, which is going to be held on 14th Feb, 2024 from 1400-1600 UTC[5]. Since we only have the cireport[2] as the source of truth, we will be looking at the vendor drivers that don't have a recent last seen date and start marking them unsupported during the midcycle-2. Any query is welcome on this thread or during the midcycle-2 topic discussion. [1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [2] http://cinderstats.ivehearditbothways.com/cireport.txt [3] https://opendev.org/openstack/cinder/src/branch/master/cinder/volume/driver… [4] https://wiki.openstack.org/wiki/ThirdPartySystems/HPE_Storage_CI [5] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… Thanks Rajat Dhasmana

3 2

[all] SLURP support survey
by Mark Goddard 07 Feb '24

07 Feb '24

Hi, The Kolla project is planning to support SLURP upgrades [1] in the Caracal release cycle, allowing users to upgrade from Antelope to Caracal. There are two areas in which I'd like to request information from the various project teams. # 1. SLURP support We understand that for various reasons there can be a gap between TC resolutions and implementation across projects. Using some rudimentary grepping through various codebases I found that many projects have added the grenade-skip-level job (or a variation of it) to their CI pipelines, and a few mention SLURP in their release notes. There's little mention of it in documentation at this stage. AFAICT the following projects have SLURP upgrade jobs: Cinder, Glance, Ironic, Manila, Neutron, Nova, Octavia While I could not find a SLURP job in these: Barbican, Bifrost, Blazar, Cloudkitty, Designate, Heat, Horizon, Keystone, Magnum, Placement Question: Does your project explicitly support SLURP upgrades? Do you have or are you planning to add testing and documentation for SLURP upgrades? # 2. Rolling SLURP upgrades The TC resolution [1] states that rolling upgrades are optional for SLURP releases. This could affect the upgrade procedure required in Kolla Ansible. Nova mentions in its Antelope release notes that it supports rolling SLURP upgrades, but I could not find any information from other projects. It would be helpful if this was documented for each project. Question: Does your project support or plan to support rolling upgrades? If changes to the upgrade procedure for SLURP are required, are they documented? Thank you in advance for your responses. Apologies if I have missed any obvious source of information on this. Regards, Mark [1] https://governance.openstack.org/tc/resolutions/20220210-release-cadence-ad…

7 7

[largescale-sig] Next meeting: February 7, 9utc
by Thierry Carrez 07 Feb '24

07 Feb '24

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 9UTC, our EU+Asia time. You can doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240207T09 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

2 2

[Kolla][Octavia] worker unable to connect amphora instance
by Jayesh Chaudhari 06 Feb '24

06 Feb '24

Folks, I have set up kolla-ansible yoga openstack and configured Octavia using VLAN. But when I am trying to create a LB, it is stuck in pending create then eventually failed. And in logs I can see octavia-worker unable to connect to amphora instance. Is there any sanity which I can do to check if my implementation is correct ? Or am I missing something? Please advise. My configuration in global.yml enable_octavia: yes octavia_network_interface: "vlan.2140" octavia_auto_configure: yes octavia_amp_flavor: name: "amphora" is_public: yes vcpus: 2 ram: 1024 disk: 5 octavia_amp_security_groups: mgmt-sec-group: name: "lb-mgmt-sec-grp" rules: - protocol: icmp - protocol: tcp src_port: 22 dst_port: 22 octavia_amp_network: name: lb-mgmt-net provider_network_type: vlan provider_segmentation_id: 2140 provider_physical_network: physnet1 external: false shared: false subnet: name: lb-mgmt-subnet cidr: "10.145.50.128/26" allocation_pool_start: "10.145.50.135" allocation_pool_end: "10.145.50.190" gateway_ip: "10.145.50.129" enable_dhcp: yes octavia_amp_image_tag" "amphora" octavia_loadbalancer_topology: "SINGLE" Thanks, Jayesh

3 8