December 2021 - openstack-discuss

Fwd: DPDK+OVS with OpenStack
by Mark Wittling 23 Apr '25

23 Apr '25

Looking for someone who knows OpenStack with OpenVSwitch, and in addition to that, DPDK with OpenStack and OVS.I am using OpenStack Queens, with OpenVSwitch. The architecture I am using is documented here: https://docs.openstack.org/neutron/queens/admin/deploy-ovs-provider.htmlThe OVS I am using on the Compute Node, is compiled with DPDK, and I have enabled the datapath to netdev (DPDK) on br-prv (provider network bridge), and br-tun (tunneling bridge). But these two bridges, br-tun and br-prv, are patched into another OpenStack bridge, called br-int. I wasn’t actually sure about whether to tinker with this bridge, and wondered what datapath it was using.Then, I realized there is a parameter in the openvswitch_agent.ini file, which I will list here: # OVS datapath to use. 'system' is the default value and corresponds to the # kernel datapath. To enable the userspace datapath set this value to 'netdev'. # (string value) # Possible values: # system - <No description provided> # netdev - <No description provided> #datapath_type = system datapath_type = netdev So in tinkering with this, what I realized, is that when you set this datapath_type to system or netdev, it will adjust the br-int bridge to that datapath type.So here is my question. How can I launch a non-DPDK VM, if all of the bridges are using the netdev datapath type?Here is another question. What if one of the flavors don’t have the largepages property set on them? I assumed OpenStack would revert to a system datapath and not use DPDK for those VM interfaces. Well, I found out in testing, that is not the case. If you set all your bridges up for netdev, and you don’t set the property on the Flavor of the VM (largepages), the VM will launch, but it simply won’t work.Is there no way, on a specific Compute Host, to support both DPDK (netdev datapaths) and non-DPDK (system datapaths)?Either on a VM interface level (VM has one interface that is netdev DPDK and another that is system datapath non-DPDK)?Or on a VM by VM basis (VM 1 has 1 or more netdev datapath interfaces and VM 2 has 1 or more system datapath interfaces)?Am I right here? Once you set up a Compute Host for DPDK, it’s DPDK or nothing on that Compute Host? (edited)

3 2

How to config DPDK compute in OVN
by dangerzone ar 22 Apr '25

22 Apr '25

Hi....as far I understand ovs does support dpdk compute to be deployed. I'm referring to the guideline ' *https://docs.openstack.org/networking-ovn/queens/admin/dpdk.html <https://docs.openstack.org/networking-ovn/queens/admin/dpdk.html>* ' ... It's too brief.. May I know how to config dpdk compute in OVN networking openstack? Hope someone could help what is the config to be done.... Currently compute is run without dpdk over openstack train ovn based. Please need some info on how I can proceed. Thank you

2 1

Live migration fails
by Szabo, Istvan (Agoda) 06 Aug '24

06 Aug '24

Hi, I have couple of compute nodes where the live migration fails with existing vms. When I quickly spawn a vm and try live migration it works so I assume shouldn't be a big problem with the compute node. However I have many existing vms where it fails with a servername not found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 ERROR nova.conductor.tasks.migrate [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] [instance: 1517a2ac-3b51-4d8d-80b3-89a5614d1ae0] Unable to find record for source node servername on servername: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 WARNING nova.scheduler.utils [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] Failed to compute_task_migrate_server: Compute host servername could not be found.: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 WARNING nova.scheduler.utils [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] [instance: 1517a2ac-3b51-4d8d-80b3-89a5614d1ae0] Setting instance to ACTIVE state.: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.672 227612 ERROR oslo_messaging.rpc.server [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] Exception during message handling: ComputeHostNotFound: Compute host am-osfecn-4025 Tried with this command: nova live-migration --block-migrate id. Any idea? Thank you. ________________________________ This message is confidential and is for the sole use of the intended recipient(s). It may also be privileged or otherwise protected by copyright or other legal rules. If you have received it by mistake please let us know by reply email and delete it from your system. It is prohibited to copy this message or disclose its content to anyone. Any confidentiality or privilege is not waived or lost by any mistaken delivery or unauthorized disclosure of the message. All messages sent to and from Agoda may be monitored to ensure compliance with company policies, to protect the company's interests and to remove potential malware. Electronic messages may be intercepted, amended, lost or deleted, or contain viruses.

5 16

[all] Dynamic Zuul results table in Gerrit 3
by Radosław Piliszek 04 Aug '22

04 Aug '22

Hello Fellow OpenStack and OpenDev Folks! TL;DR click on [3] and enjoy. I am starting this thread to not hijack the discussion happening on [1]. First of all, I would like to thank gibi (Balazs Gibizer) for hacking a way to get the place to render the table in the first place (pun intended). I have been a long-time-now user of [2]. I have improved and customised it for myself but never really got to share back the changes I made. The new Gerrit obviously broke the whole script so it was of no use to share at that particular state. However, inspired by gibi's work, I decided to finally sit down and fix it to work with Gerrit 3 and here it comes: [3]. Works well on Chrome with Tampermonkey. Not tested others. I hope you will enjoy this little helper (I do). I know the script looks super fugly but it generally boils down to a mix of styles of 3 people and Gerrit having funky UI rendering. Finally, I'd also like to thank hrw (Marcin Juszkiewicz) for linking me to the original Michel's script in 2019. [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-November/019051… [2] https://opendev.org/x/coats/src/commit/444c95738677593dcfed0cfd9667d4c4f0d5… [3] https://gist.github.com/yoctozepto/7ea1271c299d143388b7c1b1802ee75e Kind regards, -yoctozepto

5 7

[all] PyCharm Licenses Renewed till July 2021
by Swapnil Kulkarni 13 Jul '22

13 Jul '22

Hello, Happy to inform you the open source developer license for Pycharm has been renewed for 1 additional year till July 2021. Best Regards, Swapnil Kulkarni coolsvap at gmail dot com

8 13

Nova not updating to new size of an extended in-use / attached cinder volume (Ceph RBD) to guest
by Christian Rohmann 28 Jun '22

28 Jun '22

