July 2021 - openstack-discuss - lists.openstack.org

OpenStack network tap interface random rxdrops for some VMs
by hai wu 21 Jul '21

21 Jul '21

There are random very slow rxdrops for certain OpenStack VMs for their network tap interfaces. Please note that this is rxdrop, NOT txdrop. I know we could tune txqueuelen and multi-queue for tap network interface txdrop issue, but is there any known way to tune for this tap network interface rxdrop issue? Thanks, Hai

3 12

[kolla][wallaby][CEPH] bluestore partions names
by Ignazio Cassano 21 Jul '21

21 Jul '21

Hello, I am going to installa ceph under kolla wallaby and I have some questions about how I must prepare partitions for bluestore on may ceph servers. Suppose I have 6 spinning disk: sdb sdc sdd sde sdf sdf And I have 1 nvme disk: nvme1 I am labelling each spinning disk as follows: sdb KOLLA_CEPH_OSD_BOOTSTRAP_1 sdc KOLLA_CEPH_OSD_BOOTSTRAP_2 and so on On nvme I create 6 partitions with the following names: KOLLA_CEPH_OSD_BOOTSTRAP_1_BS KOLLA_CEPH_OSD_BOOTSTRAP_2_BS and so on Is the above correct ? Thanks Ignazio

2 2

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

21 Jul '21

Hello, This is a bug report from 2021-14-07 to 2021-22-07. You're welcome to join the Cinder Bug Meeting today. Weekly on Wednesday at 1500 UTC on #openstack-cinder Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- High - https://bugs.launchpad.net/cinder/+bug/1936854 "instance is using the wrong scsi disk after a stop/start". Unassigned. Medium - https://bugs.launchpad.net/cinder/+bug/1936909 [Gate failure] "c-bak appears to crash during tempest.api.volume.test_volumes_backup.VolumesBackupsTest.test_backup_create_attached_volume in CentOS 8 stream job" . Unassigned. - https://bugs.launchpad.net/cinder/+bug/1936431 "Failure on restoring imported Ceph backup". Unassigned. Cheers, Sofia -- L. 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

CI hiccup
by Cédric Jeanneret 21 Jul '21

21 Jul '21

Hello folks, A broadcast to inform you there was some issue in both gerrit (review.opendev.org) and zuul earlier today (around 7am CET). While the issue was corrected in a very short time (thank you Opendev Infra folks!), there was a small issue with zuul - the CI queue got emptied at some point. There was a notification on the IRC: NOTICE: Due to a configuration error unfortunately the Zuul queue was lost. Please recheck any in-flight changes Sooo... yeah. That's about it :). Have a great day all, and be nice to the CI ;) Cheers, C. -- Cédric Jeanneret (He/Him/His) Sr. Software Engineer - OpenStack Platform Deployment Framework TC Red Hat EMEA https://www.redhat.com/

1 0

[zun] Disk quota feature
by Cristina Mayo Sarmiento 21 Jul '21

21 Jul '21

