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

[kolla][keystone][openstack-ansible][deploy][sdk] enforcing scope in Kolla-Ansible deployment
by James Kirsch 29 Jul '21

29 Jul '21

I'm working on adding the option to enable enforce_scope in keystone during Kolla-Ansible deployment. I've revived this transaction to complete this work: https://review.opendev.org/c/openstack/kolla-ansible/+/692179 As part of that effort, I would like to also enable enforce_new_defaults in keystone. Deployment currently fails because the nova keystone user roles created during Kolla-Ansible deployment requires system scope. I can currently get around this using python-openstack: openstack role add --system all --user d7512be612454eff8a7f5bf5476b1531 admin Kolla-ansible relies on the OpenStack Ansible modules to create users and roles for deployment. Looking around the repositories, it does not appear that the openstack ansible module nor the openstacksdk supports granting system scope to a user role. Please let me know if this is not the case or if it is in current development. Otherwise, I could use guidance on what the next steps I could take or who I should talk to so I can move this forward. Thanks, James my awesome background music: http://www.generalfuzz.net about me: http://www.headphonejames.com

3 2

[kolla] Operator pain points
by Mark Goddard 29 Jul '21

29 Jul '21

Hi, The TC is looking at community goals for the Yoga release cycle, and has proposed resolving some operator pain points [1]. These pain points are naturally project-specific, and the first step is collecting some. They are looking for 1-2 points per project, but this is an interesting feedback exercise for us, so don't hold back. Please add any significant operator pain points you have for Kolla (or other projects) to the Etherpad [2]. Thanks, Mark [1] http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023659.html [2] https://etherpad.opendev.org/p/pain-point-elimination

2 1

[Openstack][kolla][wallaby] swift installation
by Ignazio Cassano 28 Jul '21

28 Jul '21

Hello all, I want install swift but I do not have disks on controllers and on compute nodes. Is it possible to inventory a group of servers other than controllers or computes to install swift? In other words, I would like to insert in multinode inventory a new group of servers with disks for reinstalling swift. Thanks. Ignazio

2 2

[all][tc] Technical Committee next weekly meeting on July 29th at 1500 UTC
by Ghanshyam Mann 28 Jul '21

28 Jul '21

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

1 1

[tc][cinder] early removal of 'enable_v3_api' option
by Brian Rosmaita 28 Jul '21

28 Jul '21

Hello TC members, Cinder has asserted the 'assert:follows-standard-deprecation' tag. This cycle, the long-deprecated Block Storage API v2 has been removed [0], at which time the 'enable_v2_api' option was also removed (which was appropriate since the option had been deprecated since Mitaka [1]). It turns out, however, that the corresponding 'enable_v3_api' option had never been deprecated. It has been deprecated in the current development branch by [0], but the team would like to know whether it is permissible to simply remove it in Xena without deprecating it for the following reasons: - The option was introduced by [1] in Mitaka. It has always had the default value: True. - In the Xena release, if the option is False, you can deploy the Block Storage API, but the only reachable resource from the endpoint is '/versions', which returns an empty list of available versions. This doesn't seem to be something that anyone would do on purpose. - If someone wants to deploy only the Block Storage API v2, this cannot be done in Xena by setting 'enable_v3_api' to False. So for that purpose, this option is already effectively a no-op in Xena. In short, we could leave the 'enable_v3_api' option as deprecated in the Xena release, but we can't imagine any circumstances under which someone would intentionally use it in its non-default value, so it seems pointless to keep it around ... except to satisfy the 'assert:follows-standard-deprecation' tag. To be clear, the Cinder team has no intention of violating or removing the 'assert:follows-standard-deprecation' tag. The point of this email is to ask the TC whether it would be permissible to simply remove the 'enable_v3_api' option in Xena (as opposed to deprecating the option in Xena and then waiting until Yoga development to remove it). Thanks for thinking about this! [0] https://review.opendev.org/c/openstack/cinder/+/792299 [1] https://review.opendev.org/c/openstack/cinder/+/224910

2 1

[ops][nova]
by DHilsbos＠performair.com 28 Jul '21

28 Jul '21

