- openstack-discuss - lists.openstack.org

Re: [openstack][sharing][kolla ansible]Problems when 1 of 3 controller was be down
by Matt Crees 24 Apr '23

24 Apr '23

Hi all, It seems worth noting here that there is a fix ongoing in oslo.messaging which will resolve the issues with HA failing when one node is down. See here: https://review.opendev.org/c/openstack/oslo.messaging/+/866617 In the meantime, we have also found that setting kombu_reconnect_delay = 0.5 does resolve this issue. As for why om_enable_rabbitmq_high_availability is currently defaulting to false, as Michal said enabling it in stable releases will impact users. This is because it enables durable queues, and the migration from transient to durable queues is not a seamless procedure. It requires that the state of RabbitMQ is reset and that the OpenStack services which use RabbitMQ are restarted to recreate the queues. I think that there is some merit in changing this default value. But if we did this, we should either add additional support to automate the migration from transient to durable queues, or at the very least provide some decent docs on the manual procedure. However, as classic queue mirroring is deprecated in RabbitMQ (to be removed in RabbitMQ 4.0) we should maybe consider switching to quorum queues soon. Then it may be beneficial to leave the classic queue mirroring + durable queues setup as False by default. This is because the migration between queue types (durable or quorum) can take several hours on larger deployments. So it might be worth making sure the default values only require one migration to quorum queues in the future, rather than two (durable queues now and then quorum queues in the future). We will need to make this switch eventually, but right now RabbitMQ 4.0 does not even have a set release date, so it's not the most urgent change. Cheers, Matt >Hi Michal, > >Feel free to propose change of default in master branch, but I don?t think we can change the default in stable branches without impacting users. > >Best regards, >Michal > >> On 11 Apr 2023, at 15:18, Michal Arbet <michal.arbet(a)ultimum.io> wrote: >> >> Hi, >> >> Btw, why we have such option set to false ? >> Michal Arbet >> Openstack Engineer >> >> Ultimum Technologies a.s. >> Na Po???? 1047/26, 11000 Praha 1 >> Czech Republic >> >> +420 604 228 897 <> >> michal.arbet(a)ultimum.io <mailto:michal.arbet@ultimum.io> >> https://ultimum.io <https://ultimum.io/> >> >> LinkedIn <https://www.linkedin.com/company/ultimum-technologies> | Twitter <https://twitter.com/ultimumtech> | Facebook <https://www.facebook.com/ultimumtechnologies/timeline> >> >> >> ?t 11. 4. 2023 v 14:48 odes?latel Micha? Nasiadka <mnasiadka(a)gmail.com <mailto:mnasiadka@gmail.com>> napsal: >>> Hello, >>> >>> RabbitMQ HA has been backported into stable releases, and it?s documented here: >>> https://docs.openstack.org/kolla-ansible/yoga/reference/message-queues/rabb… >>> >>> Best regards, >>> Michal >>> >>> W dniu wt., 11.04.2023 o 13:32 Nguy?n H?u Kh?i <nguyenhuukhoinw(a)gmail.com <mailto:nguyenhuukhoinw@gmail.com>> napisa?(a): >>>> Yes. >>>> But cluster cannot work properly without it. :( >>>> >>>> On Tue, Apr 11, 2023, 6:18 PM Danny Webb <Danny.Webb(a)thehutgroup.com <mailto:Danny.Webb@thehutgroup.com>> wrote: >>>>> This commit explains why they largely removed HA queue durability: >>>>> >>>>> https://opendev.org/openstack/kolla-ansible/commit/2764844ee2ff9393a4eebd90… >>>>> From: Satish Patel <satish.txt(a)gmail.com <mailto:satish.txt@gmail.com>> >>>>> Sent: 09 April 2023 04:16 >>>>> To: Nguy?n H?u Kh?i <nguyenhuukhoinw(a)gmail.com <mailto:nguyenhuukhoinw@gmail.com>> >>>>> Cc: OpenStack Discuss <openstack-discuss(a)lists.openstack.org <mailto:openstack-discuss@lists.openstack.org>> >>>>> Subject: Re: [openstack][sharing][kolla ansible]Problems when 1 of 3 controller was be down >>>>> >>>>> >>>>> CAUTION: This email originates from outside THG >>>>> >>>>> Are you proposing a solution or just raising an issue? >>>>> >>>>> I did find it strange that kolla-ansible doesn't support HA queue by default. That is a disaster because when one of the nodes goes down it will make the whole rabbitMQ unacceptable. Whenever i deploy kolla i have to add HA policy to make queue HA otherwise you will endup in problem. >>>>> >>>>> On Sat, Apr 8, 2023 at 6:40?AM Nguy?n H?u Kh?i <nguyenhuukhoinw(a)gmail.com <mailto:nguyenhuukhoinw@gmail.com>> wrote: >>>>> Hello everyone. >>>>> >>>>> I want to summary for who meets problems with Openstack when deploy cluster with 3 controller using Kolla Ansible >>>>> >>>>> Scenario: 1 of 3 controller is down >>>>> >>>>> 1. Login horizon and use API such as nova, cinder will be very slow >>>>> >>>>> fix by: >>>>> >>>>> nano: >>>>> kolla-ansible/ansible/roles/heat/templates/heat.conf.j2 >>>>> kolla-ansible/ansible/roles/nova/templates/nova.conf.j2 >>>>> kolla-ansible/ansible/roles/keystone/templates/keystone.conf.j2 >>>>> kolla-ansible/ansible/roles/neutron/templates/neutron.conf.j2 >>>>> kolla-ansible/ansible/roles/cinder/templates/cinder.conf.j2 >>>>> >>>>> or which service need caches >>>>> >>>>> add as below >>>>> >>>>> [cache] >>>>> backend = oslo_cache.memcache_pool >>>>> enabled = True >>>>> memcache_servers = {{ kolla_internal_vip_address }}:{{ memcached_port }} >>>>> memcache_dead_retry = 0.25 >>>>> memcache_socket_timeout = 900 >>>>> >>>>> https://review.opendev.org/c/openstack/kolla-ansible/+/849487 >>>>> >>>>> but it is not the end >>>>> >>>>> 2. Cannot launch instance or mapping block device(stuck at this step) >>>>> >>>>> nano kolla-ansible/ansible/roles/rabbitmq/templates/definitions.json.j2 >>>>> >>>>> "policies":[ >>>>> {"vhost": "/", "name": "ha-all", "pattern": "^(?!(amq\.)|(.*_fanout_)|(reply_)).*", "apply-to": "all", "definition": {"ha-mode":"all"}, "priority":0}{% if project_name == 'outward_rabbitmq' %}, >>>>> {"vhost": "{{ murano_agent_rabbitmq_vhost }}", "name": "ha-all", "pattern": ".*", "apply-to": "all", "definition": {"ha-mode":"all"}, "priority":0} >>>>> {% endif %} >>>>> ] >>>>> >>>>> nano /etc/kollla/global.conf >>>>> >>>>> [oslo_messaging_rabbit] >>>>> kombu_reconnect_delay=0.5 >>>>> >>>>> >>>>> https://bugs.launchpad.net/oslo.messaging/+bug/1993149 >>>>> https://docs.openstack.org/large-scale/journey/configure/rabbitmq.html >>>>> >>>>> I used Xena 13.4 and Yoga 14.8.1. >>>>> >>>>> Above bugs are critical, but I see that it was not fixed. I am just an operator and I want to share what I encountered for new people who come to Openstack >>>>> >>>>> >>>>> Nguyen Huu Khoi >>> -- >>> Micha? Nasiadka >>> mnasiadka(a)gmail.com <mailto:mnasiadka@gmail.com>

