- openstack-discuss - lists.openstack.org

*[glance] Request for Feature Freeze Exception*
by Abhishek Kekane 29 Feb '24

29 Feb '24

Hi Team, I would like to request FFE for "Using centralized database for cache operations" feature. Patches: https://review.opendev.org/q/topic:%22centralized-cache-db%22 Status: Base functionality is merged Pending: - Devstack patch for defaulting cache_driver to centralized_db - https://review.opendev.org/c/openstack/devstack/+/907110 - Tempest tests for caching images on remote node - https://review.opendev.org/c/openstack/tempest/+/901525 - Grenade patch to change cache-driver to centralized_db on upgrade - https://review.opendev.org/c/openstack/grenade/+/901678 - New tempest job to test centralized db - https://review.opendev.org/c/openstack/glance/+/901429 - New Grenade job to test upgrade scenario - https://review.opendev.org/c/openstack/glance/+/901649 - Make centralized_db driver default in glance - https://review.opendev.org/c/openstack/glance/+/907111 Why miss the deadline: Some useful restructuring during milestone 3 This feature is useful as we just need a single database which reduces the need of maintaining sqlite3 database and also can enhance caching operations by introducing new APIs in future. Kindly consider this feature for the current cycle and assist with reviews and suggestions. Thank you, Abhishek Kekane

3 2

[nova] dry-run migration api
by Pavlo Shchelokovskyy 29 Feb '24

29 Feb '24

Hi all, Recently I've been looking into various load optimizations tooling for OpenStack (like Watcher), and noticed a lacking feature that could make such tooling much more robust and useful. The optimization tooling usually collects some metric about compute hosts and instances that nova may be totally unaware of (e.g. power consumption of a compute node in Watts), and then tries to reshuffle the instances between hypervisors to optimize said metric in some sense. The problem is, the tool has no idea beforehand if nova will actually allow moving this given instance to this given hypervisor. I am talking about resource consumption, resource provider traits, image and aggregate metadata matching, numa placement, server group affinities etc. To know all this for sure, the optimization tool would have to duplicate most of the nova scheduler and good part of placement inside of itself - which is not feasible. This is why AFAIU in Watcher all available strategies mention that they expect "any VM to be migrateable to any hypervisor", which is far from many if not most real life deployments. What I suggest is adding a new API to nova to effectively have a 'migration dry run' - it should return the list of target hosts a given instance may be migrated to, accounting for all the knowledge nova has about the instance and the hypervisors. The list can be already sorted by nova weighers to signal the preferred choice from nova side. AFAIU such a new API would not require any drastic changes in Nova - the most of the code is already there, used during migrations, only that at the last step, instead of choosing the best compute and actually initiating the migration process, the result of filtering and weighing will be returned to the caller in some form. Would there be interest in such an API? If yes, I could start writing and proposing a spec. Best regards, -- Dr. Pavlo Shchelokovskyy Principal Software Engineer Mirantis Inc www.mirantis.com

3 2

Re: Enabling external connectivity to VMs
by Eugen Block 29 Feb '24

29 Feb '24