Hi, I've installed Openstack Wallaby of Ubuntu 20.04.2. I'm trying to specify quotas in zun containers but the zun-compute log's show this issue: > zun.common.exception.Invalid: Your host does not support disk quota feature. Does exists anyway to solve that? Currently, zun containers can "see" compute node device's mounted in /var completely: > node@compute:~$df -h > Filesystem Size Used Avail Use% Mounted on > udev 126G 0 126G 0% /dev > tmpfs 26G 2.4M 26G 1% /run > /dev/mapper/vg0-lv--root 98G 12G 82G 13% / > tmpfs 126G 0 126G 0% /dev/shm > tmpfs 5.0M 0 5.0M 0% /run/lock > tmpfs 126G 0 126G 0% /sys/fs/cgroup > /dev/sda3 976M 203M 707M 23% /boot > /dev/sda1 511M 7.9M 504M 2% /boot/efi > /dev/mapper/vg0-lv--var 2.9T 965M 2.8T 1% /var > /dev/loop0 56M 56M 0 100% /snap/core18/2074 > /dev/loop2 68M 68M 0 100% /snap/lxd/20326 > /dev/loop1 56M 56M 0 100% /snap/core18/1944 > /dev/loop3 32M 32M 0 100% /snap/snapd/10707 > /dev/loop5 33M 33M 0 100% /snap/snapd/12398 > /dev/loop4 70M 70M 0 100% /snap/lxd/19188 > tmpfs 26G 0 26G 0% /run/user/1000 > overlay 2.9T 965M 2.8T 1% /var/lib/docker/overlay2/0f88afac44d7a661c31d6b7eea85240a2ed8d84aec057f7f761be4a544d1e089/merged > shm 64M 0 64M 0% /var/lib/docker/containers/a4d60834a7ad753bc2971a446dd65c8acabf4d6df074eec846af0ddb2efc84c9/mounts/shm > test@container:~$df -h > df -h > Filesystem Size Used Available Use% Mounted on > overlay 2.9T 964.3M 2.7T 0% / > tmpfs 64.0M 0 64.0M 0% /dev > tmpfs 125.9G 0 125.9G 0% /sys/fs/cgroup > /dev/mapper/vg0-lv--var > 2.9T 964.3M 2.7T 0% /etc/resolv.conf > /dev/mapper/vg0-lv--var > 2.9T 964.3M 2.7T 0% /etc/hostname > /dev/mapper/vg0-lv--var > 2.9T 964.3M 2.7T 0% /etc/hosts > shm 64.0M 0 64.0M 0% /dev/shm > tmpfs 125.9G 0 125.9G 0% /proc/acpi > tmpfs 64.0M 0 64.0M 0% /proc/kcore > tmpfs 64.0M 0 64.0M 0% /proc/keys > tmpfs 64.0M 0 64.0M 0% /proc/timer_list > tmpfs 64.0M 0 64.0M 0% /proc/sched_debug > tmpfs 125.9G 0 125.9G 0% /proc/scsi > tmpfs 125.9G 0 125.9G 0% /sys/firmware Thanks in advance!

2 1

[puppet][TripleO] Is the OpenDev yum-puppetlabs mirror still used?
by Clark Boylan 20 Jul '21

20 Jul '21

Hello, The OpenDev team has been looking at our AFS disk utilization with an eye towards pruning and trimming out content that is no longer used. We've noticed that the yum-puppetlabs mirror [0] is fairly sizeable [1] and we're wondering if it is still being used. If it is still being used do you need all of the contents of the mirror or can we trim it back? Currently looks like there is content for older Fedora releases, SLES, and various puppet versions. It also looks like we may not have synced this recently (not sure why yet). Any info you can provide on how this is used is much appreciated. [0] https://mirror.iad.rax.opendev.org/yum-puppetlabs/ [1] https://grafana.opendev.org/d/T5zTt6PGk/afs?viewPanel=33&orgId=1 Clark

2 3

[dev][infra][tact-sig] Dropping debian-stretch images from OpenDev
by Jeremy Stanley 20 Jul '21

20 Jul '21

Due to storage pressure in a variety of our subsystems (node images, caches, package mirrors) we're looking at under-utilized aging platforms with an eye for cleaning those up to free some space and reduce our management overhead. High on that list are our debian-stretch nodes and associated mirroring. Stretch was released over four years ago, and became effectively obsolete when Buster was released two years ago. It reached normal EOL one year ago and has limited LTS for only another eleven months. We've had newer debian-buster images available in OpenDev for a couple of years already, and more recently debian-bullseye which is due to be officially released soon. Almost nothing uses the debian-stretch label in master branch configs according to codesearch, though I expect some projects are still relying on it to perform tests on a few of their older stable branches. They may also be relying on the inappropriately-named "debian-stable" nodeset which is based on debian-stretch, though again I see a very low incidence of it in master branches at least. If we were to drop our debian-stretch nodes and debian-stable nodeset definition, how much of an impact would it be on projects? Would a few weeks be enough time for those affected to prepare, or should we be thinking more on the order of months? -- Jeremy Stanley

1 0

[neutron] Virtual PTG October 2021
by Slawek Kaplonski 20 Jul '21

20 Jul '21

Hi, As You know our next PTG will held virtually in October. I just created Doodle [1] to collect best time slots for our team. Please feel it in before Tuesday 20.07 so I can book some slots before deadline which is July 21st. I also created etherpad [2] to collect ideas for the PTG sessions. So if You have anything what You would like to be discussed, please add it there. [1] https://doodle.com/poll/r4rc7z9mnxp4wwxa?utm_source=poll&utm_medium=link [2] https://etherpad.opendev.org/p/neutron-yoga-ptg -- Slawek Kaplonski Principal Software Engineer Red Hat