All; I'm having a problem, though I'm not certain of the full scope. The most obvious issue is that I can't live migrate instances. The server I want to send the instance to gets filtered out, though I don't see any logs that tell me why it's being filtered out. It might be related that all of my new instances seems to land on a single host. An pointers on where to look for logs for Host Filters? Thank you, Dominic L. Hilsbos, MBA Vice President - Information Technology Perform Air International Inc. DHilsbos(a)PerformAir.com www.PerformAir.com

3 2

[nova] Early migrate error - pain point?
by DHilsbos＠performair.com 28 Jul '21

28 Jul '21

All; Yesterday I ran into an issue where a live migration errored before starting the migration itself (libvirt version incompatibility). This left the instance in an error state, even though it continued to run normally on the original host. Has anyone else run into this? Could this be a candidate for the current pain point hunt? Thank you, Dominic L. Hilsbos, MBA Vice President - Information Technology Perform Air International Inc. DHilsbos(a)PerformAir.com www.PerformAir.com

2 4

[cinder] xena R-9 virtual mid-cycle on 4 August
by Brian Rosmaita 28 Jul '21

28 Jul '21

As mentioned at today's weekly meeting, the Cinder Xena R-9 virtual mid-cycle will be held: DATE: Wednesday 4 August 2021 TIME: 1400-1600 UTC LOCATION: https://bluejeans.com/3228528973 The meeting will be recorded. Please add topics to the mid-cycle etherpad: https://etherpad.opendev.org/p/cinder-xena-mid-cycles cheers, brian

1 0

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

28 Jul '21

Hello, This is a bug report from 2021-22-07 to 2021-28-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/1937086 "extra_capabilities not added to pool stats". Assigned to Walt Boring. Medium - https://bugs.launchpad.net/cinder/+bug/1938196 "retype available volume fails with non root file access". Unassigned. - https://bugs.launchpad.net/cinder/+bug/1938240 "when the backend does not support consistency groups, creating generic groups is successful". Unassigned. - https://bugs.launchpad.net/python-cinderclient/+bug/1938203 "misleading message about api version negotiation". Unassigned. Low - https://bugs.launchpad.net/cinder/+bug/1938254 "The cinder-volume service appears to run but does not respond to requests". Unassigned. Incomplete - https://bugs.launchpad.net/cinder/+bug/1937890 "when lack of resources backup status not update". Unassigned. - https://bugs.launchpad.net/cinder/+bug/1938146 "Disabled NFS driver snapshots still appear in Error state". Unassigned. - https://bugs.launchpad.net/cinder/+bug/1938256 "Can't delete the consistency group, which this group backend does not support .'' Unassigned. Cheers -- 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

Help : mount LVM issue
by KK CHN 28 Jul '21

28 Jul '21