6 18

Query about RBAC for subnets
by Aditya Sathish 24 Apr '23

24 Apr '23

Hello, We currently have an external network that is being interfaced from the physical interface of the compute server to an L3 switch with different subnets to different services. These services (and, by extension, the subnets) must be accessed and controlled by the operator to allow a project only a subset of these services. RBAC can only set rules for the network as a whole. Can this network be made external but only share a few subnets with each project? If not the RBAC way, is there another alternative to achieve the same? Regards, Aditya

2 1

[openstack-helm] Manila chart merged
by Vladimir Kozhukalov 24 Apr '23

24 Apr '23

Hi, everyone I would like to announce that last week we eventually merged the PR that adds the Manila chart. Thanks everyone for their contribution. -- Best regards, Kozhukalov Vladimir

1 0

[neutron] Bug Deputy Report April 17 - 23
by Lucas Alvares Gomes 24 Apr '23

24 Apr '23

Hi, This is the Neutron bug report from April 17th to 24th. *High:* * https://bugs.launchpad.net/neutron/+bug/2016704 - Listing ports creates inefficient database query - Assigned to: Ihtisham ul Haq * https://bugs.launchpad.net/neutron/+bug/2017145 - [OVN] - Logging configuration doesn't change after neutron restart - Assigned to: Elvira García Ruiz * https://bugs.launchpad.net/neutron/+bug/2017216 - [ovn-octavia-provider] batch member update generates out of sync with Octavia DB - Assigned to: Fernando Royo *Medium:* * https://bugs.launchpad.net/neutron/+bug/2016414 - Message when creating new neutron bugs has outdated links - Unassigned * https://bugs.launchpad.net/neutron/+bug/2016862 - [ovn-octavia-provider] Admin_state_up ignored on create a new member - Assigned to: Fernando Royo * https://bugs.launchpad.net/neutron/+bug/2017037 - Improve keepalived test pid termination - Assigned to: Miro Tomaska * https://bugs.launchpad.net/neutron/+bug/2017127 - [ovn-octavia-provider] Fix member update according to the Octavia API definition - Assigned to: Fernando Royo *Low:* * https://bugs.launchpad.net/neutron/+bug/2016413 - api-ref: missing documentation for subnet-onboard - Unassigned *Wishlist:* * https://bugs.launchpad.net/neutron/+bug/2016504 - [rfe]Support specify fixed_ip_address for DHCP or Metadata port - Unassigned * https://bugs.launchpad.net/neutron/+bug/2016960 - neutron fwaas support l2 firewall for ovn driver - Unassigned *Needs further triage:* * https://bugs.launchpad.net/neutron/+bug/2017023 - Tempest: remove test duplication for Compute legacy networking API and Neutron API calls - Unassigned * https://bugs.launchpad.net/neutron/+bug/2017131 - neutron-loki job fails tests with ORM session: SQL execution without transaction in progress - Unassigned Cheers, Lucas

1 0

[Networking-vSphere]
by SCAGLIA Emanuele (NPO) 23 Apr '23

23 Apr '23

