- openstack-discuss - lists.openstack.org

[sdk][cli][api][ansible-modules][ptg] Virtual PTG Planning
by Artem Goncharov 19 Oct '23

19 Oct '23

Hey, I have booked 2 hour slot on Wednesday 25 Oct 13:00-15:00 UTC for the SDK and CLI team (as usual on demand we can prolong the discussion). As I was already announcing some weeks ago we are going to discuss state of codegeneration in projects we maintain and use of OpenAPI to improve it, as well as getting OSC reworked to get a modern UX and performance. Therefore I would really appreciate a wide participation to get useful inputs. The agenda can be found at [1]. [1]: https://etherpad.opendev.org/p/oct2023-ptg-sdk-cli Regards, Artem

1 0

Openstack volume deletion
by vj66666＠gmail.com 19 Oct '23

19 Oct '23

Hi, OpenStack Kolla Ansible has been installed on Ubuntu 20 and integrated with Ceph storage. The volume associated with the instance is not being deleted by Cinder when I terminate the instance with this option (Delete Volume on Instance Delete), which is causing me problems. I need to log in to the server and run the cinder commands to manually delete the volume that is not associated with instances. I would appreciate it if you could provide a solution.

1 0

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

19 Oct '23

Welcome back to the release countdown emails! These will be sent at major points in the 2024.1 Caracal development cycle, which should conclude with a final release on April 3, 2024. Development Focus ----------------- At this stage in the release cycle, focus should be on planning the 2024.1 Caracal development cycle, assessing 2024.1 Caracal community goals and approving 2024.1 Caracal specs. General Information ------------------- 2024.1 Caracal is a 26 weeks development cycle. In case you haven't seen it yet, please take a look over the schedule for this release: https://releases.openstack.org/ <https://releases.openstack.org/caracal/schedule.html>caracal <https://releases.openstack.org/caracal/schedule.html>/schedule.html <https://releases.openstack.org/caracal/schedule.html> By default, the team PTL is responsible for handling the release cycle and approving release requests. This task can (and probably should) be delegated to release liaisons. Now is a good time to review release liaison information for your team and make sure it is up to date: https://opendev.org/openstack/releases/src/branch/master/data/release_liais… By default, all your team deliverables from the 2023.2 Bobcat release are continued in 2024.1 Caracal with a similar release model. Upcoming Deadlines & Dates -------------------------- Virtual Caracal PTG: October 23-27 2024.1 Caracal-1 milestone: November 16, 2023 -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

1 0

[interop][ptg] Virtual Caracal vPTG Planning
by Martin Kopec 19 Oct '23

19 Oct '23

Hello everyone, here is [1] our etherpad for the 2024.1 Caracal virtual PTG. Please, add your topics there if there is anything you would like to discuss / propose ... You can also vote for time slots for our session(s), so that they fit your schedule, at [2]. I have one topic I'd like to discuss - new view on interoperability testing, see [3] and this [4] article for the background info. [1] https://etherpad.opendev.org/p/oct2023-ptg-interop [2] https://framadate.org/rNFvjKVkMnXPfObf [3] https://etherpad.opendev.org/p/openstack-interop-2.0 [4] https://superuser.openinfra.dev/articles/new-view-on-interoperability-in-op… If you have any questions, feel free to reach out to me. Thanks, -- Martin Kopec Principal Software Quality Engineer Red Hat EMEA IM: kopecmartin

1 2

[qa][ptg] Virtual Caracal vPTG Planning
by Martin Kopec 19 Oct '23

19 Oct '23

Hello everyone, here is [1] our etherpad for the 2024.1 Caracal virtual PTG. Please, add your topics there if there is anything you would like to discuss / propose ... You can also vote for time slots for our sessions so that they fit your schedule at [2]. We will most likely go with 1-hour slot per day, as they usually fit easier into everyone's schedule. The number of slots will depend on the number of topics proposed in [1]. - [1] https://etherpad.opendev.org/p/oct2023-ptg-qa [2] https://framadate.org/f26R3EcZ2BOo7r8Q Thanks, -- Martin Kopec Principal Software Quality Engineer Red Hat EMEA IM: kopecmartin