Please don't drop the list from your response. I'm not very familiar with kolla, but if you're able to ping the instance via floating IP it seems okayish. Maybe you need to set neutron_external_interface to ens192 instead? Someone with more kolla experience will probably correct me here, so don't rely on my response. Zitat von KK CHN <kkchn.in(a)gmail.com>: > Hi Eugen, > > I have followed the > https://docs.openstack.org/kolla-ansible/latest/reference/networking/neutro… > > But mistakenly I have configured ens160 as neurton_external_interface: > "ens160" as the docs says an interface without IP address needed so I > create a vNIC ens160 without IP and used this without knowing What I am > doing..!!!! > > The issue is tenant VMs don't get Internet. also tenant VMs cant ping > base VM(Ubuntu 22.04 IP 10.220.0.51, or 10.176.16.128 .. ) totally > confused. > > > Could you help me to understand what I am doing wrong here ? > Greetings > Krish. > > *For more info what I have done so far : * Please refer to > the following... > > In the Base VM, I created 3 vNICs. > > 1. ens192 with my Org's dhcp LAN IP 10.176.16.128 which has the internet. > 2. ens224 with 10.220.0.51 IP which is a VLAN IP of (10.220.0.0/24) which > is created for testing purposes internally by N/W guy. This doesn't have > the internet.. > > 3. ens160 up active without IP address. ( Wrongly I specified this as the > e neutron_external_interface in globals.yml) > > > > *I have deployed the openstack..Everything up and running .. * > I am able to create Routers, Network and subnets and able to create > instances(all VMs spawning with 10.0.0.0/24 IPs) > > I created the networks(external with subnet 10.220.0.0/24 with > start=10.220.0.30 to end=10.220.0.50) and internal Network(with subnet > named demo-net 10.0.0.0/24 for tenants) > > I am able to associate the VMs with 10.0.0.0/24 IPs to Floating IPs from > 10.220.0.0/24 > > and from my Base(host) VM(Ubuntu22.04 with ens224 10.220.0.51) I am able > to ping the 10.0.0.28 tenant VM IP through the associated floating IPs as > > $ ip netns ( On base (host) VM) dsplays the router > (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ ip netns > qrouter-ecc6fe39-a733-4f30-bf67-ac42407227f8 (id: 1) > > qdhcp-c29f26ac-3594-4c40-bf20-f2d5ba7d6eea (id: 0) > > > $(kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ sudo ip netns exec > qrouter-ecc6fe39-a733-4f30-bf67-ac42407227f8 ping 10.0.0.28 ( the VM > tenant IP address) > PING 10.0.0.28 (10.0.0.28) 56(84) bytes of data. > 64 bytes from 10.0.0.28: icmp_seq=1 ttl=64 time=0.972 ms > > (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ sudo ip netns exec > qrouter-ecc6fe39-a733-4f30-bf67-ac42407227f8 ping 10.220.0.44 ( the > Floating IP associated to 10.0.0.28 VM) > PING 10.220.0.44 (10.220.0.44) 56(84) bytes of data. > 64 bytes from 10.220.0.44: icmp_seq=1 ttl=64 time=0.840 ms > 64 bytes from 10.220.0.44: icmp_seq=2 ttl=64 time=0.599 ms > > (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ sudo ip netns exec > qrouter-ecc6fe39-a733-4f30-bf67-ac42407227f8 ping 10.220.0.33 ( The router > IP through which connects floating ip 10.220.0.44 and then to tenant VM ip > 10.0.0.28 ) > > PING 10.220.0.33 (10.220.0.33) 56(84) bytes of data. > 64 bytes from 10.220.0.33: icmp_seq=1 ttl=64 time=0.038 ms > > *Hence it works somehow. * But ens224 10.220.0.51 doesn't have > internet on the base VM. But only ens192->10.170.16.128 IP has.. > > How can I provide the internet connectivity of ens192 to ens224 Is this > possible or Am I doing some dump here.? What is the other way / best way > to do this .. > I am beginning my journey with OpensStack but stuck here without much > progress.. > > > (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ grep ^[^#] /etc/kolla/globals.yml > --- > workaround_ansible_issue_8743: yes > config_strategy: "COPY_ALWAYS" > kolla_base_distro: "ubuntu" > openstack_release: "2023.1" > kolla_internal_vip_address: "10.220.0.24" > kolla_external_vip_address: "{{ kolla_internal_vip_address }}" > kolla_container_engine: docker > network_interface: "ens224" > neutron_external_interface: "ens160" > neutron_plugin_agent: "openvswitch" > nova_compute_virt_type: "qemu" > (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ > > > The following screenshot shown the tenant VM console(tty) where I am able > to ping floating IP(10.220.0.44 and its router ip 10.220.0.33 ) but > neither 10.220.0.51 the base VM ens224 IP nor ens192 10.17.16.128 > > > [image: image.png] > > > > krish > > On Tue, Feb 27, 2024 at 11:09 PM Eugen Block <eblock(a)nde.ag> wrote: > >> Hi, >> >> Check out this page: >> >> >> https://docs.openstack.org/kolla-ansible/latest/reference/networking/neutro… >> >> You need some sort of external network to provide connectivity for >> instances. >> >> Zitat von KK CHN <kkchn.in(a)gmail.com>: >> >> > List, >> > >> > I am a bit confused with the OpenStack Networking configuration for >> > Created virtual machines on a (Kolla-ansible all-in-one on an Ubuntu >> > 22.04 VM ) openstack installation. >> > >> > I am able to create virtual machines through the dashboard as well as >> CLI. >> > I have used the default network/cirros images created from init-runonce >> > script. >> > >> > But Real time, how can I configure these new VMs to communicate with Base >> > VM or external world by ping, ssh or make internet connection etc. >> > >> > Base VM is Ubuntu22.04 - with IPs ens192=>10.170.16.128(with Internet), >> > second interface => ens224 => 10.220.0.51 and ens160 up and running >> > without IP address for neutron_external_interface: >> > >> > All the VMs which I created getting IP addresses in series (10.0.0.X). >> > >> > But How to allocate Internet and make external world communication to >> and >> > from these VMs ? >> > >> > >> > Any hints/directions towards this much appreciated. >> > >> > Greetings, >> > Krish >> > >> > >> > If required more inputs here follows the additional information. >> > >> > (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ grep ^[^#] >> /etc/kolla/globals.yml >> > --- >> > workaround_ansible_issue_8743: yes >> > config_strategy: "COPY_ALWAYS" >> > kolla_base_distro: "ubuntu" >> > openstack_release: "2023.1" >> > kolla_internal_vip_address: "10.220.0.24" >> > kolla_external_vip_address: "{{ kolla_internal_vip_address }}" >> > kolla_container_engine: docker >> > network_interface: "ens224" >> > neutron_external_interface: "ens160" >> > neutron_plugin_agent: "openvswitch" >> > nova_compute_virt_type: "qemu" >> > (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ >> > >> > >> > >> > Additional inputs: >> > >> > There are 3 virtual interfaces on the base Ubuntu22.04 Virtual Machine. >> > ens192->10.170.16.128 with internet, ens224->10.220.0.51 , ens160 up >> > without IP >> > >> > 1. First Interface contain IP address from My organizations DHCP lease >> from >> > LAN(10.16.16.0) Which has Internet connectivity. >> > ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP >> group >> > default qlen 1000 link/ether 00:0c:29:33:18:3c brd ff:ff:ff:ff:ff:ff >> > altname enp11s0 >> > inet 10.170.16.128/23 brd 10.170.17.255 scope global dynamic >> noprefixroute >> > ens192 >> > valid_lft 786963sec preferred_lft 786963sec >> > inet6 fe80::cd1a:bc6c:b129:f91f/64 scope link noprefixroute >> > valid_lft forever preferred_lft forever3 >> > >> > >> > 2. Interface I have 10.220.0.51 >> > >> > ens224: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP >> group >> > default qlen 1000 >> > link/ether 00:0c:29:33:18:46 brd ff:ff:ff:ff:ff:ff >> > altname enp19s0 >> > inet 10.220.0.51/24 brd 10.220.0.255 scope global noprefixroute >> ens224 >> > valid_lft forever preferred_lft forever >> > inet 10.220.0.24/32 scope global ens224 >> > valid_lft forever preferred_lft forever >> > inet6 fe80::a8b6:f094:c47:8282/64 scope link noprefixroute >> > valid_lft forever preferred_lft forever >> > >> > 3. ens160 without any IP address which is up and running configured for >> > Kolla neutron_external_interface: "ens160" >> > >> > ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master >> > ovs-system state UP group default qlen 1000 >> > link/ether 00:0c:29:33:18:32 brd ff:ff:ff:ff:ff:ff >> > altname enp3s0 >> > >> > >> > >> > 1. What networks need to be created additionally ? >> > 2. Bridges and bonds required here or not ? >> > >> > 3. To enable these New VMs to talk to external world( ssh, ping, internet >> > connection to all these VMs ) what all the steps need to be performed or >> I >> > left out ? >> >> >> >>