1 1

[openstack-ansible] Configure API endpoints on port 443
by Gilles Mocellin 20 Jul '21

20 Jul '21

Hi OSA users, Does someone have a guide to configure a deployment via openstack-ansible and have all API endpoints on HTTPS/443 ? Of course to distinguish the services, we should user either : - DNS names : https://image.endpointdomain.tld, https:// compute.endpointdomain.tld... - URI : https://endpointdomain.tld/image, https://endpointdomain.tld/ compute... As I understand, HAproxy configuration is really different for these cases only one frontend instead of on by service ?

2 2

[masakari] Yoga PTG planning
by Radosław Piliszek 20 Jul '21

20 Jul '21

Dears, As discussed during today's meeting [1], I have reserved the October 19 (Tuesday) 07-09 UTC timeslot in the Bexar Zoom room. I have also kickstarted the etherpad for the PTG. Please feel free to add your discussion topics. Finally, please remember to register for the PTG itself. [3] [1] https://meetings.opendev.org/meetings/masakari/2021/masakari.2021-07-20-06.… [2] https://etherpad.opendev.org/p/masakari-yoga-ptg [3] https://openinfra-ptg.eventbrite.com/ Kind regards, -yoctozepto

1 1

[TripleO] Yoga PTG timeslots vote
by Marios Andreou 20 Jul '21

20 Jul '21

Hello TripleO in case you missed the announcement from Ashlee at [1] the yoga ptg will be on October 18-22. We need to decide on the timeslot to use so we can reserve a room to meet. I started a doodle poll at [2] please indicate which time works best for you. The times in the doodle poll are UTC so you need to work out what it means for your location. I arbitrarily chose tuesday 19th but same times will apply to all days. In the last two virtual PTGs used the 1300-1700 UTC - so sanity check does this time still work best for the majority of our community? Rooms should be reserved by July 21 so lets close this poll on Tue 20 and we can discuss if needed during the scheduled irc meeting on the 20th. thanks, marios [1] http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023540.html [2] https://doodle.com/poll/mre6tghmbntbivdd

1 1

Re: Setting bandwidth limit
by Rodolfo Alonso Hernandez 20 Jul '21

20 Jul '21

