December 2021 - openstack-discuss

[CLOUDKITTY][VICTORIA] - policy prohibit report:get_summary to admin
by Gaël THEROND 13 Dec '21

13 Dec '21

Hi everyone! Today I faced a weird situation with one of our cloud platforms using victoria release. When trying to get a summary of projects rates would it be through Horizon or CLI using the admin user of the platform we've got the following error message: https://paste.opendev.org/show/bIgG6owrN9B2F3O7iqYG/ >From my understanding of the default policies of cloudkitty, this error seems to be a bit odd as the admin user profile actually match the default rules. At least as exposed in: https://opendev.org/openstack/cloudkitty/src/branch/stable/victoria/cloudki… and https://opendev.org/openstack/cloudkitty/src/branch/stable/victoria/cloudki… Unless I misunderstood something (please correct me if I'm wrong), it's supposed to at least be ok with the matching.

3 7

[nova] How to update OS-EXT-SRV-ATTR:hostname
by Kamil Madáč 13 Dec '21

13 Dec '21

Hello, I would like to ask, how to update OS-EXT-SRV-ATTR:hostname via openstack CLI? We changed hostnames on bunch of instances, but metadata service still serves old hostname which causes that every future rebuild of instance reverts hostname (`hostname` command in instance console) back to old one. Kamil Madáč Slovensko IT a.s.

3 4

[Triple0] Overcloud Deployment Network Queries
by Lokendra Rathour 13 Dec '21

13 Dec '21

Hi Team, As we are trying to deploy Triple0, regarding this we have the following queries: 1. On the Overcloud machine, I have four NICs available so is there a way to bind a particular NIC to a physnet. 1. Also, can we create multiple physnet, one being flat and the other being VLAN, binded with two different NICs respectively? 2. We have created a local registry during Undercloud installation on Undercloud, What is the way to configure local registry images for overcloud deployment? -- ~ Lokendra skype: lokendrarathour

1 0

[Interop] No WG meeting on Dec 23 and 30.
by Arkady Kanevsky 11 Dec '21

11 Dec '21

Happy holidays. -- Arkady Kanevsky, Ph.D. Phone: 972 707-6456 Corporate Phone: 919 729-5744 ext. 8176456

3 2

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

10 Dec '21

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * TC this week IRC meeting held on Oct 14th Thursday. * 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-10-14-15.00.log.html * Next week's meeting is cancelled as we are meeting in PTG. We will have the next IRC meeting on Oct 28th, Thursday 15:00 UTC, feel free the topic on agenda[1] by Oct 27th. 2. What we completed this week: ========================= * None in this week. 3. Activities In progress: ================== TC Tracker for Xena cycle ------------------------------ * TC is using the etherpad[2] for Xena cycle working item. We will be checking it in PTG * Current status is: 9 completed, 3 to-be-discussed in PTG, 1 in-progress Open Reviews ----------------- * Six open reviews for ongoing activities[3]. New project 'Skyline' proposal ------------------------------------ * You might be aware of this new dashboard proposal in the previous month's discussion. * A new project 'Skyline: an OpenStack dashboard optimized by UI and UE' is now proposed in governance to be an official OpenStack project[4]. * Skyline team is planning to meet in PTG on Tue, Wed and Thu at 5UTC, please ask your queries or have feedback/discussion with the team next week. Place to maintain the external hosted ELK, E-R, O-H services ------------------------------------------------------------------------- * We had a final discussion or I will say just a status update on this which was mentioned in last week's email summary[5]. * Now onwards, discussion and migration work will be done in TACT SIG (#openstack-infra IRC channel). Add project health check tool ----------------------------------- * No updates on this, we will continue discussing it in PTG for the next steps on this and what to do with TC liaison things. * Meanwhile, we are reviewing Rico proposal on collecting stats tools [6]. Stable Core team process change --------------------------------------- * Current proposal is under review[7]. Feel free to provide early feedback if you have any. Call for 'Technical Writing' SIG Chair/Maintainers ---------------------------------------------------------- * As agreed in last week's TC meeting, we will be moving this SIG work towards TC. * TC members have been added to the core members list in the SIG repos. * We will be discussing where to move the training repos/work in PTG. TC tags analysis ------------------- * Operator feedback is asked on open infra newsletter too, and we will continue the discussion in PTG and will take the final decision based on feedback we receive, if any[9]. Complete the policy pop up team ---------------------------------------- * Policy pop team has served its purpose and we have new RBAC as one of the the community-wide goal for the Yoga cycle. * We are marking this popup team as completed[10]. Project updates ------------------- * Retiring js-openstack-lib [11] Yoga release community-wide goal ----------------------------------------- * Please add the possible candidates in this etherpad [12]. * Current status: "Secure RBAC" is selected for Yoga cycle[13]. PTG planning ---------------- * We will be meeting in PTG next week, please check the details in this etherpad [14] * Do not forget to join the TC+community leaders sessions on Monday, Oct 18 15 UTC - 17 UTC. Test support for TLS default: ---------------------------------- * Rico has started a separate email thread over testing with tls-proxy enabled[15], we encourage projects to participate in that testing and help to enable the tls-proxy in gate testing. 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[16]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [17] 3. Office hours: The Technical Committee offers a weekly office hour every Tuesday at 0100 UTC [18] 4. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://etherpad.opendev.org/p/tc-xena-tracke [3] https://review.opendev.org/q/projects:openstack/governance+status:open [4] https://review.opendev.org/c/openstack/governance/+/814037 [5]http://lists.openstack.org/pipermail/openstack-discuss/2021-October/02525… [6] https://review.opendev.org/c/openstack/governance/+/810037 [7] https://review.opendev.org/c/openstack/governance/+/810721 [9] https://governance.openstack.org/tc/reference/tags/index.html [10] https://review.opendev.org/c/openstack/governance/+/814186 [11] https://review.opendev.org/c/openstack/governance/+/798540 [12] https://review.opendev.org/c/openstack/governance/+/807163 [13] https://etherpad.opendev.org/p/y-series-goals [14] https://etherpad.opendev.org/p/tc-yoga-ptg [15] http://lists.openstack.org/pipermail/openstack-discuss/2021-June/023000.html [16] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting [18] http://eavesdrop.openstack.org/#Technical_Committee_Office_hours -gmann

9 25

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

10 Dec '21

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * 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-09-15.00.log.html * Next week's meeting is on IRC on 16th Dec, Thursday 15:00 UTC, feel free the topic on the agenda[1] by 15th Dec. 2. What we completed this week: ========================= * 'Consistent and Secure Default RBAC' is selected as community-wide goal [2] * Add NVidia vGPU plugin charm to OpenStack charms[3] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[4]. Open Reviews ----------------- * 5 open reviews for ongoing activities[5]. OpenStack Pain points discussion ---------------------------------------- We had a separate video call on Wed 8th Dec and discussed four projects' pain points[6] and also added the tag to categorize them. Details are sent by Rico in a separate email[7] and we will continue the discussion in Jan. Stay tuned on that ML thread to know the next meeting details. Skyline as an official project --------------------------------- Discussion going on in ML thread[8] regarding the things/improvement to do in Skyline project for various things to make it consistent with other OpenStack projects. Skyline team has confirmed to work on all those points on the governance patch[9] which is under review by TC. TC position on release cadence ------------------------------------- Discussion is in-progress in ML thread[10]. 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). Yoga testing runtime ------------------------- Governance patch is up for review on keeping python3.6 support in Yoga[11] Fixing Zuul config error -------------------------- If your project is listed in zuul config error, please start planning to fix those[12] Community-wide goal updates ------------------------------------ You might have seen my email[13] about goal status and planning the work, below is the current status: * Selected (active) goals[14]: ** Migrate from oslo.rootwrap to oslo.privsep ** Consistent and Secure Default RBAC * Goal proposal under review: ** FIPS compatibility and compliance [15]. Adjutant need maintainers and PTLs ------------------------------------------- We are still waiting to hear from Braden, Albert on permission to work on this project[16]. Project updates ------------------- * Retire js-openstack-lib [17] 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[18]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [19] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rb… [3] https://review.opendev.org/c/openstack/governance/+/819856 [4] https://etherpad.opendev.org/p/tc-yoga-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] https://etherpad.opendev.org/p/pain-point-elimination [7] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026245… [8] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026206… [9] https://review.opendev.org/c/openstack/governance/+/814037 [10] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025684… [11] https://review.opendev.org/c/openstack/governance/+/820195 [12] https://etherpad.opendev.org/p/zuul-config-error-openstack [13] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026218… [14] https://governance.openstack.org/tc/goals/selected/index.html [15] https://review.opendev.org/c/openstack/governance/+/816587 [16] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025786… [17] https://review.opendev.org/c/openstack/governance/+/798540 [18] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [19] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