1 2

[Glance][PTG] Caracal PTG Schedule
by Pranali Deore 19 Oct '23

19 Oct '23

Hello All, Caracal PTG is going to start next week and we have created our PTG etherpad [1] and also added day wise topics along with timings we are going to discuss. Kindly let me know if you have any concerns with allotted time slots. Friday is reserved for any unplanned discussions. So please feel free to add your topics if you haven't added yet. As a reminder, these are the time slots for our discussion. Tuesday 24 OCT 2023 1400 UTC to 1700 UTC Wednesday 25 OCT 2023 1400 UTC to 1700 UTC Thursday 26 OCT 2023 1400 UTC to 1700 UTC Friday 27 OCT 2023 1400 UTC to 1700 UTC NOTE: At the moment we don't have any sessions scheduled on Friday, if there are any last moment request(s)/topic(s) we will discuss that on Friday else we will conclude our PTG on Thursday 26th OCT. We will be using Gmeet for our discussion. The meeting URL is mentioned in etherpad [1] and will be the same throughout the PTG. [1] https://etherpad.opendev.org/p/oct2023-ptg-glance Hope to see you there!! Thanks & Regards, Pranali Deore

1 0

test
by Colin Tooley 19 Oct '23

19 Oct '23

test Colin Tooley Principal IT Support Engineer, IT Experience (ITX) Global Enterprise Support Red Hat NA <https://www.redhat.com> ctooley(a)redhat.com IM: ctooley <https://www.redhat.com>

1 0

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

19 Oct '23

Welcome back to the release countdown emails! These will be sent at major points in the 2024.1 Caracal development cycle, which should conclude with a final release on April 3, 2024. Development Focus ----------------- At this stage in the release cycle, focus should be on planning the 2024.1 Caracal development cycle, assessing 2024.1 Caracal community goals and approving 2024.1 Caracal specs. General Information ------------------- 2024.1 Caracal is a 26 weeks development cycle. In case you haven't seen it yet, please take a look over the schedule for this release: https://releases.openstack.org/ <https://releases.openstack.org/caracal/schedule.html>caracal <https://releases.openstack.org/caracal/schedule.html>/schedule.html <https://releases.openstack.org/caracal/schedule.html> By default, the team PTL is responsible for handling the release cycle and approving release requests. This task can (and probably should) be delegated to release liaisons. Now is a good time to review release liaison information for your team and make sure it is up to date: https://opendev.org/openstack/releases/src/branch/master/data/release_liais… By default, all your team deliverables from the 2023.2 Bobcat release are continued in 2024.1 Caracal with a similar release model. Upcoming Deadlines & Dates -------------------------- Virtual Caracal PTG: October 23-27 2024.1 Caracal-1 milestone: November 16, 2023 -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

1 0

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

19 Oct '23

Welcome back to the release countdown emails! These will be sent at major points in the 2024.1 Caracal development cycle, which should conclude with a final release on April 3, 2024. Development Focus ----------------- At this stage in the release cycle, focus should be on planning the 2024.1 Caracal development cycle, assessing 2024.1 Caracal community goals and approving 2024.1 Caracal specs. General Information ------------------- 2024.1 Caracal is a 26 weeks development cycle. In case you haven't seen it yet, please take a look over the schedule for this release: https://releases.openstack.org/ <https://releases.openstack.org/caracal/schedule.html>caracal <https://releases.openstack.org/caracal/schedule.html>/schedule.html <https://releases.openstack.org/caracal/schedule.html> By default, the team PTL is responsible for handling the release cycle and approving release requests. This task can (and probably should) be delegated to release liaisons. Now is a good time to review release liaison information for your team and make sure it is up to date: https://opendev.org/openstack/releases/src/branch/master/data/release_liais… By default, all your team deliverables from the 2023.2 Bobcat release are continued in 2024.1 Caracal with a similar release model. Upcoming Deadlines & Dates -------------------------- Virtual Caracal PTG: October 23-27 2024.1 Caracal-1 milestone: November 16, 2023 -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

1 0

[cinder] Cancelling this week's meeting (18 Oct)
by Rajat Dhasmana 19 Oct '23