Hello, I'd like to know if there is in your opinion any chance that the OVSvApp solution works with Openstack zed release. Regarding how to use it, I found this page: https://github.com/nephoscale-div/OVSvAPP Is it still valid? Thank you in advance, Emanuele Scaglia Emanuele Scaglia Senior System Engineer NPO TORINO s.r.l. [cid:image001.png@01D97443.46C8DCE0]<https://www.nposervices.com/> [cid:image002.png@01D97443.46C8DCE0] emanuele.scaglia(a)nposervices.com<mailto:emanuele.scaglia@nposervices.com> [cid:image003.png@01D97443.46C8DCE0] +39 3666180721<tel:3425965928> [cid:image004.png@01D97443.46C8DCE0] Via Vincenzo Lancia 27, 10141 TORINO<https://www.google.com/maps/place/Via+Vincenzo+Lancia,+27,+10141+Torino+TO/…> [cid:image005.png@01D97443.46C8DCE0] nposervices.com<https://www.nposervices.com/> [cid:image006.png@01D97443.46C8DCE0]<https://www.facebook.com/> [cid:image007.png@01D97443.46C8DCE0]<https://www.twitter.com/> [cid:image008.png@01D97443.46C8DCE0]<https://www.linkedin.com/> [cid:image009.png@01D97443.46C8DCE0]<https://www.instagram.com/> [cid:image010.png@01D97443.46C8DCE0]<https://www.youtube.com/> Sede legale: L.go Dora P. Colletta, 81, 10153- Torino Tel. +39 011 19701225 Fax. +39 011 19781413 P. IVA: 10041060012 The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future. AVVERTENZE AI SENSI DEL D.LGS. 196/2003 . Il contenuto di questo messaggio (ed eventuali allegati) e' strettamente confidenziale. L'utilizzo del contenuto del messaggio e' riservato esclusivamente al destinatario. La modifica, distribuzione, copia del messaggio da parte di altri e' severamente proibita. Se non siete i destinatari Vi invitiamo ad informare il mittente ed eliminare tutte le copie del suddetto messaggio. The contents of this message (and all attachments) are strictly confidential. The message is intended exclusively to the addressee. The modification, distribution, or replication of the message from others is strictly forbidden. If you are not the intended addressee, please notify the sender and eliminate all the copies of the message,

2 1

[tc][all] Technical Committee Weekly Summary - April 22, 2023
by Nikolla, Kristi 22 Apr '23

22 Apr '23

Hi all, Here’s another edition of “What’s happening on the Technical Committee.” Meeting ======= The Technical Committee met on April 18, 2023 on the #openstack-tc channel on OFTC IRC. The meeting was chaired by Jay Faulkner. Thanks Jay! The next meeting will be held on April 25, 2023 at 18:00UTC. For more information visit https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting Happenings ========== Leaderless projects ------------------- There's only 3 projects now remaining without a leader[0]. Monasca[1], Vitrage[2] and Winstackers[3]. We're actively looking for people with the time and desire to maintain these projects. A retirement of Winstackers would cause Windows (and Hyper-V) host support to be removed. Meanwhile, TripleO has switched to a distributed project leadership model, and is initiating the process of deprecation.[4] [0]. https://etherpad.opendev.org/p/2023.2-leaderless [1]. https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033112.h… [2]. https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033348.h… [3]. https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033342.h… [4]. https://review.opendev.org/c/openstack/governance/+/877132 Issues with docs since 2023.1 release ------------------------------------- 2023.1 is the first release that uses numeric versioning, rather than the old naming scheme. This confuses our docs build process, which produces incorrect results. For one example the Administrator Guides list for Zed lists all the projects correctly[0], but the one for 2023.1 is empty[1]. Please use the Etherpad [2] to report issues, and the same Etherpad for tracking work. We're looking for help in getting this resolved quickly. [0]. https://docs.openstack.org/zed/admin/index.html [1]. https://docs.openstack.org/2023.1.antelope/admin/index.html [2]. https://etherpad.opendev.org/p/docs-issues-2023 Weekly Gate Health Report ------------------------- The gate continues to experience failures regarding volume detach tests[0]. There's also some issues with Ironic grenade jobs. Helping out with CI is an amazing way to get involved in the community, reach out to the TC (see below how) to know more! [0]. https://meetings.opendev.org/meetings/tc/2023/tc.2023-04-18-18.00.log.html#… Changes ======= Merged Appoint Tim Burke as Swift PTL (formal-vote) | https://review.opendev.org/c/openstack/governance/+/878286 TripleO: switch to distributed project leadership (formal-vote) | https://review.opendev.org/c/openstack/governance/+/878799 Appoint Andriy Kurilin as Rally PTL (formal-vote) | https://review.opendev.org/c/openstack/governance/+/878065 Add missing governance-sigs repo in technical-committee-repos.yaml (project-update) | https://review.opendev.org/c/openstack/governance/+/880237 Consider release version as string in projects data (code-change) | https://review.opendev.org/c/openstack/governance/+/877143 New Open Update to hacking v6 (code-change) | https://review.opendev.org/c/openstack/governance/+/881266 Switch to 2023.2 testing runtime py version (code-change) | https://review.opendev.org/c/openstack/governance/+/881137 Abandoned Switch project and OpenStack versions in releases (formal-vote) | https://review.opendev.org/c/openstack/governance/+/875942 All Open https://review.opendev.org/q/project:openstack/governance+status:open How to contact the TC ===================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send an email with the tag [tc] on the openstack-discuss mailing list. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 16:00 UTC 3. IRC: Ping us using the 'tc-members' keyword on the #openstack-tc IRC channel on OFTC.

1 0

[nova]qemu-guest-agent Used in openstack
by 啧啧啧 20 Apr '23