Force specific Region for resource creation
by Ryan Bannon 09 Dec '21

09 Dec '21

Hello all, Question: is there any way to associate a Region to a Project? Would this require custom code/development in OpenStack? (By my understanding, a Project lives outside the concept of a Region, and resources associated with a Project can target any Region.) Tx, Ryan

1 0

[neutron] Drivers meeting - Friday 10.12.2021 - cancelled
by Lajos Katona 09 Dec '21

09 Dec '21

Hi Neutron Drivers! Due to the lack of agenda, let's cancel tomorrow's drivers meeting. We have only one RFE from last week: https://bugs.launchpad.net/neutron/+bug/1953170 ([RFE] Unify quota engine API) but we discussed that last week (see [0]). See You on the meeting next week. [0]: https://meetings.opendev.org/meetings/neutron_drivers/2021/neutron_drivers.… Lajos Katona (lajoskatona)

1 0

[mistral] How to import openstack actions from mistral-extra
by Oleksandr Mykhalskyi 09 Dec '21

09 Dec '21

Hello, In release Pike, I was able to import openstack actions to mistral DB using "mistral-db-manage --config-file /etc/mistral/mistral.conf populate" As I understood, from release Ussuri, all openstack actions were moved to separate mistral-extra library. But it`s unclear, how to import openstack actions to DB now. Command "mistral-db-manage populate" creates only few std* actions. I didn`t find any info in mistral documentation https://docs.openstack.org/mistral/latest/user/index.html about these changes. In https://github.com/openstack/mistral-extra also there is no useful readme. Can you please clarify, how to work with mistral-extra library and openstack actions in latest openstack releases? Thank you! Oleksandr Mykhalskyi, System Engineer, IT Servers and Services, LAUT Netcracker Technology +38 (044) 238-8727 ext 6404 | office ________________________________ The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

1 0

RE: [ops] [kolla] RabbitMQ High Availability
by Braden, Albert 09 Dec '21

09 Dec '21

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? 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 -----Original Message----- From: Arnaud Morin <arnaud.morin(a)gmail.com> Sent: Monday, November 29, 2021 2:04 PM To: Bogdan Dobrelya <bdobreli(a)redhat.com> Cc: DHilsbos(a)performair.com; openstack-discuss(a)lists.openstack.org Subject: [EXTERNAL] Re: [ops]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. Hi, After a talk on this ml (which starts at [1]), we endup building a documentation with Large Scale group. The doc is accessible at [2]. Hope this will help. [1] http://secure-web.cisco.com/1gFccuTyEVGnFd9aBOZ-RTPG0hbVIPGAbuLBNnoXP4onSZG… [2] https://secure-web.cisco.com/1OtQ3pcnPPBNwevAFxS8yOS2xFlkHo0tY4SmkFE-wpAU_Y… On 24.11.21 - 11:31, Bogdan Dobrelya wrote: > On 11/24/21 12:34 AM, DHilsbos(a)performair.com wrote: > > All; > > > > In the time I've been part of this mailing list, the subject of RabbitMQ high availability has come up several times, and each time specific recommendations for both Rabbit and Open Stack are provided. I remember it being an A or B kind of recommendation (i.e. configure Rabbit like A1, and Open Stack like A2, OR configure Rabbit like B1, and Open Stack like B2). > > There is no special recommendations for rabbitmq setup for openstack, > but probably a few, like instead of putting it behind a haproxy, or the > like, list the rabbit cluster nodes in the oslo messaging config > settings directly. Also, it seems that durable queues makes a very > little sense for highly ephemeral RPC calls, just by design. I would > also add that the raft quorum queues feature of rabbitmq >=3.18 does > neither fit well into the oslo messaging design for RPC calls. > > A discussable and highly opinionated thing is also configuring > ha/mirror queue policy params for queues used for RPC calls vs > broad-casted notifications. > > And my biased personal humble recommendation is: use the upstream OCF RA > [0][1], if configuring rabbitmq cluster by pacemaker. > > [0] https://secure-web.cisco.com/1N1wD9gW7NZho0LdTVNuiU2ZIB7NW-eJMfDgVzBH3D3E6U… > > [1] > https://secure-web.cisco.com/1iDK1NnL9JTkQqkpBda06xTQNrWY2W0pVOTDwUoadfQbSX… > > > > > Unfortunately, I can't find the previous threads on this topic. > > > > Does anyone have this information, that they would care to share with me? > > > > Thank you, > > > > Dominic L. Hilsbos, MBA > > Vice President - Information Technology > > Perform Air International Inc. > > DHilsbos(a)PerformAir.com > > www.PerformAir.com > > > > > > > > > -- > Best regards, > Bogdan Dobrelya, > Irc #bogdando > >

5 4

Re: [ops] [kolla] RabbitMQ High Availability
by Bogdan Dobrelya 09 Dec '21

09 Dec '21

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]. [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

2 1

Swift Account Reaper Deletion Status
by Matthew Grinnell 09 Dec '21

09 Dec '21

Hello, I was curious about expected account-reaper behavior after deleting an account and if there is a way to be able to tell when all data for the account has been reaped. When I issue a delete on a swift account, I see subsequent HEAD requests on the account then return 410 Gone. Testing with debug logging I can see that after passing the delay_reaping time I see the reaper report my test object is deleted, HEAD requests against the account still return the same 410 Gone. Is there a way to tell when everything for an account has been purged, ie does the 410 return change at some point when that happens? Thanks, Matt

2 1

[all][tc] Technical Committee next weekly meeting on Dec 9th at 1500 UTC
by Ghanshyam Mann 09 Dec '21

09 Dec '21

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

1 1

[nova][placement] Cancelling Dec 21st and Dec 28th IRC meetings
by Sylvain Bauza 08 Dec '21

08 Dec '21

As we agreed on yesterday's meeting [1] we are about to cancel Dec 21st and Dec 28th meetings as we won't have a quorum for contributors during those weeks :-) -Sylvain [1] https://meetings.opendev.org/meetings/nova/2021/nova.2021-12-07-16.00.html

1 0

[Triple0] [Undercloud] Overcloud deployment getting failed at Introspection
by Lokendra Rathour 08 Dec '21

08 Dec '21

Hi Team, we are trying to deploy the triple0 Stein release on Centos 7. Undercloud is getting deployed successfully but the introspection of the overcloud node is getting failed with the reason as below: *on the DNS podman logs:* ()[root@undercloud dhcp-hostsdir]# tail -f /var/log/ironic-inspector/dnsmasq.log Dec 7 11:21:08 dnsmasq-dhcp[8]: DHCPDISCOVER(br-ctlplane) f8:f2:1e:9e:82:51 ignored Dec 7 11:21:08 dnsmasq-dhcp[8]: DHCPDISCOVER(br-ctlplane) f8:f2:1e:9e:82:50 ignored Dec 7 11:21:12 dnsmasq-dhcp[8]: DHCPDISCOVER(br-ctlplane) f8:f2:1e:9e:82:51 ignored *Checking the TCPDUMP at the same time gives:* 11:38:38.308660 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from f8:f2:1e:9e:82:51 (oui Unknown), length 300 11:38:38.435173 IP6 fe80::f53a:6448:4a29:e051 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 11:38:38.435184 IP6 fe80::f53a:6448:4a29:e051 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 11:38:41.155784 IP6 fe80::322d:3253:e3b2:316e > ff02::2: ICMP6, router solicitation, length 8 11:38:41.394304 IP6 fe80::f53a:6448:4a29:e051 > ff02::2: ICMP6, router solicitation, length 8 11:38:42.563182 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from f8:f2:1e:9e:82:50 (oui Unknown), length 300 11:38:42.611973 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from f8:f2:1e:9e:82:51 (oui Unknown), length 300 *We observed that DHCP Server is not offering the IP to the baremetal. * *DHCP discovery comes at br-ctlplane but no ip is offered.* Any input would be really helpful. Best Regards, Lokendra

2 3

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

08 Dec '21