Hello Openstack-Discuss, after some digging I found out that cinder learned to resize attached (in-use) volumes quite a while ago with the introduction of the initial "extend 'in-use' volume" feature: https://review.opendev.org/c/openstack/cinder/+/454287/ The support was then extended to also cover Ceph RBD backed volumes with: https://review.opendev.org/c/openstack/nova/+/613039/ Since this is only about the cinder part, I was wondering if nova would ever find out and would actively rescan the device / volume and quintessentially present an increased new size to the guest. Apparently this is where a certain volume-extended event comes into play: https://review.opendev.org/c/openstack/nova/+/454322/ that is to be emitted by cinder when a volume had been extened. I then went head and tried this with the openstack cli (as Horizon does not seem to support / offer to resize in-use volumes. I run Openstack Train with Ceph RBD as storage. First I ran into an issue with the openstack cli (https://bugs.launchpad.net/cinder/+bug/1871759/comments/2 <https://bugs.launchpad.net/cinder/+bug/1871759/comments/2>) but using cinder extend $volumeid $newsize I was able to resize in-use volumes just fine. The only thing missing was the propagation to the guest. I played around with SCSI rescans, but that did not work, reboots also failed to do anyting in this regards. Stopping and starting the VM did work, but why having the capability to online-resize an attached volume when not being able to resize the guest volume as well? Apparently there seems to be an old and somewhat similar observation / bug with https://bugs.launchpad.net/nova/+bug/1369465 So I was simply wondering if this is expected to be working? Are there any special settings / options I need to set to enable this feature? Thanks and with kind regards Christian

4 9

[oslo] Propose to EOL stable/queens, stable/rocky on all the oslo scope
by Herve Beraud 24 Jun '22

24 Jun '22

Hi, On our last meeting of the oslo team we discussed the problem with broken stable branches (rocky and older) in oslo's projects [1]. Indeed, almost all these branches are broken. Előd Illés kindly generated a list of periodic-stable errors on Oslo's stable branches [2]. Given the lack of active maintainers on Oslo and given the current status of the CI in those branches, I propose to make them End Of Life. I will wait until the end of month for anyone who would like to maybe step up as maintainer of those branches and who would at least try to fix CI of them. If no one will volunteer for that, I'll EOLing those branches for all the projects under the oslo umbrella. Let us know your thoughts. Thank you for your attention. [1] https://meetings.opendev.org/meetings/oslo/2021/oslo.2021-10-04-15.00.log.t… [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023939.html -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

5 5

[TripleO] Core team cleanup
by James Slagle 30 Mar '22

30 Mar '22

Hello, I took a look at our core team, "tripleo-core" in gerrit. We have a few individuals who I feel have moved on from TripleO in their focus. I looked at the reviews from stackalytics.io for the last 180 days[1]. These individuals have less than 6 reviews, which is about 1 review a month: Bob Fournier Dan Sneddon Dmitry Tantsur Jiří Stránský Juan Antonio Osorio Robles Marius Cornea These individuals have publicly expressed that they are moving on from TripleO: Michele Baldessari wes hayutin I'd like to propose we remove these folks from our core team, while thanking them for their contributions. I'll also note that I'd still value +1/-1 from these folks with a lot of significance, and encourage them to review their areas of expertise! If anyone on the list plans to start reviewing in TripleO again, then I also think we can postpone the removal for the time being and re-evaluate later. Please let me know if that's the case. Please reply and let me know any agreements or concerns with this change. Thank you! [1] https://www.stackalytics.io/report/contribution?module=tripleo-group&projec… -- -- James Slagle --

5 6

[all][tc] Relmgt team position on release cadence
by Thierry Carrez 14 Feb '22

14 Feb '22

Hi everyone, The (long) document below reflects the current position of the release management team on a popular question: should the OpenStack release cadence be changed? Please note that we only address the release management / stable branch management facet of the problem. There are other dimensions to take into account (governance, feature deprecation, supported distros...) to get a complete view of the debate. Introduction ------------ The subject of how often OpenStack should be released has been regularly debated in the OpenStack community. OpenStack started with a 3-month release cycle, then switched to 6-month release cycle starting with Diablo. It is often thought of a release management decision, but it is actually a much larger topic: a release cadence is a trade-off between pressure to release more often and pressure to release less often, coming in from a lot of different stakeholders. In OpenStack, it is ultimately a Technical Committee decision. But that decision is informed by the position of a number of stakeholders. This document gives historical context and describes the current release management team position. The current trade-off --------------------- The main pressure to release more often is to make features available to users faster. Developers get a faster feedback loop, hardware vendors ensure software is compatible with their latest products, and users get exciting new features. "Release early, release often" is a best practice in our industry -- we should generally aim at releasing as often as possible. But that is counterbalanced by pressure to release less often. From a development perspective, each release cycle comes with some process overhead. On the integrators side, a new release means packaging and validation work. On the users side, it means pressure to upgrade. To justify that cost, there needs to be enough user-visible benefit (like new features) in a given release. For the last 10 years for OpenStack, that balance has been around six months. Six months let us accumulate enough new development that it was worth upgrading to / integrating the new version, while giving enough time to actually do the work. It also aligned well with Foundation events cadence, allowing to synchronize in-person developer meetings date with start of cycles. What changed ------------ The major recent change affecting this trade-off is that the pace of new development in OpenStack slowed down. The rhythm of changes was divided by 3 between 2015 and 2021, reflecting that OpenStack is now a mature and stable solution, where accessing the latest features is no longer a major driver. That reduces some of the pressure for releasing more often. At the same time, we have more users every day, with larger and larger deployments, and keeping those clusters constantly up to date is an operational challenge. That increases the pressure to release less often. In essence, OpenStack is becoming much more like a LTS distribution than a web browser -- something users like moving slow. Over the past years, project teams also increasingly decoupled individual components from the "coordinated release". More and more components opted for an independent or intermediary-released model, where they can put out releases in the middle of a cycle, making new features available to their users. This increasingly opens up the possibility of a longer "coordinated release" which would still allow development teams to follow "release early, release often" best practices. All that recent evolution means it is (again) time to reconsider if the 6-month cadence is what serves our community best, and in particular if a longer release cadence would not suit us better. The release management team position on the debate -------------------------------------------------- While releasing less often would definitely reduce the load on the release management team, most of the team work being automated, we do not think it should be a major factor in motivating the decision. We should not adjust the cadence too often though, as there is a one-time cost in switching our processes. In terms of impact, we expect that a switch to a longer cycle will encourage more project teams to adopt a "with-intermediary" release model (rather than the traditional "with-rc" single release per cycle), which may lead to abandoning the latter, hence simplifying our processes. Longer cycles might also discourage people to commit to PTL or release liaison work. We'd probably need to manage expectations there, and encourage more frequent switches (or create alternate models). If the decision is made to switch to a longer cycle, the release management team recommends to switch to one year directly. That would avoid changing it again anytime soon, and synchronizing on a calendar year is much simpler to follow and communicate. We also recommend announcing the change well in advance. We currently have an opportunity of making the switch when we reach the end of the release naming alphabet, which would also greatly simplify the communications around the change. Finally, it is worth mentioning the impact on the stable branch work. Releasing less often would likely impact the number of stable branches that we keep on maintaining, so that we do not go too much in the past (and hit unmaintained distributions or long-gone dependencies). We currently maintain releases for 18 months before they switch to extended maintenance, which results in between 3 and 4 releases being maintained at the same time. We'd recommend switching to maintaining one-year releases for 24 months, which would result in between 2 and 3 releases being maintained at the same time. Such a change would lead to longer maintenance for our users while reducing backporting work for our developers. -- Thierry Carrez (ttx) On behalf of the OpenStack Release Management team