List, I am in the process of uploading OS and data LVM disk image from ovirt(KVM) files fo our OpenStack Ussuri setup with KVM and glance. I am able to upload the disk ( qcow2 images and profile the VM image). But I could not able to get the logical volume visible to the populated VM. Here the data volume is LVM partition as another disk image handed over to us by our service provider. here the steps I followed to get the LVM partition (/dev/vdc2) in question to get visible to our VM without success. Kindly help to solve this issue. ################################################## [root@ma-app ~]# fdisk -l Disk /dev/vda: 64.4 GB, 64424509440 bytes, 125829120 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x0009e4d7 Device Boot Start End Blocks Id System /dev/vda1 * 2048 125829086 62913519+ 83 Linux Disk /dev/vdb: 10.7 GB, 10737418240 bytes, 20971520 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/vdc: 53.7 GB, 53687091200 bytes, 104857600 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x000ac064 Device Boot Start End Blocks Id System /dev/vdc1 * 2048 2099199 1048576 83 Linux /dev/vdc2 2099200 104857599 51379200 8e Linux LVM [root@ma-app ~]# vgs VG #PV #LV #SN Attr VSize VFree rhel 1 2 0 wz--n- <49.00g 0 [root@ma-app ~]# vgs VG #PV #LV #SN Attr VSize VFree rhel 1 2 0 wz--n- <49.00g 0 [root@ma-app ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/vda1 59G 1.5G 56G 3% / devtmpfs 3.9G 0 3.9G 0% /dev tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs 3.9G 8.5M 3.9G 1% /run tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup tmpfs 783M 0 783M 0% /run/user/0 [root@ma-app ~]# vgs VG #PV #LV #SN Attr VSize VFree rhel 1 2 0 wz--n- <49.00g 0 [root@ma-app ~]# lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert root rhel -wi------- <44.00g swap rhel -wi------- 5.00g [root@ma-app ~]# vgs VG #PV #LV #SN Attr VSize VFree rhel 1 2 0 wz--n- <49.00g 0 [root@ma-app ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/vda1 59G 1.5G 56G 3% / devtmpfs 3.9G 0 3.9G 0% /dev tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs 3.9G 8.5M 3.9G 1% /run tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup tmpfs 783M 0 783M 0% /run/user/0 [root@ma-app ~]# lvdisplay --- Logical volume --- LV Path /dev/rhel/swap LV Name swap VG Name rhel LV UUID Q2X9BK-7VXr-g9BB-JA5v-K7yR-yRBf-G61vZV LV Write Access read/write LV Creation host, time localhost, 2018-04-19 12:01:04 -0400 LV Status NOT available LV Size 5.00 GiB Current LE 1280 Segments 1 Allocation inherit Read ahead sectors auto --- Logical volume --- LV Path /dev/rhel/root LV Name root VG Name rhel LV UUID laUf04-Ecwg-OHDc-vr1s-SB85-yN8O-Us116d LV Write Access read/write LV Creation host, time localhost, 2018-04-19 12:01:05 -0400 LV Status NOT available LV Size <44.00 GiB Current LE 11263 Segments 1 Allocation inherit Read ahead sectors auto [root@ma-app ~]# lvscan inactive '/dev/rhel/swap' [5.00 GiB] inherit inactive '/dev/rhel/root' [<44.00 GiB] inherit [root@ma-app ~]# pvscan PV /dev/vdc2 VG rhel lvm2 [<49.00 GiB / 0 free] Total: 1 [<49.00 GiB] / in use: 1 [<49.00 GiB] / in no VG: 0 [0 ] [root@ma-app ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/vda1 59G 1.5G 56G 3% / devtmpfs 3.9G 0 3.9G 0% /dev tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs 3.9G 8.5M 3.9G 1% /run tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup tmpfs 783M 0 783M 0% /run/user/0 [root@ma-app ~]# lvscan inactive '/dev/rhel/swap' [5.00 GiB] inherit inactive '/dev/rhel/root' [<44.00 GiB] inherit [root@ma-app ~]# vgchange -ay rhel 2 logical volume(s) in volume group "rhel" now active [root@ma-app ~]# lvscan ACTIVE '/dev/rhel/swap' [5.00 GiB] inherit ACTIVE '/dev/rhel/root' [<44.00 GiB] inherit [root@ma-app ~]# fdisk -l Disk /dev/vda: 64.4 GB, 64424509440 bytes, 125829120 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x0009e4d7 Device Boot Start End Blocks Id System /dev/vda1 * 2048 125829086 62913519+ 83 Linux Disk /dev/vdb: 10.7 GB, 10737418240 bytes, 20971520 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/vdc: 53.7 GB, 53687091200 bytes, 104857600 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x000ac064 Device Boot Start End Blocks Id System /dev/vdc1 * 2048 2099199 1048576 83 Linux /dev/vdc2 2099200 104857599 51379200 8e Linux LVM Disk /dev/mapper/rhel-swap: 5368 MB, 5368709120 bytes, 10485760 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mapper/rhel-root: 47.2 GB, 47240445952 bytes, 92266496 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes [root@ma-app ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/vda1 59G 1.5G 56G 3% / devtmpfs 3.9G 0 3.9G 0% /dev tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs 3.9G 8.5M 3.9G 1% /run tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup tmpfs 783M 0 783M 0% /run/user/0 [root@ma-app ~]# mount /dev/vdc1 /mnt [root@ma-app ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/vda1 59G 1.5G 56G 3% / devtmpfs 3.9G 0 3.9G 0% /dev tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs 3.9G 8.5M 3.9G 1% /run tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup tmpfs 783M 0 783M 0% /run/user/0 /dev/vdc1 1014M 178M 836M 18% /mnt [root@ma-app ~]# umount /mnt [root@ma-app ~]# mount /dev/vdc2 /mnt mount: unknown filesystem type 'LVM2_member' [root@ma-app ~]# How to make this /dev/vdc2(LVM partiton) attached to the VM. ? Thank you, Kris

3 2