19 Oct '23

Hello Argonauts, As you might be aware, we are going to have 2024.1 Caracal Cinder PTG next week from 24 October to 28 October, 2023. We will get a lot of time to meet and discuss topics there so let's cancel this week's cinder meeting (which was going to be held on 18 October). Don't forget to add topics to the planning etherpad[1]. See you all at the PTG! [1] https://etherpad.opendev.org/p/caracal-ptg-cinder-planning Thanks Rajat Dhasmana

1 0

[neutron] create_port with fixed_Ips is disallowed by policy
by Satish Patel 19 Oct '23

19 Oct '23

Folks, I am trying to give permission to end users to create fixed IP ports and attach to VMs but so far no luck. Release: Zed (OVN based deployment) I have added following in policy.yml file in neutron server "create_port:fixed_ips": "rule:context_is_advsvc or rule:network_owner or rule:admin_only or rule:shared" "create_port:fixed_ips:ip_address": "rule:context_is_advsvc or rule:network_owner or rule:admin_only or rule:shared" "create_port:fixed_ips:subnet_id": "rule:context_is_advsvc or rule:network_owner or rule:admin_only or rule:shared" $ openstack port create --network public-network-1 --fixed-ip subnet=dba7a427-dccb-4a5a-a8e0-23fcda64666d,ip-address=xx.xx.xx.xx my-port1 ForbiddenException: 403: Client Error for url: http://192.168.18.100:9696/v2.0/ports, (rule:create_port and (rule:create_port:fixed_ips and (rule:create_port:fixed_ips:subnet_id and rule:create_port:fixed_ips:ip_address))) is disallowed by policy I found some reference bug but not sure they are fixed or not: https://bugs.launchpad.net/neutron/+bug/1833455

4 6

[Glance][PTG] Caracal vPTG Schedule
by Pranali Deore 18 Oct '23

18 Oct '23

Hello All, Caracal PTG is going to start next week and we have created our PTG etherpad [1] and also added day wise topics along with timings we are going to discuss. Kindly let me know if you have any concerns with allotted time slots. Friday is reserved for any unplanned discussions. So please feel free to add your topics if you haven't added yet. As a reminder, these are the time slots for our discussion. Tuesday 24 OCT 2023 1400 UTC to 1700 UTC Wednesday 25 OCT 2023 1400 UTC to 1700 UTC Thursday 26 OCT 2023 1400 UTC to 1700 UTC Friday 27 OCT 2023 1400 UTC to 1700 UTC NOTE: At the moment we don't have any sessions scheduled on Friday, if there are any last moment request(s)/topic(s) we will discuss that on Friday else we will conclude our PTG on Thursday 26th OCT. We will be using Gmeet for our discussion. The meeting URL is mentioned in etherpad [1] and will be the same throughout the PTG. [1] https://etherpad.opendev.org/p/oct2023-ptg-glance Hope to see you there!! Thanks & Regards, Pranali Deore

1 0

[horizon] Cancelling Today's Weekly meeting
by vishal manchanda 18 Oct '23

18 Oct '23

Hello Team, As discussed in the last Horizon weekly meeting, there won't be a weekly meeting today. I look forward to seeing you at the PTG. If anything urgent, please reach out to me on IRC. Thanks & regards, Vishal Manchanda

1 0

[horizon] Caracal Virtual PTG Schedule
by vishal manchanda 18 Oct '23

18 Oct '23

Hello Team, Please Find the Schedule for Horizon Caracal PTG in the eherpad [1]. Feel Free to add the topics you want to discuss in the PTG. Don't forget to register for PTG, if not done yet [2]. See you at the PTG! Thanks & Regards, Vishal Manchanda (irc: vishalmanchanda) [1] https://etherpad.opendev.org/p/horizon-caracal-ptg [2] https://openinfra-ptg.eventbrite.com/

1 0

[kolla-ansible][yoga] Cannot authenticate to openstack after deploying self-signed cert
by wodel youchi 18 Oct '23

18 Oct '23