15 45

[magnum] dropping mesos code
by Mohammed Naser 01 Feb '22

01 Feb '22

Hi there, Does it make sense for us to drop the Mesos driver code from the code base? I don't know of anyone that actually uses it and I believe it's likely not been tested for years. Mohammed -- Mohammed Naser VEXXHOST, Inc.

4 5

[nova][powervm][zvm] Time to mark powervm and zvm drivers as deprecated for removal?
by Stephen Finucane 28 Jan '22

28 Jan '22

I've had a PR open against the pypowervm library for over a fortnight now [1] with no activity. This has prompted me to go looking into the state of the powervm driver and what I've found isn't great. It doesn't seem there has been any feature development on the driver for many years, and the last change I can see that wasn't simply of a case of "I need to do this to get tests to pass" was over three years ago [2]. The CI also doesn't appear to have been touched in years. The situation for zvm isn't any better. The last functional change to that driver was nearly 2 years ago and I wasn't able to spot any CI running (though it's possible I just missed this). This means the powervm and zvm drivers stand out from the other non-libvirt drivers in-tree, each of which are getting at least some activity (albeit out- of-tree for Hyper-V, from what I recall). It also begs the question: are these drivers something we want to keep around? If we do, how are we going to maintain them long term? If not, how aggressive should we be in removing that now dead code? I'll open patches to mark both powervm and zvm as deprecated shortly so that, assuming nothing changes in the interim, we can look to remove it early in the Z cycle. Please respond here or on the reviews if you have concerns. Stephen [1] https://github.com/powervm/pypowervm/pull/17 [2] Change ID I89ad36f19672368a1f795e1f29c5af6368ccfeec

1 1

Re: Re: [ops] [kolla] RabbitMQ High Availability
by Albert Braden 25 Jan '22

25 Jan '22

Replying from my home email because I've been asked to not email the list from my work email anymore, until I get permission from upper management. I'm not sure I follow. I was planning to add 2 lines to etc/kolla/config/global.conf: [oslo_messaging_rabbit] amqp_durable_queues = False Is that not sufficient? What is involved in configuring dedicated control exchanges for each service? What would that look like in the config? From: Herve Beraud <hberaud(a)redhat.com> Sent: Thursday, December 9, 2021 2:45 AM To: Bogdan Dobrelya <bdobreli(a)redhat.com> Cc: openstack-discuss(a)lists.openstack.org Subject: [EXTERNAL] Re: [ops] [kolla] RabbitMQ High Availability Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Le mer. 8 déc. 2021 à 11:48, Bogdan Dobrelya <bdobreli(a)redhat.com> a écrit : Please see inline >> I read this with great interest because we are seeing this issue. Questions: >> >> 1. We are running kola-ansible Train, and our RMQ version is 3.7.23. Should we be upgrading our Train clusters to use 3.8.x? >> 2. Document [2] recommends policy '^(?!(amq\.)|(.*_fanout_)|(reply_)).*'. I don't see this in our ansible playbooks, nor in any of the config files in the RMQ container. What would this look like in Ansible, and what should the resulting container config look like? >> 3. It appears that we are not setting "amqp_durable_queues = True". What does this setting look like in Ansible, and what file does it go into? > > Note that even having rabbit HA policies adjusted like that and its HA > replication factor [0] decreased (e.g. to a 2), there still might be > high churn caused by a large enough number of replicated durable RPC > topic queues. And that might cripple the cloud down with the incurred > I/O overhead because a durable queue requires all messages in it to be > persisted to a disk (for all the messaging cluster replicas) before they > are ack'ed by the broker. > > Given that said, Oslo messaging would likely require a more granular > control for topic exchanges and the durable queues flag - to tell it to > declare as durable only the most critical paths of a service. A single > config setting and a single control exchange per a service might be not > enough. Also note that therefore, amqp_durable_queue=True requires dedicated control exchanges configured for each service. Those that use 'openstack' as a default cannot turn the feature ON. Changing it to a service specific might also cause upgrade impact, as described in the topic [3]. The same is true for `amqp_auto_delete=True`. That requires dedicated control exchanges else it won't work if each service defines its own policy on a shared control exchange (e.g `openstack`) and if policies differ from each other. [3] https://review.opendev.org/q/topic:scope-config-opts > > There are also race conditions with durable queues enabled, like [1]. A > solution could be where each service declare its own dedicated control > exchange with its own configuration. > > Finally, openstack components should add perhaps a *.next CI job to test > it with durable queues, like [2] > > [0] https://www.rabbitmq.com/ha.html#replication-factor > > [1] > https://zuul.opendev.org/t/openstack/build/aa514dd788f34cc1be3800e6d7dba0e8… > > [2] https://review.opendev.org/c/openstack/nova/+/820523 > >> >> Does anyone have a sample set of RMQ config files that they can share? >> >> It looks like my Outlook has ruined the link; reposting: >> [2] https://wiki.openstack.org/wiki/Large_Scale_Configuration_Rabbit > > > -- > Best regards, > Bogdan Dobrelya, > Irc #bogdando -- Best regards, Bogdan Dobrelya, Irc #bogdando -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

6 16

[ops][nova][victoria] Power State = Suspended?
by DHilsbos＠performair.com 24 Jan '22

24 Jan '22

All; I had something unusual happen this morning; one of my VMs was showing "Suspended" under the Power State in the Horizon dashboard. I've never seen that. What does it mean? Any search that I do points me to a bunch of resources for Status Suspended. Thank you, Dominic L. Hilsbos, MBA Vice President - Information Technology Perform Air International Inc. DHilsbos(a)PerformAir.com www.PerformAir.com

4 8

OpenInfra Summit Berlin 2022 Programming Committee Nominations Now Open
by Erin Disney 19 Jan '22

19 Jan '22

Hey everyone- Programming Committee nominations <https://openinfrafoundation.formstack.com/forms/programmingcommittee2022> for the 2022 OpenInfra Summit in Berlin (June 7-9, 2022) are now open! Programming Committees for each Track will help build the Summit schedule, and are made up of individuals working in open infrastructure. Responsibilities include: Help the Summit team put together the best possible content based on your subject matter expertise Promote the individual Tracks within your networks Review the submissions and Community voting results in your particular Track Determine if there are any major content gaps in your Track, and if so, potentially solicit additional speakers directly to submit Ensure diversity of speakers and companies represented in your Track Avoid vendor sales pitches, focusing more on real-world user stories and technical, in-the-trenches experiences Identify which submissions would make good content for OpenInfra Live, the virtual show hosted by the OpenInfra Foundation that encourages live questions from a global audience 2022 Summit Tracks: 5G, NFV & Edge AI, Machine Learning & HPC CI/CD Container Infrastructure Getting Started Hands-on Workshops NEW: Hardware Enablement Open Development Private & Hybrid Cloud Public Cloud Security Full track descriptions are available here <https://etherpad.opendev.org/p/r.86088dcd62bc50a6381c19f7f26995b6>. If you’re interested in nominating yourself or someone else to be a member of the Summit Programming Committee for a specific Track, please fill out the nomination form <https://openinfrafoundation.formstack.com/forms/programmingcommittee2022>. Nominations will close on January 19, 2022. Programming Committee selections will occur before we close the Call for Presentations (CFP) so that the Committees can host office hours to consult on submissions, and help promote the event. CFP will be opening in January, registration <https://www.eventbrite.com/e/openinfra-summit-berlin-2022-tickets-211374997…> and sponsorship <https://openinfra.dev/summit/> information are already available. Please email speakersupport(a)openinfra.dev with any questions or feedback. Cheers, Erin Disney Event Marketing Open Infrastructure Foundation

1 1

Can neutron-fwaas project be revived?
by Dazhong Qin (秦海中)-云数据中心集团 17 Jan '22

17 Jan '22

Hi： The firewall project is a necessary function when the project is delivered. The lack of firewall function after switching OVN is not acceptable to customers. We intend to maintain this project and develop the fwaas driver based on ovn. Whether the neutron-fwaas project can be reactivate? What should I do ?

4 10

[Deploy] Can three all-in-one nodes form a OpenStack cluster?
by 韩光宇 10 Jan '22

10 Jan '22

Dear all, I am deploing OpenStack Victoria. Can I make a cluster with three all-in-one nodes? Will this have any problems or points to be aware of? Sorry to bother, Thank you very much. Han Guangyu.

3 4

[nova][dev] Revisiting qemu emulation where guest arch != host arch
by Apsey, Christopher 05 Jan '22

05 Jan '22

All, A few years ago I asked a question[1] about why nova, when given a hw_architecture property from glance for an image, would not end up using the correct qemu-system-xx binary when starting the guest process on a compute node if that compute nodes architecture did not match the proposed guest architecture. As an example, if we had all x86 hosts, but wanted to run an emulated ppc guest, we should be able to do that given that at least one compute node had qemu-system-ppc already installed and libvirt was successfully reporting that as a supported architecture to nova. It seemed like a heavy lift at the time, so it was put on the back burner. I am now in a position to fund a contract developer to make this happen, so the question is: would this be a useful blueprint that would potentially be accepted? Most of the time when people want to run an emulated guest they would just nest it inside of an already running guest of the native architecture, but that severely limits observability and the task of managing any more than a handful of instances in this manner quickly becomes a tangled nightmare of networking, etc. I see real benefit in allowing this scenario to run natively so all of the tooling that exists for fleet management 'just works'. This would also be a significant differentiator for OpenStack as a whole. Thoughts? [1] http://lists.openstack.org/pipermail/openstack-operators/2018-August/015653… Chris Apsey Director | Georgia Cyber Range GEORGIA CYBER CENTER 100 Grace Hopper Lane | Augusta, Georgia | 30901 https://www.gacybercenter.org

2 2

[charms] nominate Hemanth Nakkina for charms-core
by Edward Hope-Morley 04 Jan '22

04 Jan '22

I would like propose Hemanth Nakkina for charms-core. Hemanth has really stepped up his efforts to provide invaluable contributions both in code and reviews and I beleive he is in a good position to be considered for core where he will be able to provide additional value to the project. Hemanth has demonstrated rigour for quality through his contributions and is always keen to help others with his deep knowledge of the charms and Openstack. Here is a list of all his contributions: patches: https://review.opendev.org/q/owner:hemanth.nakkina%2540canonical.com reviews: https://review.opendev.org/q/reviewedby:hemanth.nakkina%2540canonical.com I hope you will join me in voting for Hemanth. - Ed

6 5

[nova] Getting away from cdrkit / genisoimage
by Thomas Goirand 04 Jan '22

04 Jan '22

Hi, Please see: https://bugs.debian.org/982241 It looks like cdrkit / genisoimage wont be available in the next Debian 12 (and therefore probably it will also be dropped in Ubuntu). As per the bug report: "I'm told xorriso and libburnia are alternatives and are alive and doing well." Would it be possible to switch to that? Cheers, Thomas Goirand (zigo)

2 1

cpu pinning
by open infra 04 Jan '22

04 Jan '22

3 7

[all][qa][triplo] Help need to maintain OpenStack health dashboard
by Ghanshyam Mann 04 Jan '22

04 Jan '22

Hello Everyone, In the QA meeting[1], we discussed the help needed to maintain the OpenStack health dashboard which is broken currently and the QA team does not have the JS developer and bandwidth to fix it. While discussing it meeting, we found that the TripleO team might be working on a similar dashboard for their CI results. If that is the case, can we collaborate on maintaining the existing dashboard? OpenStack health dashboard: https://opendev.org/openstack/openstack-health Repo: http://status.openstack.org/openstack-health/#/ [1] https://meetings.opendev.org/meetings/qa/2021/qa.2021-11-16-15.00.log.html#… -gmann

5 7

[tempest] Extending tempest for mixed-architecture stacks
by James LaBarre 03 Jan '22

03 Jan '22

Recently I had been running Tempest on my setup testing a mixed-architecture deployment (x86_64 ans ppc64le compute nodes at the same time). It seems that some of the migration and affinity tests will check if there's more than one Compute node before they run. However, it would seem that's as far as they check, without checking if they are in fact compatible or even of the same architecture. (my test cluster is very small, and normally includes two ppc64le Compute nodes, and sometimes one x86_64 Compute node. Currently one ppc64le machine is down for repair). Because the two compute nodes are different architectures, I am getting failures in various migration and affinity tests, maybe more if I tested a larger subset. Now granted my particular setup is a special case, but it does bring to mind some extensions that may be needed for Tempest in the future. I could see it being possible to have x86_64 and ARM mixed together in one stack, maybe even tossing in RISC-v someday. I'm thinking we need to start adding in extra test images, flavors, etc into the Tempest configurations (as in defining multiple options so that each architecture can have test images, etc assigned to it, rather than the current primary and alt image for just one architecture) Additionally, there should be testcases taking into account the architectures involved (such as seeing that an instance on one arch cannot be migrated to the other, as an example). I know this involves a bit of refactoring, I didn't know if it had even been considered yet. -- James LaBarre Software Engineer, OpenStack MultiArch Red Hat <https://www.redhat.com> jlabarre(a)redhat.com <mailto:jlabarre@redhat.com> <https://www.redhat.com>

3 2

[tc][all] Follow up pain point discussion
by Rico Lin 03 Jan '22

03 Jan '22

Dear all The pain point collection etherpad [1] seems to get good attention from teams. We plan to host a one-hour video meeting to keep the discussion going. Please fill in the doodle to select your preferred time if you can join us: https://doodle.com/poll/kur2mfywceerqcvh?utm_source=poll&utm_medium=link The discussion will be hosted in video format. Here are some items (but not limited to) I expect we will discuss and hopefully put some actions/efforts on. - General Pain point: RabbitMQ - General Pain point: OpenStackClient support - General project pain point discussion: How to encourage teams to work/reply on pain points. Meanwhile, we encourage all to check the etherpad and provide your feedback. Also if teams can help to answer questions/concerns on etherpad (like Nova team does) will be greatly appreciated. [1] https://etherpad.opendev.org/p/pain-point-elimination *Rico Lin*

7 11

[octavia] Management Network Issue
by Ammad Syed 03 Jan '22

03 Jan '22

Hi, I am using octavia 9.0. I have created a neutron vlan based management network of octavia. I am creating a loadbalancer with a subnet in the tenant network, its getting created successfully. Then added a listener and created a pool, both created successfully. Now a weird situation is happening. Now when I add a member in the pool, the management network interface get detached automatically from the AMPHORA instance and amphora keeps in PENDING_UPDATE state. I have created a dedicated service-project for octavia and management network and subnet resides there. Any advise how to fix it ? Ammad

2 2

[release] Release countdown for week R-12, Jan 03-07
by Előd Illés 31 Dec '21

31 Dec '21

Development Focus ----------------- Happy new year! The Yoga-2 milestone is next week, on January6th, 2022. Yoga-related specs should now be finalized so that teams can move to implementation ASAP. Some teams observe specific deadlines on the second milestone (mostly spec freezes): please refer to https://releases.openstack.org/ <https://releases.openstack.org/yoga/schedule.html>yoga <https://releases.openstack.org/yoga/schedule.html>/schedule.html <https://releases.openstack.org/yoga/schedule.html>for details. General Information ------------------- Libraries need to be released at least once per milestone period. Next week, the release team will propose releases for any library that has not been otherwise released since milestone 1. PTL's and release liaisons, please watch for these and give a +1 to acknowledge them. If there is some reason to hold off on a release, let us know that as well. A +1 would be appreciated, but if we do not hear anything at all by the end of the week, we will assume things are OK to proceed. Remember that non-library deliverables that follow the cycle-with-intermediary release model should have an intermediary release before milestone-2. Those who haven't will be proposed to switch to the cycle-with-rc model, which is more suited to deliverables that are released only once per cycle. Next week is also the deadline to freeze the contents of the final release. All new 'Yoga' deliverables need to have a deliverable file in https://opendev.org/openstack/releases/src/branch/master/deliverables <https://opendev.org/openstack/releases/src/branch/master/deliverables> and need to have done a release by milestone-2. Changes proposing missingdeliverables for inclusion in Yogahave been posted, so if you have one in your project team please update them with an actual release request before the milestone-2 deadline if you plan on including that deliverable in Yoga, or -1 if you need one more cycle to be ready. Upcoming Deadlines & Dates -------------------------- Yoga-2 Milestone:January6th, 2022 Előd Illés irc: elodilles

1 0

[cinder] proposing Simon Dodsley for cinder-specs-core
by Brian Rosmaita 31 Dec '21

31 Dec '21

As everyone is painfully aware, we have review bandwidth issues in the Cinder project. I propose to address this issue with respect to cinder specs, at least, by adding a contributor who is not currently a cinder-core as a member of the cinder-specs-core team. (Right now, the only members of cinder-specs-core are the cinder-core team.) Simon Dodsley (simondodsley on IRC) has been a cinder contributor for a long time, and has been especially active in PTGs and midcycle meetings over the past few cycles. He's done quality reviews, especially of specs, this cycle. As a vendor representative, he brings a useful perspective to reviews that affect drivers, as well as general deployment and usability issues. Additionally, given that the current core team has reviewing responsibilities spread over multiple repositories, having a person focused primarily on specs should help us to get more timely feedback for specs proposers. Finally, don't forget that it is thanks to Simon that the Cinder mascot finally has a name ("Argo"), which in turn has given the Cinder team the really cool name "The Argonauts". In the absence of objections, I'll add Simon to the cinder-specs-core team shortly after 1500 UTC on Friday 31 December. Please communicate any concerns to me before that time. cheers, brian

4 4

PTR records in Designate
by Albert Braden 30 Dec '21

30 Dec '21

We have hacked Designate to add PTR records and it is a mess. Every upgrade turns into a bug hunt. I'd like to advocate for going back to vanilla kolla-ansible but then we wouldn't have PTR records. How are other Designate users dealing with the PTR issue?

2 2

[neutron] Do I need to replace NetworkManager with network.service in centos8?
by 韩光宇 29 Dec '21

29 Dec '21

Dear all, I am deploing OpenStack Victoria. I want to ask a question. Do I need to replace NetworkManager with network-scripts in centos8? I saw that "OpenStack Networking does not work on systems that have the Network Manager service enabled" in past redhat documentation and some other places. But I don't see this in latest documentation of OpenStack community（ https://docs.openstack.org/install-guide/environment-packages-rdo.html）. And If NetworkManager is confit will OpenStack network, Do anyone know where I can see the reason of confit. I would appreciate any kind of guidance. Thanks, Han Guangyu. Past redhat documentation: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/11…

2 1

[cinder] Bug deputy report for week of 12-29-2021
by Sofia Enriquez 29 Dec '21

29 Dec '21

No meeting today. This is a bug report from 12-22-2021 to 12-29-2021. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/1955670 "Unable to delete a group volume after transfer". Unassigned. 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

[TripleO] Unable to deploy Overcloud Machines
by Anirudh Gupta 28 Dec '21

28 Dec '21

Hi Team, I am trying to deploy TripleO Train with 3 controller and 1 Compute. For overcloud images, I have a registry server at undercloud only. I executed the following command to deploy overcloud openstack overcloud deploy --templates \ -r /home/stack/templates/roles_data.yaml \ -e /home/stack/templates/node-info.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/podman.yaml \ -e /home/stack/containers-prepare-parameter.yaml The command ran for around 1.5 hrs and initially stack got successfully created and after that for 45 mins, ansible tasks were getting executed. It then gave following error in overcloud-controller-0 2021-12-27 11:12:27,507 p=181 u=mistral n=ansible | 2021-12-27 11:12:27.506838 | 525400b1-b522-2a06-ea9d-00000000356f | OK | Debug output for task: Start containers for step 2 | overcloud-novacompute-0 | result={ "changed": false, "failed_when_result": false, "start_containers_outputs.stdout_lines | default([]) | union(start_containers_outputs.stderr_lines | default([]))": [ "f206c31a781641313aa4a0499c62475efc335de6faea785cd4e855dc32ebb571", "", "Info: Loading facts", "Notice: Compiled catalog for overcloud-novacompute-0.localdomain in environment production in 0.05 seconds", "Info: Applying configuration version '1640604309'", "Notice: /Stage[main]/Tripleo::Profile::Base::Neutron::Ovn_metadata_agent_wrappers/Tripleo::Profile::Base::Neutron::Wrappers::Haproxy[ovn_metadata_haproxy_process_wrapper]/File[/var/lib/neutron/ovn_metadata_haproxy_wrapper]/ensure: defined content as '{md5}5bb050ca70c01981975efad9d8f81f2d'", "Info: Tripleo::Profile::Base::Neutron::Wrappers::Haproxy[ovn_metadata_haproxy_process_wrapper]: Unscheduling all events on Tripleo::Profile::Base::Neutron::Wrappers::Haproxy[ovn_metadata_haproxy_process_wrapper]", "Info: Creating state file /var/lib/puppet/state/state.yaml", "Notice: Applied catalog in 0.01 seconds", "Changes:", " Total: 1", "Events:", " Success: 1", "Resources:", " Changed: 1", " Out of sync: 1", " Skipped: 7", " Total: 8", "Time:", " File: 0.00", " Transaction evaluation: 0.01", " Catalog application: 0.01", " Config retrieval: 0.09", " Last run: 1640604309", " Total: 0.01", "Version:", " Config: 1640604309", " Puppet: 5.5.10", * "Error executing ['podman', 'container', 'exists', 'nova_compute_init_log']: returned 1", "Did not find container with \"['podman', 'ps', '-a', '--filter', 'label=container_name=nova_compute_init_log', '--filter', 'label=config_id=tripleo_step2', '--format', '{{.Names}}']\" - retrying without config_id", "Did not find container with \"['podman', 'ps', '-a', '--filter', 'label=container_name=nova_compute_init_log', '--format', '{{.Names}}']\"", "Error executing ['podman', 'container', 'exists', 'create_haproxy_wrapper']: returned 1", "Did not find container with \"['podman', 'ps', '-a', '--filter', 'label=container_name=create_haproxy_wrapper', '--filter', 'label=config_id=tripleo_step2', '--format', '{{.Names}}']\" - retrying without config_id", "Did not find container with \"['podman', 'ps', '-a', '--filter', 'label=container_name=create_haproxy_wrapper', '--format', '{{.Names}}']\""* ] } I am also attaching ansible.log file for more information. Note: On Centos 8, there is no docker, so I didn't pass docker-ha.yml Can someone please help in resolving my issue Regards Anirudh Gupta

2 9

[neutron] bug deputy report of week 2021-12-20
by Bence Romsics 27 Dec '21

27 Dec '21

Hi Team, We only had a few new bugs last week, here they are: High: * https://bugs.launchpad.net/neutron/+bug/1955478 Scenario test failed due to metadata service not available slaweq investigated this gate failure, but did not find enough information in the logs. * https://bugs.launchpad.net/neutron/+bug/1955546 [stable only] Logging service plugin expects wrong arguments in the callback function fixes mostly merged: https://review.opendev.org/q/I0003bd566dc769436ad1342351ad058394bd52da * https://bugs.launchpad.net/neutron/+bug/1955578 OVN transaction could not be completed due to a race condition proposed fix: https://review.opendev.org/c/openstack/neutron/+/821401 * https://bugs.launchpad.net/neutron/+bug/1955775 Error when l3-agent get filter id for ip proposed fix: https://review.opendev.org/c/openstack/neutron/+/822987 Medium: * https://bugs.launchpad.net/neutron/+bug/1955639 Performance of mariadb's neutron.agents table unassigned Incomplete: * https://bugs.launchpad.net/neutron/+bug/1955503 [ovn] OVN agents showing as dead until neutron services restarted If ovn folks have an intuition what may go wrong with agent caching, then please look at it, but we don't have reproduction steps, so marked as Incomplete. Other: * https://bugs.launchpad.net/neutron/+bug/1955765 Devstack - Can no longer enable qos with neutron-qos Now that we un-deprecated the legacy plugin what do we want to do with the new plugin? Possible discussion point for the next meeting. Cheers, Bence

1 0

[cloudkitty] No weekly meeting today
by Rafael Weingärtner 27 Dec '21

27 Dec '21

Hello guys, As agreed in the previous meeting, we will skip IRC meeting this week and be on 10th Jan next year. I hope you all had a merry Christmans, and happy holidays! -- Rafael Weingärtner

1 0

[kolla] No IRC meeting this week
by Michał Nasiadka 26 Dec '21

26 Dec '21

Hello Koalas, As agreed in the previous meeting, we will skip IRC meeting this week (planned for 29th Dec) and meet on 5th Jan. Happy new year! Michal -- Michał Nasiadka mnasiadka(a)gmail.com

1 0

[tacker] No weekly meeting until 2022
by Yasufumi Ogawa 26 Dec '21

26 Dec '21

Hi, As agreed in the previous meeting, we will skip IRC meeting this week and be on 11th Jan next year. Happy holidays! Cheers, yasufumi

1 0

No network access for Openstack instances
by A Monster 26 Dec '21

26 Dec '21

I have used kolla ansible to deploy openstack on two machine servers, but after setting up the images and the virtual networks, the vm instances don't get the ip address that neutron provides for them, so I had to manually set the addresses inside the vm's, but even with that I can't seem to connect vm's to neither internet nor any other network. I'm on centos 7 and trying to deploy openstack train using kolla ansible 9.3.1 Ansible 2.9.25 And neutron open vSwitch.

3 2

[all][tc] What's happening in Technical Committee: summary 24th Dec, 21: Reading: 5 min
by Ghanshyam Mann 24 Dec '21

24 Dec '21

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had a quick meeting yesterday. Most of the meeting discussions are summarized below (Completed or in-progress activities section). Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2021/tc.2021-12-23-15.00.log.html * Next week's meeting on 30th Dec is canceled. We will continue our weekly meeting from Jan 6th, Thursday 15:00 UTC, feel free the topic on the agenda[1] by 5th Jan. 2. What we completed this week: ========================= * Nothing much in this week. 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[2]. Open Reviews ----------------- * 4 open reviews for ongoing activities[3]. SIG i18n status check -------------------------- Ian (SIG chair) responded on ML thread and will look into the things after he is back from leave next month[4]. OpenStack Pain points discussion ---------------------------------------- No updates in this week. Stay tuned on the ML thread[5] and Rico will inform you about the next meeting details. TC position on release cadence ------------------------------------- No updates on this. Discussion is in-progress in ML thread[6]. No other updates from TC on this and we will set up a separate call to continue the discussion sometime in Jan (after the Christmas holidays). Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[7]. Skyline as official projects ------------------------------ We accepted the Skyline as an official project last week and next work on project renaming etc are also started. Adjutant need maintainers and PTLs ------------------------------------------- We are still waiting to hear from Braden, Albert on permission to work on this project[8]. Project updates ------------------- * Retire js-openstack-lib (waiting on Adjutant to have new PTL/maintainer) [9] 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[10]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [11] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. Marry Chirsmas and Happy new year to everyone and stay safe! [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://etherpad.opendev.org/p/tc-yoga-tracker [3] https://review.opendev.org/q/projects:openstack/governance+status:open [4] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026441… [5] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026245… [6] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025684… [7] https://etherpad.opendev.org/p/zuul-config-error-openstack [8] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025786… [9] https://review.opendev.org/c/openstack/governance/+/798540 [10] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [11] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[gate][tempest][plugins][stable] Stable/train tempest plugins jobs are broken
by Ghanshyam Mann 23 Dec '21

23 Dec '21

Hello Everyone, gthiemonge reported the issue for tempest plugin stable/train jobs are broken. I have explained the issue in https://bugs.launchpad.net/tempest/+bug/1955418 and fix is up (it is under testing). This is applicable for any tempest plugin job on stable/train. Please hold the recheck until the below fix is merged: https://review.opendev.org/c/openstack/tempest/+/822339 -gmann

1 1

[tc][sig][i18n] What's the status for Xena translation?
by Akihiro Motoki 23 Dec '21

23 Dec '21

Hi, # I include TC and SIG tags to get broader attractions to this topic. # Also Cc'ed to Ian (i18n SIG char) and Andreas. I would like to ask the status of Xena translation in translate.openstack.org (Zanata). In past releases, stable-XXX branches were created on Zanata, but a branch for Xena translation has not been created yet. Ajaeger usually prepared these branches as a volunteer (I am really appreciated) but AFAIK he no longer works on OpenStack actively. Who takes care of the translatio preparation around the release now? I hope the i18n SIG is not dead. Thanks, Akihiro Motoki (amotoki)

3 2

Re: [kolla-ansible][cinder] MPIO - how to set "storage_interface" when using two NICs for storage connection
by Adam Tomas 23 Dec '21

23 Dec '21

Hi again, I found some informations about MPIO here (https://docs.oracle.com/cd/E78305_01/E78304/html/setup-cinder.html) : "By default, the Cinder block storage service uses the iSCSI protocol to connect instances to volumes. The iscsid container runs on compute nodes and handles the iSCSI session using an iSCSI initiator name that is generated when you deploy Nova compute services. The Nova compute service supports iSCSI multipath for failover purposes and increased performance. Multipath is enabled by default (configured with the enable_multipathd property). When multipath is enabled, the iSCSI initiator (the Compute node) is able to obtain a list of addresses from the storage node that the initiator can use as multiple paths to the iSCSI LUN." But still - how should I set storage_interface, if I have two NICs for storage connection (let’s say eth4 and eth5)? storage_interface=eth4,eth5 ? Best regards Adam Tomas > Hi, > I’d like to use MPIO in connection to storage array, so I have two physical NIC’s in different VLANS on each node and also 4 NIC’s in the storage array (2 in each storage VLAN) so it should result in 4 MPIO paths from every node (2 paths in each VLAN). But how to set it in kolla-ansible? Can I point to more than one interface using storage_interface variable? Or maybe I should configure it in different way?

2 4

Networks for different availability zones in Horizon
by hai wu 23 Dec '21

23 Dec '21

In Horizon "Launch Instance" workflow, in its 4th step of selecting networks for the new instance, it would always show all the available networks from all availability zones, regardless of which "Availability Zone" got picked in 1st step of "Details". I tried to update some DB field for availability zone hint for the relevant network, and that did not help. Any way to ensure in Horizon "Launch Instance" GUI workflow, after a user picking one availability zone in step 1, it would only show the related networks in that availability zone as available networks in step 4?

6 10

[all][tc] Technical Committee next weekly meeting on Dec 23rd at 1500 UTC
by Ghanshyam Mann 22 Dec '21

22 Dec '21

Hello Everyone, Technical Committee's next weekly meeting is scheduled for Dec 23rd at 1500 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Wednesday, Dec 22nd, at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

[adjutant][requirements] Adjutant Django version
by Dmitriy Rabotyagov 22 Dec '21

22 Dec '21

2 1

[requirements][OpenStackClients][rally][tempest][watcher][nova][glance] Use prettytable in requirements
by Dmitriy Rabotyagov 22 Dec '21

22 Dec '21

2 2

[cinder] Bug deputy report for week of 12-22-2021
by Sofia Enriquez 22 Dec '21

22 Dec '21

No meeting today. This is a bug report from 12-15-2021 to 12-22-2021. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/os-brick/+bug/1955020 "multipath -l <device_name> is failing". Assigned to Rajat Dhasmana. Low - https://bugs.launchpad.net/cinder/+bug/1955057 "NetApp driver fails to compare ONTAP version". Assigned to Nahim Alves de Souza. Wishlist - https://bugs.launchpad.net/cinder/+bug/1955360 "Cannot clone a volume from the image within the same ceph cluster". Assigned to Eric Xie. 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

[tripleo][ussuri] Log4j add protection to haproxy {even it is not impacted
by Ruslanas Gžibovskis LPIC 22 Dec '21

22 Dec '21

3 2

[kolla-ansible][cinder]
by Adam Tomas 22 Dec '21

22 Dec '21

Hi, I’d like to use MPIO in connection to storage array, so I have two physical NIC’s in different VLANS on each node and also 4 NIC’s in the storage array (2 in each storage VLAN) so it should result in 4 MPIO paths from every node (2 paths in each VLAN). But how to set it in kolla-ansible? Can I point to more than one interface using storage_interface variable? Or maybe I should configure it in different way? Best regards Adam Tomas

1 0

[neutron] CI meeting 28.12.2021 cancelled
by Slawek Kaplonski 21 Dec '21

21 Dec '21

Hi, Next week Neutron CI meeting is cancelled. Happy holidays for all of You and see You on the meetings in 2022! We will start with CI meeting 4.01.2022 :) -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[cinder] weekly meetings for the remainder of december
by Brian Rosmaita 21 Dec '21

21 Dec '21

As agreed at last week's cinder meeting, our meetings for the remainder of 2021 will be: * Wednesday, December 22: no meeting * Wednesday, December 29: no meeting The next weekly cinder meeting will be Wednesday, January 5 at the usual time (1400 UTC) in the usual place (#openstack-meeting-alt on OFTC). The meeting agenda is here: https://etherpad.opendev.org/p/cinder-yoga-meetings cheers, brian

1 0

[Triple0] Unable to pxeBoot overcloud Nodes via ipv6
by Lokendra Rathour 20 Dec '21

20 Dec '21

Hi Team, we have installed Undercloud with Train release on Centos8 using ipv6 as loca_ip in undercloud.conf file. Undercloud seems to be installed successfully and we are able to see IPv6 endpoints as well. Also, the OpenStack overcloud images are uploaded and well visible on http://<ipv6>:8088 tftp link. Problem Statement: During introspection start, we see that ipv6 is allocated to the node, further no action is being performed. Please refer the screen attached. [image: image.png] As we can see ipv6 bbbb:bbbb:bbbb::9 is allocated to the desired machine. Furthermore, we see that the link is shown as down for the same mac, which also becomes up as can be seen but the configuring on that NIC eventually fails for some reason. Any idea/inputs on this please? -- ~ Lokendra

1 0

[TripleO] Tomorrow's (Dec 21) meeting cancelled, next meeting Jan 3
by James Slagle 20 Dec '21

20 Dec '21

As we have no items on the agenda[1] for tomorrow's meeting, let's cancel it and hold our next meeting on Tuesday, January 3rd. Thanks! [1] https://etherpad.opendev.org/p/tripleo-meeting-items -- -- James Slagle --

1 0