1 0

[oslo][release][requirement] FFE request for oslo.context
by Takashi Kajinami 29 Feb '24

29 Feb '24

Hello, I'd like to request an exception to merge a change[1] to oslo.context and create a new stable/2024.1 release. This change is required to fix the problem which is current blocking us from bumping oslo.messaging to the final 2024.2 release version (14.7.0)[2]. The change is small and has quite limited impact. I've tested the modification locally and confirmed it fixes the heat unit tests. [1] https://review.opendev.org/c/openstack/oslo.context/+/910153 [2] https://review.opendev.org/c/openstack/requirements/+/909906 -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

3 4

[magnum] Dropping default Cluster API driver
by Mohammed Naser 29 Feb '24

29 Feb '24

Hi everyone, It seems that based on a recent post that I saw on the Twitter-sphere[1], it seems that the Magnum team has decided to move forward with setting a default driver for the Cluster API. I don't agree with this. Unfortunately, we don't have much recordings of our PTG conversations, and since the notes on the PTG are pretty light[2], I don't see any details of that. I don't see why we should be merging a native Cluster API driver and not allowing the operators and deployment tools decide which one they want to support. Personally, I think that the Helm driver should be built in a separate repository and then installed by the user as a Python package once they understand what are the backends and their options, as opposed to shipping one out of the box with far less features. We already have successful users which are using our implementation in production that have also posted blogs and shared their experience, we'd be doing them a disservice by now announcing a 'native' built-in driver. Can the decision be changed so that there is no built-in driver, and you must decide to install one yourself? Also, I would be really happy to hear feedback from users of the driver for their comments here. Thanks, Mohmamed [1]: https://www.stackhpc.com/magnum-clusterapi.html [2]: https://etherpad.opendev.org/p/r.5b94a5a9dbf4e3bf8202b5e57cb93770

