September 2022 - openstack-discuss

[kolla-ansible][Yoga] What are the benefits to run libvirt daemon on host rather on a container?
by wodel youchi 26 Sep '22

26 Sep '22

Hi, What are the benefits to run libvirt daemon directly on the host rather than on a container? In Yoga's release note, it is said : "Currently this is only supported for fresh deployments without an existing nova_libvirt container" But Also it it is said : "Adds a kolla-ansible nova-libvirt-cleanup command, which may be used to clean up the nova_libvirt container. This may be useful if switching to a host libvirt daemon". Is switching supported? I am in ther verge of upgrading from Xena to Yoga and I ma wondering about this. - What is the gain to use libvirt daemon? - Could the switch be done after the upgrade to Yoga? Regards.

2 1

[kolla-ansible] question about network nodes number
by wodel youchi 26 Sep '22

26 Sep '22

Hi, Is it a good idea to configure more than 02 network nodes? Regards.

2 1

[ptls][zed] OpenInfra Live: OpenStack Zed
by Allison Price 26 Sep '22

26 Sep '22

Hi everyone, As we get closer to the OpenStack release, I wanted to reach out to see if any PTLs were interested in providing their Zed cycle highlights in an OpenInfra Live[1] episode on Thursday, October 6 at 1400 UTC. Ideally, we would get 4-6 projects represented. Previous examples of OpenStack release episodes can be found here[2] and here[3]. Please let me know if you’re interested and I can provide next steps. If you would like to provide a project update but that time doesn’t work for you, please share a recording with me and I can get it added to the project navigator. Thanks, Allison [1] https://openinfra.dev/live/ <https://openinfra.dev/live/> [2] https://www.youtube.com/watch?v=hwPfjvshxOM <https://www.youtube.com/watch?v=hwPfjvshxOM> [3] https://www.youtube.com/watch?v=aqilhEmkEBw <https://www.youtube.com/watch?v=aqilhEmkEBw>

1 1

