- openstack-discuss - lists.openstack.org

[ptl] Need PTL volunteer for OpenStack Winstackers
by Ghanshyam Mann 13 Apr '23

13 Apr '23

Hi Lukas, I am reaching out to you as you were PTL for OpenStack Winstackers project in the last cycle. There is no PTL candidate for the next cycle (2023.2), and it is on the leaderless project list. Please check if you or anyone you know would like to lead this project. - https://etherpad.opendev.org/p/2023.2-leaderless Also, if anyone else would like to help leading this project, this is time to let TC knows. -gmann

7 14

[qa][patrole] Retiring Patrole project
by Ghanshyam Mann 13 Apr '23

13 Apr '23

Hello Everyone, You might know that Patrole project[1] which was created to test the RBAC but had some design challenges, and we never got much attention to this project to align it with the new SRBAC or efficient way to test the RBAC. Since the last couple of years (After AT&T's focus was changed from OpenStack), we hardly had any maintainer in this project. In this cycle, the QA team decided to retire this project. There is always an option to bring it back in OpenStack if anyone is interested in maintaining it. I have pushed the changes required for retirement, including governance change. If anyone using or interested in this project, feel free to reply here or in governance change[2]. [1] https://wiki.openstack.org/wiki/QA#Patrole_.28RETIRED.29 [2] https://review.opendev.org/c/openstack/governance/+/880014 -gmann

1 0

[heat] Performance scaling with number of resources
by John Bartelme 13 Apr '23

13 Apr '23

Hello, I'm wondering about heat performance when I scale to a larger number of resources. A single resource deploys quite quickly but when I deploy the below template it takes 2 minutes for this stack to deploy. This occurs on Antelope via DevStack on Ubuntu 22.04 as well as a full production cluster(yoga) deployed with OpenStack-Ansible on RHEL 8. Not only does this template take 2 minutes to deploy it also takes 2 minutes to update without any changes. Is there anything in the stack configuration or heat configuration I can do to speed up the process of updating the stack when very little changes? Or this something inherit in the design of heat? --- heat_template_version: 2021-04-16 description: test resources: test-resources: type: OS::Heat::ResourceGroup properties: count: 100 resource_def: type: OS::Heat::None --- A little more detail: Obviously I have no need to deploy this template but it is a much more simplified case of what I really want to deploy. I'm deploying resource groups that contain hundreds of custom resources(containing network/compute/storage etc.) that are conditionally enabled or disabled based on a JSON property array(in general only about 20 or so resources are deployed but depending on needs any one of the resources might be needed in the near future). The JSON properties array is complex enough that I really want to have it all defined so that changing a boolean value is all that is needed to turn on and off resources without having to fully write new complex heat templates. Additionally the nature of the workflow is that I want to add future resources to the existing stack. I don't change the number of the resources to the resource group, i.e. count=20 instead of 100 because when I conditionally add another resource it causes all the existing resources to be renumbered. Ideally I could rapidly modify one value to the json array and then update the stack and have it quickly modified. Thanks, john

1 0

[manila] Cancelling next week's weekly meeting
by Carlos Silva 13 Apr '23

13 Apr '23

Hello everyone! As we will have a significant drop in attendance in next week's IRC weekly meeting (Apr 20th), we will be cancelling it. The next IRC weekly meeting will be on Apr 27th. Thanks, carloss

1 0

[oslo.messaging][nova][neutron] quorum queues
by Arnaud Morin 13 Apr '23

13 Apr '23

Hey team, I am currently looking into using quorum queues (see patch [1] introduced in oslo_messaging) for openstack services (nova, neutron mostly). After switching the value to true and bootstraping a new cluster, all queues are quorum except the fanout and reply queues. I understand that transient queues are managed differently in openstack, but why is it so? I am asking this because when using rabbit in cluster mode, the quorum queues are replicated accross the cluster. But because the fanout and reply queues are not replicated, if one of the cluster is shutting down during an instance boot, the boot may endup in error (the reply queue may be on the faulty node). Is there any reason to not enable quorum on transient queues? [1] https://github.com/openstack/oslo.messaging/commit/7e8acbf87070354cd2438f3a…

1 0

Updating OS-TRAITS in placement stable/yoga and stable/zed
by Karl Kloppenborg 13 Apr '23

13 Apr '23

Hello Placement and OS-Traits teams. Karl from Openstack-Helm. After debugging a number of issues in Cyborg, it has become necessary to update the pinned OS-TRAITs version in stable/yoga and stable/zed. I have submitted the following two reviews for updating the pinned versions to 2.10.0 https://review.opendev.org/c/openstack/placement/+/880249 https://review.opendev.org/c/openstack/placement/+/880249 By merging these changes, it will allow us to continue to use vGPU capabilities in cyborg in the stable/yoga and stable/zed onwards branches. Kind Regards, -- Karl Kloppenborg, (BCompSc, CNCF-[KCNA, CKA, CKAD], LFCE, CompTIA Linux+ XK0-004) Managing Director, Invention Labs.

3 2

[Cloudkitty][ptg] CloudKitty 2023.2 Bobcat PTG outcome
by Rafael Weingärtner 13 Apr '23

13 Apr '23

Hello, Thanks to everyone who attended the CloudKitty PTG sessions, we covered a lot during the meeting. The Etherpad is available at [1]. [1] https://etherpad.opendev.org/p/march2023-ptg-cloudkitty -- Rafael Weingärtner

1 0

Does cinder-backup support multi-backend?
by wodel youchi 13 Apr '23

13 Apr '23

Hi, Could cinder-backup be configured with multiple-backends, ceph and nfs for example? Regards.

5 9

[kolla-ansible][mariadb] socat: Connection reset by peer
by Satish Patel 12 Apr '23

12 Apr '23

Folks, I am getting the following errors in logs constantly and continually. I have 3 node galera clusters. Everything looks good except this error making me nervous. I have deployed Zed release of kolla openstack. ==> /var/log/kolla/mariadb/mariadb-clustercheck.log <== 2023/04/12 02:42:16 socat[1574755] W read(7, 0x5653c4a4c000, 8192): Connection reset by peer 2023/04/12 02:42:16 socat[1574761] W read(7, 0x5653c4a4c000, 8192): Connection reset by peer 2023/04/12 02:42:16 socat[1574755] W read(6, 0x5653c4a4c000, 8192): Connection reset by peer 2023/04/12 02:42:16 socat[1574761] W read(6, 0x5653c4a4c000, 8192): Connection reset by peer 2023/04/12 02:42:18 socat[1574767] W read(7, 0x5653c4a4c000, 8192): Connection reset by peer 2023/04/12 02:42:18 socat[1574767] W read(6, 0x5653c4a4c000, 8192): Connection reset by peer

2 2

[kolla-ansible][yoga] how to configure cinder to connect to iscsi target?
by wodel youchi 12 Apr '23

12 Apr '23

Hi, I am trying to configure cinder to connect to an iscsi target. I am using targetcli as my target server. I have tested the connection from the node using iscsiadm and it works from the OS. Now I am trying to use the iscsid container to do the job. I added this to my globals.yml enable_iscsid: "yes" enable_cinder_backend_iscsi: "yes" enable_cinder_backend_lvm: "no" And I created the cinder.conf file like this [DEFAULT] enabled_backends = rbd1,nfs-1,*lvmtnas * # add follows to the end [lvmtnas] target_helper = lioadm target_protocol = iscsi target_ip_address = 20.1.0.32 (my target server) volume_backend_name = lvmtnas # volume group name created volume_group = *vg_volume01 * volume_driver = cinder.volume.drivers.lvm.LVMVolumeDriver use_chap_auth = false I did create the vg_volume01 on the LUN prior to the test. I did a deploy, the container has been created, but nothing happened, it's like I am missing something. docker logs iscsid fome one the compute nodes + sudo -E kolla_set_configs INFO:__main__:Loading config file at /var/lib/kolla/config_files/config.json INFO:__main__:Validating config file INFO:__main__:Kolla config strategy set to: COPY_ALWAYS INFO:__main__:Copying service configuration files INFO:__main__:Writing out command to execute ++ cat /run_command + CMD='iscsid -d 8 -f' + ARGS= + sudo kolla_copy_cacerts + [[ ! -n '' ]] + . kolla_extend_start ++ [[ ! -f /etc/iscsi/initiatorname.iscsi ]] + echo 'Running command: '\''iscsid -d 8 -f'\''' + exec iscsid -d 8 -f Running command: 'iscsid -d 8 -f' iscsid: sysfs_init: sysfs_path='/sys' iscsid: in ctldev_open iscsid: created NETLINK_ISCSI socket... iscsid: InitiatorName=iqn.1994-05.com.redhat:2a318909ad8 iscsid: InitiatorName=iqn.1994-05.com.redhat:2a318909ad8 iscsid: InitiatorAlias=computehci01 iscsid: Max file limits 1048576 1048576 iscsid: current time 258465 iscsid: nothing on pend_list, deactivating alarm Any idea? Regards.

2 4