19 34

[ptl][election][trove] PTL candidacy for 2024.2
by chunyang wu 29 Feb '24

29 Feb '24

Hello everyone: I would like to announce my candidacy for PTL of the Trove project for the 2024.2 cycle. For the Dalmatian cycle, i'd like to focus on the following: * review the coming patches * Add more tempest tests * Add CI tests for the latest datastore(mysql, mariadb, postgresql) version * improve docs thanks wu.chunyang

2 2

[all][elections][tc] TC Election Campaigning Kickoff
by Ian Y. Choi 29 Feb '24

29 Feb '24

Developers, The TC Election Campaigning Period has now started[1]. During the next couple days, you are all encouraged to ask the candidates questions about their platforms[2], opinions on OpenStack, community governance, and anything else that will help you to better determine how you will vote. This is the time to raise any issues you wish the future TC to consider, and to evaluate the opinions of the nominees prior to their election. Candidates, Each of you has posted a platform[2], and announced your nomination to the developers. From this point, you are encouraged to ask each other questions about the posted platforms, and begin discussion of any points that you feel are particularly important during the next cycle. While you are not yet TC members, your voices and opinions about the issues raised in your platforms and questions raised by the wider community will help ensure that the future TC has the widest possible input on the matters of community concern, and the electorate has the best information to determine the ideal TC composition to address these and other issues that may arise. [1] https://governance.openstack.org/election/ [2] https://opendev.org/openstack/election/src/branch/master/candidates/2024.2/…

1 0

[all][elections][ptl][tc] Combined PTL/TC 2024.2 cycle Election Nominations End
by Ian Y. Choi 29 Feb '24

29 Feb '24

The PTL and TC Nomination period is now over. The official candidate lists for PTLs [0] and TC seats [1] are available on the election website. -- PTL Election Details -- There are 11 projects without candidates, so according to this resolution[2], the TC will have to decide how the following projects will proceed: Ec2_Api, Freezer, Kuryr, Murano, OpenStack_Charms, Sahara, Senlin, Skyline, Solum, Trove, Watcher There are 0 projects that will have elections: . -- TC Election Details -- The official candidate list is available on the election website[1]. Now begins the campaigning period where candidates and electorate may debate their statements. Polling will start Mar 06, 2024 23:45 UTC. Thank you, [0] https://governance.openstack.org/election/#2024.2-ptl-candidates [1] https://governance.openstack.org/election/#2024.2-tc-candidates [2] https://governance.openstack.org/resolutions/20141128-elections-process-for…

1 0

Ansible performance
by Gk Gk 28 Feb '24

28 Feb '24

Hi, Is there any way to speedup the playbooks execution of openstack ansible ? Can we remove gather facts for any tasks without affecting the installation ?

5 4

Ansible variables
by Gk Gk 28 Feb '24

28 Feb '24

