August 2022 - openstack-discuss - lists.openstack.org

[all][tc] 2023.1 Antelope TC-PTG Planning
by Ghanshyam Mann 20 Oct '22

20 Oct '22

Hello Everyone, As you already know that the 2023.1 cycle virtual PTG will be held between Oct 17th - 21[1]. I have started the preparation for the Technical Committee PTG sessions. Please do the following: 1. Fill the below poll as per your availability. - https://framadate.org/yi8LNQaph5wrirks 2. Add the topics you would like to discuss to the below etherpad. - https://etherpad.opendev.org/p/tc-2023-1-ptg NOTE: this is not limited to TC members only; I would like all community members to fill the doodle poll and, add the topics you would like or want TC members to discuss in PTG. [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030041.… -gmann

2 4

[Ceilometer] Pollster cannot get RadosGW metrics when API endpoints are based on URL instead of port number
by Taltavull Jean-François 10 Oct '22

10 Oct '22

Hi All, In our OpenStack deployment, API endpoints are defined by using URLs instead of port numbers and HAProxy forwards requests to the right bakend after having ACLed the URL. In the case of our object-store service, based on RadosGW, the internal API endpoint is "https://<FQDN>/object-store/swift/v1/AUTH_<tenant_id>" When Ceilometer RadosGW pollster tries to connect to the RadosGW admin API with the object-store internal endpoint, the URL becomes https://<FQDN>/admin, as shown by HAProxy logs. This URL does not match any API endpoint from HAProxy point of view. The line of code that rewrites the URL is this one: https://opendev.org/openstack/ceilometer/src/branch/stable/wallaby/ceilomet… What would you think of adding a mechanism based on new Ceilometer configuration option(s) to control the URL rewriting ? Our deployment characteristics: - OpenStack release: Wallaby - Ceph and RadosGW version: 15.2.16 - deployment tool: OSA 23.2.1 and ceph-ansible Best regards, Jean-Francois

2 23

[ptg][edge]OpenStack at the Edge discussions
by Ildiko Vancsa 26 Sep '22

26 Sep '22

Hi, I’m reaching out to you in preparation to the upcoming PTG. The Edge Computing Group already started to prepare for the event and OpenStack came up during our conversations to have cross-project discussions with. The number of edge computing use cases in production is growing and OpenStack is a key infrastructure building block. Some edge related discussions regarding the project came up at previous PTGs and it would be great to continue and extend them. We covered areas in networking and looked into storage a little bit, and the question of finding a central place to store edge related documentation also came up. To identify new topics and follow up on ones we already started to discuss I added an OpenStack section to the Edge WG’s planning etherpad: https://etherpad.opendev.org/p/ecg-ptg-october-2022 If you are working on related features, have requirements or case studies to share, please add them to the above etherpad, so we can discuss them at the PTG and identify areas we can work together on to solve challenges and share information about exiting solutions. Please let me know if you have any questions or comments. Thanks, Ildikó

1 1

Cinder-volume active active setup
by Eugen Block 22 Sep '22

22 Sep '22

Hi, I didn't mean to hijack the other thread so I'll start a new one. There are some pages I found incl. Gorkas article [1], but I don't really understand yet how to configure it. We don't use any of the automated deployments (we created our own) like TripleO etc., is there any guide showing how to setup cinder-volume active/active? I see in my lab environment that python3-tooz is already installed on the control node, but how do I use it? Besides the "cluster" config option in the cinder.conf (is that defined when setting up the DLM?) what else is required? I also found this thread [2] pointing to the source code, but that doesn't really help me at this point. Any pointers to a how-to or deployment guide would be highly appreciated! Thanks, Eugen [1] https://gorka.eguileor.com/a-cinder-road-to-activeactive-ha/ [2] https://www.mail-archive.com/openstack@lists.openstack.org/msg18385.html

2 5

[all] Deprecated Zuul queue syntax
by Clark Boylan 16 Sep '22

16 Sep '22