Hi, Our ssl certificate expired a couple of days ago, and we started experiencing failed login, to workaround the problem rapidly we decided to deploy the self-signed certificates generated by kolla. We generated the certificates then we did a reconfigure, but still the problem remains : An error occurred authenticating. Please try again later. on horizon.log we have : [Wed Oct 18 00:25:55.379383 2023] [wsgi:error] [pid 103:tid 140182314505984] [remote 10.10.3.5:40848] Login failed for user "admin" using domain "default", remote address 10.10.3.5 The openstack command line works fine. How can we debug this? The second problem we have is with cloudkitty that refuses to reconfigure with the generated self-signed certificate, we had to ignore it from the reconfiguration process by putting the cloudkitty variable to no before restarting the reconfigure process. How can we debug this? Regards. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free.www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2 2

[kolla-ansible]
by Franck VEDEL 18 Oct '23

18 Oct '23

I'm coming back to you all to help me with a new problem that I've never had before. I want to show students how to install Openstack with Kolla-ansible. They will each have a computer (DELL Precison 3660 Tower, 32G RAM, 500G SDD). Ubuntu is the system, version 22.04. I want to start with an "all-in-one" installation. So I test my-self first… I follow these procedure https://docs.openstack.org/kolla-ansible/latest/user/quickstart.html . everything works with the parameters I choose for my configuration, until the following problem: ___________________________________________________ ___________________________________________________ TASK [nova-cell : Ensuring config directories exist] ************************************************ ok: [localhost] TASK [nova-cell : Copying over config.json files for nova-cell-bootstrap] *************************** ok: [localhost] TASK [nova-cell : Copying over nova.conf for nova-cell-bootstrap] *********************************** ok: [localhost] TASK [nova-cell : Running Nova cell bootstrap container] ******************************************** ok: [localhost] TASK [nova-cell : Get a list of existing cells] ***************************************************** ok: [localhost] TASK [nova-cell : Extract current cell settings from list] ****************************************** fatal: [localhost]: FAILED! => {"msg": "template error while templating string: Could not load \"extract_cell\": 'extract_cell'. String: {{ existing_cells_list | extract_cell(nova_cell_name) }}. Could not load \"extract_cell\": 'extract_cell'"} NO MORE HOSTS LEFT ********************************************************************************** PLAY RECAP ****************************************************************************************** localhost : ok=146 changed=8 unreachable=0 failed=1 skipped=64 rescued=0 ignored=0 ___________________________________________________ ___________________________________________________ My globals.yml ___________________________________________________ ___________________________________________________ kolla_base_distro = "ubuntu" kolla_internal_vip_address: "172.16.60.15" network_interface : "enp0s31f6" neutron_external_interface: "enp3s0" neutron_plugin_agent: "openvswitch" enable_haproxy: "no" enable_cells: "no" nova_compute_virt_type: « kvm" …. ___________________________________________________ ___________________________________________________ What can be the problem ? Where can this come from ? I think the CPU is OK for virtualization. I have no idea, I don't know where this error could come from. Do you have an idea? Thanks in advance Franck

3 5

[largescale-sig] Next meeting: October 18, 8utc
by Thierry Carrez 18 Oct '23

18 Oct '23

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

1 1

[cyborg][sahara][senlin][trove][venus][mistral][ec2-api][monasca][openstack-chef]: Next step for 2024.1 cycle leaderless projects
by Ghanshyam Mann 18 Oct '23

18 Oct '23

Hi, As you know, the listed projects in subject/etherpad[1] are leaderless for 2024.1 development cycle. We have PTL volunteer for all those projects now. As next step, I would like to request each volunteer to propose the governance change for their PTL appointment and TC will be discussing the same on gerrit/PTG. Example: https://review.opendev.org/c/openstack/governance/+/896585 [1] https://etherpad.opendev.org/p/2024.1-leaderless -gmann

1 0

[all][tc][policy] RBAC goal discussion in 2024.1 PTG
by Ghanshyam Mann 18 Oct '23

18 Oct '23

Hello Everyone, I have booked the Monday 13-14 UTC slot Austin room for the RBAC goal discussion. Feel free to add the topics/queries to be discussed in vPTG in the below etherpad. Also, add your project related RBAC sessions details in same etherpad. - https://etherpad.opendev.org/p/rbac-2024.1-ptg -gmann

