April 2023 - openstack-discuss - lists.openstack.org

[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) 20 Apr '23

20 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 19 Apr '23

19 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