20 Apr '23

Hi, We discovered the use of qemu-guest-agent in openstack,Set hw_qemu_guest_agent=yes to the metadata parameter on the image. https://docs.openstack.org/mitaka/config-reference/compute/hypervisor-kvm.h… Meanwhile, the application of qemu-guest-agent in cloud scenarios is investigated. It is found that Qemu-guest-Agent can be used for guest os performance monitoring, snapshot backup, and guest OS-level failover. But these things can be done in openstack with prometheus and  instance backup,There may be some differences between them. Sorry, I am not familiar with how hw_qemu_guest_agent is used in openstack, and I do not know the operations that can be performed on guest os in openstack by configuring hw_qemu_guest_agent. Only through qemu official know some of the effects.I want to clarify the use of hw_qemu_guest_agent. Other components of openstack, such as the prometheus service, can be used instead.

2 2

[qa][all] New hacking 6.0.0 is available
by Ghanshyam Mann 20 Apr '23

20 Apr '23

Hello Everyone, Hacking 6.0.0 is available to use now which includes flake8 5.0 changes. There are no other changes than bumping flake8 version to 5.0.1, you can refer to the changes done in flake8 5.0.0 (or 5.0.1) directly in flake8 release notes - https://flake8.pycqa.org/en/latest/release-notes/5.0.0.html Note: hacking is pinned in test-requirements.txt (for almost all the repo), do not forget to bump the version there while moving your code to new hacking. -gmann

1 0

[Glance] Bobcat PTG summary
by Abhishek Kekane 20 Apr '23

20 Apr '23

Hi Team, We had our seventh virtual PTG between 27th March to 31st March 2023. Thanks to everyone who joined the virtual PTG sessions. Using bluejeans app we had lots of discussion around different topics for glance, glance + cinder, fips and Secure RBAC. You can find the topics discussed in etherpad [1] with Notes from the session and which also includes the recordings of each discussion. Here I am going to highlight a few important topics which we are going to target this cycle. # Glance Image Direct URL access - OSSN-0090 This is the most important and high priority work item for us in this cycle. We are going to move the spec to the current cycle and implement glance, client and osc side work this cycle. We are also going to implement tempest side work for the same. Once it is completed, Rajat (current cinder PTL) is going to write consumer side spec for nova and cinder. https://bluejeans.com/s/dKF1IG2h8PC chapter 2 (from 22 minutes onward) # Bridge gap between Glance client and OSC Last cycle we have prepared the list of missing commands [2] and started submitting patches to implement the same. Our biggest hurdle at the moment is lack of reviews from the osc team (which has only one/two cores). Glance PTL is going to communicate with TC/existing core(s) of OSC whether they can add any glance core to the team so that we can prioritize our work and get reviews immediately. This cycle we are planning to complete this work. Recording: https://bluejeans.com/s/XZoRGceEhW3/ - Chapter 4 # Default glance to configure multistore Efforts has been started from last cycle but this work needs to be divided in small parts such as removing unnecessary tests, migrating existing tests to support multistore and so on. This cycle we are going to ensure that existing tests are supporting multistore configs. Recording: https://bluejeans.com/s/XZoRGceEhW3/ - Chapter 3 # Secure RBAC So far we are good with the goals decided by the community. This cycle PTL is going to discuss with the QE/TC team regarding deprecation of policies (migrating policies to use manager role) and decide further action. Recording: https://bluejeans.com/s/RHgqQi28_Hk/ - chapter 1 # Fips Overview ade_lee is going to submit some patches for us and we are going to help him in debugging failures if there are any. Recording: https://bluejeans.com/s/RHgqQi28_Hk/ - chapter 5 # Native Image encryption Finally the Barbican work is complete and we can move ahead with glance side work in this cycle. We need to move glance side spec to Bobcat and check whether there will be any changes in the implementation. Luzi is going to work on glance changes and the team is going to assist her in reviews and testing. Recording: https://bluejeans.com/s/RHgqQi28_Hk/ - chapter 3 # RBD deferred deletion Eric from cinder team is working on PoC/code for glance-store side changes for the same. Once we have PoC ready, the glance team will assist him to create a detailed spec and start working on tests for the same. https://bluejeans.com/s/dKF1IG2h8PC - chapter 2 Apart from above topics you can find other miscellaneous topics discussed in PTG etherpad [1] along with milestone wise priorities at the end. If you have any questions/suggestions then please join us in our weekly meeting (each Thursday #openstack-meeting irc channel at 1400 UTC). [1] https://etherpad.opendev.org/p/glance-bobcat-ptg [2] https://docs.google.com/spreadsheets/d/1tlipscCDeWmYGz3Hfp74czPW7BBJb4ST84q… Thanks and Regards, Abhishek Kekane

5 10

[cinder] festival of feature reviews 21 April 2023
by Rajat Dhasmana 20 Apr '23

20 Apr '23

Hello Argonauts, We will be having our monthly festival of reviews tomorrow i.e. 21st April (Friday) from 1400-1600 UTC. Our priorities for M-1 are DB changes for compatibility with sqlalchemy 2.0 and cinder-specs. Following are some additional details: Date: 21st April, 2023 Time: 1400-1600 UTC Meeting link: will be shared before meeting etherpad: https://etherpad.opendev.org/p/cinder-festival-of-reviews See you there! Thanks Rajat Dhasmana

1 0

[blazar] Meeting cancelled today
by Pierre Riteau 20 Apr '23