1 0

[tc] TC Meeting for Oct 24 Cancelled due to PTG
by Jay Faulkner 18 Oct '23

18 Oct '23

The weekly TC meeting, scheduled for October 24, has been cancelled to allow all members the freedom to participate in PTG sessions. See you at the PTG! Thanks, Jay Faulkner OpenStack TC Chair

1 0

Installing OpenStack with limited switch ports
by John van Ommen 18 Oct '23

18 Oct '23

Is there an OpenStack installer that offers the option of using tagged VLANs during the installation? I'm building an OpenStack environment that uses redundant hardware, but I have limited space for switches. The idea that I had was to use tagged VLANs for the external network. But all of the installers that I've seen, they only work if each physical port on the server corresponds to a network. IE, one of my physical ports on my server needs to be connected to a management switch, another port needs to be connected to the switch for the external network, etc. I'd like to reduce the physical footprint of the switches, by using a single switch with tagged VLAN: 1) one VLAN for the management network 2) one tagged VLAN for the external network 3) etc Taken to the extreme, it seems like it might be possible to use as few as one or two physical ports for all of the OpenStack networks. Is this possible, and if so, which OpenStack distribution offers this?

3 2

[magnum] Cancelling weekly meetings for 18 and 25 Oct
by Jake Yip 18 Oct '23

18 Oct '23

Hi all, Unfortunately, we will have to cancel the meeting this week as I will be away for a conference. Next week is our vPTG, we will have it at a separate timeslot so the weekly meeting will be cancelled too. I will send vPTG details in a separate email. Regards, Jake

1 0

[nova] [libvirt] About libvirt autoconverge
by hai wu 17 Oct '23

17 Oct '23

Do you enable auto-converge for nova instance live migration on all production hypervisor hosts?

2 4

[OPENSTACK][rabbitmq] using quorum queues
by Nguyễn Hữu Khôi 17 Oct '23

17 Oct '23

Hello guys. IS there any guy who uses the quorum queue for openstack? Could you give some feedback to compare with classic queue? Thank you. Nguyen Huu Khoi

9 19

[neutron] bug deputy report (Oct 9-15)
by Akihiro Motoki 17 Oct '23

17 Oct '23

Hi, I was a bug deputy last week. Here is a report on bugs last week. Three unassigned bugs are worth investigating. We also had three bugs on fwaas related to gate failures. It would be nice if FWaaS folks can look into them. # New disallowed by policy error when user try to create_port with fixed_Ips https://bugs.launchpad.net/neutron/+bug/2039464 This may need a detail investigation. There might be a gap between network RBAC and policy handling like "create_port:fixed_ips". [OVN] Floating IP <=> Floating IP across subnets https://bugs.launchpad.net/neutron/+bug/2038978 Unassigned, but mnaser shared a workaround and proposed a WIP patch. ovsfw: OVS br-int rule disappears from the table=60 after stop/start VM https://bugs.launchpad.net/neutron/+bug/2038931 This needs to be investigated. Liu had an initial look ## FWaaS [neutron-fwaas] "neutron-fwaas-fullstack" job broken https://bugs.launchpad.net/neutron/+bug/2039285 [fwaas] Scenario job fails randomly https://bugs.launchpad.net/neutron/+bug/2039012 [fwaas] CI job "neutron-fwaas-v2-dsvm-tempest-multinode" failing https://bugs.launchpad.net/neutron/+bug/2038936 # In Progress [fullstack] The "dhclient" kill command can take more than 90 seconds https://bugs.launchpad.net/neutron/+bug/2039038 Assigned to ralonsoh openstacksdk-functional-devstack-networking periodic job broken in xena/yoga/zed https://bugs.launchpad.net/neutron/+bug/2039066 Assigned to yatin A patch to skip these tests was merged in yoga and zed. xena job was also fixed not to use the master branch. Looks completed but I would like to wait for yatin. # Fix Released tempest nftables jobs are not running in periodic queue https://bugs.launchpad.net/neutron/+bug/2039027 Thanks, Akihiro Motoki (amotoki)

1 0