This is a bug report from 11-24-2021 to 12-08-2021. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/1953168 ``Argument error in log message capacity filter". Assigned to caiquemello and Fix proposed. - https://bugs.launchpad.net/cinder/+bug/1952804 "cinder schedules backups on disabled backup services". Unassigned. - https://bugs.launchpad.net/cinder/+bug/1953185 "[IBM Storwize] Restore VM snapshot issue with replication volumes". Unassigned. - https://bugs.launchpad.net/cinder/+bug/1952927 "HPE 3PAR: migrating the vm attached with volume has been retyped will cause old volume to attach back again". Unassigned. - https://bugs.launchpad.net/cinder/+bug/1952805 "[posix] cinder schedules incremental backups on the wrong node". Unassigned. - https://bugs.launchpad.net/cinder/+bug/1952355 "[powerflex] Allocated capacity calculation doesn't work with powerflex driver". Unassigned. Low - https://bugs.launchpad.net/cinder/+bug/1953050 "A service should use a service specific control exchange for rpc". Fix proposed on master. *Quotas and more:* - https://bugs.launchpad.net/cinder/+bug/1952420 "Quota shows warnings on backup creation". Assigned to Gorka and Fix proposed. - https://bugs.launchpad.net/cinder/+bug/1952635 "When changing no_snapshot_gb_quota the gigabytes are wrong". Assigned to Gorka and Fix proposed. - https://bugs.launchpad.net/cinder/+bug/1952463 " Quota defaults and limits are not deleted when a volume type is deleted". Assigned to Gorka and Fix proposed. - https://bugs.launchpad.net/cinder/+bug/1952443 "Slow listings with many projects and deleted resources". Assigned to Gorka and Fix proposed. - https://bugs.launchpad.net/cinder/+bug/1952456 " Incorrect limit for private type volumes". Assigned to Gorka and Fix proposed. - https://bugs.launchpad.net/cinder/+bug/1952683 "Documentation typos". Fix proposed on master. Incomplete - https://bugs.launchpad.net/cinder/+bug/1952998 "[Ceph] Volume backup created with multiple snapshots preventing removal". 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

[ironic] [ops] RFC: deprecating instance network boot in Ironic
by Dmitry Tantsur 08 Dec '21

08 Dec '21

Hi folks, As discussed at the PTG, I'd like to collect thoughts about this proposal. I would like to deprecate support for network-booting **normal instances**. This does not concern the deployment process, ramdisk deploy or booting from volume! Historically, Ironic has been able to boot the final instances from network (or ISO in case of virtual media). This is no longer the recommended mode, except for the ramdisk deploy or boot-from-volume. It adds quite a bit of complexity to deploy interfaces and has one serious security implication: there is no way to update kernel/ramdisk once the instance is deployed (without rebuilding it). For this reason, I don't think anybody should use instance network booting in production. I would like to announce the deprecation in the Yoga cycle with the intention of removing the feature in Z. Then we can also get rid of the boot_option capability (which is not really a capability). Am I missing something? Any objections? Dmitry -- Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill

1 0

How to config vGPU in cyborg
by norman.kern 08 Dec '21

08 Dec '21

Hi guys, I want to config cyborg with kolla in openstack wallaby cluster, but I found that few docs can be found to config vGPU, Where can I find the details in configuration from openstack website? And I found another question, Cyborg can not config different types of vGPU for a pGPU. Waiting for you replies. Thanks.

1 0

[horizon] No Weekly meeting today
by vishal manchanda 08 Dec '21

08 Dec '21

Hello Team, Since there are no agenda items [1] to discuss for today's horizon weekly meeting. So let's cancel today's weekly meeting. Next weekly meeting will be on 15 December. Thanks & Regards, Vishal Manchanda [1] https://etherpad.opendev.org/p/horizon-release-priorities

1 0

[all][ptl][tc] Updates on Community wide goal: Current Active goals
by Ghanshyam Mann 08 Dec '21

08 Dec '21

Hello Everyone, You might know, TC has de-coupled the community-wide goals from the release cycle[1]. As per the new structure, community-wide goals are tied or have to be finished within the release cycle. Instead, it can have target dates which can be a particular cycle release date or multi-cycle or even in between a release cycle. Target dates will be selected by considering the amount of work needed and the community bandwidth. This will help to make sure the goal is ready to start and also continue working on the goal until work is completed. 'Secure RBAC' goal is one example of a new structure that has different milestones targeting the different set of work[2]. I think this will be helpful for PTLs and project teams to plan the active goals for their project. Current Selected (Active) Goals: ------------------------------------- We have two Selected/Active goals. The project team can start/continue working on: 1. Migrate from oslo.rootwrap to oslo.privsep [3]. This is contouring from the previous cycle. 2. Consistent and Secure Default RBAC [4]. New design/implementation details are finalized now, please read those and for any queries, plan to attend the policy popup team biweekly meeting[5]. [1] https://review.opendev.org/c/openstack/governance/+/816387 [2] https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rb… [3] https://governance.openstack.org/tc/goals/selected/migrate-to-privsep.html [4] https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rb… [5] https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popu… -gmann

1 0

Glance review party - 2021-12-10T14:00:00Z
by Cyril Roelandt 07 Dec '21

07 Dec '21

Hello, On Friday (2021-12-10), at 14:00 UTC, we will have a "review party" for Glance. The party should last 2 to 3 hours, and the goal will be to clean the backlogs of glance_store and glanceclient, and try to work on the glance backlog as well if there is enough time. If some of your patches are currently in "merge conflict", please rebase them and make sure the tests pass, which will allow us to review them. If you think some of your *Glance* patches are a top priority for the project, please answer this email with a link to them, and we will try to make time to review them on Friday. We will be using https://bluejeans.com/u/croeland to coordinate. Happy Hacking! Cyril Roelandt

1 0

[neutron] Instances can't get IP from the DHCP server in OpenStack
by 韩光宇 07 Dec '21

07 Dec '21