Hi, We have an OSA setup. During a service playbook, for example, say rabbitmq, which task or play is responsible for creating it's haproxy configuration ? I mean, where is the code in openstack ansible to say to gather the values from user_variables file for that particular service or gather it from conf.d ? For instance, for rabbitmq service, where is the code which says to get the rabbitmq management port for the backend to be 15671 ? I mean where is the source code for pulling it from user_variables file and also which variable from it ?

3 2

[ptl][election][barbican] PTL Candidacy for 2024.2
by Grzegorz Grasza 28 Feb '24

28 Feb '24

Hello, I would like to propose my candidacy for Barbican PTL in the 2024.2 cycle. I've been the PTL since Antelope and I would like to continue to contribute in this role. As in the past cycles, I will continue to focus on Barbican maintenance and stability. Thanks you for your consideration, Grzegorz Grasza (xek)

1 0

[election][cloudkitty] PTL candidacy for the 2024.2 release cycle
by Rafael Weingärtner 28 Feb '24

28 Feb '24

Hi all, I would like to self-nominate for the role of PTL of CloudKitty for the 2024.2 release cycle. I have been PTL since the Victoria cycle and I am willing to continue in this role. I will keep working with existing contributors to maintain CloudKitty for their use cases and encourage the addition of new functionalities. I have opened the patch with my candidacy: https://review.opendev.org/c/openstack/election/+/910519 -- Rafael Weingärtner

1 0

[ptl][election][keystone] PTL Candidacy for 2024.2
by Dave Wilde 28 Feb '24

28 Feb '24

Hello, I would like to continue my tenure as PTL of Keystone. Over the past cycle we have made some great progress especially around the cadence in getting patches reviewed and merged. I would like to focus this next cycle on seeing that [1] is implemented as well as some much needed backlog cleanup. I would also, finally, like to get a "known-issues" section added to the documentation as well as ensuring that our documentation is up to date. Thanks for your time and support and I'm looking forward to another great cycle. [1]: https://specs.openstack.org/openstack/keystone-specs/specs/keystone/2024.1/… /Dave

1 0

TC Candidacy
by Amy Marrich 28 Feb '24

28 Feb '24

I am declaring my candidacy for the Technical Committee. I currently serve on the TC and have contributed to multiple projects over the years within OpenStack as well as being an operator which I feel gives me a well rounded view of what makes OpenStack and how the pieces should work together and what the users need. I feel I represent all members of the community from the small private clouds to the teams running large public clouds. I also feel my experiences helping with OpenStack Upstream Institute, OpenStack OPS Meetup team, the OpenStack mentoring program, and the Git and Gerrit workshops help me to connect with contributors from those just starting out to those who have been here from the beginning. My main goal for rejoining the TC is to take my experiences with Operators and making sure they have a voice within the our decisions so that we can better meet the needs of our users. Thanks, Amy Marrich (spotz)

1 0

[ptl][election][kuryr] PTL non-candidacy for 2024.2
by Roman Dobosz 28 Feb '24

28 Feb '24

Hello, I'm not going to run for PTL of Kuryr for Dalmation. I encourage Kuryr contributors to run for PTL and will offer any assistance needed for whoever is elected. Thanks, Roman Dobosz (gryf)

1 0

[election][tc] Candidacy for the TC
by James Page 28 Feb '24

28 Feb '24

Hi All, I'd like to announce my candidacy for the Technical Committee. For those of you who do not know me, I've been involved with OpenStack from the very early days of the project. I've attended many OpenStack summits and Project Teams Gatherings over the years and have been privileged to help the project grow from its small beginnings to the established cloud platform that it has now become. I was the main driver behind migration of the OpenStack Charms to its current home as an official OpenStack project which I then led for many cycles as PTL and I remain an active core developer on this project. I'm the current PTL of Sunbeam which was accepted into OpenStack last year as a new incubating project, providing a reboot of the charmed approach to deploying OpenStack utilising the many new projects that have appeared since we started the OpenStack Charms project back in 2011. I also work as part of the team responsible for the packaging and distribution of OpenStack as part of Ubuntu. I have been a member of the TC for the last year providing a voice from a deployment tooling and distribution perspective. I would like the opportunity to continue in this role providing what I believe is a valuable perspective to the technical governance of the OpenStack project. In particular I think we need to address some of the challenges around the general health of wider ecosystem dependencies of OpenStack to ensure that we move forward onto a stable base benefiting operators, distributors and developers. Thank you for taking the time to consider my candidacy for this role. Regards James Page (irc:jamespage)