[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

[neutron] bug deputy report of week 2022-09-19
by Bence Romsics 26 Sep '22

26 Sep '22

Hi All, Here comes last week's deputy report (we had only a handful of reports): Unassigned: * https://bugs.launchpad.net/neutron/+bug/1990229 [OVN] Stop using external_ids from SB Chassis table Edit Medium: * https://bugs.launchpad.net/neutron/+bug/1990129 [ovn-octavia-provider] Avoid LB in ERROR status on delete due to LR/LS not found proposed fix: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/857716 Low: * https://bugs.launchpad.net/neutron/+bug/1990285 Help for `network create --external` is incorrect Edit proposed fix: https://review.opendev.org/c/openstack/python-openstackclient/+/858708 Incomplete: * https://bugs.launchpad.net/neutron/+bug/1990561 Network filtering by provider attributes has a race condition with network removal Cheers, Bence

1 0

Re: RE : RE : [neutron][nova][ipv6]instance on compute node not getting dhcpv6
by mhazan＠mandint.org 26 Sep '22

26 Sep '22

no joy with the accept_ra fiddling, the image are all ubuntu or debian cloud-init ready and are working on all in one node but not dedicated compute node, it's as if the dhcpv6 packet (before address is allocated to interface) are not passing between the control node and the dedicated compute node. Le 2022-09-20 10:53, Michael Hazan a écrit : > Thanks for the suggestion, i will look into the accept_ra setting. However, the very same image that boot on the « old » all in one node are getting ipv6 and ipv4 without issue. The network interfaces are configured similarly on all nodes. > > Michael > > DE : Neil Jerram > ENVOYÉ LE :mardi, 20 septembre 2022 10:47 > À : Michael Hazan > CC : Lajos Katona; openstack-discuss(a)lists.openstack.org > OBJET :Re: RE : [neutron][nova][ipv6]instance on compute node not getting dhcpv6 > > They may be outdated now, but I wonder if any of the steps described at https://projectcalico.docs.tigera.io/networking/openstack/ipv6 would help you? In particular, given that you have no route, perhaps you need the accept_ra config. > > Best wishes, > > Neil > > On Tue, Sep 20, 2022 at 9:12 AM Michael Hazan <mhazan(a)mandint.org> wrote: > >> Hello, >> >> The 3 nodes are running Ubuntu 20.04 and using libvirt. The instance are Ubuntu or debian based. The openstack virtual network is configured with both a v4 and a v6 dhcp pool. The instance should be getting both v4 and v6 (on the same interface) but the instance that are hosted on the compute node only get v4. If i run the dhclient -6 -r the instance actually get it's ipv6 but it's wrongly configured with a /128 (instead of 64) and no route. >> >> Michael >> >> DE : Lajos Katona >> ENVOYÉ LE :mardi, 20 septembre 2022 09:39 >> À : mhazan(a)mandint.org >> CC : openstack-discuss(a)lists.openstack.org >> OBJET :Re: [neutron][nova][ipv6]instance on compute node not getting dhcpv6 >> >> Hi, >> >> Do you have some more details of your environment, which backend you use? OVS? >> >> Your VMs have both IPv4 and v6 addresses and you mean that they got IPv4 as expected? >> >> Lajos >> >> <mhazan(a)mandint.org> ezt írta (időpont: 2022. szept. 19., H, 16:19): >> >> Hello all, >> >> i manage a small openstack cluster installed via Ubuntu package, it has >> been upgraded since the day of Newton and currently running Victoria. it >> started as a single node with the basic services installed, later a >> dedicated storage node and compute node were added. after upgrading to >> victoria, any instance that boot on the dedicated compute node start up >> but fails to get it's global ipv6 via stateful dhcp6, only >> linklocal(fe80) ip is shown by the instance. The ipv6 is created in >> openstack, the dhcpv4 works and there are no issue if the instance boot >> on the "old" all in one node. i can manually allocate (by editing the >> instance network config file) the ipv6 config and it works. any pointer >> as to what could cause this issue ? >> >> BR, Michael

1 1

[magnum][heat][requirements][release] Potential blocker for release with python-magnumclient 4.0.0
by Tony Breeds 26 Sep '22

26 Sep '22

Hello all, In [1] baymodel code was removed, although it still seems to be listed in the API-ref. Story [2] states it's been deprecated for a long time, but a quick check failed to see this documented anywhere. Heat still supports baymodel and the removal is causing failures. Blocking the use of python-magnumclient 4.0.0[3] inzed, even though the 4.0.0 release is clearly meant for zed. I can see a couple of paths forward. 0. Remove the documentation in the api-ref for baymodels 1. Remove the support in heat for baymodels (I think the newer clusters API can be used instead?) 2. Revert the change in magnumclient and re-release etc etc 3. Keep 4.0.0 for the Antelope release, and reset the stable/zed branch python-magnumclient to fd0cb1e (before the removal of baymodels) Obviously option 1 looks like the least disruptive change, but potentially causes a problem for heat depending on the published state of baymodel support [1] https://review.opendev.org/c/openstack/python-magnumclient/+/803629 [2] https://storyboard.openstack.org/#!/story/2009104 [3] https://review.opendev.org/c/openstack/requirements/+/858089 -- Yours Tony.

3 4

[openstack-helm] OpenStack-Helm PTG
by Gage Hugo 25 Sep '22

25 Sep '22

Hey team, The next PTG is coming up (Oct 17-21). I've booked a slot for project discussions on Tue Oct 18th @ 1500 UTC Please sign up to the etherpad if you wish to propose any topics: https://etherpad.opendev.org/p/oct2022-ptg-openstack-helm See you there!

1 0

[all][tc] What's happening in Technical Committee: summary 2022 Sept 23: Reading: 5 min
by Ghanshyam Mann 23 Sep '22

23 Sep '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Sept 22. Most of the meeting discussions are summarized in this email. Meeting logs are available @ https://meetings.opendev.org/meetings/tc/2022/tc.2022-09-22-15.00.log.html * Next TC weekly meeting will be on Sept 29 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Sept 28. 2. What we completed this week: ========================= * Antelope Elections[2]. Thanks to all the leaders who step up for the role. Also thanks to the election official. * Updated node.js version to 18 in 2023.1 testing runtime[3] 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[4], Five are completed and other items are in-progress. Open Reviews ----------------- * Thirteen open reviews for ongoing activities[5]. New community-wide goal proposal "Migration CI/CD to Ubuntu 22.04" -------------------------------------------------------------------------------------- As we decided to migrate the CI/CD testing from Ubuntu 20.04 to 22.04 in 2023.1 cycle, we need to define this task as a community-wide goal. This work requires more testing than changes which are covered in base jobs. The goal proposal is under review[6]. Thanks, Dmitriy to compose and volunteer to drive this goal. 2023.1 cycle Leaderless projects & TC Chair ---------------------------------------------------- * We had 9 projects that missed the PTL nomination but the good news is that we found the leaders for all 9 projects now[7]. TC is discussing their appointment on gerrit reviews. * TC Chair: we have two nominations for the TC Chair[8][9] which is really a good thing having multiple people stepping up for the role. We will keep nomination open until Tuesday (27 Sept) if anyone else also would like to add a nomination. On Tuesday, we can start the CIVS poll among TC members to select the chair for next term. 2023.1 cycle TC PTG planning ------------------------------------ Updates on PTG planning: * TC decided to meet at the below slots [10]: ** Monday 15:00 - 17:00 UTC (2 hours) for TC+leaders interaction discussion. ** Thursday 15:00 - 19:00 UTC (4 hours) ** Friday 15:00 - 19:00 UTC (4 hours) * Etherpads: ** https://etherpad.opendev.org/p/tc-2023-1-ptg ** https://etherpad.opendev.org/p/tc-leaders-interaction-2023-1 * I sent an email about the 'Operator Hours' slots in this PTG, please check and reserve the operator hour slot for your project[11] 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[12]. Feel free to check and provide feedback. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[13]14]. Project updates ------------------- * None. 4. 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 the email with tag [tc] on openstack-discuss ML[15]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [16] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/858539 [3] https://review.opendev.org/c/openstack/governance/+/856927 [4] https://etherpad.opendev.org/p/tc-zed-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] https://review.opendev.org/c/openstack/governance/+/858690 [7] https://etherpad.opendev.org/p/2023.1-leaderless [8] https://review.opendev.org/c/openstack/governance/+/858947 [9] https://review.opendev.org/c/openstack/governance/+/858957 [10] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0305… [11] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… [12] https://review.opendev.org/c/openstack/governance/+/836888 [13] https://etherpad.opendev.org/p/zuul-config-error-openstack [14] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [15] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [16] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[manila] Antelope PTG planning
by Carlos Silva 23 Sep '22

23 Sep '22

Greetings, Zorillas and interested stackers! At this point, I bet you already know that the PTG is coming. It goes from 17th to 21st of October 2022, and if you have not registered yet, there is still time! [1] We have already booked the slots for our discussions, please add it to your agenda: 17th: 16:00 UTC to 17:00 UTC (Monday) 19th: 14:00 UTC to 17:00 UTC (Wednesday) 20th: 14:00 UTC to 17:00 UTC (Thursday) 21st: 13:00 UTC to 17:00 UTC (Friday) Please add the topics you would like to bring up to our planning etherpad [2]. Looking forward to meeting you there! [1] https://openinfra.dev/ptg/ [2] https://etherpad.opendev.org/p/antelope-ptg-manila-planning - carloss

1 0