Hi, I'm trying to create instance in OpenStack Victoria. But, I am facing a issues about dhcp of neutron. I have OpenStack Victoria running in one baremetl server with uniontech os(a downstream of centos 8). I have a Flat network created in the range of 10.12.21.190-10.12.21.195. I selected to have a DHCP. The instance ran, and neutron-dhcp-agent.service had allocated a IP to it.  # openstack server list +--------------------------------------+-------+--------+-----------------------+----------------+--------+ | ID | Name | Status | Networks | Image | Flavor | +--------------------------------------+-------+--------+-----------------------+----------------+--------+ | 4ccae37e-fbfe-4acb-a109-e1bc9175c2e0 | inst1 | ACTIVE | provider=10.12.21.192 | centos8-server | h2 | +--------------------------------------+-------+--------+-----------------------+----------------+--------+ But the instance can't get a response from DHCP.  No any error in log. And if I setup the ip manually in the instance I can get access to the gateway, dhcp port and external network. I can catpure the DHCP request in any network device in the server, include dhcp port(10.12.21.190). But no response.  Dnsmasq process was running and had  # openstack port list +--------------------------------------+------+-------------------+-----------------------------------------------------------------------------+--------+ | ID | Name | MAC Address | Fixed IP Addresses | Status | +--------------------------------------+------+-------------------+-----------------------------------------------------------------------------+--------+ | 5ab32ca8-2d1d-47cf-9a62-7c01d21abaf0 | | fa:16:3e:1d:48:45 | ip_address='10.12.21.192', subnet_id='3daf5a55-e76a-4093-8533-78d9464b1beb' | ACTIVE | | 63fb2306-7759-4933-8d93-590e3a56f315 | | fa:16:3e:c5:59:9a | ip_address='10.12.21.190', subnet_id='3daf5a55-e76a-4093-8533-78d9464b1beb' | ACTIVE | +--------------------------------------+------+-------------------+-----------------------------------------------------------------------------+--------+ # ip netns qdhcp-ec2c4d9d-888b-4312-b0af-ab2127b76e0e (id: 0) # sudo ip netns exec qdhcp-ec2c4d9d-888b-4312-b0af-ab2127b76e0e sudo tcpdump -n -S -i tap63fb2306-77|grep DHCP ## notes: fa:16:3e:1d:48:45 is the mac of nic of inst1 dropped privs to tcpdump tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on tap63fb2306-77, link-type EN10MB (Ethernet), capture size 262144 bytes 16:47:18.194028 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:1d:48:45, length 276 16:47:21.146736 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:1d:48:45, length 276 16:47:25.226387 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:1d:48:45, length 276 more detail informations: # ps -ef|grep dnsmasq dnsmasq 7441 1 0 12月03 ? 00:00:00 dnsmasq --no-hosts --no-resolv --pid-file=/var/lib/neutron/dhcp/ec2c4d9d-888b-4312-b0af-ab2127b76e0e/pid --dhcp-hostsfile=/var/lib/neutron/dhcp/ec2c4d9d-888b-4312-b0af-ab2127b76e0e/host --addn-hosts=/var/lib/neutron/dhcp/ec2c4d9d-888b-4312-b0af-ab2127b76e0e/addn_hosts --dhcp-optsfile=/var/lib/neutron/dhcp/ec2c4d9d-888b-4312-b0af-ab2127b76e0e/opts --dhcp-leasefile=/var/lib/neutron/dhcp/ec2c4d9d-888b-4312-b0af-ab2127b76e0e/leases --dhcp-match=set:ipxe,175 --dhcp-userclass=set:ipxe6,iPXE --local-service --bind-dynamic --dhcp-range=set:subnet-3daf5a55-e76a-4093-8533-78d9464b1beb,10.12.21.0,static,255.255.255.0,86400s --dhcp-option-force=option:mtu,1500 --dhcp-lease-max=256 --conf-file= --domain=openstacklocal dnsmasq 317868 1 0 14:33 ? 00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper root 317869 317868 0 14:33 ? 00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper root 340315 317310 0 18:43 pts/2 00:00:00 grep --color=auto dnsmasq [root@a16 ~]# cat /var/lib/neutron/dhcp/ec2c4d9d-888b-4312-b0af-ab2127b76e0e/host fa:16:3e:c5:59:9a,host-10-12-21-190.openstacklocal,10.12.21.190 fa:16:3e:1d:48:45,host-10-12-21-192.openstacklocal,10.12.21.192 # ovs-vsctl show adbd4b0c-cb78-4b8f-b8a6-197c5948312c Manager "ptcp:6640:127.0.0.1" is_connected: true Bridge br0 Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure datapath_type: system Port enp5s0 Interface enp5s0 Port phy-br0 Interface phy-br0 type: patch options: {peer=int-br0} Port br0 Interface br0 type: internal Bridge br-tun Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure datapath_type: system Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=patch-tun} Bridge br-int Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure datapath_type: system Port int-br0 Interface int-br0 type: patch options: {peer=phy-br0} Port br-int Interface br-int type: internal Port tap63fb2306-77 tag: 1 Interface tap63fb2306-77 type: internal Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port qvo5ab32ca8-2d tag: 1 Interface qvo5ab32ca8-2d ovs_version: "2.13.0". # ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master ovs-system state UP group default qlen 1000 link/ether 1c:69:7a:92:be:30 brd ff:ff:ff:ff:ff:ff 3: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether ea:f5:ce:24:93:12 brd ff:ff:ff:ff:ff:ff 4: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 1c:69:7a:92:be:30 brd ff:ff:ff:ff:ff:ff inet 10.12.21.142/24 scope global br0 valid_lft forever preferred_lft forever inet6 fe80::1e69:7aff:fe92:be30/64 scope link valid_lft forever preferred_lft forever 5: br-int: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether ba:5d:16:cf:89:40 brd ff:ff:ff:ff:ff:ff inet6 fe80::b85d:16ff:fecf:8940/64 scope link valid_lft forever preferred_lft forever 9: br-tun: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 86:bb:24:69:7e:43 brd ff:ff:ff:ff:ff:ff 11: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 52:54:00:4d:96:e4 brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 12: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000 link/ether 52:54:00:4d:96:e4 brd ff:ff:ff:ff:ff:ff 13: qbr5ab32ca8-2d: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 76:0e:be:40:a6:ee brd ff:ff:ff:ff:ff:ff 14: qvo5ab32ca8-2d@qvb5ab32ca8-2d: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master ovs-system state UP group default qlen 1000 link/ether 12:90:d5:07:2a:a2 brd ff:ff:ff:ff:ff:ff inet6 fe80::1090:d5ff:fe07:2aa2/64 scope link valid_lft forever preferred_lft forever 15: qvb5ab32ca8-2d@qvo5ab32ca8-2d: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master qbr5ab32ca8-2d state UP group default qlen 1000 link/ether 76:0e:be:40:a6:ee brd ff:ff:ff:ff:ff:ff inet6 fe80::740e:beff:fe40:a6ee/64 scope link valid_lft forever preferred_lft forever 16: tap5ab32ca8-2d: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master qbr5ab32ca8-2d state UNKNOWN group default qlen 1000 link/ether fe:16:3e:1d:48:45 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fe1d:4845/64 scope link valid_lft forever preferred_lft forever # cat /etc/neutron/plugins/ml2/openvswitch_agent.ini [ovs] local_ip = 10.12.21.142 datapath_type = system bridge_mappings = provider:br0 [vxlan] enable_vxlan = true local_ip = 10.12.21.142 l2_population = true prevent_arp_spoofing = True [securitygroup] enable_security_group = True firewall_driver = neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver # cat /etc/neutron/dhcp_agent.ini [DEFAULT] interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver dhcp_driver = neutron.agent.linux.dhcp.Dnsmasq enable_isolated_metadata = true     I would very very appreciate any kind of guidance or help. Thanks, Han Guangyu

2 4

[neutron][CI] How to reduce number of rechecks - brainstorming
by Slawek Kaplonski 07 Dec '21

07 Dec '21

Hi, Recently I spent some time to check how many rechecks we need in Neutron to get patch merged and I compared it to some other OpenStack projects (see [1] for details). TL;DR - results aren't good for us and I think we really need to do something with that. Of course "easiest" thing to say is that we should fix issues which we are hitting in the CI to make jobs more stable. But it's not that easy. We are struggling with those jobs for very long time. We have CI related meeting every week and we are fixing what we can there. Unfortunately there is still bunch of issues which we can't fix so far because they are intermittent and hard to reproduce locally or in some cases the issues aren't realy related to the Neutron or there are new bugs which we need to investigate and fix :) So this is never ending battle for us. The problem is that we have to test various backends, drivers, etc. so as a result we have many jobs running on each patch - excluding UT, pep8 and docs jobs we have around 19 jobs in check and 14 jobs in gate queue. In the past we made a lot of improvements, like e.g. we improved irrelevant files lists for jobs to run less jobs on some of the patches, together with QA team we did "integrated-networking" template to run only Neutron and Nova related scenario tests in the Neutron queues, we removed and consolidated some of the jobs (there is still one patch in progress for that but it should just remove around 2 jobs from the check queue). All of that are good improvements but still not enough to make our CI really stable :/ Because of all of that, I would like to ask community about any other ideas how we can improve that. If You have any ideas, please send it in this email thread or reach out to me directly on irc. We want to discuss about them in the next video CI meeting which will be on November 30th. If You would have any idea and would like to join that discussion, You are more than welcome in that meeting of course :) [1] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/ 025759.html -- Slawek Kaplonski Principal Software Engineer Red Hat

11 19

[ops]RabbitMQ High Availability
by DHilsbos＠performair.com 06 Dec '21

06 Dec '21

All; In the time I've been part of this mailing list, the subject of RabbitMQ high availability has come up several times, and each time specific recommendations for both Rabbit and Open Stack are provided. I remember it being an A or B kind of recommendation (i.e. configure Rabbit like A1, and Open Stack like A2, OR configure Rabbit like B1, and Open Stack like B2). Unfortunately, I can't find the previous threads on this topic. Does anyone have this information, that they would care to share with me? Thank you, Dominic L. Hilsbos, MBA Vice President - Information Technology Perform Air International Inc. DHilsbos(a)PerformAir.com www.PerformAir.com

3 3

[kolla-ansible] Default masakari configuration should evacuate instances across nodes in wallaby?
by Rodrigo Lima 06 Dec '21

06 Dec '21

I'm working on upgrading an openstack farm from victoria to wallaby. After successful upgrade, I would like to enable hacluster and masakari to test HA between failing compute nodes. Everything seems to be running (pacemaker with the remote nodes OK, corosync without errors, masakari-monitors detects the 2 compute nodes online), but... when I simulate the failure of a node with shutdown, the failure and notification appears in the hostmonitor log, but the instances that were on the failed node don't evacuate, and I couldn't find documentation that explains how to do this specific configuration, if necessary. Does anyone have any ideas?

3 5

[dev][panko] deprecation doubts
by Soares Sarto, Ricardo 06 Dec '21

06 Dec '21