Hello, Zuul deprecated declaring shared queues at a pipeline level with release 4.1.0 [0]. Zuul's current plan is to stop accepting this form of configuration with a future 7.0.0 release. More details on what needs to change can be found in Zuul's reminder notice on the Zuul mailing list [1]. I expect we have about a month before the v7 release which should give us plenty of time to fix this. If we don't fix this before the v7 release the expected fallout will be that these project branches will not have any pipelines defined, which means no Zuul jobs will run against that project branch until the configs are updated. I've marked this for everyone because 98 repositories are affected, and I'm not sure listing them all in the subject would be productive. Here is the list of affected repos: openstack/adjutant openstack/ansible-collection-kolla openstack/ansible-role-collect-logs openstack/ansible-role-tripleo-modify-image openstack/barbican openstack/barbican-tempest-plugin openstack/barbican-ui openstack/blazar openstack/blazar-tempest-plugin openstack/ceilometer openstack/cinderlib openstack/cloudkitty openstack/cloudkitty-tempest-plugin openstack/cyborg-tempest-plugin openstack/designate openstack/designate-dashboard openstack/designate-tempest-plugin openstack/devstack-gate openstack/ec2-api openstack/ec2api-tempest-plugin openstack/freezer openstack/freezer-tempest-plugin openstack/heat openstack/heat-dashboard openstack/heat-tempest-plugin openstack/horizon openstack/ironic openstack/ironic-inspector openstack/ironic-lib openstack/ironic-prometheus-exporter openstack/ironic-python-agent openstack/ironic-tempest-plugin openstack/kayobe openstack/kayobe-config openstack/kayobe-config-dev openstack/kolla openstack/kolla-ansible openstack/kuryr openstack/magnum openstack/magnum-tempest-plugin openstack/manila openstack/manila-tempest-plugin openstack/masakari openstack/masakari-monitors openstack/mistral openstack/mistral-tempest-plugin openstack/monasca-api openstack/monasca-common openstack/monasca-events-api openstack/monasca-log-api openstack/monasca-tempest-plugin openstack/murano openstack/murano-tempest-plugin openstack/networking-generic-switch openstack/octavia openstack/octavia-tempest-plugin openstack/openstack-chef openstack/os-net-config openstack/os-win openstack/oswin-tempest-plugin openstack/paunch openstack/project-config openstack/puppet-pacemaker openstack/puppet-tripleo openstack/python-designateclient openstack/python-ironicclient openstack/python-saharaclient openstack/python-tripleoclient openstack/python-troveclient openstack/sahara openstack/sahara-tests openstack/senlin openstack/senlin-tempest-plugin openstack/solum openstack/solum-tempest-plugin openstack/telemetry-tempest-plugin openstack/tenks openstack/tripleo-ci openstack/tripleo-ci-health-queries openstack/tripleo-common openstack/tripleo-heat-templates openstack/tripleo-quickstart openstack/tripleo-quickstart-extras openstack/tripleo-upgrade openstack/trove openstack/trove-tempest-plugin openstack/vitrage openstack/vitrage-tempest-plugin openstack/watcher openstack/watcher-tempest-plugin openstack/zaqar openstack/zaqar-tempest-plugin openstack/zun openstack/zun-tempest-plugin windmill/windmill windmill/windmill-backup x/neutron-classifier x/vmware-nsx I'll go ahead and push changes to windmill/* and x/* as those are leftovers from splitting things up into tenants and haven't ended up in their own tenants yet. But it would be great if OpenStack can work on cleaning up this deprecated syntax in the OpenStack repos. I've attached a file with a listing that includes more details for each repo (branches and specific config files) to make it easier for people to find where the old syntax is located so that it can be replaced with the new syntax. [0] https://zuul-ci.org/docs/zuul/latest/releasenotes.html#relnotes-4-1-0-depre… [1] https://lists.zuul-ci.org/pipermail/zuul-discuss/2022-May/001801.html

2 2

[ironic] Ilya Etingof Passed Away
by Iury Gregory 14 Sep '22

14 Sep '22

With a heavy heart, I am sorry to announce that after a long struggle with an illness, Ilya Etingof (etingof on IRC) passed away on Wednesday, 10th August, 2022. He is survived by his mother and two daughters. Born in Russia, Ilya had moved to Czechia and in 2015 joined Red Hat. In 2017, Ilya started contributing to the Ironic project. He was the lead contributor to the Sushy project, Sushy Redfish emulator, an important contributor to Ironic and worked tirelessly to make hardware management reliable and consistent. His important contributions included boot management, out-of-band hardware inspection and virtual media boot. Outside of the OpenStack community, he has maintained Python packages with a particular focus on SNMP. For example: pysnmp, pysmi, pyasn1, softboxen and many others. Ilya was dedicated to helping younger and under-represented people. He used to run a virtualisation technologies course at the Masaryk University in Brno where he spoke about OpenStack and Kubernetes. He was also an active participant in the Outreachy program where he mentored those who contributed to Open Source projects. Goodbye Ilya from the Ironic community, may you rest in peace. -- *Att[]'s* *Iury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Ironic PTL * *Senior Software Engineer at Red Hat Brazil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

2 1

[all] GovStack community seeking for infrastructure expertise
by Lueck, Nico GIZ 10 Sep '22

10 Sep '22

Do you believe in the potential of digital public goods for positive impact? Ever wished for more digitally-enabled government services? GovStack [1] is a community-driven initiative on a mission to accelerate the digital transformation of government services in order to better serve citizens - and we want you to join us! We create and maintain an openly licenced blueprint for a modular architecture based on reusable building blocks [2]. Our various working groups work to define the (non-)functional and API specifications for building blocks, leveraging existing standards such as OpenStack. These specifications are then used for implementations in our partner countries across the world, to facilitate the delivery of foundational, life-enhancing services. Learn more about the call for contributions here [3]. We are specifically looking for experts with experience in infrastructure and security. The initiative is founded by the German Federal Ministry for Economic Cooperation and Development, Deutsche Gesellschaft fuer Internationale Zusammenarbeit (GIZ), the Ministry of Foreign Affairs of the Republic of Estonia, the International Telecommunication Union (ITU) and the Digital Impact Alliance. Thank you to the team of the Open Infrastructure Foundation for their support. Also, thank you to the whole community and please feel free to directly contact us. Nico (Lueck) <nico.lueck(a)giz.de> [1] https://www.govstack.global/ [2] https://govstack.gitbook.io/ [3] https://www.govstack.global/call-for-expression-of-interest/ ________________________________ Deutsche Gesellschaft fuer Internationale Zusammenarbeit (GIZ) GmbH; Sitz der Gesellschaft Bonn und Eschborn/Registered offices Bonn and Eschborn, Germany; Registergericht/Registered at Amtsgericht Bonn, Germany; Eintragungs-Nr./Registration no. HRB 18384 und/and Amtsgericht Frankfurt am Main, Germany; Eintragungs-Nr./Registration no. HRB 12394; USt-IdNr./VAT ID no. DE 113891176; Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Jochen Flasbarth; Vorstand/Management Board: Tanja Goenner (Vorstandssprecherin/Chair of the Management Board), Ingrid-Gabriela Hoven, Thorsten Schaefer-Guembel

3 2

[DIB][diskimage-builder] Rocky Linux image build method
by Pierre Riteau 07 Sep '22

07 Sep '22

Hello, I am curious about the choice of providing only a rocky-container element in DIB, which works differently to the centos element, which uses cloud images. It makes it hard to produce working images for VMs or bare metal, as various packages that would normally be installed are missing, such as cloud-utils-growpart or openssh-server. See the kickstarts for reference [1] [2]. It seems to also occasionally cause complex failures such as the one that rendered Rocky Linux 8 images unbootable last week [3]. I am guessing this wouldn't have happened had the build been from a cloud image. Would the DIB community be open to also have a rocky element using GenericCloud images, like centos? Thanks, Pierre Riteau (priteau) [1] https://git.rockylinux.org/rocky/kickstarts/-/blob/r8/Rocky-8-Container-Bas… [2] https://git.rockylinux.org/rocky/kickstarts/-/blob/r8/Rocky-8-GenericCloud.… [3] https://review.opendev.org/c/openstack/diskimage-builder/+/851687

6 6

[election][tripleo] PTL Candidacy for Antelope cycle
by Rabi Mishra 06 Sep '22

06 Sep '22

Hi All, I would like to nominate myself for Antelope cycle TripleO PTL. As some of you would know, I have been part of the OpenStack community for a long time and have been a core contributor for TripleO and Heat. I have also served as Heat PTL for Ocata cycle. James has done a great job as PTL for the last few cycles. I would like to take the opportunity to thank him for all his effort and we all would agree that he needs a well deserved break. I am looking forward to take the opportunity to help the community to achieve some of the already planned goals and in-progress workstreams like standalone roles, multi-rhel and other challenges that come along the way. Also, as before, our focus would continue to be on review prioritization, in progress work streams and collaboration on common priorities. Regards, Rabi Mishra

9 8

[manila] LVM shares are unmounted on reboot
by Vaibhav 05 Sep '22

05 Sep '22

Dear All, One of the host running Manila-share service has rebooted. After the reboot the LVMs are not mounted on the Manila mount points. I use LVM Driver with DHSS=False. default_share_type = default_share_type share_name_template = manila-%s rootwrap_config = /etc/manila/rootwrap.conf api_paste_config = /etc/manila/api-paste.ini auth_strategy = keystone my_ip=192.168.82.2 enabled_share_backends = lvm enabled_share_protocols = NFS state_path=/var/lib/manila [lvm] share_backend_name = LVM share_driver = manila.share.drivers.lvm.LVMShareDriver driver_handles_share_servers = False lvm_share_volume_group = VGZunManila lvm_share_export_ips = 192.168.82.2 lvm_share_export_root = $state_path/mnt After the reboot LVMs are there but they are mounted on their respective share location. Any way to solve this and this to be done automatically? Regards, Vaibhav

2 2