Hello Felipe: Did you configure both the server and the agent? Probably you configured the server correctly, this is why you can create and apply the QoS policies. But you also need to configure the OVS agent [1]. In the plugin ML2 config (by default /etc/neutron/plugins/ml2/ml2_conf.ini), you need to configure the agent extension: [agent]extensions = qos Check this config file and then enable the OVS agent debug logs (restarting the agent). Check the logs for any QoS message there. You should also check: - For BW limit ingress rules (ingress from the VM point of view, this is the default point of view): the OVS agent creates a QoS register and a queue register in the OVS DB table. You should see them using ovs-vsctl tool. - For BW limit egress: the OVS agent modifies the port Interface table, setting the "ingress_policing_rate" and "ingress_policing_burst" (we don't do traffic shaping, we drop packets exceeding the max rate but it works). I hope that helps you to debug what is happening there. Regards. [1]https://docs.openstack.org/neutron/rocky/admin/config-qos.html On Mon, Jul 19, 2021 at 8:28 AM Felipe Mogollon <fmogollon(a)vicomtech.org> wrote: > Hi, > > I am using OVS as backend. > > I can set networking limit by QoS and openstack accepts and can check QoS > settings (bandwith, etc..) but nothing matters, I always get maximun > transfer speed. > > Regards > > Felipe > > On Fri, Jul 16, 2021 at 3:47 PM Rodolfo Alonso Hernandez < > ralonsoh(a)redhat.com> wrote: > >> Hello Felipe: >> >> What network backend are you using? OVS, SR-IOV, OVN or Linux Bridge? Or >> any other out-of-tree backend? >> >> Regards. >> >> On Fri, Jul 16, 2021 at 2:32 PM Felipe Mogollon <fmogollon(a)vicomtech.org> >> wrote: >> >>> Hi, >>> >>> I am running openstack victoria installed using packstack. >>> >>> Everything things to be fine except bandwidth limit. I have tried to >>> limit internal traffic between two instances and between instances and >>> "Internet" but I always get maximum data transfer speed. >>> >>> I have set up following rules >>> >>> openstack network qos rule create --type bandwidth-limit --max-kbps 3 >>> --max-burst-kbits 2 --ingress bw-choke >>> openstack network qos rule create --type bandwidth-limit --max-kbps 3 >>> --max-burst-kbits 2 --egress bw-choke >>> >>> and applied bw-choke policy to the internal network where my instances >>> are deployed: >>> >>> openstack network set --qos-policy bw-choke newdeploylab_private_network >>> >>> and to ports where machines connect to subnet: >>> >>> openstack port set --qos-policy bw-choke >>> 503a07b8-2da0-4abe-8251-ede648ba42b4 >>> openstack port set --qos-policy bw-choke >>> 776d5fb3-639c-47cc-9b0f-6ec855397df7 >>> >>> but nothing happens. >>> >>> Each time I try to download something from internet or copy data from an >>> instance to another I always get maximum data transfer speed. >>> >>> I have followed instructions from >>> https://docs.openstack.org/neutron/victoria/admin/config-qos.html >>> >>> Any ideas? >>> >>> >>> -- >>> <https://www.vicomtech.org> >>> >>> Juan Felipe Mogollón Rodríguez >>> Researcher | Investigador >>> >>> fmogollon(a)vicomtech.org >>> +[34] 943 30 92 30 >>> Digital Media >>> >>> <https://www.linkedin.com/company/vicomtech> >>> <https://www.youtube.com/user/VICOMTech> >>> <https://twitter.com/@Vicomtech> >>> >>> member of: <https://graphicsvision.ai/> >>> >>> La información que contiene este mensaje y sus adjuntos son >>> confidenciales y están dirigidos exclusivamente a sus destinatarios. Si >>> recibe este mensaje por error, se ruega nos lo comunique y proceda a su >>> borrado. >>> >>> The information contained in this electronic message is intended only >>> for the personal and confidential use of the recipients designated in the >>> original message. If you have received this communication in error, please >>> notify us immediately by replying to the message and deleting it from your >>> computer. >>> >>

2 1

[rpm-packaging] logging override in openstack packages
by Piotr Mossakowski 20 Jul '21

20 Jul '21

Hello, There is a logging override in almost all openstack packages, for example in nova: https://opendev.org/openstack/rpm-packaging/src/branch/stable/victoria/open… <https://opendev.org/openstack/rpm-packaging/src/branch/stable/victoria/open…> It lands in /etc/nova/nova.conf.d/010-nova.conf as stated in the spec: https://opendev.org/openstack/rpm-packaging/src/branch/stable/victoria/open… <https://opendev.org/openstack/rpm-packaging/src/branch/stable/victoria/open…> Let's assume following scenario: in kolla-ansible based deployment I want to disable logging globally using /etc/kolla/config/global.conf: [DEFAULT] log_dir = log_file = For kolla images built from RPMs, the file '/etc/nova/nova.conf.d/010-nova.conf' will override what I want to achieve by global.conf. We have a situation when kolla images log inside the container into '/var/log/nova' where there is no log rotation. There is no easy way to change that in kolla-ansible based deployments. Is there any specific reason why default logging has been hardcoded like that? Can we agree to change that situation to be able to override logging as expected? -- Pozdrawiam serdecznie / Best regards, *Piotr Mossakowski* Lead System Engineer, Product Development Services, Cloud Infra & Applications Email piotr.mossakowski(a)tietoevry.com <mailto:piotr.mossakowski@tietoevry.com>, +48795515407 <tel:%2B48795515407> Aleja Piastów 30, 71-064 Szczecin, Poland, www.tietoevry.com <http://www.tieto.com/>

3 3

[kolla][wallaby][manila] urgent: new BUG ???
by Ignazio Cassano 20 Jul '21

20 Jul '21

Hello, probably we discovered a new bug in kolla wallaby manila generic driver. Starting by victoria release, the manila share conf requires the section [glance] otherwise it cannot create the service instance. We modified the manila conf inserting the section [glance] like the following: [glance] auth_uri = http://10.102.119.194:5000 auth_url = http://10.102.119.194:35357 auth_type = password project_domain_id = default user_domain_id = default region_name = RegionOne endpoint_type = internalURL project_name = service username = glance password = password cafile = memcache_security_strategy = ENCRYPT memcache_secret_key = password memcached_servers = 10.102.119.195:11211,10.102.119.196:11211, 10.102.119.197:11211 And now it can create the service instance. Could anyone verify it, please ? Ignazio

3 3

PTG October 2021 Team Signup
by Ashlee Ferguson 19 Jul '21

19 Jul '21

Hi everyone, Last week, we announced the next PTG will held virtually from Monday, October 18 to Friday, October 22, 2021. We will have the same schedule set up available as last time with three windows of time spread across the day to cover all timezones with breaks in between. To signup your team, you must complete BOTH the survey[1] AND reserve time in the ethercalc[2] by end of day July 21. We ask that the PTL/SIG Chair/Team lead sign up for time to have their discussions with 3 rules/guidelines: 1. Cross project discussions (like SIGs or support project teams) should be scheduled towards the start of the week so that any discussions that might shape those of other teams happen first. 2. No team should sign up for more than 4 hours per UTC day to help keep participants actively engaged. 3. No team should sign up for more than 16 hours across all time slots to avoid burning out our contributors and to enable participation in multiple teams discussions. Again, you need to fill out BOTH the ethercalc AND the survey to complete your team's sign up. If you have any issues with signing up your team, due to conflict or otherwise, please let me know! While we are trying to empower you to make your own decisions as to when you meet and for how long (after all, you know your needs and teams timezones better than we do), we are here to help! Once your team is signed up, please register[3]! And remind your team to register! Registration is free, but it's important that you sign up to let us know you'll be attending because that's how you'll receive event details, passwords, and other relevant information about the PTG. Continue to visit openstack.org/ptg for updates. Ashlee [1] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2021_vptg_survey [2] Ethercalc Signup: https://ethercalc.openstack.org/8tum5yl1bx43 [3] PTG Registration: https://openinfra-ptg.eventbrite.com

1 1

[neutron] bug deputy report for week of 2021-07-12
by Rodolfo Alonso Hernandez 19 Jul '21

19 Jul '21

Hello Neutrinos: I would like to highlight https://bugs.launchpad.net/neutron/+bug/1935959. This bug has been confirmed but not assigned yet. This is the classified list of bugs: Critical: - https://bugs.launchpad.net/neutron/+bug/1935983/. “[OVN] Regression when using ML2/OVN with Neutron DHCP agent”. Assigned. - (master): https://review.opendev.org/c/openstack/neutron/+/800679 - (stable branches): https://review.opendev.org/#/q/I1a14f217d0b6bca84cd074ef5aa4e07797fdf7e0 High: - Nothing this week... Medium: - https://bugs.launchpad.net/neutron/+bug/1935959. “[OVN]Unable to access port forwarding”. Not assigned. - https://bugs.launchpad.net/neutron/+bug/1935888. “When multiple neutron servers are restarted, the update from neutron MariaDB to ovn North database is triggered, and the neutron server generates contention lock, loses lock and reports an error”. Assigned: - https://review.opendev.org/c/openstack/neutron/+/800751 Low: - https://bugs.launchpad.net/neutron/+bug/1935842. “[OVN] Set inactivity_probe for NB/SB databases”. Assigned: - https://review.opendev.org/c/openstack/neutron/+/800521 - https://bugs.launchpad.net/neutron/+bug/1936667. “Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated since Python 3.3”. Assigned: - https://review.opendev.org/c/openstack/neutron/+/801068 - https://bugs.launchpad.net/neutron/+bug/1936675. Do not coerce a subquery into a select, create a proper select condition. Assigned: - https://review.opendev.org/c/openstack/neutron/+/801076 Whishlist: - https://bugs.launchpad.net/neutron/+bug/1935847. “[RFE] Basic Authentication Support for Standalone Neutron”. Assigned. This RFE should be discussed in the Neutron Drivers meeting. - https://review.opendev.org/c/openstack/neutron/+/800410 - https://bugs.launchpad.net/neutron/+bug/1936408: [RFE] Neutron quota change should check available existing resources. Assigned. Regards.

1 0

VM Migration To New Hardware with OpenStack
by KK CHN 19 Jul '21

19 Jul '21

QUERY Section A: We are in the process of migrating VMs from a Vendor to OpenStack . The Vendor has hosted the VMs using RedHat Virtualization and HyperV around 100 VMs. Each VM size varies from 50 GB to 150 GB size. What is the best way to migrate these VMs to New Hardware infra Installed with OpenStack Ussuri. What need to be done at the existing live VMs with the Vendor and in what file format we have to ask the vendor to give the snapshot of VMs to be migrated ? I am new to the migration of VMs from a live production setup ( the present Vendor deployed VMs with all aplications running on the VM with HyperV and RedeHat KVM. ) We are also using KVM hypervisor. Kindly advise and direct me with all good practices followed to perform this migration from existing vendor to our own setup with OpenStack and KVM. Pls shed some light on this. QUERY SECTION B Another question below ffor a trail the existing vendor has given a demo VM, which is a Windows VM with an ERP application hosted on it . But the vendor handed over three files of single VM , Three qcow2 files. They handed over three qcow2 files for this VM as follows. 1. First file is OS image as qcow2 2. /boot as another qcow2 image 3. /lv-datat as another qcow2 image How to combine these files and we can create a Running VM from these files and put it on bare metal installed with KVM only. Is this possible ? How ? What need to take care while doing this operation?. your hints and direcitons highly appreciated. Thanks in Advance, Kris

3 2

openstack-nova-consoleauth/scheduler failed to start up
by Pete Zhang 19 Jul '21

19 Jul '21

We are installing openstack in a new DC and seeing openstack-nova-consoleauth/scheduler failed to start up. Checking log and found this. Host 10.160.4.5 is not allowed to connect to this MariaDB server. Three controller nodes are installed with MariaDB/Galera Cluster, none of them with this ip. -- <https://smart.salesforce.com/sig/peiyong.zhang//us_mb/default/link.html>

3 6

[kolla][wallaby] config drive vm fails live migration
by Ignazio Cassano 19 Jul '21

19 Jul '21

Hello All, I installed kolla wallaby with ubuntu source images. I have cinder installed, so live migration works but does not work with instances configured with config drive. Any help,please? Ignazio

1 1

[wallaby][neutron][ovn][vpnaas] Openstack VPNaaS with OVN Networking
by Malik Obaid 19 Jul '21

19 Jul '21

Hi, I am using Openstack Wallaby release on Ubuntu 20.04. I just want to know when openstack VPNaaS will be available with OVN networking. I would really appreciate any input in this regard. Thank you. Regards, Malik Obaid

1 0

[baremetal-sig][ironic] Tue July 13, 2021, 2pm UTC: Introduction to Bifrost
by Arne Wiebalck 19 Jul '21

19 Jul '21

Dear all, The Bare Metal SIG will meet tomorrow Tue July 13, 2021, at 2pm UTC on zoom. The meeting will feature a "topic-of-the-day" presentation by Julia Kreger (TheJulia): "Getting started with Ironic: Bifrost" Bifrost allows to install Ironic in standalone mode (without other OpenStack components) and is also often chosen as a starting point to get familiar Ironic. As usual, all details on https://etherpad.opendev.org/p/bare-metal-sig Everyone is welcome, hope to see you there! Cheers, Arne

2 1

Fwd: [Kolla] [ Kolla-Ansible] Existing Workloads getting Impacted on Upgrade
by Anirudh Gupta 17 Jul '21

17 Jul '21

Hi Team, We have deployed the Openstack Victoria release using Multinode Kolla Ansible deployment. There are 2 nodes - one for compute and other for Controller+Network Following the below link, we also upgraded the setup from Victoria to wallaby https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html During the Upgrade process, we figured out that the VM which was spawned before Upgrade went to shut off during the middle of Upgrade process and post completion of the upgrade process, we had to manually start the VM again. Ideally we were expecting that the existing Workloads would remain unimpacted in this process. Can someone please suggest if our observation is correct or any steps that needs to be taken in order to avoid this? Regards Anirudh Gupta

4 4

[Kolla][wallaby] vpnaas
by Ignazio Cassano 17 Jul '21

17 Jul '21

Hello, I tried to enable vpnaas in my global.yml file with ubuntu source images but pull action does not download any vpnaas image. Must I switch to binary or centos image type? Regards Ignazio

2 2

[all][tc] What's happening in Technical Committee: summary 16th July, 21: Reading: 5 min
by Ghanshyam Mann 17 Jul '21

17 Jul '21

Hello Everyone, Here is last week's summary of the Technical Committee activities. 1. What we completed this week: ========================= * Added Hashicorp Vault deployment repo under OpenStack-ansible project[1] * Proposed 'consistent and secure RBAC' as a community-wide goal[2] 2. TC Meetings: ============ * TC held this week meeting on Thursday; you can find the full meeting logs in the below link: - https://meetings.opendev.org/meetings/tc/2021/tc.2021-07-15-15.00.log.html * We will have next week's meeting on July 22th, Thursday 15:00 UTC[3]. 3. Activities In progress: ================== TC Tracker for Xena cycle ------------------------------ TC is using the etherpad[4] for Xena cycle working item. We will be checking and updating the status biweekly in the same etherpad. Open Reviews ----------------- * Six open reviews for ongoing activities[5]. ELK services next plan and help status --------------------------------------------- * We continue the discussion in the this week TC meeting, below is the summary: ** Help status: as of now, there are no volunteers to help. ** Clark announced the deadline (Yoga cycle end) on ML[6]. ** Clark checked the result by reducing the load on log worker as well as the ELK instance. ** Based on results, his current propose is to shrink log workers to 60% of their total size and reduce the elasticsearch cluster size by one instance. ** Before taking final decision, we will monitor the result during Xena release (when we have more load). Migration from Freenode to OFTC ----------------------------------------- * I started updating the remaining project side wiki/doc page, please review those. ** https://review.opendev.org/q/topic:%2522oftc%2522+status:open * I request to merge the current open patches ** https://review.opendev.org/q/topic:%2522oftc%2522+status:open * I am leaving the retired repo because 1. there are lot of retired repo[7] 2. it need to add gate setup in project-config to sync the change in github repo. * All the required work for this migration is tracked in this etherpad[8] Test support for TLS default: ---------------------------------- * Rico has started a separate email thread over testing with tls-proxy enabled[9], we encourage projects to participate in that testing and help to enable the tls-proxy in gate testing. Project updates: ------------------- * Retiring js-openstack-lib [10] * Properly retire neutron-lbaas[11] * Deprecate os-panko role [12] * Retire tripleo-common-tempest-plugin[13] Yoga release community-wide goal ----------------------------------------- * Please add the possible candidates in this etherpad [14]. * Current status: One goal "Secure RBAC" is proposed. Other Changes ------------------ * Defining Yoga release testing runtime15] 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://review.opendev.org/c/openstack/governance/+/799826 [2] https://review.opendev.org/c/openstack/governance/+/799705 [3] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [4] https://etherpad.opendev.org/p/tc-xena-tracker [5] https://review.opendev.org/q/project:openstack/governance+status:open [6] http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023578.html [7] https://opendev.org/openstack/governance/src/branch/master/reference/legacy… [8] https://etherpad.opendev.org/p/openstack-irc-migration-to-oftc [9] http://lists.openstack.org/pipermail/openstack-discuss/2021-June/023000.html [10] https://review.opendev.org/c/openstack/governance/+/798540 [11] https://review.opendev.org/c/openstack/governance/+/800148 [12] https://review.opendev.org/c/openstack/governance/+/799817 [13] https://review.opendev.org/c/openstack/governance/+/800432 [14] https://etherpad.opendev.org/p/y-series-goals [15] https://review.opendev.org/c/openstack/governance/+/799927 [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

1 0

[manila][ptg] Yoga cycle Project Teams Gathering information
by Goutham Pacha Ravi 16 Jul '21

16 Jul '21

Hello Zorillas and other interested stackers, We've reserved some time-slots for the upcoming Virtual Project Teams Gathering [1]. Based on experience these timings have generally worked for us, albeit they're bound to be too early or too late in some time zones. We'll try to be accommodative and schedule additional meetings if you're interested but cannot make it at the designated time. Please use the PTG Planning Etherpad at [2] to add your IRC nicknames and topics you wish to bring up. As usual, we will record all our discussions and post minutes to this mailing list, as well as upload them [3]. Will post more information closer to the event! Thanks, Goutham [1] https://ethercalc.openstack.org/8tum5yl1bx43 [2] https://etherpad.opendev.org/p/yoga-ptg-manila-planning [3] https://www.youtube.com/channel/UCCnLeIR8V1Fl7ym1c7H3e0A

1 0