Hi Everyone Now that Panko has been deprecated, where are the events stored? What is the evolution strategy for OpenStack Telemetry? What is a current list of data generated by core openstack services (nova, neutron, keystone, glance, cinder, heat, etc.) to ceilometer ? (e.g. this link is from ocata … where is the current one ? https://docs.openstack.org/ocata/admin-guide/telemetry-data-collection.html ) Thank you!

1 0

OpenInfra Live - December 9, 2021 at 9am CT
by Ashlee Ferguson 06 Dec '21

06 Dec '21

Hi everyone, This week’s OpenInfra Live episode is brought to you by the OpenStack community. This new episode of the “Large Scale OpenStack” show will discuss operators' tricks and tools. In a live and direct discussion, our guests will reveal tricks and homegrown tools that they use in the trenches to keep their OpenStack clusters ticking like clockwork. Episode: Large Scale OpenStack: Operators’ tricks and tools Date and time: December 9, 2021 at 9am CT (1500 UTC) You can watch us live on: YouTube: https://www.youtube.com/watch?v=F_9KKAQE4fc LinkedIn: https://www.linkedin.com/feed/update/urn:li:ugcPost:6873686260419055616/ Facebook: https://www.facebook.com/104139126308032/posts/4596356560419577/ WeChat: recording will be posted on OpenStack WeChat after the live stream Speakers: Shatadru Bandyopadhyay (Workday) Thierry Carrez (OpenInfra Foundation) Thomas Goirand (Infomaniak) Axel Jacquet (Infomaniak) Gene Kuo (LINE) Belmiro Moreira (CERN) Arnaud Morin (OVHCloud) Adrien Pensart (OVHCloud) Have an idea for a future episode? Share it now at ideas.openinfra.live. Thanks! Ashlee Ashlee Ferguson Carlson Community & Events Open Infrastructure Foundation

1 0

[cinder] midcycle R-17 followup meeting thursday
by Brian Rosmaita 06 Dec '21

06 Dec '21

The poll results are in and our midcycle followup meeting will be held: DATE: Thursday, 9 December 2021 TIME: 1400-1430 UTC LOCATION: https://bluejeans.com/3228528973 The meeting will be recorded. The midcycle etherpad is here: https://etherpad.opendev.org/p/cinder-yoga-midcycles (Followup info starts at line 34, unless some joker has added a bunch of stuff at the top of the etherpad.) The primary topic is Gorka's proposal to revamp the quota system. There are links to the proposed spec and some POC patches on the etherpad. It's worth taking a look in advance so that we can have a short and productive meeting! cheers, brian

1 0

Re: [ops] [kolla] RabbitMQ High Availability
by Bogdan Dobrelya 06 Dec '21

06 Dec '21

> 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. 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

1 0

[cinder][OpenstackAnsible] Xena Cycle-Trailing Release Deadline
by Előd Illés 06 Dec '21

06 Dec '21

Hello teams with trailing projects, Next week is the Xena cycle-trailing release deadline [1], and all projects following the cycle-trailing release model must release their Xena deliverables by 16 December, 2021. The following trailing projects haven't been released yet for Xena: Cinder team's deliverables: - cinderlib OSA team's deliverables: - openstack-ansible-roles - openstack-ansible Patches were generated 2 weeks ago [2], feel free to update those if they are not up to date anymore. This is just a friendly reminder to allow you to release these projects in time. Do not hesitate to ping us if you have any questions or concerns. [1] https://releases.openstack.org/yoga/schedule.html#y-cycle-trail [2] https://review.opendev.org/q/topic:trailing-xena Előd Illés irc: elodilles

1 0

[neutron] Bug deputy report for week of November 29
by Lajos Katona 06 Dec '21

06 Dec '21

Hi Neutron Team I was bug deputy in neutron last week. Summary ========== 3 bugs need more attention, one is related to db upgrade (upgrade from Rocky to Stein), one bug is an issue between Nova and Neutron and related to network-vif-plug event, and one seems to be related to IPv6 Metadata. If you have time please check them and help solve them and check the reviews I linked. Needs attention ================ * "neutron-db-manage upgrade" is interrupted with error about neutron.portuplinkstatuspropagation ( https://bugs.launchpad.net/neutron/+bug/1952675 ) * VirtualInterfaceCreateException due to "Timeout waiting for [('network-vif-plugged'..." (https://bugs.launchpad.net/neutron/+bug/1944779 ) * DHCP agent fails to fully configure DHCP namespaces because of duplicate address detected (https://bugs.launchpad.net/neutron/+bug/1953165 ) ** Seems to be an issue with IPv6 metadata. Bugs with assignees =================== * Neurton linuxbridge agent does not create VXLAN interface ( https://bugs.launchpad.net/neutron/+bug/1952611 ) ** Fix proposed by mnaser to oslo.privsep: https://review.opendev.org/c/openstack/oslo.privsep/+/819996 * Segment updates may cause unnecessary overload ( https://bugs.launchpad.net/neutron/+bug/1952730 ) ** fix from rubasov: https://review.opendev.org/c/openstack/neutron/+/819777 * Cannot setup IPv6 overlay network in xena ( https://bugs.launchpad.net/neutron/+bug/1952897 ) ** https://review.opendev.org/c/openstack/neutron/+/820376 * Allow modification of max retries in OVSNeutronAgent ( https://bugs.launchpad.net/neutron/+bug/1952898 ) ** https://review.opendev.org/c/openstack/neutron/+/819816 * Gratuitous ARPs are not sent during master transition ( https://bugs.launchpad.net/neutron/+bug/1952907 ): ** Possible fix from Liu: https://review.opendev.org/c/openstack/neutron/+/712474 * On IPv6 overlay networks linuxbridge vxlans are created always on loopback device (https://bugs.launchpad.net/neutron/+bug/1953139 ): ** https://review.opendev.org/c/openstack/neutron/+/820484 RFEs ====== * [RFE] Unify quota engine API ( https://bugs.launchpad.net/neutron/+bug/1953170 ) ** We discussed the need for this rfe on last Friday's drivers meeting: https://meetings.opendev.org/meetings/neutron_drivers/2021/neutron_drivers.… Regards Lajos Katona (lajoskatona)

1 0

[kolla] Plan to deprecate binary and unify on single distrubition
by Michał Nasiadka 06 Dec '21

06 Dec '21

Hello Koalas, On the PTG we have discussed two topics: 1) Deprecate and drop binary type of Kolla images 2) Use a common base (single Linux distribution) for Kolla images This is a call for feedback - for people that have not been attending the PTG. What this essentially mean for consumers: 1) In Yoga cycle we will deprecate binary type of Kolla images, and in Z cycle those will be dropped. 2) We are not going to support CentOS Stream 9 (cs9) as a base operating system, and the source type build will rely on CentOS Stream 8 in Z release. 3) Beginning from A release Kolla will build only Debian source images - but Kolla-Ansible will still support deployment of those images on CentOS/Ubuntu/Debian Host operating systems (and Rocky Linux to be added in Yoga to that mix). Justification: The Kolla project team is limited in numbers, therefore supporting current broad mix of operating systems (especially with CentOS Stream 9 ,,on the way’’) is a significant maintenance burden. By dropping binary type of images - users would be running more tested images (since Kolla/Kolla-Ansible CI runs source images jobs as voting). In Xena we’ve already changed the default image type Kolla-Ansible uses to source. We also feel that using a unified base OS for Kolla container images is a way to remove some of the maintenance burden (including CI cycles and Request for feedback: If any of those changes is a no go from your perspective - we’d like to hear your opinions. Best regards, Michal Nasiadka

9 17

[TripleO] IPV6 Support
by Lokendra Rathour 03 Dec '21

03 Dec '21

Hi, I am trying to install the undercloud using the ipv6 address on Centos 8 using Train release. It is seen that the deployment of undercloud is getting failed with error as mentioned below. Same deployment is working in the normal ipv4 case. So Questions: 1. is IPV6 supported in TripleO , if yes then please suggest how. Error: nied", " attempt(s): 2", "2021-11-25 07:25:31,535 WARNING: 65355 -- Retrying running container: zaqar", "2021-11-25 07:25:34,887 ERROR: 65355 -- ['/usr/bin/podman', 'run', '--user', '0', '--name', 'container-puppet-zaqar', '--env', 'PUPPET_TAGS=file,file_line,concat,augeas,cron,zaqar_config', '--env', 'NAME=zaqar', '--env', 'HOSTNAME=undercloud', '--env', 'NO_ARCHIVE=', '--env', 'STEP=6', '--env', 'NET_HOST=true', '--env', 'DEBUG=False', '--volume', '/etc/localtime:/etc/localtime:ro', '--volume', '/tmp/tmp06nvxzzz:/etc/config.pp:ro', '--volume', '/etc/puppet/:/tmp/puppet-etc/:ro', '--volume', '/etc/pki/ca-trust/extracted:/etc/pki/ca-trust/extracted:ro', '--volume', '/etc/pki/tls/certs/ca-bundle.crt:/etc/pki/tls/certs/ca-bundle.crt:ro', '--volume', '/etc/pki/tls/certs/ca-bundle.trust.crt:/etc/pki/tls/certs/ca-bundle.trust.crt:ro', '--volume', '/etc/pki/tls/cert.pem:/etc/pki/tls/cert.pem:ro', '--volume', '/var/lib/config-data:/var/lib/config-data/:rw', '--volume', '/var/lib/container-puppet/puppetlabs/facter.conf:/etc/puppetlabs/facter/facter.conf:ro', '--volume', '/var/lib/container-puppet/puppetlabs/:/opt/puppetlabs/:ro', '--volume', '/dev/log:/dev/log:rw', '--rm', '--log-driver', 'k8s-file', '--log-opt', 'path=/var/log/containers/stdouts/container-puppet-zaqar.log', '--security-opt', 'label=disable', '--volume', '/usr/share/openstack-puppet/modules/:/usr/share/openstack-puppet/modules/:ro', '--entrypoint', '/var/lib/container-puppet/container-puppet.sh', '--net', 'host', '--volume', '/etc/hosts:/etc/hosts:ro', '--volume', '/var/lib/container-puppet/container-puppet.sh:/var/lib/container-puppet/container-puppet.sh:ro', 'undercloud.ctlplane.localdomain:8787/tripleotraincentos8/centos-binary-zaqar-wsgi:current-tripleo'] run failed after Error: container_linux.go:370: starting container process caused: error adding seccomp filter rule for syscall bdflush: permission denied: OCI permission denied", " attempt(s): 3", "2021-11-25 07:25:34,888 WARNING: 65355 -- Retrying running container: zaqar", "2021-11-25 07:25:34,888 ERROR: 65355 -- Failed running container for zaqar", "2021-11-25 07:25:34,888 INFO: 65355 -- Finished processing puppet configs for zaqar", "2021-11-25 07:25:34,889 ERROR: 65345 -- ERROR configuring crond", "2021-11-25 07:25:34,889 ERROR: 65345 -- ERROR configuring glance_api", "2021-11-25 07:25:34,889 ERROR: 65345 -- ERROR configuring heat_api", "2021-11-25 07:25:34,889 ERROR: 65345 -- ERROR configuring heat", "2021-11-25 07:25:34,889 ERROR: 65345 -- ERROR configuring ironic_api", "2021-11-25 07:25:34,889 ERROR: 65345 -- ERROR configuring ironic", "2021-11-25 07:25:34,889 ERROR: 65345 -- ERROR configuring ironic_inspector", "2021-11-25 07:25:34,889 ERROR: 65345 -- ERROR configuring neutron", "2021-11-25 07:25:34,889 ERROR: 65345 -- ERROR configuring iscsid", "2021-11-25 07:25:34,889 ERROR: 65345 -- ERROR configuring keystone", "2021-11-25 07:25:34,890 ERROR: 65345 -- ERROR configuring memcached", "2021-11-25 07:25:34,890 ERROR: 65345 -- ERROR configuring mistral", "2021-11-25 07:25:34,890 ERROR: 65345 -- ERROR configuring mysql", "2021-11-25 07:25:34,890 ERROR: 65345 -- ERROR configuring nova", "2021-11-25 07:25:34,890 ERROR: 65345 -- ERROR configuring rabbitmq", "2021-11-25 07:25:34,890 ERROR: 65345 -- ERROR configuring placement", "2021-11-25 07:25:34,890 ERROR: 65345 -- ERROR configuring swift", "2021-11-25 07:25:34,890 ERROR: 65345 -- ERROR configuring swift_ringbuilder", "2021-11-25 07:25:34,890 ERROR: 65345 -- ERROR configuring zaqar" ], "stderr_lines": [], "_ansible_no_log": false, "attempts": 15 } ] ] Not cleaning working directory /home/stack/tripleo-heat-installer-templates Not cleaning ansible directory /home/stack/undercloud-ansible-mw4crw92 Install artifact is located at /home/stack/undercloud-install-20211125072536.tar.bzip2 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Deployment Failed! ERROR: Heat log files: /var/log/heat-launcher/undercloud_deploy-o_qf1b4w !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Deployment failed. Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/tripleoclient/v1/tripleo_deploy.py", line 1345, in _standalone_deploy raise exceptions.DeploymentError('Deployment failed') tripleoclient.exceptions.DeploymentError: Deployment failed During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/tripleoclient/v1/tripleo_deploy.py", line 1363, in _standalone_deploy raise exceptions.DeploymentError(six.text_type(e)) tripleoclient.exceptions.DeploymentError: Deployment failed During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/cliff/app.py", line 401, in run_subcommand result = cmd.run(parsed_args) File "/usr/lib/python3.6/site-packages/cliff/command.py", line 185, in run return_code = self.take_action(parsed_args) or 0 File "/usr/lib/python3.6/site-packages/tripleoclient/v1/tripleo_deploy.py", line 1451, in take_action if self._standalone_deploy(parsed_args) != 0: File "/usr/lib/python3.6/site-packages/tripleoclient/v1/tripleo_deploy.py", line 1400, in _standalone_deploy raise exceptions.DeploymentError('Deployment failed.') tripleoclient.exceptions.DeploymentError: Deployment failed. clean_up Deploy: Deployment failed. Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/tripleoclient/v1/tripleo_deploy.py", line 1345, in _standalone_deploy raise exceptions.DeploymentError('Deployment failed') tripleoclient.exceptions.DeploymentError: Deployment failed During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/tripleoclient/v1/tripleo_deploy.py", line 1363, in _standalone_deploy raise exceptions.DeploymentError(six.text_type(e)) tripleoclient.exceptions.DeploymentError: Deployment failed During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/osc_lib/shell.py", line 136, in run ret_val = super(OpenStackShell, self).run(argv) File "/usr/lib/python3.6/site-packages/cliff/app.py", line 281, in run result = self.run_subcommand(remainder) File "/usr/lib/python3.6/site-packages/osc_lib/shell.py", line 176, in run_subcommand ret_value = super(OpenStackShell, self).run_subcommand(argv) File "/usr/lib/python3.6/site-packages/cliff/app.py", line 401, in run_subcommand result = cmd.run(parsed_args) File "/usr/lib/python3.6/site-packages/cliff/command.py", line 185, in run return_code = self.take_action(parsed_args) or 0 File "/usr/lib/python3.6/site-packages/tripleoclient/v1/tripleo_deploy.py", line 1451, in take_action if self._standalone_deploy(parsed_args) != 0: File "/usr/lib/python3.6/site-packages/tripleoclient/v1/tripleo_deploy.py", line 1400, in _standalone_deploy raise exceptions.DeploymentError('Deployment failed.') tripleoclient.exceptions.DeploymentError: Deployment failed. END return value: 1 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! An error has occured while deploying the Undercloud. See the previous output for details about what went wrong. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Command '['sudo', '--preserve-env', 'openstack', 'tripleo', 'deploy', '--standalone', '--standalone-role', 'Undercloud', '--stack', 'undercloud', '--local-domain=localdomain', '--local-ip=abce:abce:abce::1/64', '--templates=/usr/share/openstack-tripleo-heat-templates/', '--networks-file=network_data_undercloud.yaml', '--heat-native', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/undercloud.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/use-dns-for-vips.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/podman.yaml', '-e', '/home/stack/containers-prepare-parameter.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/services/ironic.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/services/ironic-inspector.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/services/mistral.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/services/zaqar-swift-backend.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/disable-telemetry.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/services/tempest.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/ssl/no-tls-endpoints-public-ip.yaml', '--deployment-user', 'stack', '--output-dir=/home/stack', '-e', '/home/stack/tripleo-config-generated-env-files/undercloud_parameters.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/tripleo-validations.yaml', '--debug', '--log-file=install-undercloud.log', '-e', '/usr/share/openstack-tripleo-heat-templates/undercloud-stack-vstate-dropin.yaml']' returned non-zero exit status 1. Command '['sudo', '--preserve-env', 'openstack', 'tripleo', 'deploy', '--standalone', '--standalone-role', 'Undercloud', '--stack', 'undercloud', '--local-domain=localdomain', '--local-ip=abce:abce:abce::1/64', '--templates=/usr/share/openstack-tripleo-heat-templates/', '--networks-file=network_data_undercloud.yaml', '--heat-native', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/undercloud.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/use-dns-for-vips.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/podman.yaml', '-e', '/home/stack/containers-prepare-parameter.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/services/ironic.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/services/ironic-inspector.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/services/mistral.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/services/zaqar-swift-backend.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/disable-telemetry.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/services/tempest.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/ssl/no-tls-endpoints-public-ip.yaml', '--deployment-user', 'stack', '--output-dir=/home/stack', '-e', '/home/stack/tripleo-config-generated-env-files/undercloud_parameters.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/tripleo-validations.yaml', '--debug', '--log-file=install-undercloud.log', '-e', '/usr/share/openstack-tripleo-heat-templates/undercloud-stack-vstate-dropin.yaml']' returned non-zero exit status 1. END return value: 1 [stack@undercloud ~]$

2 5

[all][tc] What's happening in Technical Committee: summary 3rd Dec, 21: Reading: 10 min
by Ghanshyam Mann 03 Dec '21

03 Dec '21

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * Most of the meeting discussions are summarized below (Completed or in-progress activities section). Meeting full logs are available @ - Recording: https://www.youtube.com/watch?v=PwGYse8j4UY - Topic Info logs: https://meetings.opendev.org/meetings/tc/2021/tc.2021-12-02-15.02.log.html * Next week's meeting is on IRC on 9th Dec, Thursday 15:00 UTC, feel free the topic on the agenda[1] by 8th Dec. 2. What we completed this week: ========================= * Goal proposal for RBAC is merged and the next step is to select it[2] * Add ansible-collection-kolla repo to Kolla project[3] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[4]. Open Reviews ----------------- * 9 open reviews for ongoing activities[5]. TC position on release cadence ------------------------------------- You might have seen the ML thread on the release cadence[6]. We discussed it in this week's TC meeting so that we can provide the TC stand on this. There are mixed amounts of opinions on the different proposals like doing 1-year release, no coordinated release, more releases, mixed LTS release and keeping it same which is 6-month release etc. One of the key things we discussed is how to improve the upgrade process which is one of the key points to revise the current release model. Dan made a good proposal on grenade testing the 'n-1' -> 'n' (current) and 'n-2' -> 'n' (new) so that we make sure 'n' release is upgrade-able from 'n-1' as well as 'n-2' release. For that, we need to think about the deprecation phase to be n+2 release then n+1. Along with that, we can add/improve our upgrade documentation. These are a few ideas we discussed but due to time constraints, we have not concluded yet. We will set up a separate call to continue the discussion sometime in Jan start(after the Christmas holidays) Yoga testing runtime ------------------------- We have an agreement now on Yoga testing runtime and keeping python3.6 support in Yoga, you can see the details in this ML[7] Fixing Zuul config error -------------------------- If your project is listed in zuul config error, please start planning to fix those[8] RBAC discussion: continuing from PTG ---------------------------------------------- The goal proposal is not merged and the next step is to select this goal which is in progress[8] with a good amount of positive votes and no objection yet. Community-wide goal updates ------------------------------------ * Proposed goals: ** RBAC goal is pretty much in good shape now, feel free to review it[9] * Under review: ** FIPS compatibility and compliance [10]. Adjutant need maintainers and PTLs ------------------------------------------- We are waiting to hear from Braden, Albert on permission to work on this project[11]. New project 'Skyline' proposal ------------------------------------ * TC is still waiting for skyline team to respond to open queries[12]. TC tags analysis ------------------- * TC agreed to remove the framework and it is communicated in ML[13]. Project updates ------------------- * Add NVidia vGPU plugin charm to OpenStack charms[14] * Retire js-openstack-lib [15] 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[16]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [17] 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/+/815158 [3] https://review.opendev.org/c/openstack/governance/+/819331 [4] https://etherpad.opendev.org/p/tc-yoga-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025684… [7] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026164… [8] https://etherpad.opendev.org/p/zuul-config-error-openstack [9] https://review.opendev.org/c/openstack/governance/+/818817 [10] https://review.opendev.org/c/openstack/governance/+/816587 [11] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025786… [12] https://review.opendev.org/c/openstack/governance/+/814037 [13] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025571.… [14] https://review.opendev.org/c/openstack/governance/+/819856 [15] https://review.opendev.org/c/openstack/governance/+/807163 [16] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[release] Release countdown for week R-16, Dec 06-10
by Előd Illés 03 Dec '21

03 Dec '21

Development Focus ---------------------------- The Yoga-2 milestone will happen in next month, on 06 January, 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 ---------------------------- Please remember that libraries need to be released at least once per milestone period. At milestone 2, the release team will propose releases for any library that has not been otherwise released since milestone 1. Other 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. At milestone-2 we also freeze the contents of the final release. If you have a new deliverable that should be included in the final release, you should make sure it has a deliverable file in: https://opendev.org/openstack/releases/src/branch/master/deliverables/ <https://opendev.org/openstack/releases/src/branch/master/deliverables/yoga>yoga <https://opendev.org/openstack/releases/src/branch/master/deliverables/yoga> You should request a beta release (or intermediary release) for those new deliverables by milestone-2. We understand some may not be quite ready for a full release yet, but if you have something minimally viable to get released it would be good to do a 0.x release to exercise the release tooling for your deliverables. See the MembershipFreeze description for more details: https://releases.openstack.org/ <https://releases.openstack.org/yoga/schedule.html#y-mf>yoga <https://releases.openstack.org/yoga/schedule.html#y-mf>/schedule.html# <https://releases.openstack.org/yoga/schedule.html#y-mf>y <https://releases.openstack.org/yoga/schedule.html#y-mf>-mf <https://releases.openstack.org/yoga/schedule.html#y-mf> Finally, now may be a good time for teams to check on any stable releases that need to be done for your deliverables. If you have bugfixes that have been backported, but no stable release getting those. If you are unsure what is out there committed but not released, in the openstack/releases repo, running the command "tools/list_stable_unreleased_changes.sh <cycle_name>" gives a nice report. Upcoming Deadlines & Dates ----------------------------------------- Yoga-2 Milestone:06 January, 2022 Előd Illés irc: elodilles

1 0

[ironic][meeting] Postpone meeting time until end of March 2022
by Riccardo Pittau 03 Dec '21

03 Dec '21

Hello ironicers! Due to some overlapping time with other meetings that cause me to attend to 2 (or sometimes 3.....) meetings at the same time, I'd like to propose to move the time for the weekly ironic upstream meeting 1 hour later, so from the current 15:00-16:00 UTC to 16:00-17:00 UTC, until the next Daylight saving time change that should happen at the end of March 2022. Thank you! Ciao, Riccardo

4 5

[neutron] Drivers meeting agenda - 03.12.2021
by Lajos Katona 03 Dec '21

03 Dec '21

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. I would like to discuss one bug which I feel is more an RFE: * https://bugs.launchpad.net/neutron/+bug/1952867 : [ml2][ovs] allow multiple physical networks map to one physical ovs bridge As physnet-bridge mapping is deep in Neutron I feel that a discussion is necessary to have a common understanding of the possible benefits and pitfalls of such shange. I wrote to Liu to ask him to join, but I'm not sure if he can participate. We have one more "On Demand" topic from Rodolfo: * https://review.opendev.org/c/openstack/python-openstackclient/+/819627/1: To deprecate "force" behaviour in OSC "quota" commands. This is currently the default behaviour in Neutron; what is proposed in this patch is to move Neutron to, by default, check the quota limits and use "--force" parameter to commit the quota limits without any check. [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 1

[kolla[ Issue running masakari-hostmonitor
by Chris DiLorenzo 03 Dec '21

03 Dec '21

Hello, I am running Kolla-12.0.0 with Openstack Victoria. I have mostly successfully deployed masakari. The instance monitoring works, I can set up segments in Horizon and via CLI. But I can't get masakari-hostmonitor to start: 2021-12-02 16:50:44.999 7 INFO oslo.privsep.daemon [-] Running privsep helper: ['sudo', 'privsep-helper', '--config-file', '/etc/masakari-monitors/masakari -monitors.conf', '--privsep_context', 'masakarimonitors.privsep.monitors_priv', '--privsep_sock_path', '/tmp/tmpf_65hc7m/privsep.sock'] 2021-12-02 16:50:44.892 261 INFO oslo.privsep.daemon [-] privsep daemon starting 2021-12-02 16:50:44.898 261 INFO oslo.privsep.daemon [-] privsep process running with uid/gid: 0/0 2021-12-02 16:50:44.902 261 ERROR oslo.privsep.daemon [-] [Errno 1] Operation not permitted Traceback (most recent call last): File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep/daemon.py", line 593, in helper_main Daemon(channel, context).run() File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep/daemon.py", line 403, in run self._drop_privs() File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep/daemon.py", line 439, in _drop_privs capabilities.drop_all_caps_except(self.caps, self.caps, []) File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep/capabilities.py", line 156, in drop_all_caps_except raise OSError(errno, os.strerror(errno)) PermissionError: [Errno 1] Operation not permitted 2021-12-02 16:50:45.001 7 DEBUG oslo_privsep.comm [-] EOF on privsep read channel _reader_main /var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep /comm.py:149 2021-12-02 16:50:45.475 7 WARNING oslo.privsep.daemon [-] privsep log: [Errno 1] Operation not permitted 2021-12-02 16:50:45.565 7 INFO oslo.privsep.daemon [-] Spawned new privsep daemon via rootwrap 2021-12-02 16:50:45.565 7 DEBUG oslo.privsep.daemon [-] Accepted privsep connection to /tmp/tmpf_65hc7m/privsep.sock __init__ /var/lib/kolla/venv/lib/pytho n3.8/site-packages/oslo_privsep/daemon.py:371 2021-12-02 16:50:45.467 267 INFO oslo.privsep.daemon [-] privsep daemon starting 2021-12-02 16:50:45.471 267 INFO oslo.privsep.daemon [-] privsep process running with uid/gid: 0/0 2021-12-02 16:50:45.474 267 ERROR oslo.privsep.daemon [-] [Errno 1] Operation not permitted Traceback (most recent call last): File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep/daemon.py", line 593, in helper_main Daemon(channel, context).run() File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep/daemon.py", line 403, in run self._drop_privs() File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep/daemon.py", line 439, in _drop_privs capabilities.drop_all_caps_except(self.caps, self.caps, []) File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep/capabilities.py", line 156, in drop_all_caps_except raise OSError(errno, os.strerror(errno)) PermissionError: [Errno 1] Operation not permitted sudoers in the container appears to be set up correctly. Thanks Chris

2 3

python_requires >= 3.8 during Yoga
by Stephen Finucane 03 Dec '21

03 Dec '21

gmann has been helpfully proposing patches to change the versions of Python we're testing against in Yoga. I've suggested that we might want to bump 'python_requires' in 'setup.cfg' to indicate that we no longer support any version of Python before 3.8 [1]. As gmann has noted, doing so would mean nova would no longer be installable on Python 3.6 or 3.7 and there has been a small bit of back and forth on the pros and cons of this. I'm wondering what other people's thoughts on this are. Is this something we should be doing? Should we do it for libraries too or just services? Do we ever want to do this? Thoughts, please! Stephen [1] https://review.opendev.org/c/openstack/nova/+/819194/comment/72ecf24f_2bd29…

17 61

[cyborg] Cancel IRC meeting
by Brin Zhang(张百林) 03 Dec '21

03 Dec '21

Hi all, Due to the conflict between the team members and the IRC meeting time, the IRC meeting of this week will be cancelled. If you have any questions, please feel free to ping us through ML or #openstack-cyborg channel. Thanks. brinzhang Inspur Electronic Information Industry Co.,Ltd.

1 0

[cinder] R-17 midcycle followup meeting poll
by Brian Rosmaita 02 Dec '21

02 Dec '21

We had some very useful discussions at yesterday's midcycle but ran out of time before we could discuss Gorka's new quotas proposals. It turns out that due to 8 December being a public holiday in many locations, the next Cinder meeting won't work for a video followup, so we'll hold a special half-hour video meeting on this topic next week. The meeting will be 1400-1430 UTC on one of Tuesday, Thursday, or Friday. If you have a preference, please express it in this poll: https://doodle.com/poll/mnddwtp99uu6hsuq The poll closes at 1300 UTC on Monday 6 December, and I'll announce the selected time shortly thereafter. cheers, brian

1 0

Windows imaging process
by Gaël THEROND 02 Dec '21

02 Dec '21

Hi everyone, On one of our Openstack platforms, we maintain windows based workloads. We currently have the following build process: 1°/- We download windows ISO image. 2°/- Use hyper-v to create a gold image that bring virtio drivers. 3°/- We upload this image on glance and publish it for our users. 4°/- Our users use packer to create their own windows custom image from our gold image. This workflow works pretty fine, it’s simple enough and as Microsoft isn’t releasing a new major Windows every two months it’s pretty ok not having all the steps automated until now. However, I’m wondering if there is a way to automate my first two steps using Openstack? So far, from my early tests, I didn’t managed to get all of appropriate gears to work together, did I missed something? I need to create a VM that at least can use the Windows ISO plus a virtio ISO as a second cdrom device and an additional user-data payload that will instruct the Windows installer to go automatically through the installation steps plus loads missing drivers from the virtio iso. This is perfectly working on a native kvm as you can add multiple cdrom device but I didn’t find a way to replicate that on Openstack. Starting from an unaltered Microsoft originated ISO image is a mandatory requirement for this project (Because of security constraints that I can’t have any impact on). Help from anyone that already had to deal with such situation would be very appreciated ! Thanks!

2 3

[kuryr] Propose to EOL stable branches (Stein, Rocky and Queens) for all the kuryr scope
by Maysa De Macedo Souza 02 Dec '21

02 Dec '21

Hello, We have plenty of stable branches in Kuryr repositories still open with the oldest being stable/queens. We haven't seen many backports[0] proposed to Stein, Rocky and Queens, so I would like to propose retiring these branches. Let me know if anybody is interested in keeping any of those branches. [0] https://review.opendev.org/q/(project:%255Eopenstack/kuryr.*)AND((branch:st… Thank you, Maysa Macedo.

2 3

[all][tc] Technical Committee next weekly meeting on Dec 2nd at 1500 UTC
by Ghanshyam Mann 01 Dec '21

01 Dec '21

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

1 1

[ceilometer][octavia][Victoria] No metrics from octavia loadbalancer
by Iain Stott 01 Dec '21

01 Dec '21

Has anyone had any progress on this? We are currently in the same situation, we can see if loadblancers exists, but unable to see a way to configure the polling agent to poll endpoints like v2/lbaas/loadbalancers/[ID]/stats Cheers, Iain > OK. I have some progress. I created meters.d and pollster.d (in pollsters.d I’ve created octavia.yaml with sample type gauge and unit load balancer) and now I can see some measures, but only if load balancer exists or not. > Is there any way to force dynamic pollster to ask for url v2/lbaas/loadbalancers/[ID]/stats? > Best regards > Adam Iain Stott OpenStack Engineer The Hut Group<http://www.thehutgroup.com/> Tel: Email: Iain.Stott(a)thehutgroup.com<mailto:Iain.Stott@thehutgroup.com> For the purposes of this email, the "company" means The Hut Group Limited, a company registered in England and Wales (company number 6539496) whose registered office is at Fifth Floor, Voyager House, Chicago Avenue, Manchester Airport, M90 3DQ and/or any of its respective subsidiaries. Confidentiality Notice This e-mail is confidential and intended for the use of the named recipient only. If you are not the intended recipient please notify us by telephone immediately on +44(0)1606 811888 or return it to us by e-mail. Please then delete it from your system and note that any use, dissemination, forwarding, printing or copying is strictly prohibited. Any views or opinions are solely those of the author and do not necessarily represent those of the company. Encryptions and Viruses Please note that this e-mail and any attachments have not been encrypted. They may therefore be liable to be compromised. Please also note that it is your responsibility to scan this e-mail and any attachments for viruses. We do not, to the extent permitted by law, accept any liability (whether in contract, negligence or otherwise) for any virus infection and/or external compromise of security and/or confidentiality in relation to transmissions sent by e-mail. Monitoring Activity and use of the company's systems is monitored to secure its effective use and operation and for other lawful business purposes. Communications using these systems will also be monitored and may be recorded to secure effective use and operation and for other lawful business purposes. hgvyjuv

2 1

[RDO][Meeting] December Meeting Hiatus (12/22 and 12/29)
by Amy Marrich 01 Dec '21

01 Dec '21

In today's RDO meeting we decided to cancel the meetings which would have been held on 12/22 and 12/29. We will still be holding meetings the other weeks in December in the #RDO channel on OFTC and hope to see you there. Thanks, Amy (spotz)

1 0

[cinder] : SAN migration
by Gauurav Sabharwal1 01 Dec '21

01 Dec '21

Hi Experts , I need some expert advise of one of the scenario, I have multiple isolated OpenStack cluster running with train & rocky edition. Each OpenStack cluster environment have it's own isolated infrastructure of SAN ( CISCO fabric ) & Storage ( HP, EMC & IBM). Now company planning to refresh their SAN infrastructure. By procuring new Brocade SAN switches. But there are some migration relevant challenges we have. As we understand under one cinder instance only one typer of FC zone manager is supported . Currently customer configured & managing CISCO . Is it possible to configure two different vendor FC Zone manager under one cinder instance. Migration of SAN zoning is supposedly going to be happen offline way from OpenStack point of view. We will be migrating all ports of each existing cisco fabric to Brocade with zone configuration using brocade CLI. Our main concern is that after migration How CINDER DB update new zone info & path via Brocade SAN. Regards Gauurav Sabharwal IBM India Pvt. Ltd. IBM towers Ground floor, Block -A , Plot number 26, Sector 62, Noida Gautam budhnagar UP-201307. Email:gauurav.sabharwal@in.ibm.com Mobile No.: +91-9910159277

3 3

[cinder] reminder: yoga R-17 midcycle today at 1400 utc
by Brian Rosmaita 01 Dec '21

01 Dec '21

he Cinder Yoga R-17 virtual midcycle will be held: DATE: Today, Wednesday 1 December 2021 TIME: 1400-1600 UTC LOCATION: https://bluejeans.com/3228528973 The meeting will be recorded. The midcycle etherpad is here: https://etherpad.opendev.org/p/cinder-yoga-midcycles cheers, brian

1 0