1 0

[puppet][murano] Retiring puppet-murano
by Takashi Kajinami 28 Feb '24

28 Feb '24

Hello, As you may know, TC decided to exclude Murano from 2024.1 release because of its health status[1]. Based on this fact, and also another fact that puppet-murano has had no real development activities for long, I'd propose retiring puppet-murano now. It may be too late to make release deliverable decision. However our puppet modules are tightly coupled with openstack release cycles and we can't assure compatibility between our modules and inactive components, which are no longer aligned with the consistent release cycle. Please let me know if you have any concerns. Thank you, Takashi [1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

1 0

[ptl][election][sunbeam] PTL candidacy for 2024.2
by Hemanth N 28 Feb '24

28 Feb '24

Hello OpenStack Community, I am nominating myself for the Sunbeam PTL position during the 2024.2 cycle. I am a core team member of the Sunbeam project from the incubation stage and contributed to most of the charms that are part of the sunbeam project. In the last cycle we focussed on moving the 20+ charm repo's to a mono repo which helped reduce the codebase and easy maintenance of all the sunbeam charms. In the 2024.2 cycle, my priorities will be * Adding new features or charms and filling gaps to enable charms to be production ready * Stabilise the existing charms or libraries * Bug smashing * CI stability Thank you for your support. Best Regards, Hemanth Nakkina (hemanth, hemanth.nakkina(a)canonical.com)

1 0

Tim Burke candidacy for Swift PTL
by Tim Burke 28 Feb '24

28 Feb '24

I'm pleased to announce my candidacy for Swift PTL for the Dalmation cycle. As usual, we have a great many projects currently in flight: - Supporting Python 3.12 - Adding more fine-grained metrics, while keeping it configurable to not break existing metrics pipelines nor overwhelm them - Improving S3 compatibility, enabling a broader community of tools to work out of the box - More operator tooling for expiring objects - Better process management for WSGI servers - Backend ratelimiting to improve per-node load shedding I'm excited to see how each of these will move forward over the next cycle. Tim Burke

2 1

[all][elections][ptl][tc] Combined PTL/TC 2024.2 cycle Election Nominations Last Days
by Ian Y. Choi 28 Feb '24

28 Feb '24

A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Feb 28, 2024 23:45 UTC. If you want to stand for election, don't delay, follow the instructions at[1] to make sure the community knows your intentions. Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. All members of the community are encouraged to confirm their email address and opt in to the CIVS election as described at: https://governance.openstack.org/election/#electorate Election statistics[2]: Nominations started @ 2024-02-14 23:45:00 UTC Nominations end @ 2024-02-28 23:45:00 UTC Nominations duration : 14 days, 0:00:00 Nominations remaining : 23:49:45 Nominations progress : 92.91% --------------------------------------------------- Projects[1] : 47 Projects with candidates : 30 ( 63.83%) Projects with election : 0 ( 0.00%) --------------------------------------------------- Need election : 0 () Need appointment : 17 (Barbican Cloudkitty Ec2_Api Freezer Glance Keystone Kuryr Magnum Murano OpenStackAnsible OpenStack_Charms Sahara Senlin Skyline Solum Trove Watcher) --------------------------------------------------- TC Candidates : 7 (5 Required) =================================================== Stats gathered @ 2024-02-27 23:55:15 UTC This means that with approximately 2 days left, 17 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. Thank you, [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] Any open reviews at https://review.opendev.org/q/project:openstack/election+is:open+file:candid… have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for…

1 0

[ptl][election][cinder] PTL candidacy for 2024.2
by Jon Bernard 27 Feb '24

27 Feb '24

Hi All, I would like to announce my candidacy for PTL of the Cinder project for the 2024.2 cycle. I think Rajat has done an excellent job serving the project and I would like to carry existing efforts forward while continuing to focus maintaining a healthy and productive community around the Cinder project. I've been contributing to the Cinder project in varying capacity for close to 10 years. I've worked on migration and replication at the driver layer, mentored new contributors from the outreachy project, and provided bug fixes and reviews wherever possible. I'm a core reviewer and also a stable core. I have served as the release liaison for the last 2 cycles and run a weekly bug squashing meeting to help maintain our launchpad backog. We continue to face review bandwidth pressure. Emphasis should be placed on encouraging contributors to do code reviews and to recognize the efforts of those currently participating. There are several potential core reviewers and I feel that empowering the community is one way to increase engagement and the quality of our releases. 3rd party CI continues to be crucial resource for evaluating driver-specific changes. Maintaining good 3rd party CI for the drivers supported in Cinder by providing clear documentation and requirements will be a focus. Additionally, we have room for improvement in our backup and restore use case. My goal is to improve the entire backup/restore situation so that it can be leveraged by users in production environments. Our customers are using 3rd party backup products to backup workloads and volumes and I think this is one are where improvements here can directly benefit users. In summary, I would like to continue the efforts made by Rajat and continue to focus the areas most in need of attention for the 2024.2 cycle. I will do my best to make a positive contribution to both the technical and community aspects of Cinder during my time as PTL. Thank you for your consideration. -- Jon Bernard (jbernard)

1 0

Enabling external connectivity to VMs
by KK CHN 27 Feb '24

27 Feb '24

List, I am a bit confused with the OpenStack Networking configuration for Created virtual machines on a (Kolla-ansible all-in-one on an Ubuntu 22.04 VM ) openstack installation. I am able to create virtual machines through the dashboard as well as CLI. I have used the default network/cirros images created from init-runonce script. But Real time, how can I configure these new VMs to communicate with Base VM or external world by ping, ssh or make internet connection etc. Base VM is Ubuntu22.04 - with IPs ens192=>10.170.16.128(with Internet), second interface => ens224 => 10.220.0.51 and ens160 up and running without IP address for neutron_external_interface: All the VMs which I created getting IP addresses in series (10.0.0.X). But How to allocate Internet and make external world communication to and from these VMs ? Any hints/directions towards this much appreciated. Greetings, Krish If required more inputs here follows the additional information. (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ grep ^[^#] /etc/kolla/globals.yml --- workaround_ansible_issue_8743: yes config_strategy: "COPY_ALWAYS" kolla_base_distro: "ubuntu" openstack_release: "2023.1" kolla_internal_vip_address: "10.220.0.24" kolla_external_vip_address: "{{ kolla_internal_vip_address }}" kolla_container_engine: docker network_interface: "ens224" neutron_external_interface: "ens160" neutron_plugin_agent: "openvswitch" nova_compute_virt_type: "qemu" (kolla_ansible_venv3) ubuntu@ubuntu-VM:~$ Additional inputs: There are 3 virtual interfaces on the base Ubuntu22.04 Virtual Machine. ens192->10.170.16.128 with internet, ens224->10.220.0.51 , ens160 up without IP 1. First Interface contain IP address from My organizations DHCP lease from LAN(10.16.16.0) Which has Internet connectivity. ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:0c:29:33:18:3c brd ff:ff:ff:ff:ff:ff altname enp11s0 inet 10.170.16.128/23 brd 10.170.17.255 scope global dynamic noprefixroute ens192 valid_lft 786963sec preferred_lft 786963sec inet6 fe80::cd1a:bc6c:b129:f91f/64 scope link noprefixroute valid_lft forever preferred_lft forever3 2. Interface I have 10.220.0.51 ens224: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:0c:29:33:18:46 brd ff:ff:ff:ff:ff:ff altname enp19s0 inet 10.220.0.51/24 brd 10.220.0.255 scope global noprefixroute ens224 valid_lft forever preferred_lft forever inet 10.220.0.24/32 scope global ens224 valid_lft forever preferred_lft forever inet6 fe80::a8b6:f094:c47:8282/64 scope link noprefixroute valid_lft forever preferred_lft forever 3. ens160 without any IP address which is up and running configured for Kolla neutron_external_interface: "ens160" ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000 link/ether 00:0c:29:33:18:32 brd ff:ff:ff:ff:ff:ff altname enp3s0 1. What networks need to be created additionally ? 2. Bridges and bonds required here or not ? 3. To enable these New VMs to talk to external world( ssh, ping, internet connection to all these VMs ) what all the steps need to be performed or I left out ?

2 1

Re: Use Openstack SDK for Swift
by gtema 27 Feb '24

27 Feb '24

> I didn't see a response to this email so I am re-sending. That's interesting because I responded. My Email client decided by default to respond to a single person dropping discuss, but response to you went out. Anyway, reposting my answer On Thursday, 22 February 2024 12:11:31 CET you wrote: > Hey > > this is a tricky thing explained by a single auth concept: in OpenStack when > you connect to the cloud as a regular user you request certain scope which > normally grants you access to the single domain or the project. Moreover > with this authorization you get list of endpoints you can communicate with > and for Swift this is a project bound endpoint that look somehow like > https:// swift.example.com/v1/AUTH_<project_id>. But the "AUTH_" part may > be actually different since it is part of the swift config. If you are an > admin the situation is a bit different > > In summary that means that you want to do something in the way the API was > not designed for. > > Solutions: > > generally first question you must address is the authorization: is your user > able to access containers of different projects or not. If not you have no > chance and you need to establish new connection with another credentials > When the answer is "yes" you have some options: > > - switch your authorization using > https://opendev.org/openstack/openstacksdk/ > src/branch/master/openstack/cloud/openstackcloud.py#L123. That gives you > new session for a different project that you can use in scope of a certain > project > > - use you single session for pure API calls. This has a disadvantage that > you have raw API communication and need to do lot of tricky things yourself > ``` > conn.get("../AUTH_<another_project_id>/") > ``` > > Unfortunately there is nothing else what could help you, but even with > alternative API wrappers you have the same issue. > > Hope this helps, > Artem > > On Tuesday, 20 February 2024 21:59:19 CET Albert Braden wrote: > > I'm writing a script that will use admin credentials to check user > > projects > > for containers. I'm already doing something similar for non-swift > > accounts, > > doing things like: > > > > cloud.network.networks(project_id=projectid): > > > > I read here about the Object SDK: > > > > https://docs.openstack.org/openstacksdk/latest/user/guides/object_store.ht > > ml > > > > And I tried this: > > > > cloud.object_store.containers(project_id=projectid): > > > > But I get an error: > > > > Invalid query params: project_id > > > > I read the Object SDK document here and it doesn't seem to say anything > > about how to specify a project: > > > > https://docs.openstack.org/openstacksdk/latest/user/proxies/object_store.h > > tm l > > > > But when I read the Swift API document, I see that I can use > > "/v1/{account}/{container}", so I'm guessing that there must be a way to > > do > > it via the SDK. > > > > https://docs.openstack.org/api-ref/object-store/#show-container-details-an > > d-> list-objects > > > > Is it possible to specify the project in an Object SDK call, or do I need > > to use the old python API for this?

2 1

[cinder] This week's meeting will be in video+IRC
by Rajat Dhasmana 27 Feb '24

27 Feb '24

Hello Argonauts, As we keep last meeting of the month in video + IRC mode, this week's meeting (tomorrow) will be held in video + IRC mode with the following details: Date: 28th February, 2024 Time: 1400 UTC Meeting link: https://meet.google.com/xqc-ekpa-dao IRC Channel: #openstack-meeting-alt Make sure you're connected to both the gmeet meeting and IRC. Thanks Rajat Dhasmana

1 0

[Kolla][Ironic] Ironic inspector ignore BareMetal node mac address
by Jayesh5.Chaudhari＠ril.com 27 Feb '24

27 Feb '24

Hi All, I have implemented ironic in my kolla ansible yoga cloud. When I am adding new BareMetal node, it's getting added successfully. But the ironic inspector put the ignore label in the data directory in front of its mac address. I tried to remove it manually, but inspector immediately reverted it. Please help me, how I can proceed from here? Thanks, Jayesh "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s). are confidential and may be privileged. If you are not the intended recipient. you are hereby notified that any review. re-transmission. conversion to hard copy. copying. circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient. please notify the sender immediately by return email. and delete this message and any attachments from your system. Virus Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email. The company cannot accept responsibility for any loss or damage arising from the use of this email or attachment."

2 1