20 Apr '23

Hello, I won't be able to run the Blazar IRC meeting today. Let's skip this one. Thanks, Pierre Riteau (priteau)

1 0

[neutron] Neutron drivers meeting
by Rodolfo Alonso Hernandez 20 Apr '23

20 Apr '23

Hello Neutrinos: Please remember tomorrow we have the drivers meeting at 14UTC. The agenda is here [1]. We have, so far, a couple of topics to discuss. See you tomorrow. [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

1 0

[nova]qemu-guest-agent Used in openstack
by 任亮 20 Apr '23

20 Apr '23

Hi, We discovered the use of qemu-guest-agent in openstack,Set hw_qemu_guest_agent=yes to the metadata parameter on the image. https://docs.openstack.org/mitaka/config-reference/compute/hypervisor-kvm.h… Meanwhile, the application of qemu-guest-agent in cloud scenarios is investigated. It is found that Qemu-guest-Agent can be used for guest os performance monitoring, snapshot backup, and guest OS-level failover. But these things can be done in openstack with prometheus and cinder-backup,There may be some differences between them, Sorry, I am not familiar with how hw_qemu_guest_agent is used in openstack, and I do not know the operations that can be performed on guest os in openstack by configuring hw_qemu_guest_agent. Only through qemu official know some of the effects.I want to clarify the use of hw_qemu_guest_agent. Other components of openstack, such as the prometheus service, can be used instead.

1 0

[security-sig] Ask base recommendation for handling vulnerability which affects both OpenStack code and vendor code
by Vanou Ishii (Fujitsu) 19 Apr '23

19 Apr '23

Hi OpenStack community, I’m working on OpenStack project under my employee company. In OpenStack, few of projects (e.g. Cinder and Ironic) uses vendor supplied library in it. This means vendor-neutral base code of project is hosted under OpenStack project repository but vendor hardware specific logic is delegated to vendor library which is called by base code and is maintained by each hardware vendor under their repository. In the past, I faced situation to handle vulnerability in which cause of vulnerability is in vendor library but, to handle vulnerability, both OpenStack code and vendor library code should be modified. To handle this, I consulted community member and asked them to coordinate to fix vulnerability in private way (i.e. review patch and prepare commit in not public but private as usual security handling manner). However member are not willing to working on together because cause of vulnerability is in vendor provided library. I felt it’s better for community to, at least, be open to working on such vulnerability because that policy may benefit community. So I think it’s better to include policy in VMT document[1] like “Community is encouraged to make effort to be open to handling vulnerability in which both OpenStack community code and vendor provided code should be modified”. How do you think about this? Regards, Vanou Ishii [1] https://security.openstack.org/vmt-process.html

3 4

[neutron] questions about bond and port ip
by 韩光宇 19 Apr '23

19 Apr '23

Hello, I have a victoria cluster. I am a bit perplexed about OpenStack networking and was wondering if you could enlighten me on the topic. 1. bond When configuring bond interfaces (bond0/1/2/3) in an OpenStack instance, can I follow the same steps as I would on a physical machine? Are there any particular considerations to keep in mind? Also, when it comes to switch configuration, do I configure virtual machine switches directly or are there specific OpenStack interfaces to use? 2. `openstack port create --network net1 --no-fixed-ip port_net1` I was able to obtain a port with an ip_allocation value of "none" using the above command. I noticed that the ip_allocation value can be set to "none", "deferred", or "immediate". Is there a CLI interface to modify the ip_allocation value of a port, for example, changing "none" to "deferred"? Alternatively, what is the recommended method to make this change? 3. Is it possible for users to set IP addresses within an instance system? For example, if I create an instance without an IP address, is there a mechanism that allows me to set an IP address within the instance system, or can I only modify the port bindings or switch ports externally to change the IP address of an instance? Thank you for your attention to this matter. Best regards, Han Guangyu

3 2

Re: openstack-discuss Digest, Vol 54, Issue 85
by Kristin Barrientos 19 Apr '23

19 Apr '23

Hi everyone, There seems to have been an error regarding the time for the next Large Scale SIG meeting. It was supposed to be 14 UTC, not 15 UTC. Is there anyone that is able to join the meeting now? So sorry about that. Please join now if you can! Thanks, Kristin Barrientos Marketing Coordinator OpenInfra Foundation > On Apr 17, 2023, at 7:00 AM, openstack-discuss-request(a)lists.openstack.org wrote: > > Send openstack-discuss mailing list submissions to > openstack-discuss(a)lists.openstack.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss > > or, via email, send a message with subject or body 'help' to > openstack-discuss-request(a)lists.openstack.org > > You can reach the person managing the list at > openstack-discuss-owner(a)lists.openstack.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of openstack-discuss digest..." > > > Today's Topics: > > 1. [largescale-sig] Next meeting: April 19, 15utc (Thierry Carrez) > 2. Re: [largescale-sig] Next meeting: April 19, 15utc > (Thierry Carrez) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 17 Apr 2023 13:14:19 +0200 > From: Thierry Carrez <thierry(a)openstack.org> > To: "openstack-discuss(a)lists.openstack.org" > <openstack-discuss(a)lists.openstack.org> > Subject: [largescale-sig] Next meeting: April 19, 15utc > Message-ID: <25b05623-92e2-f01e-70c3-5aac26a4f256(a)openstack.org> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hi everyone, > > The Large Scale SIG will be meeting this Wednesday in > #openstack-operators on OFTC IRC, at 15UTC, our EU+US-friendly time. > > You can doublecheck how that UTC time translates locally at: > https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230322T14 > > Feel free to add topics to the agenda: > https://etherpad.opendev.org/p/large-scale-sig-meeting > > Regards, > > -- > Thierry Carrez > > > > ------------------------------ > > Message: 2 > Date: Mon, 17 Apr 2023 13:15:26 +0200 > From: Thierry Carrez <thierry(a)openstack.org> > To: "openstack-discuss(a)lists.openstack.org" > <openstack-discuss(a)lists.openstack.org> > Subject: Re: [largescale-sig] Next meeting: April 19, 15utc > Message-ID: <90db3bfb-b6b4-c0ef-6b9f-8593c7dcc324(a)openstack.org> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Thierry Carrez wrote: >> You can doublecheck how that UTC time translates locally at: >> https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230322T14 > > Wrong URL, try out this one instead: > https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230419T15 > > Sorry about that. > > -- > Thierry] > > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > openstack-discuss mailing list > openstack-discuss(a)lists.openstack.org > > > ------------------------------ > > End of openstack-discuss Digest, Vol 54, Issue 85 > *************************************************

1 0

[kolla-ansible] bootstrap-server docker version question
by Satish Patel 19 Apr '23

19 Apr '23

Folks, Playing with kolla and i decided to use docker.io installation (ubuntu 20.04) on controller nodes but when i run bootstrap-server it removed docker.io and installed docker-ce version. Question: What is the best docker version to run in production for operator point of view and better support and stability. docker.io maintained by debian community and native support with Ubuntu distro. docker-ce is maintained by the docker community which has better features etc but rapid growth but does that matter for kolla? Just curious, what if I add compute nodes in an existing cluster after many months? In that case the docker-ce version will be changed. How to maintain or pin docker-ce version? ~S

5 10

[cinder] Bug Report | Bugs from 2023-04-12 to 2023-04-19
by Sofia Enriquez 19 Apr '23

19 Apr '23

Hello Argonauts, I've recently updated a personal script <https://github.com/enriquetaso/launchpad-bug-reporter> I've been using to fetch bugs from Launchpad. I wanted to share it with you all in case anyone has ideas on how to make it better or wants to contribute to the project. Your suggestions and input would be super valuable! *Medium* - Dell Compellent:- DSM is unable to fetch WWNs from mapping personality objects which are stored with lowercase letters in SC. <https://bugs.launchpad.net/cinder/+bug/2016840> - *Status*: The bug report says *In Progress *but I couldn't find any patch on Gerrit. - NVMe-oF connector doesn't create the hostid <https://bugs.launchpad.net/os-brick/+bug/2016029> - Status: Fix proposed to branch: master <https://review.opendev.org/c/openstack/os-brick/+/880222>. - [rbac] list, show and show_default volume type command response does not contain "os-volume-type-access:is_public" property when using reader user <https://bugs.launchpad.net/cinder/+bug/2016402> - *Status*: The reporter updated the bug report with references to the Tempest test. *Incomplete* - Cleanup of backups fails for non-existing volume <https://bugs.launchpad.net/cinder/+bug/2016138>. - *Status*: Waiting on reporter update. Cheers, -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

Survey Invitation on Code Snippets in Code Reviews
by Beiqi Zhang 18 Apr '23

18 Apr '23

Dear OpenStack Contributors, In the code review process, reviewers and developers engage in asynchronous online discussions to exchange information with each other, aiming at promoting the acceptence of proposed code changes. During the discussions, code snippets might be served as a way to meet the information needs of reviewers or developers (e.g., reviewers may make a suggestion by providing code snippet). However, little is known about the practices of providing code snippets in code reviews (e.g., what is the intention behind providing code snippet). To this end, we plan to conduct this survey to gain knowledge and experience from the perspective of developers in industry. We would greatly appreciate your help with our research by filling out the questionnaire below: Our questionnaire contains 4 close-ended questions and 2 open-ended questions, which may take about 3-5 minutes. The link of the questionnaire (hosted at Google Forms): https://forms.gle/nrLaZXQUq4QMS3bu6 Thank you very much for your participation! Best regards, Beiqi Zhang (on Behalf of the Team) Wuhan University, China

1 0

RDO Antelope Released
by Amy Marrich 18 Apr '23

18 Apr '23

The RDO community is pleased to announce the general availability of the RDO build for OpenStack 2023.1 Antelope for RPM-based distributions, CentOS Stream and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds. Antelope is the 27th release from the OpenStack project, which is the work of more than 1,000 contributors from around the world. The release is already available for CentOS Stream 9 on the CentOS mirror network in: http://mirror.stream.centos.org/SIGs/9-stream/cloud/x86_64/openstack-antelo… The RDO community project curates, packages, builds, tests and maintains a complete OpenStack component set for RHEL and CentOS Stream and is a member of the CentOS Cloud Infrastructure SIG. The Cloud Infrastructure SIG focuses on delivering a great user experience for CentOS users looking to build and maintain their own on-premise, public or hybrid clouds. All work on RDO and on the downstream release, Red Hat OpenStack Platform, is 100% open source, with all code changes going upstream first. The highlights of the broader upstream OpenStack project may be read via https://releases.openstack.org/antelope/highlights.html but here are some highlights: - The continuation of SRBAC and FIPS to make OpenStack a more secure platform across various services, along with additional support in images. - Additional drivers and features for Block Storage to support more technologies from vendors such as Dell, Hitachi and NetApp, among others. - DNS Zones that can now be shared with other tenants (projects) allowing them to create and manage recordsets within the Zone. - Networking port forwarding was added to the dashboard for Floating IPs. - Additional networking features to support OVN. - Compute now allows PCI devices to be scheduled via the Placement API and power consumption can be managed for dedicated CPUs. - Load balancing now allows users to enable cpu-pinning. - Community testing of compatibility between non-adjacent upstream versions. OpenStack Antelope is the first release marked as Skip Level Upgrade Release Process or SLURP. According to this model ( https://governance.openstack.org/tc/resolutions/20220210-release-cadence-ad…) this means that upgrades will be supported between these (SLURP) releases, in addition to between adjacent major releases. *TripleO removal in the RDO Antelope release:* During the Antelope cycle, The TripleO team communicated the decision of abandoning the development of the project and deprecating the master branches. According to that upstream decision, TripleO packages have been removed from the RDO distribution and will not be included in the Antelope release. *Contributors* During the Zed cycle, we saw the following new RDO contributors: - Adrian Fusco Arnejo - Bhagyashri Shewale - Eduardo Olivares - Elvira Garcia Ruiz - Enrique Vallespí - Jason Paroly - Juan Badia Payno - Karthik Sundaravel - Roberto Alfieri - Tom Weininger Welcome to all of you and Thank You So Much for participating! But we wouldn’t want to overlook anyone. A super massive Thank You to all *52* contributors who participated in producing this release. This list includes commits to rdo-packages, rdo-infra, and rdo-website repositories: - Adrian Fusco Arnejo - Alan Pevec - Alfredo Moralejo Alonso - Amol Kahat - Amy Marrich - Ananya Banerjee - Artom Lifshitz - Arx Cruz - Bhagyashri Shewale - Cédric Jeanneret - Chandan Kumar - Daniel Pawlik - Dariusz Smigiel - Dmitry Tantsur - Douglas Viroel - Eduardo Olivares - Elvira Garcia Ruiz - Emma Foley - Eric Harney - Enrique Vallespí - Fabien Boucher - Harald Jensas - Jakob Meng - Jason Paroly - Jesse Pretorius - Jiří Podivín - Joel Capitao - Juan Badia Payno - Julia Kreger - Karolina Kula - Karthik Sundaravel - Leif Madsen - Luigi Toscano - Luis Tomas Bolivar - Marios Andreou - Martin Kopec - Matthias Runge - Matthieu Huin - Nicolas Hicher - Pooja Jadhav - Rabi Mishra - Riccardo Pittau - Roberto Alfieri - Ronelle Landy - Sandeep Yadav - Sean Mooney - Slawomir Kaplonski - Steve Baker - Takashi Kajinami - Tobias Urdin - Tom Weininger - Yatin Karel *The Next Release Cycle* At the end of one release, focus shifts immediately to the next release i.e Bobcat. *Get Started* To spin up a proof of concept cloud, quickly, and on limited hardware, try an All-In-One Packstack installation. You can run RDO on a single node to get a feel for how it works. Finally, for those that don’t have any hardware or physical resources, there’s the OpenStack Global Passport Program. This is a collaborative effort between OpenStack public cloud providers to let you experience the freedom, performance and interoperability of open source infrastructure. You can quickly and easily gain access to OpenStack infrastructure via trial programs from participating OpenStack public cloud providers around the world. *Get Help* The RDO Project has our users(a)lists.rdoproject.org for RDO-specific users and operators. For more developer-oriented content we recommend joining the dev(a)lists.rdoproject.org mailing list. Remember to post a brief introduction about yourself and your RDO story. The mailing lists archives are all available at https://mail.rdoproject.org. You can also find extensive documentation on RDOproject.org. The #rdo channel on OFTC IRC is also an excellent place to find and give help. We also welcome comments and requests on the CentOS devel mailing list and the CentOS IRC channels (#centos, #centos-cloud, and #centos-devel in Libera.Chat network), however we have a more focused audience within the RDO venues. *Get Involved* To get involved in the OpenStack RPM packaging effort, check out the RDO contribute pages, peruse the CentOS Cloud SIG page, and inhale the RDO packaging documentation. Join us in #rdo on the OFTC IRC network and follow us on Twitter @RDOCommunity. You can also find us on Facebook and YouTube.

1 0

[Horizon]: allow user to access calendar on horizon
by James Leong 18 Apr '23

18 Apr '23

Hi all, I am using kolla-ansible for OpenStack deployment in the yoga version. Is it possible to allow the user (member role) to view the calendar graph under the reservation tab (lease)? Currently, only the admin will be able to view the calendar graph with all the reserved leases. However, a user with other roles cannot load the calendar information. On the dashboard, I saw it displayed " Unable to load reservations." When I look into the log file, I get the below error message. "blazarclient.exception.BlazarClientException: ERROR: Policy doesn't allow blazar:oshosts:get to be performed." Is there a way to allow the policy? Thanks for your help. James

2 2

[kolla][kolla-ansible] Kolla-Ansible mirror update and kolla images
by Nguyễn Hữu Khôi 18 Apr '23

18 Apr '23

Hello. I have a question. I use kolla-ansible 13.0.0 and kolla 13.0.0 images then I upgrade kolla-ansible to 13.8.0. I will use kolla 13.8.0 to build new images? Thank you. Regards Nguyen Huu Khoi

3 4

[neutron] Bug deputy April 10-16th
by Rodolfo Alonso Hernandez 18 Apr '23

18 Apr '23

Hello Neutrinos: This is the bug list from the last week: High: * https://bugs.launchpad.net/neutron/+bug/2015847: Functional job db missconfiguration. Assigned to Rodolfo. * https://bugs.launchpad.net/neutron/+bug/2016142: [sqlalchemy-20] Error in "get_ports_on_host_by_subnet" execution. Fixed. * https://bugs.launchpad.net/neutron/+bug/2016266: [Secure RBAC] Get availability zone API should be available for READER role. Assigned to Slawek. Patch proposed: https://review.opendev.org/c/openstack/neutron/+/880461 Medium: * https://bugs.launchpad.net/neutron/+bug/2016198: [L3][HA] race condition between first two router creations when tenant has no HA network. Related to https://bugs.launchpad.net/neutron/+bug/2016197. Not assigned. Low: * https://bugs.launchpad.net/neutron/+bug/2015844: Remove netifaces dependency from neutron. To be discussed during the Neutron meeting. * https://bugs.launchpad.net/neutron/+bug/1988039: ovs idl not monitor tables after reconnect. Patch proposed: https://review.opendev.org/c/openstack/neutron/+/857010 * https://bugs.launchpad.net/neutron/+bug/2016413: api-ref: missing documentation for subnet-onboard. Not assigned. Whislist: * https://bugs.launchpad.net/neutron/+bug/2016158: [OVN] How to deal with SB "Chassis"/"Chassis_Private" duplicated registers. Assigned to Rodolfo. * https://bugs.launchpad.net/neutron/+bug/2016197: [Open Discussion] neutron can create port from network which has no subnet. Not assigned (maybe it won’t be necessary). Regards.

1 0

[zun][zun_api][blazar][config][yoga][kolla-ansible] Adding more configuration to config file
by James Leong 18 Apr '23

18 Apr '23

Hi all, I am playing around with Zun. I have used kolla-ansible as a deployment tool for deploying the yoga version of OpenStack. I am trying to add an option to the configuration file. However, those added options are not recognized by OpenStack when being called. For instance, Zun.conf, I am adding a new database (blazar) information to it so I can access blazar information in the zun service. Would that be possible to allow the zun_api container to access the blazar database? Thanks for your help, James

3 2

Re: [all][stable][ptl] Propose to EOL Rocky series
by Elõd Illés 17 Apr '23

17 Apr '23

Hi, thanks for all the feedbacks from teams so far! @Zigo: Extended Maintenance process was created just for the same situation: to give space to interested parties to cooperate and keep things maintained even when stable releases are over their 'supported' lifetime. So it's good to see that there is interest in it! Unfortunately, with very old branches we've reached the state where gates can't be maintained and without a functional gate it's not safe to merge patches (yes, even security fixes) and they are just using resources (CI & maintainers' time). When gate is broken in such extent, then i think the community have to accept that it is not possible to merge patches confidently and needs to EOL that release. (Yes, it means that some vendors still have to do it for their own sake, testing it by their own, etc). Keeping things open in such state gives the false signal to vendors that 'it is maintained' however this is done without fully testing the changes. Another aspect is that code cannot be cleaned up until those old branches are still present (CI jobs, project configurations, etc) which gives pain for developers. So, however some vendors would appreciate probably to keep things open forever, for the community this is not beneficial and doable I think. Seeing that teams want to EOL their old branches is a proof that this is needed (unfortunately). Thanks, Előd Illés irc: elodilles @ #openstack-stable / #openstack-release ________________________________ From: Thomas Goirand <thomas(a)goirand.fr> Sent: Saturday, January 28, 2023 2:25 PM Cc: openstack-discuss(a)lists.openstack.org <openstack-discuss(a)lists.openstack.org> Subject: Re: [all][stable][ptl] Propose to EOL Rocky series Hi, I understand the gate is broken, however, Rocky is in Debian LTS, and I would like to keep the possibility to merge patches, even with the gate tests disabled. CVE-2022-47951 is an example why this is important... Thomas Goirand (zigo) On Jan 28, 2023 11:54, Radosław Piliszek <radoslaw.piliszek(a)gmail.com> wrote: > > Masakari is happy to EOL Rocky too. > > Radek > -yoctozepto > > On Fri, 27 Jan 2023 at 20:59, Jay Faulkner <jay(a)gr-oss.io> wrote: > > > > Thanks for doing all this cleanup work Elod. Ironic is OK with retirements of these shared resources up to Train. > > > > - > > Jay Faulkner > > > > On Fri, Jan 27, 2023 at 10:12 AM Elõd Illés <elod.illes(a)est.tech> wrote: > >> > >> Hi, > >> > >> Similarly like the Queens branch EOL proposal [1] I would like to propose > >> to transition every project's stable/rocky to End of Life: > >> > >> - gates are mostly broken > >> - minimal number of activity can be seen on this branch > >> - some core projects already transitioned their stable/rocky to EOL > >> recently (like ironic, neutron, nova) > >> - gate job definitions are still using the old, legacy zuul syntax > >> - gate jobs are based on Ubuntu Xenial, which is also beyond its public > >> maintenance window date and hard to maintain > >> > >> Based on the above, if there won't be any project who wants to keep open > >> their stable/rocky, then I'll start the process of EOL'ing Rocky stable > >> series as a whole. If anyone has any objection then please respond to > >> this mail. > >> > >> Thanks, > >> > >> Előd Illés > >> irc: elodilles @ #openstack-stable / #openstack-release > >> > >> [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-October/031030… > >> >

3 4