October 2021 - openstack-discuss - lists.openstack.org

is OVS+DPDK useful for general purpose workload
by Satish Patel 01 Nov '21

01 Nov '21

Folks, I have deployed openstack and configured OVS-DPDK on compute nodes for high performance networking. My workload is general purpose workload like running haproxy, mysql, apache and XMPP etc. When I did load testing I found performance was average and after 200kpps packet rate I noticed packet drops. I heard and read that DPDK can handle millions of packets but in my case its not true. I am using virtio-net in guest vm which processes packets in the kernel so I believe my bottleneck is my guest VM. I don't have any guest based DPDK applications like testpmd etc. does that mean OVS+DPDK isn't useful for my cloud? How do I take advantage of OVS+DPDK with general purpose workload? Maybe I have the wrong understanding about DPDK so please help me :) Thanks ~S

2 2

Using ceph for openstack storage
by A Monster 01 Nov '21

01 Nov '21

I'm in the process of deploying an Openstack cloud and I've been aiming at maximize the number of computing node and in order to do that I've thought of using Ceph distributed storage and use an All in one openstack deployment, so that swift objects and glance's blocks are stored through Ceph. I have a total of 12 servers, so I'll end up with 1 Controller node for openstack services and use the remaining nodes for ceph cluster and computing. Is it worth it to use a ceph storage system , and what would be the minimum number of nodes required to deploy it.

2 1

Re: kolla-ansible wallaby manila ceph pacific
by wodel youchi 31 Oct '21

31 Oct '21

Hi, To *Buddhika Godakuru* I took a look into the manila-share docker deployed on my platforme and it contains the patch you mentioned in [1]. The Manila code does integrate the ceph test for version. [1] https://review.opendev.org/c/openstack/manila/+/797955 Regards. Le mar. 26 oct. 2021 à 09:06, wodel youchi <wodel.youchi(a)gmail.com> a écrit : > Hi, > My deployment is from source, and I have little experience on how to > rebuild docker images, I can perhaps pull new images (built recently I > mean). > I took a look into docker hub and there are new manila images pushed 2 > days ago. > > Regards. > > Le lun. 25 oct. 2021 à 19:23, Buddhika Godakuru <bsanjeewa(a)kln.ac.lk> a > écrit : > >> Is your deployment type is source or binary? >> If it is binay, I wonder if this patch [1] is built into the repos. >> If source, could you try rebuilding the manila docker images? >> >> [1] https://review.opendev.org/c/openstack/manila/+/797955 >> >> On Mon, 25 Oct 2021 at 20:21, wodel youchi <wodel.youchi(a)gmail.com> >> wrote: >> >>> Hi, >>> >>> I tried with pacific then with octopus, the same problem. >>> The patch was applied to kolla-ansible. >>> >>> Regards. >>> >>> Le ven. 22 oct. 2021 00:34, Goutham Pacha Ravi <gouthampravi(a)gmail.com> >>> a écrit : >>> >>>> >>>> >>>> On Thu, Oct 21, 2021 at 1:56 AM wodel youchi <wodel.youchi(a)gmail.com> >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> I did that already, I changed the keyring to "*ceph auth >>>>> get-or-create client.manila -o manila.keyring mgr 'allow rw' mon 'allow r'* >>>>> " it didn't work, then I tried with ceph octopus, same error. >>>>> I applied the patch, then I recreated the keyring for manila as >>>>> wallaby documentation, I get the error "*Bad target type 'mon-mgr'*" >>>>> >>>> >>>> Thanks, the error seems similar to this issue: >>>> https://tracker.ceph.com/issues/51039 >>>> >>>> Can you confirm the ceph version installed? On the ceph side, some >>>> changes land after GA and get back ported; >>>> >>>> >>>> >>>>> >>>>> Regards. >>>>> >>>>> Le jeu. 21 oct. 2021 à 05:29, Buddhika Godakuru <bsanjeewa(a)kln.ac.lk> >>>>> a écrit : >>>>> >>>>>> Dear Wodel, >>>>>> I think this is because manila has changed the way how to set/create >>>>>> auth ID in Wallaby for native CephFS driver. >>>>>> For the patch to work, you should change the command >>>>>> *ceph auth get-or-create client.manila mon 'allow r' mds 'allow r, >>>>>> allow rw path=/' osd 'allow rw pool=cephfs_data' mgr 'allow rw'* >>>>>> to something like, >>>>>> ceph auth get-or-create client.manila -o manila.keyring mgr 'allow >>>>>> rw' mon 'allow r' >>>>>> >>>>>> Please see Manila Wallaby CephFS Driver document [1] >>>>>> >>>>>> Hope this helps. >>>>>> >>>>>> Thank you >>>>>> [1] >>>>>> https://docs.openstack.org/manila/wallaby/admin/cephfs_driver.html#authoriz… >>>>>> >>>>>> On Wed, 20 Oct 2021 at 23:19, wodel youchi <wodel.youchi(a)gmail.com> >>>>>> wrote: >>>>>> >>>>>>> Hi, and thanks >>>>>>> >>>>>>> I tried to apply the patch, but it didn't work, this is the >>>>>>> manila-share.log. >>>>>>> By the way, I did change to caps for the manila client to what is >>>>>>> said in wallaby documentation, that is : >>>>>>> [client.manila] >>>>>>> key = keyyyyyyyy..... >>>>>>> >>>>>>> * caps mgr = "allow rw" caps mon = "allow r"* >>>>>>> >>>>>>> [root@ControllerA manila]# cat manila-share.log >>>>>>> 2021-10-20 10:03:22.286 7 INFO oslo_service.periodic_task [-] >>>>>>> Skipping periodic task update_share_usage_size because it is disabled >>>>>>> 2021-10-20 10:03:22.310 7 INFO oslo_service.service >>>>>>> [req-5b253656-4fe2-4087-b4ab-9ba2a8a0443f - - - - -] Starting 1 workers >>>>>>> 2021-10-20 10:03:22.315 30 INFO manila.service [-] Starting >>>>>>> manila-share node (version 12.0.1) >>>>>>> 2021-10-20 10:03:22.320 30 INFO manila.share.drivers.cephfs.driver >>>>>>> [req-9e549670-d131-4572-b57e-761b513abc75 - - - - -] [CEPHFS1] Cep >>>>>>> h client found, connecting... >>>>>>> 2021-10-20 10:03:22.368 30 INFO manila.share.drivers.cephfs.driver >>>>>>> [req-9e549670-d131-4572-b57e-761b513abc75 - - - - -] [CEPHFS1] Cep >>>>>>> h client connection complete. >>>>>>> 2021-10-20 10:03:22.372 30 ERROR manila.share.manager >>>>>>> [req-9e549670-d131-4572-b57e-761b513abc75 - - - - -] Error encountered >>>>>>> during i >>>>>>> n*itialization* >>>>>>> >>>>>>> * of driver CephFSDriver@ControllerA@cephfsnative1: >>>>>>> manila.exception.ShareBackendException: json_command failed - prefix=fs >>>>>>> volume ls, argdict={'format': 'json'} - exception message: Bad target type >>>>>>> 'mon-mgr'. 2021-10-20 10:03:22.372 30 ERROR manila.share.manager Traceback >>>>>>> (most recent call last): * >>>>>>> 2021-10-20 10:03:22.372 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 191, in rados_command >>>>>>> 2021-10-20 10:03:22.372 30 ERROR manila.share.manager >>>>>>> timeout=RADOS_TIMEOUT) >>>>>>> 2021-10-20 10:03:22.372 30 ERROR manila.share.manager File >>>>>>> "/usr/lib/python3.6/site-packages/ceph_argparse.py", line 1460, in json_ >>>>>>> command >>>>>>> 2021-10-20 10:03:22.372 30 ERROR manila.share.manager inbuf, >>>>>>> timeout, verbose) >>>>>>> 2021-10-20 10:03:22.372 30 ERROR manila.share.manager File >>>>>>> "/usr/lib/python3.6/site-packages/ceph_argparse.py", line 1330, in send_ >>>>>>> command_retry >>>>>>> 2021-10-20 10:03:22.372 30 ERROR manila.share.manager return >>>>>>> send_command(*args, **kwargs) >>>>>>> 2021-10-20 10:03:22.372 30 ERROR manila.share.manager File >>>>>>> "/usr/lib/python3.6/site-packages/ceph_argparse.py", line 1412, in send_ >>>>>>> command >>>>>>> 2021-10-20 10:03:22.372 30 ERROR manila.share.manager raise >>>>>>> ArgumentValid("Bad target type '{0}'".format(target[0])) >>>>>>> 2021-10-20 10:03:22.372 30 ERROR manila.share.manager >>>>>>> ceph_argparse.ArgumentValid: Bad target type 'mon-mgr' >>>>>>> 2021-10-20 10:03:22.372 30 ERROR manila.share.manager >>>>>>> 2021-10-20 10:03:22.372 30 ERROR manila.share.manager During >>>>>>> handling of the above exception, another exception occurred: >>>>>>> 2021-10-20 10:03:22.372 30 ERROR manila.share.manager >>>>>>> 2021-10-20 10:03:22.372 30 ERROR manila.share.manager Traceback >>>>>>> (most recent call last): >>>>>>> 2021-10-20 10:03:22.372 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/manager.py >>>>>>> ", line 346, in _driver_setup >>>>>>> 2021-10-20 10:03:22.372 30 ERROR manila.share.manager >>>>>>> self.driver.do_setup(ctxt) >>>>>>> 2021-10-20 10:03:22.372 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 251, in do_setup >>>>>>> 2021-10-20 10:03:22.372 30 ERROR manila.share.manager >>>>>>> volname=self.volname) >>>>>>> 2021-10-20 10:03:22.372 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 401, in volname >>>>>>> 2021-10-20 10:03:22.372 30 ERROR manila.share.manager >>>>>>> self.rados_client, "fs volume ls", json_obj=True) >>>>>>> 2021-10-20 10:03:22.372 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 205, in rados_command >>>>>>> 2021-10-20 10:03:22.372 30 ERROR manila.share.manager raise >>>>>>> exception.ShareBackendException(msg) >>>>>>> 2021-10-20 10:03:22.372 30 ERROR manila.share.manager >>>>>>> manila.exception.ShareBackendException: json_command failed - prefix=fs >>>>>>> volume >>>>>>> ls, argdict={'format': 'json'} - exception message: Bad target type >>>>>>> 'mon-mgr'. >>>>>>> 2021-10-20 10:03:22.372 30 ERROR manila.share.manager >>>>>>> 2021-10-20 10:03:26.379 30 ERROR manila.share.manager >>>>>>> [req-9e549670-d131-4572-b57e-761b513abc75 - - - - -] Error encountered >>>>>>> during i >>>>>>> nitialization of driver CephFSDriver@ControllerA@cephfsnative1: >>>>>>> manila.exception.ShareBackendException: json_command failed - prefix= >>>>>>> fs volume ls, argdict={'format': 'json'} - exception message: Bad >>>>>>> target type 'mon-mgr'. >>>>>>> 2021-10-20 10:03:26.379 30 ERROR manila.share.manager Traceback >>>>>>> (most recent call last): >>>>>>> 2021-10-20 10:03:26.379 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 191, in rados_command >>>>>>> 2021-10-20 10:03:26.379 30 ERROR manila.share.manager >>>>>>> timeout=RADOS_TIMEOUT) >>>>>>> 2021-10-20 10:03:26.379 30 ERROR manila.share.manager File >>>>>>> "/usr/lib/python3.6/site-packages/ceph_argparse.py", line 1460, in json_ >>>>>>> command >>>>>>> 2021-10-20 10:03:26.379 30 ERROR manila.share.manager inbuf, >>>>>>> timeout, verbose) >>>>>>> 2021-10-20 10:03:26.379 30 ERROR manila.share.manager File >>>>>>> "/usr/lib/python3.6/site-packages/ceph_argparse.py", line 1330, in send_ >>>>>>> command_retry >>>>>>> 2021-10-20 10:03:26.379 30 ERROR manila.share.manager return >>>>>>> send_command(*args, **kwargs) >>>>>>> 2021-10-20 10:03:26.379 30 ERROR manila.share.manager File >>>>>>> "/usr/lib/python3.6/site-packages/ceph_argparse.py", line 1412, in send_ >>>>>>> command >>>>>>> 2021-10-20 10:03:26.379 30 ERROR manila.share.manager raise >>>>>>> ArgumentValid("Bad target type '{0}'".format(target[0])) >>>>>>> 2021-10-20 10:03:26.379 30 ERROR manila.share.manager >>>>>>> ceph_argparse.ArgumentValid: Bad target type 'mon-mgr' >>>>>>> 2021-10-20 10:03:26.379 30 ERROR manila.share.manager >>>>>>> 2021-10-20 10:03:26.379 30 ERROR manila.share.manager During >>>>>>> handling of the above exception, another exception occurred: >>>>>>> 2021-10-20 10:03:26.379 30 ERROR manila.share.manager >>>>>>> 2021-10-20 10:03:26.379 30 ERROR manila.share.manager Traceback >>>>>>> (most recent call last): >>>>>>> 2021-10-20 10:03:26.379 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/manager.py >>>>>>> ", line 346, in _driver_setup >>>>>>> 2021-10-20 10:03:26.379 30 ERROR manila.share.manager >>>>>>> self.driver.do_setup(ctxt) >>>>>>> 2021-10-20 10:03:26.379 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 251, in do_setup >>>>>>> 2021-10-20 10:03:26.379 30 ERROR manila.share.manager >>>>>>> volname=self.volname) >>>>>>> 2021-10-20 10:03:26.379 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 401, in volname >>>>>>> 2021-10-20 10:03:26.379 30 ERROR manila.share.manager >>>>>>> self.rados_client, "fs volume ls", json_obj=True) >>>>>>> 2021-10-20 10:03:26.379 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 205, in rados_command >>>>>>> 2021-10-20 10:03:26.379 30 ERROR manila.share.manager raise >>>>>>> exception.ShareBackendException(msg) >>>>>>> 2021-10-20 10:03:26.379 30 ERROR manila.share.manager >>>>>>> manila.exception.ShareBackendException: json_command failed - prefix=fs >>>>>>> volume >>>>>>> ls, argdict={'format': 'json'} - exception message: Bad target type >>>>>>> 'mon-mgr'. >>>>>>> 2021-10-20 10:03:26.379 30 ERROR manila.share.manager >>>>>>> 2021-10-20 10:03:34.387 30 ERROR manila.share.manager >>>>>>> [req-9e549670-d131-4572-b57e-761b513abc75 - - - - -] Error encountered >>>>>>> during i >>>>>>> nitialization of driver CephFSDriver@ControllerA@cephfsnative1: >>>>>>> manila.exception.ShareBackendException: json_command failed - prefix= >>>>>>> fs volume ls, argdict={'format': 'json'} - exception message: Bad >>>>>>> target type 'mon-mgr'. >>>>>>> 2021-10-20 10:03:34.387 30 ERROR manila.share.manager Traceback >>>>>>> (most recent call last): >>>>>>> 2021-10-20 10:03:34.387 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 191, in rados_command >>>>>>> 2021-10-20 10:03:34.387 30 ERROR manila.share.manager >>>>>>> timeout=RADOS_TIMEOUT) >>>>>>> 2021-10-20 10:03:34.387 30 ERROR manila.share.manager File >>>>>>> "/usr/lib/python3.6/site-packages/ceph_argparse.py", line 1460, in json_ >>>>>>> command >>>>>>> 2021-10-20 10:03:34.387 30 ERROR manila.share.manager inbuf, >>>>>>> timeout, verbose) >>>>>>> 2021-10-20 10:03:34.387 30 ERROR manila.share.manager File >>>>>>> "/usr/lib/python3.6/site-packages/ceph_argparse.py", line 1330, in send_ >>>>>>> command_retry >>>>>>> 2021-10-20 10:03:34.387 30 ERROR manila.share.manager return >>>>>>> send_command(*args, **kwargs) >>>>>>> 2021-10-20 10:03:34.387 30 ERROR manila.share.manager File >>>>>>> "/usr/lib/python3.6/site-packages/ceph_argparse.py", line 1412, in send_ >>>>>>> command >>>>>>> 2021-10-20 10:03:34.387 30 ERROR manila.share.manager raise >>>>>>> ArgumentValid("Bad target type '{0}'".format(target[0])) >>>>>>> 2021-10-20 10:03:34.387 30 ERROR manila.share.manager >>>>>>> ceph_argparse.ArgumentValid: Bad target type 'mon-mgr' >>>>>>> 2021-10-20 10:03:34.387 30 ERROR manila.share.manager >>>>>>> 2021-10-20 10:03:34.387 30 ERROR manila.share.manager During >>>>>>> handling of the above exception, another exception occurred: >>>>>>> 2021-10-20 10:03:34.387 30 ERROR manila.share.manager >>>>>>> 2021-10-20 10:03:34.387 30 ERROR manila.share.manager Traceback >>>>>>> (most recent call last): >>>>>>> 2021-10-20 10:03:34.387 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/manager.py >>>>>>> ", line 346, in _driver_setup >>>>>>> 2021-10-20 10:03:34.387 30 ERROR manila.share.manager >>>>>>> self.driver.do_setup(ctxt) >>>>>>> 2021-10-20 10:03:34.387 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 251, in do_setup >>>>>>> 2021-10-20 10:03:34.387 30 ERROR manila.share.manager >>>>>>> volname=self.volname) >>>>>>> 2021-10-20 10:03:34.387 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 401, in volname >>>>>>> 2021-10-20 10:03:34.387 30 ERROR manila.share.manager >>>>>>> self.rados_client, "fs volume ls", json_obj=True) >>>>>>> 2021-10-20 10:03:34.387 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 205, in rados_command >>>>>>> 2021-10-20 10:03:34.387 30 ERROR manila.share.manager raise >>>>>>> exception.ShareBackendException(msg) >>>>>>> 2021-10-20 10:03:34.387 30 ERROR manila.share.manager >>>>>>> manila.exception.ShareBackendException: json_command failed - prefix=fs >>>>>>> volume >>>>>>> ls, argdict={'format': 'json'} - exception message: Bad target type >>>>>>> 'mon-mgr'. >>>>>>> 2021-10-20 10:03:34.387 30 ERROR manila.share.manager >>>>>>> 2021-10-20 10:03:50.404 30 ERROR manila.share.manager >>>>>>> [req-9e549670-d131-4572-b57e-761b513abc75 - - - - -] Error encountered >>>>>>> during i >>>>>>> nitialization of driver CephFSDriver@ControllerA@cephfsnative1: >>>>>>> manila.exception.ShareBackendException: json_command failed - prefix= >>>>>>> fs volume ls, argdict={'format': 'json'} - exception message: Bad >>>>>>> target type 'mon-mgr'. >>>>>>> 2021-10-20 10:03:50.404 30 ERROR manila.share.manager Traceback >>>>>>> (most recent call last): >>>>>>> 2021-10-20 10:03:50.404 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 191, in rados_command >>>>>>> 2021-10-20 10:03:50.404 30 ERROR manila.share.manager >>>>>>> timeout=RADOS_TIMEOUT) >>>>>>> 2021-10-20 10:03:50.404 30 ERROR manila.share.manager File >>>>>>> "/usr/lib/python3.6/site-packages/ceph_argparse.py", line 1460, in json_ >>>>>>> command >>>>>>> 2021-10-20 10:03:50.404 30 ERROR manila.share.manager inbuf, >>>>>>> timeout, verbose) >>>>>>> 2021-10-20 10:03:50.404 30 ERROR manila.share.manager File >>>>>>> "/usr/lib/python3.6/site-packages/ceph_argparse.py", line 1330, in send_ >>>>>>> command_retry >>>>>>> 2021-10-20 10:03:50.404 30 ERROR manila.share.manager return >>>>>>> send_command(*args, **kwargs) >>>>>>> 2021-10-20 10:03:50.404 30 ERROR manila.share.manager File >>>>>>> "/usr/lib/python3.6/site-packages/ceph_argparse.py", line 1412, in send_ >>>>>>> command >>>>>>> 2021-10-20 10:03:50.404 30 ERROR manila.share.manager raise >>>>>>> ArgumentValid("Bad target type '{0}'".format(target[0])) >>>>>>> 2021-10-20 10:03:50.404 30 ERROR manila.share.manager >>>>>>> ceph_argparse.ArgumentValid: Bad target type 'mon-mgr' >>>>>>> 2021-10-20 10:03:50.404 30 ERROR manila.share.manager >>>>>>> 2021-10-20 10:03:50.404 30 ERROR manila.share.manager During >>>>>>> handling of the above exception, another exception occurred: >>>>>>> 2021-10-20 10:03:50.404 30 ERROR manila.share.manager >>>>>>> 2021-10-20 10:03:50.404 30 ERROR manila.share.manager Traceback >>>>>>> (most recent call last): >>>>>>> 2021-10-20 10:03:50.404 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/manager.py >>>>>>> ", line 346, in _driver_setup >>>>>>> 2021-10-20 10:03:50.404 30 ERROR manila.share.manager >>>>>>> self.driver.do_setup(ctxt) >>>>>>> 2021-10-20 10:03:50.404 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 251, in do_setup >>>>>>> 2021-10-20 10:03:50.404 30 ERROR manila.share.manager >>>>>>> volname=self.volname) >>>>>>> 2021-10-20 10:03:50.404 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 401, in volname >>>>>>> 2021-10-20 10:03:50.404 30 ERROR manila.share.manager >>>>>>> self.rados_client, "fs volume ls", json_obj=True) >>>>>>> 2021-10-20 10:03:50.404 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 205, in rados_command >>>>>>> 2021-10-20 10:03:50.404 30 ERROR manila.share.manager raise >>>>>>> exception.ShareBackendException(msg) >>>>>>> 2021-10-20 10:03:50.404 30 ERROR manila.share.manager >>>>>>> manila.exception.ShareBackendException: json_command failed - prefix=fs >>>>>>> volume >>>>>>> ls, argdict={'format': 'json'} - exception message: Bad target type >>>>>>> 'mon-mgr'. >>>>>>> 2021-10-20 10:03:50.404 30 ERROR manila.share.manager >>>>>>> 2021-10-20 10:04:22.436 30 ERROR manila.share.manager >>>>>>> [req-9e549670-d131-4572-b57e-761b513abc75 - - - - -] Error encountered >>>>>>> during i >>>>>>> nitialization of driver CephFSDriver@ControllerA@cephfsnative1: >>>>>>> manila.exception.ShareBackendException: json_command failed - prefix= >>>>>>> fs volume ls, argdict={'format': 'json'} - exception message: Bad >>>>>>> target type 'mon-mgr'. >>>>>>> 2021-10-20 10:04:22.436 30 ERROR manila.share.manager Traceback >>>>>>> (most recent call last): >>>>>>> 2021-10-20 10:04:22.436 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 191, in rados_command >>>>>>> 2021-10-20 10:04:22.436 30 ERROR manila.share.manager >>>>>>> timeout=RADOS_TIMEOUT) >>>>>>> 2021-10-20 10:04:22.436 30 ERROR manila.share.manager File >>>>>>> "/usr/lib/python3.6/site-packages/ceph_argparse.py", line 1460, in json_ >>>>>>> command >>>>>>> 2021-10-20 10:04:22.436 30 ERROR manila.share.manager inbuf, >>>>>>> timeout, verbose) >>>>>>> 2021-10-20 10:04:22.436 30 ERROR manila.share.manager File >>>>>>> "/usr/lib/python3.6/site-packages/ceph_argparse.py", line 1330, in send_ >>>>>>> command_retry >>>>>>> 2021-10-20 10:04:22.436 30 ERROR manila.share.manager return >>>>>>> send_command(*args, **kwargs) >>>>>>> 2021-10-20 10:04:22.436 30 ERROR manila.share.manager File >>>>>>> "/usr/lib/python3.6/site-packages/ceph_argparse.py", line 1412, in send_ >>>>>>> command >>>>>>> 2021-10-20 10:04:22.436 30 ERROR manila.share.manager raise >>>>>>> ArgumentValid("Bad target type '{0}'".format(target[0])) >>>>>>> 2021-10-20 10:04:22.436 30 ERROR manila.share.manager >>>>>>> ceph_argparse.ArgumentValid: Bad target type 'mon-mgr' >>>>>>> 2021-10-20 10:04:22.436 30 ERROR manila.share.manager >>>>>>> 2021-10-20 10:04:22.436 30 ERROR manila.share.manager During >>>>>>> handling of the above exception, another exception occurred: >>>>>>> 2021-10-20 10:04:22.436 30 ERROR manila.share.manager >>>>>>> 2021-10-20 10:04:22.436 30 ERROR manila.share.manager Traceback >>>>>>> (most recent call last): >>>>>>> 2021-10-20 10:04:22.436 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/manager.py >>>>>>> ", line 346, in _driver_setup >>>>>>> 2021-10-20 10:04:22.436 30 ERROR manila.share.manager >>>>>>> self.driver.do_setup(ctxt) >>>>>>> 2021-10-20 10:04:22.436 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 251, in do_setup >>>>>>> 2021-10-20 10:04:22.436 30 ERROR manila.share.manager >>>>>>> volname=self.volname) >>>>>>> 2021-10-20 10:04:22.436 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 401, in volname >>>>>>> 2021-10-20 10:04:22.436 30 ERROR manila.share.manager >>>>>>> self.rados_client, "fs volume ls", json_obj=True) >>>>>>> 2021-10-20 10:04:22.436 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 205, in rados_command >>>>>>> 2021-10-20 10:04:22.436 30 ERROR manila.share.manager raise >>>>>>> exception.ShareBackendException(msg) >>>>>>> 2021-10-20 10:04:22.436 30 ERROR manila.share.manager >>>>>>> manila.exception.ShareBackendException: json_command failed - prefix=fs >>>>>>> volume >>>>>>> ls, argdict={'format': 'json'} - exception message: Bad target type >>>>>>> 'mon-mgr'. >>>>>>> 2021-10-20 10:04:22.436 30 ERROR manila.share.manager >>>>>>> 2021-10-20 10:05:26.438 30 ERROR manila.share.manager >>>>>>> [req-9e549670-d131-4572-b57e-761b513abc75 - - - - -] Error encountered >>>>>>> during i >>>>>>> nitialization of driver CephFSDriver@ControllerA@cephfsnative1: >>>>>>> manila.exception.ShareBackendException: json_command failed - prefix= >>>>>>> fs volume ls, argdict={'format': 'json'} - exception message: Bad >>>>>>> target type 'mon-mgr'. >>>>>>> 2021-10-20 10:05:26.438 30 ERROR manila.share.manager Traceback >>>>>>> (most recent call last): >>>>>>> 2021-10-20 10:05:26.438 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 191, in rados_command >>>>>>> 2021-10-20 10:05:26.438 30 ERROR manila.share.manager >>>>>>> timeout=RADOS_TIMEOUT) >>>>>>> 2021-10-20 10:05:26.438 30 ERROR manila.share.manager File >>>>>>> "/usr/lib/python3.6/site-packages/ceph_argparse.py", line 1460, in json_ >>>>>>> command >>>>>>> 2021-10-20 10:05:26.438 30 ERROR manila.share.manager inbuf, >>>>>>> timeout, verbose) >>>>>>> 2021-10-20 10:05:26.438 30 ERROR manila.share.manager File >>>>>>> "/usr/lib/python3.6/site-packages/ceph_argparse.py", line 1330, in send_ >>>>>>> command_retry >>>>>>> 2021-10-20 10:05:26.438 30 ERROR manila.share.manager return >>>>>>> send_command(*args, **kwargs) >>>>>>> 2021-10-20 10:05:26.438 30 ERROR manila.share.manager File >>>>>>> "/usr/lib/python3.6/site-packages/ceph_argparse.py", line 1412, in send_ >>>>>>> command >>>>>>> 2021-10-20 10:05:26.438 30 ERROR manila.share.manager raise >>>>>>> ArgumentValid("Bad target type '{0}'".format(target[0])) >>>>>>> 2021-10-20 10:05:26.438 30 ERROR manila.share.manager >>>>>>> ceph_argparse.ArgumentValid: Bad target type 'mon-mgr' >>>>>>> 2021-10-20 10:05:26.438 30 ERROR manila.share.manager >>>>>>> 2021-10-20 10:05:26.438 30 ERROR manila.share.manager During >>>>>>> handling of the above exception, another exception occurred: >>>>>>> 2021-10-20 10:05:26.438 30 ERROR manila.share.manager >>>>>>> 2021-10-20 10:05:26.438 30 ERROR manila.share.manager Traceback >>>>>>> (most recent call last): >>>>>>> 2021-10-20 10:05:26.438 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/manager.py >>>>>>> ", line 346, in _driver_setup >>>>>>> 2021-10-20 10:05:26.438 30 ERROR manila.share.manager >>>>>>> self.driver.do_setup(ctxt) >>>>>>> 2021-10-20 10:05:26.438 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 251, in do_setup >>>>>>> 2021-10-20 10:05:26.438 30 ERROR manila.share.manager >>>>>>> volname=self.volname) >>>>>>> 2021-10-20 10:05:26.438 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 401, in volname >>>>>>> 2021-10-20 10:05:26.438 30 ERROR manila.share.manager >>>>>>> self.rados_client, "fs volume ls", json_obj=True) >>>>>>> 2021-10-20 10:05:26.438 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 205, in rados_command >>>>>>> 2021-10-20 10:05:26.438 30 ERROR manila.share.manager raise >>>>>>> exception.ShareBackendException(msg) >>>>>>> 2021-10-20 10:05:26.438 30 ERROR manila.share.manager >>>>>>> manila.exception.ShareBackendException: json_command failed - prefix=fs >>>>>>> volume >>>>>>> ls, argdict={'format': 'json'} - exception message: Bad target type >>>>>>> 'mon-mgr'. >>>>>>> 2021-10-20 10:05:26.438 30 ERROR manila.share.manager >>>>>>> 2021-10-20 10:07:34.539 30 ERROR manila.share.manager >>>>>>> [req-9e549670-d131-4572-b57e-761b513abc75 - - - - -] Error encountered >>>>>>> during i >>>>>>> nitialization of driver CephFSDriver@ControllerA@cephfsnative1: >>>>>>> manila.exception.ShareBackendException: json_command failed - prefix= >>>>>>> fs volume ls, argdict={'format': 'json'} - exception message: Bad >>>>>>> target type 'mon-mgr'. >>>>>>> 2021-10-20 10:07:34.539 30 ERROR manila.share.manager Traceback >>>>>>> (most recent call last): >>>>>>> 2021-10-20 10:07:34.539 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 191, in rados_command >>>>>>> 2021-10-20 10:07:34.539 30 ERROR manila.share.manager >>>>>>> timeout=RADOS_TIMEOUT) >>>>>>> 2021-10-20 10:07:34.539 30 ERROR manila.share.manager File >>>>>>> "/usr/lib/python3.6/site-packages/ceph_argparse.py", line 1460, in json_ >>>>>>> command >>>>>>> 2021-10-20 10:07:34.539 30 ERROR manila.share.manager inbuf, >>>>>>> timeout, verbose) >>>>>>> 2021-10-20 10:07:34.539 30 ERROR manila.share.manager File >>>>>>> "/usr/lib/python3.6/site-packages/ceph_argparse.py", line 1330, in send_ >>>>>>> command_retry >>>>>>> 2021-10-20 10:07:34.539 30 ERROR manila.share.manager return >>>>>>> send_command(*args, **kwargs) >>>>>>> 2021-10-20 10:07:34.539 30 ERROR manila.share.manager File >>>>>>> "/usr/lib/python3.6/site-packages/ceph_argparse.py", line 1412, in send_ >>>>>>> command >>>>>>> 2021-10-20 10:07:34.539 30 ERROR manila.share.manager raise >>>>>>> ArgumentValid("Bad target type '{0}'".format(target[0])) >>>>>>> 2021-10-20 10:07:34.539 30 ERROR manila.share.manager >>>>>>> ceph_argparse.ArgumentValid: Bad target type 'mon-mgr' >>>>>>> 2021-10-20 10:07:34.539 30 ERROR manila.share.manager >>>>>>> 2021-10-20 10:07:34.539 30 ERROR manila.share.manager During >>>>>>> handling of the above exception, another exception occurred: >>>>>>> 2021-10-20 10:07:34.539 30 ERROR manila.share.manager >>>>>>> 2021-10-20 10:07:34.539 30 ERROR manila.share.manager Traceback >>>>>>> (most recent call last): >>>>>>> 2021-10-20 10:07:34.539 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/manager.py >>>>>>> ", line 346, in _driver_setup >>>>>>> 2021-10-20 10:07:34.539 30 ERROR manila.share.manager >>>>>>> self.driver.do_setup(ctxt) >>>>>>> 2021-10-20 10:07:34.539 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 251, in do_setup >>>>>>> 2021-10-20 10:07:34.539 30 ERROR manila.share.manager >>>>>>> volname=self.volname) >>>>>>> 2021-10-20 10:07:34.539 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 401, in volname >>>>>>> 2021-10-20 10:07:34.539 30 ERROR manila.share.manager >>>>>>> self.rados_client, "fs volume ls", json_obj=True) >>>>>>> 2021-10-20 10:07:34.539 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 205, in rados_command >>>>>>> 2021-10-20 10:07:34.539 30 ERROR manila.share.manager raise >>>>>>> exception.ShareBackendException(msg) >>>>>>> 2021-10-20 10:07:34.539 30 ERROR manila.share.manager >>>>>>> manila.exception.ShareBackendException: json_command failed - prefix=fs >>>>>>> volume >>>>>>> ls, argdict={'format': 'json'} - exception message: Bad target type >>>>>>> 'mon-mgr'. >>>>>>> 2021-10-20 10:07:34.539 30 ERROR manila.share.manager >>>>>>> 2021-10-20 10:11:50.596 30 ERROR manila.share.manager >>>>>>> [req-9e549670-d131-4572-b57e-761b513abc75 - - - - -] Error encountered >>>>>>> during i >>>>>>> nitialization of driver CephFSDriver@ControllerA@cephfsnative1: >>>>>>> manila.exception.ShareBackendException: json_command failed - prefix= >>>>>>> fs volume ls, argdict={'format': 'json'} - exception message: Bad >>>>>>> target type 'mon-mgr'. >>>>>>> 2021-10-20 10:11:50.596 30 ERROR manila.share.manager Traceback >>>>>>> (most recent call last): >>>>>>> 2021-10-20 10:11:50.596 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 191, in rados_command >>>>>>> 2021-10-20 10:11:50.596 30 ERROR manila.share.manager >>>>>>> timeout=RADOS_TIMEOUT) >>>>>>> 2021-10-20 10:11:50.596 30 ERROR manila.share.manager File >>>>>>> "/usr/lib/python3.6/site-packages/ceph_argparse.py", line 1460, in json_ >>>>>>> command >>>>>>> 2021-10-20 10:11:50.596 30 ERROR manila.share.manager inbuf, >>>>>>> timeout, verbose) >>>>>>> 2021-10-20 10:11:50.596 30 ERROR manila.share.manager File >>>>>>> "/usr/lib/python3.6/site-packages/ceph_argparse.py", line 1330, in send_ >>>>>>> command_retry >>>>>>> 2021-10-20 10:11:50.596 30 ERROR manila.share.manager return >>>>>>> send_command(*args, **kwargs) >>>>>>> 2021-10-20 10:11:50.596 30 ERROR manila.share.manager File >>>>>>> "/usr/lib/python3.6/site-packages/ceph_argparse.py", line 1412, in send_ >>>>>>> command >>>>>>> 2021-10-20 10:11:50.596 30 ERROR manila.share.manager raise >>>>>>> ArgumentValid("Bad target type '{0}'".format(target[0])) >>>>>>> 2021-10-20 10:11:50.596 30 ERROR manila.share.manager >>>>>>> ceph_argparse.ArgumentValid: Bad target type 'mon-mgr' >>>>>>> 2021-10-20 10:11:50.596 30 ERROR manila.share.manager >>>>>>> 2021-10-20 10:11:50.596 30 ERROR manila.share.manager During >>>>>>> handling of the above exception, another exception occurred: >>>>>>> 2021-10-20 10:11:50.596 30 ERROR manila.share.manager >>>>>>> 2021-10-20 10:11:50.596 30 ERROR manila.share.manager Traceback >>>>>>> (most recent call last): >>>>>>> 2021-10-20 10:11:50.596 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/manager.py >>>>>>> ", line 346, in _driver_setup >>>>>>> 2021-10-20 10:11:50.596 30 ERROR manila.share.manager >>>>>>> self.driver.do_setup(ctxt) >>>>>>> 2021-10-20 10:11:50.596 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 251, in do_setup >>>>>>> 2021-10-20 10:11:50.596 30 ERROR manila.share.manager >>>>>>> volname=self.volname) >>>>>>> 2021-10-20 10:11:50.596 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 401, in volname >>>>>>> 2021-10-20 10:11:50.596 30 ERROR manila.share.manager >>>>>>> self.rados_client, "fs volume ls", json_obj=True) >>>>>>> 2021-10-20 10:11:50.596 30 ERROR manila.share.manager File >>>>>>> "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/ce >>>>>>> phfs/driver.py", line 205, in rados_command >>>>>>> 2021-10-20 10:11:50.596 30 ERROR manila.share.manager raise >>>>>>> exception.ShareBackendException(msg) >>>>>>> 2021-10-20 10:11:50.596 30 ERROR manila.share.manager >>>>>>> manila.exception.ShareBackendException: json_command failed - prefix=fs >>>>>>> volume >>>>>>> ls, argdict={'format': 'json'} - exception message: Bad target type >>>>>>> 'mon-mgr'. >>>>>>> 2021-10-20 10:11:50.596 30 ERROR manila.share.manager >>>>>>> >>>>>>> Regards >>>>>>> >>>>>>> Le mer. 20 oct. 2021 à 00:14, Goutham Pacha Ravi < >>>>>>> gouthampravi(a)gmail.com> a écrit : >>>>>>> >>>>>>>> >>>>>>>> On Tue, Oct 19, 2021 at 2:35 PM wodel youchi < >>>>>>>> wodel.youchi(a)gmail.com> wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> Has anyone been successful in deploying Manila wallaby using >>>>>>>>> kolla-ansible with ceph pacific as a backend? >>>>>>>>> >>>>>>>>> I have created the manila client in ceph pacific like this : >>>>>>>>> >>>>>>>>> *ceph auth get-or-create client.manila mon 'allow r' mds 'allow r, >>>>>>>>> allow rw path=/' osd 'allow rw pool=cephfs_data' mgr 'allow rw'* >>>>>>>>> >>>>>>>>> When I deploy, I get this error in manila's log file : >>>>>>>>> Bad target type 'mon-mgr' >>>>>>>>> Any ideas? >>>>>>>>> >>>>>>>> >>>>>>>> Could you share the full log from the manila-share service? >>>>>>>> There's an open bug related to manila/cephfs deployment: >>>>>>>> https://bugs.launchpad.net/kolla-ansible/+bug/1935784 >>>>>>>> Proposed fix: >>>>>>>> https://review.opendev.org/c/openstack/kolla-ansible/+/802743 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> Regards. >>>>>>>>> >>>>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> බුද්ධික සංජීව ගොඩාකුරු >>>>>> Buddhika Sanjeewa Godakuru >>>>>> >>>>>> Systems Analyst/Programmer >>>>>> Deputy Webmaster / University of Kelaniya >>>>>> >>>>>> Information and Communication Technology Centre (ICTC) >>>>>> University of Kelaniya, Sri Lanka, >>>>>> Kelaniya, >>>>>> Sri Lanka. >>>>>> >>>>>> Mobile : (+94) 071 5696981 >>>>>> Office : (+94) 011 2903420 / 2903424 >>>>>> >>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>>>> University of Kelaniya Sri Lanka, accepts no liability for the >>>>>> content of this email, or for the consequences of any actions taken on the >>>>>> basis of the information provided, unless that information is subsequently >>>>>> confirmed in writing. If you are not the intended recipient, this email >>>>>> and/or any information it contains should not be copied, disclosed, >>>>>> retained or used by you or any other party and the email and all its >>>>>> contents should be promptly deleted fully from our system and the sender >>>>>> informed. >>>>>> >>>>>> E-mail transmission cannot be guaranteed to be secure or error-free >>>>>> as information could be intercepted, corrupted, lost, destroyed, arrive >>>>>> late or incomplete. >>>>>> >>>>>> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>>>> >>>>> >> >> -- >> >> බුද්ධික සංජීව ගොඩාකුරු >> Buddhika Sanjeewa Godakuru >> >> Systems Analyst/Programmer >> Deputy Webmaster / University of Kelaniya >> >> Information and Communication Technology Centre (ICTC) >> University of Kelaniya, Sri Lanka, >> Kelaniya, >> Sri Lanka. >> >> Mobile : (+94) 071 5696981 >> Office : (+94) 011 2903420 / 2903424 >> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> University of Kelaniya Sri Lanka, accepts no liability for the content of >> this email, or for the consequences of any actions taken on the basis of >> the information provided, unless that information is subsequently confirmed >> in writing. If you are not the intended recipient, this email and/or any >> information it contains should not be copied, disclosed, retained or used >> by you or any other party and the email and all its contents should be >> promptly deleted fully from our system and the sender informed. >> >> E-mail transmission cannot be guaranteed to be secure or error-free as >> information could be intercepted, corrupted, lost, destroyed, arrive late >> or incomplete. >> >> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> >

3 3

[kuryr][ptg] Yoga cycle PTG summary
by Maysa De Macedo Souza 30 Oct '21

30 Oct '21

Hello, I would like to thank you for the great discussion and engagement during the PTG sessions. It was a really productive week. Here follows the summary of the Kuryr sessions during the PTG: *Day 1 - Tuesday* Etherpad: https://etherpad.opendev.org/p/kuryr-yoga-ptg - Xena retrospective: - We celebrated the contributions from many Outreachy applicants and the interns. - The addition of new features, such as: - The Reconciliation mechanisms that enforces the matching of a Kubernetes Service with a load-balancer. - The setting of Octavia Listener timeout based on annotation of the Kubernetes Service. - Improvements on the logs to facilitate debuggability and troubleshooting. - Usage of Kubeadm to facilitate configuration of Kubernetes cluster with Devstack. - Many documentation improvements. - Stable branches: - We have many stable branches which are not highly maintained anymore - action items: EOL the branches till Stein - As we currently release with OpenStack, it was proposed that we release with Kubernetes - action items: Keep following the OpenStack release, but make sure that when there is a Kubernetes release it's updated in Kuryr. - Future of the CI: - action items: - Move all the gates to use CRI-O and have one with Docker. - Attempt to remove the Amphora dependency for the API load-balancer when OVN Octavia driver is available. - Move the jobs that use OVN to voting. - Rate limit requests: - Possibility to limit the requests to Octavia during the reconciliation between load-balancers and Kubernetes Service . - Possibility to limit the amount of requests sent to Neutron *Day 2 - Wednesday* Etherpad: https://etherpad.opendev.org/p/kuryr-yoga-ptg - Merge of Kuryr lib into Kuryr-kubernetes: - action items: analyze the feasibility of moving the needed pieces into Kuryr-kubernetes and sync with other projects that use it. - Different log levels: - action items: - clean up some unnecessary debugging messages and move the level of some to warning or info. - Feasibility of reducing the current approach of one Network per Namespace, to one Network per cluster to reduce resource usage: - action items: - check if there is a plan to implement Network cascade delete with the Neutron team - attempt to create a PoC with one Pod Network per Cluster - Possibility of creating external reachable services without Amphora. - Discussion about the open Kubernetes proposal of notifying the user when a Network Policy is actually enforced. - Drop the liveness checks for certain scenarios: - The controller and CNI restarts has helped with certain cornes cases, but it can decrease the availability of Kuryr if restarted many times - action items: - drop restarts on unavailability of Neutron/k8s API - enforce restarts when all the Kuryr watches, handlers and drivers are not running - Drop usage of Flask debug servers - Currently many servers created by Kuryr like Health, Prometheus exporter and Kuryr daemon are based on flask and could likely be moved to another type of server. - action item: Move the kuryr-cni to kuryr-daemon communication to use gRPC Don't exitate to contact us either on IRC or email if you have any questions. Cheers, Maysa Macedo.

1 0

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

30 Oct '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 28th 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-28-15.00.log.html * Next week's meeting will be video call on google meet on Oct 28th, Thursday 15:00 UTC, feel free the topic on agenda[1] by Oct 27th. 2. What we completed this week: ========================= * Add openstack/ci-log-processing project into TaCT[2] * PTG and Summary: I have summarized the TC summary along with the TC+community leaders interaction sessions. Recordings: Day1: https://www.youtube.com/watch?v=uQRKYummsHM Day2: https://www.youtube.com/watch?v=IHj7cpBlbYo Day3: https://www.youtube.com/watch?v=RT492bi6Xto Summary: http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025554.… Two topics 1. RBAC and 2. Pain points will be continue to discuss in post-PTG call or TC weekly meeting. 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * I have started the etherpad to collect the Yoga cycle targets for TC[3]. Open Reviews ----------------- * Nine open reviews for ongoing activities[4]. RBAC discussion: continuing from PTG ---------------------------------------------- We are continuing the RBAC discussion we left in PTG. I have sent the doodle poll to select the appropriate time, feel free to add your vote if you are interested to be part of it[5]. Yoga release community-wide goal ----------------------------------------- * With the continuing the discussion on RBAC, we are re-working on the RBAC goal, please wait until we finalize the implementation[6] Adjutant need maintainers and PTLs ------------------------------------------- You might have seen the email[7] from Adrian to call the maintainer for Adjutant project, please reply to that email or here or on openstack-tc channel if you are interested to maintain this project. New project 'Skyline' proposal ------------------------------------ * We discussed it in TC PTG and there are few open points about python packaging, repos, and plugins plan which we are discussion on ML. Updating the Yoga testing runtime ---------------------------------------- * We agreed to update the below things in the Yoga testing runtime: 1. Add Debian 11 as tested distro 2. Bump highest python version to test to 3.9 Patch is up for the review[8], once that is merged I will update the job template. Stable Core team process change --------------------------------------- * Current proposal is under review[9]. Feel free to provide early feedback if you have any. Merging 'Technical Writing' SIG Chair/Maintainers to TC ------------------------------------------------------------------ * Work to merge this SIG to TC is up for review[10]. One repo of this SIG openstack/training-labs is called for maintainers[11] and rest other are moved under TC & FC SIG. TC tags analysis ------------------- * TC agreed to remove the framework and it is communicated in ML[12]. Project updates ------------------- * Retiring js-openstack-lib [13] * Retiring kolla-cli [14] 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[15]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [16] 3. Office hours: The Technical Committee offers a weekly office hour every Tuesday at 0100 UTC [17] 4. 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/+/815318 [3] https://etherpad.opendev.org/p/tc-yoga-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025569.… [6] https://review.opendev.org/c/openstack/governance/+/815158 [7] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025555.… [8] https://review.opendev.org/c/openstack/governance/+/815851 [9] https://review.opendev.org/c/openstack/governance/+/810721 [10] https://review.opendev.org/c/openstack/governance/+/815869 [11] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025586.… [12] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025571.… [13] https://review.opendev.org/c/openstack/governance/+/807163 [14] https://review.opendev.org/c/openstack/governance/+/814603 [15] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [16] http://eavesdrop.openstack.org/#Technical_Committee_Meeting [17] http://eavesdrop.openstack.org/#Technical_Committee_Office_hours -gmann

1 0

[PTL] PTG Summaries Blog
by helena＠openstack.org 30 Oct '21

30 Oct '21

Hi PTLs, I have loved seeing all the PTG summaries that have been rolling in! I am working to gather all of them and create a blog post for [ openstack.org/blog ]( http://openstack.org/blog ). If you would like for your summary to be included in the blog please post it to the mailing list and send me the link to the archived email by Tuesday, November 2nd. Thank you all for your involvement in PTG and I look forward to seeing all the summaries! Cheers, Helena

2 1

[TC][First Contact][Skyline][OpenDev][Release][OpenStackSDK] Oct 2021 PTG Summaries
by Kendall Nelson 30 Oct '21

30 Oct '21

Hello! I tried to summarize some of the discussions I was in throughout the week for those that could not join! Hopefully some of it is helpful :) Technical Committee[1] Monday- 25 people Monday we focused on the relationship between the Project Team Leads (PTLs) and the Technical Committee (TC). We discussed the role of the TC, and what PTLs look to us for, what we should be doing that we are not, what we are doing that we shouldn’t be. Things we do that maybe might not be the best use of everyone’s time, etc. Some of the main things that came out of discussions were: - Creating a repo (possibly) to house documents about how certain things should be implemented if a project is going to implement them, for example quotas. These technical guidelines will hopefully give more direction to new projects entering the OpenStack space and help unify and standardize the implementations of features across already established OpenStack projects. These documents will not have accompanying deadlines like community goals, but will instead be used as resources and reference documents to further enhance OpenStack. - How to engage with OpenStack Operators and get them to be more vocal about feedback and encouraging interaction with the project specific communities with regards to bugs and project direction. Ideas included making sure to use the [ops] tag on emails to the openstack-discuss list and ensuring that users and operators know the mailing list is for them just as much as it is for developers. Also, making sure to communicate topics to the twitter handle for wider engagement to those that might not be watching the mailing list closely. Thursday- 18 people Another full day of discussions. We covered the Docs SIG state of affairs, Yoga testing runtime, TC tags, a project adoption ladder, and release name process changes (yes, again). The tldrs; of all of that: - Some of the Docs SIG repos are being retired, some are going to live with the First Contact SIG. - Python 3.9 is now a voting test and 3.10 will be added as non voting. Python 3.6 will be kept until CentOS Stream 8 is replaced by Stream 9. - There is a proposal to drop the tag framework altogether[1.1]. - We do NOT want to add a whole process for incubating new projects; simply keep the process we have and apply a ‘tech preview’ note to their first release where applicable. - We are going to change back to having the community vote for the names which will also be proposed by the community, but also pre-vetted by the community before voting begins. The final vetting will be the Open Infra Foundation’s legal team as it always has been. Friday- 28 people Another nother full day of discussions! We covered operator pain point targeting, Skyline project proposal, RBAC, Community Goals, Xena Wrap up, and were also joined at the very end by several members of the Kubernetes Steering Committee (YAY cross community collaboration!). Those tldrs; - We want to make sure all the pain points are being actively tracked and if there are things that are common across many projects those get more attention as potential community goals down the road. - Skyline is largely ready to be proposed as a project. There are a few things that might need to get rearranged and changed so that it can be released as a part of OpenStack but that shouldn’t stop them from being approved. They could be included in the Yoga release as a ‘tech preview’. - I don’t even know how to summarize the RBAC stuff lol. That one I can’t tldr for you. Go check out those notes in the etherpad[1]. - The main thing we discussed wrt community goals is that things like RBAC that we want as a community goal cannot be scoped to a single release and we are fine with that. - In the Xena wrap up, we did a retrospective of the things we accomplished and also agreed to keep monthly video meetings in the upcoming cycle. - We again loved having members of the k8s steering committee join us! We chatted about how the CNCF project ladder works, how the OpenStack’s ‘Upstream Investment Opportunities' works, and CI/CD resourcing struggles for both communities. OpenStackSDK / OpenStackClient[2] - 10 people First we kicked off with Artem giving us an update on the r1 branch which is nearing the point that we can merge it! There is only one part missing- compute has not been completely reconfigured to use proxy; there are still a number of sections of the code that rely on the cloud layer and directly touch the APIs. Once that is completed however; we will be able to merge r1 into master and celebrate! We legitimately discussed having a party and publicizing it, so if you have opinions about any of that (or want to help wrap things up), please reach out to us in #openstack-sdks. We talked a little bit about the exceptional cases where we might consider deprecating OSC commands. Basically we concluded that we still don’t want to do it except in very specific circumstances. We are generally okay with doing it for removed APIs such that they are actually being completely removed from the API and not just removed in a microversion and are essentially still reachable in older microversions. Lastly, we chatted with the Korea user group about their mentoring program that is in the process of wrapping up. It sounds like it will be a yearly thing for them and we (the SDK team) want to try to help support those efforts more going forward if the organizers of the mentoring program can give us heads up like they did this last time. We look forward to working with them more in the future! First Contact SIG[3] - 2 people Discussions were pretty brief as not many people attended, but we did follow up on a discussion earlier in the day that the Technical Committee had about having the First Contact SIG become the new owners of a couple of repositories formerly owned by the Docs SIG (a reaction to a general lack of spoons on that team and moving in the direction of moving the status of that SIG inactive). The First Contact SIG agreed to take ownership of the contributor-guide repo and the training-guides repo. Work on that migration/reconfiguration of ACLs will begin soon. If you have any questions or are interested in getting involved, please contact the First Contact SIG or the Technical Committee OpenDev[4] - 4 people The session was mostly just a working one, but we also had a little time to catch up and chat and stay connected as a team :) Not much to say here really. Skyline[5]- 4 people I attended their sessions on Tuesday and while it was largely quiet when I was there we did chat a little bit about the upcoming TC discussions about the project and I invited them to join in those- spoiler; they came! Release Management [6] - 6 People The largest topic we discussed in the release management ptg session was everyone’s favorite topic- release cadence! We talked about how it might finally be time to move to 12 month cadence. Things have slowed down sufficiently with regards to feature development (and this has been consistent throughout the last couple releases). It would reduce the frequent upgrades that distros have to work through, and the process we currently maintain can be easily stretched to accommodate a year. All in all, the release team supports the idea and think that if we are to make the transition, when we finish the ‘Z’ release and start over at the beginning of the alphabet again, that would be a natural time to also switch to a one year release cycle rather than the 6th month cadence we have been keeping up with for quite some time. The decision is ultimately up to the Technical Committee, but the release team supports the idea. -Kendall Nelson (diablo_rojo) [1] https://etherpad.opendev.org/p/tc-yoga-ptg [1.1] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025571.… [2] https://etherpad.opendev.org/p/oct2021-ptg-sdk-cli [3] https://etherpad.opendev.org/p/oct2021-ptg-first-contact [4] https://etherpad.opendev.org/p/oct2021-ptg-opendev [5] https://etherpad.opendev.org/p/oct2021-ptg-skyline [6] https://etherpad.opendev.org/p/relmgmt-yoga-ptg

1 0

[tc][operators][all] TC tags framework to be dropped
by Radosław Piliszek 30 Oct '21

30 Oct '21

Dear OpenStack Operators, Due to no response to the original query about usefulness of the TC tags framework [1] (which was repeated in each and every following TC newsletter), the TC has decided to drop the tags framework entirely. [2] [3] [1] http://lists.openstack.org/pipermail/openstack-discuss/2021-September/02480… [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025554.… [3] https://etherpad.opendev.org/p/tc-yoga-ptg Kind regards, -yoctozepto

2 2

[OpenStack-Ansible] LXC containers apt upgrade
by Taltavull Jean-Francois 29 Oct '21

29 Oct '21

Hi All, Following the recent Let's Encrypt certificates expiration, I was wondering what was the best policy to apt upgrade the operating system used by LXC containers running on controller nodes. Has anyone ever defined such a policy ? Is there an OSA tool to do this ? Regards, Jean-François

2 2

[masakari] Yoga PTG summary
by Radosław Piliszek 29 Oct '21

29 Oct '21

Hi! This is a quick summary of Masakari's Yoga PTG. Quick as the PTG itself was quite quick. :-) We have summarised the progress made in Xena and decided to continue the efforts related to supporting monitoring with Consul and tracking issued evacuations. We have also discussed one new topic regarding circuit breaking in case of a mass failure of instances (e.g., due to a storage network failing in one location). To this end, the proposal is to introduce a protection mechanism (circuit breaking) based on a static time window (static at least in the first iteration) per segment. suzhengwei is to write the spec for this. Raw notes are available at https://etherpad.opendev.org/p/masakari-yoga-ptg Kind regards, -yoctozepto

1 0

[sahara][ptg] Yoga PTG Summary
by Juntingqiu Qiujunting (邱军婷) 29 Oct '21

29 Oct '21

Hi all: Thank everyone for taking time and attending session. The discussion content of the PTG meeting is as follows: https://etherpad.opendev.org/p/sahara-yoga-ptg 1、Sahara has supported boot virtual machine from volume. https://specs.openstack.org/openstack/sahara-specs/specs/backlog/boot-from-… 2、Sahara deploys a dedicated clusters need the network to be a flat one for instances. Could set up a "jumphost" which can be reached by the controllers, and that can reach the instances, need not the network to be a flat one for instance. https://docs.openstack.org/sahara/latest/admin/advanced-configuration-guide… 3、Discuss about which Plugins should be kept and updated and which ones should be dropped? The conclusion is that such as HDP、CDH、MapR Storm and Spark can be deleted in Yoga. 4、Improve the unit testing and documentation of Sahara project. Currently, the activity of the Sahara project is relatively low. We can discover its potential and expand its usage scenarios. Thank you Fossen --------------------------------- Fossen Qiu | 邱军婷 CBRD | 云计算与大数据研发部 T: 18249256272 E: qiujunting(a)inspur.com<mailto:qiujunting@inspur.com> 浪潮云海

1 0

[ptg][cinder] yoga virtual PTG summary
by Brian Rosmaita 29 Oct '21

29 Oct '21

Sorry for the delay, it's posted here: https://wiki.openstack.org/wiki/CinderYogaPTGSummary The wiki page contains links to all the recordings. It's a wiki page, so feel free to make clarifications or corrections. Action items are noted in the "conclusions" sections of most of the summaries, so please look to remind yourself what you have committed yourself to. cheers, brian

1 0

Problems with Openstack internal:external router
by Jibsan Joel Rosa Toirac 29 Oct '21

29 Oct '21

Hello I finished to set up a brand new Openstack server, I had already other up and running without any problems, yet on mine the router wich allows the external connection has all the interfaces down and I don't know what else to do. I've tried everything but it still not working. Please any help with this? I let you here a couple of screenshots of my network topology

1 0

[manila] FIPS compliance (Notice: third party drivers)
by Carlos Silva 29 Oct '21

29 Oct '21

Hello Zorillas and interested stackers! During the PTG week, we had a session where we discussed FIPS compatibility and compliance. In this PTG recording [1] you can see the discussion around this topic and our motivations to achieve such things for Manila. We're writing to follow up on the PTG discussion we had, and to update you on our move towards FIPS compatibility and compliance. We're aiming for manila FIPS compatibility with the Yoga cycle, meaning our CI jobs should be passing. FIPS compliance is a Z(orilla) cycle goal. For third party maintainers, to test if your code is FIPS compatible, use an image with fips enabled as discussed in [3]. In the etherpad we used in our previous discussion [2], there's a mention for some drivers that are using non-FIPS compliant libraries, and some examples of libraries that shouldn't be used. If FIPS is enabled in the controller where the driver is, and the driver is using one of the non permitted libraries, it will possibly lead the driver to malfunctioning. If you have any questions, please feel free to reach out to us (carloss and ashrod98) in #openstack-manila. We're always here to support our community. [1] https://youtu.be/mlTx71GIp1w?t=4864 [2] https://etherpad.opendev.org/p/yoga-manila-FIPS [3] https://etherpad.opendev.org/p/state-of-fips-in-openstack-ci-yoga Thanks! ---- Carlos da Silva (carloss) Ashley Rodriguez (ashrod98)

1 0

[kolla] Yoga PTG summary
by Michał Nasiadka 28 Oct '21

28 Oct '21

Hi everyone, Thank you all who participated in the PTG discussions and shared their thoughts and opinions. Here is the summary of the topics we have discussed: # General ## We agreed to stop using Launchpad’s Blueprints functionality (which was inconsistently used by us). ## We’ve discussed recently proposed services to Kolla: Adjutant has a complicated status now (vacant PTL seat and looking for contributors) Skyline Venus We agreed that a project can be added to Kolla/Kolla-Ansible once it fulfills following the criteria of being in OpenStack governance for 1 cycle and having 1 release. An exception to this criteria is when the patch content is in good quality and there are core reviewers interested in making this functionality merged (but still the project needs to be in OpenStack governance). ## We also discussed adding OSISM collection of Grafana dashboards and Prometheus Alertmgr rules in order to improve the “default deployment” experience for Kolla-Ansible users. ## There was a decision taken to finally retire kolla-cli (since it has been deprecated long time ago). # Kolla ## We have discussed deprecating and dropping of binary type of Kolla images: Pros: * less CI load, less maintenance burden (for a limited Kolla team), users would be running more tested images (since Kolla/Kolla-Ansible CI runs source images CI jobs as voting) Cons: * User survey showed that a considerable amount of users is using them - unclear if because that’s a default - or they have chosen to do so. * Overriding package versions in source variant can be more troublesome than it is in binary Action plan: * Improve documentation for source images, especially focusing on its advantages and what might change for current users of binary (when they make the transition) * Mark binary images as deprecated in Yoga cycle (add a note about deprecation in kolla-build CLI output) * Improve override options for source images (upper-constraints, etc) ## The next discussion item was to use a common base (single Linux distribution) for Kolla images Action plan (to make it possible): * Fix Bifrost and OVN builds for Debian (which are broken now) * Create CI jobs for mixed host-os/in-container-image-os (including upgrade jobs) * Deprecate binary images after those two actions are done * Provide a decent plan with justification and operator feedback in https://etherpad.opendev.org/p/kolla-only-on-debian <https://etherpad.opendev.org/p/kolla-only-on-debian> * Deprecate CentOS only images (like qdrouterd) At the same time we agreed on not pursuing CentOS Stream 9 or Ubuntu 22.04 LTS image builds, when those will show up/be required. ## Migration from ElasticSearch to AWS OpenSearch (Elasticsearch fork after ES changed license) Action items: * Deprecate Elasticsearch in Yoga * Build OpenSearch in Yoga # Kolla-Ansible ## Podman support We agreed to implement it with as minimum Ansible playbooks/roles changes as possible (mainly rework kolla_docker.py) Action plan: * Reduce scope of existing patch to deploy a single service (e.g. MariaDB) * Write up a rough implementation plan in https://etherpad.opendev.org/p/kolla-docker-systemd-podman <https://etherpad.opendev.org/p/kolla-docker-systemd-podman> * Add systemd units support for existing Docker implementation * Add podman installation in Kolla-Ansible’s baremetal role * Add podman support upon systemd support for Docker ## Change default deployment to use ML2/OVN (instead of ML2/OVS) We agreed on the criteria to do so: * Debian OVN packages in Yoga * Working and reliable migration path * A way to prevent accidental migration to OVN for existing deployments And until that is resolved - we’re not going to pursue that decision. ## Keystone system scope continued Action plan: * Proposed to split into 3 parts ** use system scope for keystone admin user (done in Xena) ** assign admin role to service users with system scope ** provide flags to enable scope enforcement and new defaults ## Let’s Encrypt Resume efforts to implement it (since we upgraded to HaProxy 2.2 which enables seamless TLS key/cert replacement) ## More HA settings by default Action plan: * Add a docs HA page that describes typical Kolla-Ansible deployment (haproxy, galera cluster, etc) with references to other projects HA configurations (e.g. neutron, octavia) ## Rocky Linux Host OS support Proposal: Replace CentOS Stream support to Rocky Linux in the longer run Action plan: * Add support for Rocky Linux as Host OS (no Kolla container images) # Kayobe ## Multiple environments part 3 Proposed improvements: * merge OpenStack custom configs * merge Kolla Ansible group_vars * dependencies between environments * CI testing ## Support RAID with Bifrost via cleaning steps and deploy steps Action plan: * Add support to baremetal_node_action Ansible module for manual cleaning and passing deploy steps * Option: Enable automated cleaning to erase metadata * Add support for using this functionality to Bifrost * Add passing of deploy_steps and cleaning_steps from Kayobe to Bifrost ## Create collection(s) for external Ansible roles that Kayobe depends on (those from StackHPC namespace) * Group Kayobe external roles to collections (the whole ,,ecosystem’’ of stackhpc.* roles) * Encourage Kayobe role users to move to collections * Add/improve CI testing for the collection For details please check the Kolla Yoga PTG etherpad: https://etherpad.opendev.org/p/kolla-yoga-ptg <https://etherpad.opendev.org/p/kolla-yoga-ptg> And see you on the weekly meetings: https://meetings.opendev.org/#Kolla_Team_Meeting <https://meetings.opendev.org/#Kolla_Team_Meeting> Best Regards, Michal Nasiadka

1 0

答复: [cyborg][ptg] Yoga PTG Summary
by Brin Zhang(张百林) 28 Oct '21

28 Oct '21

More details on etherpad: https://etherpad.opendev.org/p/cyborg-yoga-ptg brinzhang 发件人: Brin Zhang(张百林) 发送时间: 2021年10月28日 19:37 收件人: 'openstack-discuss(a)lists.openstack.org' <openstack-discuss(a)lists.openstack.org> 抄送: 'xin-ran.wang(a)intel.com' <xin-ran.wang(a)intel.com>; Alex Song (宋文平) <songwenping(a)inspur.com>; Jorhson Deng (邓兆森) <dengzhaosen(a)inspur.com>; Juntingqiu Qiujunting (邱军婷) <qiujunting(a)inspur.com>; 'eric_xiett(a)163.com' <eric_xiett(a)163.com> 主题: [cyborg][ptg] Yoga PTG Summary Hi everyone! First of all I would like to thank everyone for taking time and attending session. I think we had pretty productive time and discussions. You may find discussion summaries below: * With nova-cyborg interaction ** Cyborg vGPU support, we write a spec that adds the prefilter and the traits against every Nova RP and then cyborg contributors to provide a subsequent spec for Cyborg using their own trait ** Continue to work on resume/suspend feature, add the unit tests and update the PoC codes ** Works on PMEM instance cold migration in Nova, the spec is already merged in Xena release, and it need to re-propose it in Yoga release * Introducing some new accelerators driver ** xilin FPGA Driver ** PMEM Driver ** Optimization the exist device function, such as FPGA program interface, GPU/vGPU support * New feature will be support in Yoga release ** Get device profile get by name. It’s need to add a microversion, because of the request path_url changed, proposed the spec but need to update *** SPEC URL: https://review.opendev.org/c/openstack/cyborg-specs/+/813183 ** Add disable/enable device status to mark the device whether can be use or not ***SPEC URL: https://review.opendev.org/c/openstack/cyborg-specs/+/815460 ** We would like to improve the parameter validation, consider checking the api parameters with schema ** Add batch query ARQs for more than one instance support in Get *One* Accelerator Request API * Docs improving, such as nova-cyborg interaction manual and API ref docs * Improve the exception mechanism, improve the efficiency of abnormal judgment in unit testing * Improve the abnormal instance handling scenarios, for example, when the host is disconnected and the device is damaged, how should we set the device status and the accelerator instance state at this time. brinzhang

1 0

[cyborg][ptg] Yoga PTG Summary
by Brin Zhang(张百林) 28 Oct '21

28 Oct '21

Hi everyone! First of all I would like to thank everyone for taking time and attending session. I think we had pretty productive time and discussions. You may find discussion summaries below: * With nova-cyborg interaction ** Cyborg vGPU support, we write a spec that adds the prefilter and the traits against every Nova RP and then cyborg contributors to provide a subsequent spec for Cyborg using their own trait ** Continue to work on resume/suspend feature, add the unit tests and update the PoC codes ** Works on PMEM instance cold migration in Nova, the spec is already merged in Xena release, and it need to re-propose it in Yoga release * Introducing some new accelerators driver ** xilin FPGA Driver ** PMEM Driver ** Optimization the exist device function, such as FPGA program interface, GPU/vGPU support * New feature will be support in Yoga release ** Get device profile get by name. It’s need to add a microversion, because of the request path_url changed, proposed the spec but need to update *** SPEC URL: https://review.opendev.org/c/openstack/cyborg-specs/+/813183 ** Add disable/enable device status to mark the device whether can be use or not ***SPEC URL: https://review.opendev.org/c/openstack/cyborg-specs/+/815460 ** We would like to improve the parameter validation, consider checking the api parameters with schema ** Add batch query ARQs for more than one instance support in Get *One* Accelerator Request API * Docs improving, such as nova-cyborg interaction manual and API ref docs * Improve the exception mechanism, improve the efficiency of abnormal judgment in unit testing * Improve the abnormal instance handling scenarios, for example, when the host is disconnected and the device is damaged, how should we set the device status and the accelerator instance state at this time. brinzhang

1 0

[manila][ptg] Yoga cycle PTG summary
by Goutham Pacha Ravi 28 Oct '21

28 Oct '21

Hello Zorillas and other awesome Stackers, Thank you for participating in the Yoga cycle Project Teams Gathering. A special thanks to the folks at the OpenInfra Foundation who provided the platform for this event! We brainstormed on numerous topics. You'll find the unabridged notes and links in the main etherpad [1]. Video recordings from the event are posted on our Youtube channel [2]. The following is my summary of the proceedings. Please feel free to follow up here, or on OFTC's #openstack-manila if you have any questions. == Xena cycle retrospective == Etherpad: https://etherpad.opendev.org/p/manila-xena-retrospective * We celebrated successful Outreachy internships (Kafilat Adeleke and Archana Kumari), completion of the senior design project of students from Boston University (Ashley Rodriguez, Nicole Chen and Mark Tony) and two Open Source Day mentoring events at the Grace Hopper Celebration. * We have long term contributors in kafilat and archanaserver, along the lines of ashrod98 (who is now a Red Hatter!), disap (at Microsoft!), kiwi_36 (continuing his unified limits work), maaritamm (at city network, is manila core!) and many others. Very proud of the effort the team puts in to attract and retain such talent in the community. * We also discussed the mentoring efforts coinciding with the Yoga release (Northeastern University Cloud Computing course project, Outreachy internships, others). * We anticipate more changes to the maintainers team in the Yoga cycle in our continued effort to build domain expertise around the team, and avoid reviewer burn out. * Thanks to the enthusiastic participation, and to a well groomed bug backlog (kudos, vhari) we had two successful bugsquash weeks and a hack-a-thon during the Xena cycle. We're pruning down the list of stale issues collaboratively. The team liked the frequency of these events. * We discussed the responses for the 2021 User Survey and key takeaways (need for active/active HA, unified limits, unified cli, virtiofs) * Action Items: ** Plan a hack-a-thon in Yoga (topics welcome) ** Update questions for the 2022 user survey ** Plan periodic collaborative code review events alongside the bug squash events to prevent languishing patches. == Share transfers == * haixin highlighted the need for APIs to safely transfer shares across project namespaces and discussed some caveats, and a rough workflow for the feature * To ensure secure multi-tenancy, many back end share drivers use the project_id metadata in their provisioning paths - so transferring resources must send appropriate notifications * For DHSS=True, transfering the share alone makes little sense without first transfering the share network onto which the share is exported - however, multiple shares can be associated with one share network, so this could need a multi-phase transfer needing an ability to rollback. * Action Items: * Propose a spec and discuss the multi-stage implementation of this feature == Project testing and Interoperability improvements == * vhari shared plans for the improvement of the interop guidelines associated with manila * We touched upon the work lkuchlan and vhari are doing to align optional feature testing with tempest's best practices * Third party CI maintainers were reminded that they must be running scenario tests * Action Items: * Team looks at the possible tests to add as advisory to the 2021.11 guideline: https://etherpad.opendev.org/p/refstack-test-analysis == CephFS driver and integration changes == Etherpad: https://etherpad.opendev.org/p/yoga-ptg-manila-cephfsnfs-cephadm * vkmc highlighted the changes intended in the Manila CephFS driver to adopt the ceph mgr nfs APIs instead of the DBUS interactions that the Ganesha interace is coded to perform. The ceph mgr NFS APIs would only work on cephadm-deployed ceph nfs (nfs-ganesha) clusters. * Ceph nfs can be deployed like any other ceph daemon in an active/active HA cluster. One concern was the backwards incompatible changes to default nfs-ganesha configuration - this is being worked out. * TripleO developers joined us to discuss deployment changes, and the upgrade concerns including the eventual change in the NFS VIP. * Action Items: * Share notes about the deployment and upgrade changes necessary to get manila's CephFS driver to work with an active/active NFS HA cluster for the benefit of operators as well as deployment tools like tripleo, kolla-ansible, juju charms, etc. == Manila deployment at the Edge == Etherpad: https://etherpad.opendev.org/p/yoga-ptg-manila-at-the-edge * I quizzed fultonj about the use cases and architecture of the Distributed Compute Node edge deployments that tripleo is capable of orchestrating. * DCN now supports persistent block storage, and enables setting up the service in a multi-backend configuration with local-to-compute backends associated with availability zones that represent the edge sites. * We captured work items to similarly support manila-share at edge sites in this architecture to enable RWX storage at edge sites, and brainstormed future possibilities around the feature (cross site share replication) * Action Items: - A spec to support manila-share in an active/active HA configuration - Testing template for A/A with vendor share drivers == Metadata APIs for all user facing resources == Etherpad: https://etherpad.opendev.org/p/yoga-manila-metadata * ashrod98 discussed the ongoing work to generalize user defined metadata to all end-user facing resources. Currently users can attach metadata to shares and access rules, and the service provides metadata to export locations. * There are changes to the initial design that were brainstormed wrt RBAC and service/operator metadata. * The new APIs are going to be supported in the openstackclient shell implementation * Action Items: * Reviewer attention needed for the changes to the metadata spec, and for new RBAC guarding operator metadata. == Manila UI updates == * vkmc, carloss and haixin presented the plan to update the UI's feature parity * We have two outreachy internship proposals around implementing new UX around share networks and for enhancing integration testing for manila-ui * Action items: * Outreachy contributor period is open, lookout for applicants seeking reviews * Identify trivial API features that can be supported with little effort for the Yoga cycle hack-a-thon == VirtIOFS == Etherpad: https://etherpad.opendev.org/p/nova-manila-virtio-fs-support-yptg-october-2… * tbarron presented updates regarding the ongoing prototyping for nova's support of virtiofs. * There's a demo of how the feature's expected to work: https://asciinema.org/a/IZ7UrhwspxBN63XsOl9JrTcUX?speed=1.5 * The nova discussion (https://etherpad.opendev.org/p/nova-yoga-ptg) included mechanics of supporting read-only attachments, os-share library, mount tags and use cases for baremetal nodes. The specification will be refined to answer some of these questions. * This continues to be a multi-release effort as changes in libvirt, qemu, kvm were needed for live virtiofs attachments. * Action Items: * Review/Refine nova spec: https://review.opendev.org/c/openstack/nova-specs/+/813180 == Multiple share network subnets in an AZ == Etherpad: https://etherpad.opendev.org/p/ptg-multiple-subnet * nahimsouza and felipe_rodrigues presented the use case for share networks to allow multiple subnets per availability zone. * This proposal would make dual stack ipv4/ipv6 networking possible for DHSS=True * Users would also have the ability to modify share networks that were in use - new network allocations will be possible for existing share servers, however, network allocations cannot be deleted. * Concerns were raised regarding the user experience and error signalling when port allocations cannot be made from all relevant subnets. * Action items: * Determine what needs to happen when a subnet has run out of allocations * Propose a specification discussing the API and driver interface impact to accommodate this change == FIPS compatibility and compliance == Etherpad: https://etherpad.opendev.org/p/yoga-manila-FIPS * carloss, ashrod98 and ade_lee spoke of the cross project effort to get FIPS compatibility and compliance testing * We discussed manila's direct/indirect use of cryptographic libraries and FIPS compliant alternatives (md5 in code, and paramiko's use of non-fips compliant digests); manila-tempest-plugin needs fixes along the same lines since it relies on paramiko. * Currently, the team's writing new CI jobs to test compatibility - these should merge by the end of the Yoga release cycle; the goal for compliance would be the Zorilla release (yes, i said it). * Action items: * Work on FIPS compatibility jobs in the Yoga release cycle == Secure RBAC changes in Yoga == Etherpad: https://etherpad.opendev.org/p/yoga-ptg-manila-srbac * vhari and I rounded up the work done so far to update the default RBAC policies across manila APIs and highlighted known issues, and pending work items * Cross service arbitrations on behalf of a user are ongoing discussions elsewhere - examples of these include manila's generic driver where the user's namespace and quota are consumed to create the nas server, backing volume and networking * We are continuing to implement tempest tests and anticipate a large portion to be completed during the Yoga cycle. * We don't plan to support cloud profiles with the manilaclient shell. Users are encouraged to switch to the openstackclient shell to use cloud profiles. * Action items: * Close on known issues in manila code * Complete protection and tempest test coverage == Paying down some technical debt in Yoga == * python-manilaclient still uses keystoneclient instead of keystoneauth1 - vkmc and gouthamr will work on this early in the Yoga release cycle * sqlalchemy2.0 changes - ack'ing SADeprecationWarnings and switching to using the new db engine facade exposed by oslo.db - felipe_rodrigues and gouthamr will work on this during the Yoga cycle * these are wishlist items that need volunteers to drive them to completion: * the generic driver doesn't yet support online extensions - * the generic driver can support more than 26 volumes per share server - this is a wishlist item that needs a volunteer to drive it * we need to publish the container driver image to a container registry from its development within the manila-image-elements project == Backing up shares == Etherpad: https://etherpad.opendev.org/p/ptg-backup-manila * We were joined by operators and storage experts from SAP, CSI Piemonte, NetApp, Red Hat and CERN to discuss current use cases and methods to backing up manila shares * Existing data protection and disaster recovery tools within manila (creating and mounting snapshots, cloning snapshots to new shares, reverting snapshots in-place, replicating shares and snapshots) were compared against the need for scheduling, efficient, incremental, durable/ex-situ/non-homogenous backup destinations, whole container vs selective file backup and recovery. * Available DIY external tooling (restic, borg, urbackup, other) and wrappers were discussed * Creating a backup solution based off-of the manila-data service was considered in the past, the spec was abandoned. It could be revived; however, we could benefit from presenting the need, a state of affairs as they are before exploring solutions. * Action Items: * We'll write up a doc on data protection for manila shares and invite operators to review them and propose future plans; anyone interested in collaborating in this space can get in touch with felipe_rodrigues == OpenStackCLI updates == Etherpad: https://etherpad.opendev.org/p/manila-osc-yoga * Thanks to maaritamm's awesome work, and the enthusiastic hack-a-thon participation from the community, we're very close to parity between OSC and the manilaclient shell. So, the team decided to stop adding new features in the manilaclient shell as a way to gradually wean users off of it. * When using the manilaclient shell from the Yoga release, users will be shown a deprecation warning suggesting an eventual removal (looking at the "A" release for this one, thoughts are welcome). * maaritamm proposed a hack-a-thon for completing the functional testing around manilaclient's osc plugin. * The osc plugin also needs the api microversion negotiation bits that the manilaclient shell currently has. * Action items: * We assigned owners to pending reviews, and missing osc commands * Deprecate the native manilaclient shell. == Manila CSI updates == Etherpad: https://etherpad.opendev.org/p/yoga-ptg-manila-csi * gman0 and tbarron presented the state of the kitchen for manila-csi since the Xena PTG and shared future plans * share backup is now a focus area for pvs serviced by manila-csi - the design involves being able to mount manila snapshots as read only PVs on backup pods and extracting relevant files. * we discussed e2e testing that's being added to the cloud-provider-openstack repository and the results of the perf/scale testing with manila-csi on openshift == OpenStackSDK updates == Etherpad: https://etherpad.opendev.org/p/yoga-manila-openstacksdk-update * we've had several interns working on exposing manila APIs within the openstacksdk since the wallaby release * kafilat has numerous open changes, wrapped up a successful outreachy internship recently * megharth, Jiabo, tutkuna and rishabhdutta from Northeastern University picked up the implementation of the remaining API resources for the Yoga cycle * this continues to be a multi-cycle effort and the plan is to eventually use manila APIs via the openstacksdk within manila-ui, ansible-collections-openstack and manila's OSC plugin. * Action Items: * team will review open changes against the openstacksdk repository pertaining to manila Thanks for reading thus far. It's possible a lot can get lost in translation :) As a reminder, do check out the complete recordings on our Youtube channel! [2] -- Goutham Pacha Ravi PTL, OpenStack Manila [1] https://etherpad.opendev.org/p/yoga-ptg-manila [2] https://www.youtube.com/watch?v=wVAClI82Ths&list=PLnpzT0InFrqDhp1A3lBi_guLA…

1 0

Router interfaces are down
by Jibsan Joel Rosa Toirac 28 Oct '21

28 Oct '21

Hello, I'm trying to route all the requests from a private vlan to internet. I have a private network and all the Virtual Machines inside the subnet config can do everything between they, but if I ping to Internet, it doesn't work. When I see the router_external it says all the interfaces are DOWN. I have search in everywhere but I can't find a solution for this. Thank you for your time

2 1

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

28 Oct '21

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

1 1

SSSE3 CPU flag not available
by tarun singhal 28 Oct '21

28 Oct '21

Hello, I have an Openstack cluster which was created using devstack. And recently I was involved in project in which there is a dependency on SSSE3 cpu flag in an Openstack VM instance, to accomplish certain tasks. I searched many posts but couldn't find a definitive solution. The suggestion mentioned didn't worked for me either. I have added below in /etc/nova/nova.conf and restarted devstack(a)n-cpu.service cpu_mode = host-model cpu_model_extra_flags = ssse3 Please let me know a possible way to enable SSSE3 cpu flag in a vm instance. Thanks, Tarun

1 0

[tripleo] x509 certificate Issue in Overcloud Deployment
by Anirudh Gupta 28 Oct '21

28 Oct '21

Hi Team, I am trying to install the Tripleo setup on the Openstack Train. While deploying the overcloud, I am getting an x509 certificate error in downloading the images from quay.io This is because of a proxy certificate in the LAB. Before installing Undercloud, I manually placed the certificate in order to avoid this issue. How can I take care of placing such certificates in case of an overcloud. Regards Anirudh Gupta

2 1

Xena RDO Release Announcement
by Amy Marrich 27 Oct '21

27 Oct '21

If you're having trouble with the formatting, this release announcement is available online at https://blogs.rdoproject.org/2021/10/rdo-xena-released/ ---- *RDO Xena Released* The RDO community is pleased to announce the general availability of the RDO build for OpenStack Xena for RPM-based distributions, CentOS Stream and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds. Xena is the 24th release from the OpenStack project, which is the work of more than 1,000 contributors from around the world. The release is already available on the CentOS mirror network at http://mirror.centos.org/centos/8-stream/cloud/x86_64/openstack-xena/. The RDO community project curates, packages, builds, tests and maintains a complete OpenStack component set for RHEL and CentOS Stream and is a member of the CentOS Cloud Infrastructure SIG. The Cloud Infrastructure SIG focuses on delivering a great user experience for CentOS users looking to build and maintain their own on-premise, public or hybrid clouds. All work on RDO and on the downstream release, Red Hat OpenStack Platform, is 100% open source, with all code changes going upstream first. PLEASE NOTE: RDO Xena provides packages for CentOS Stream 8 only. Please use the Victoria release for CentOS Linux 8 which will reach End Of Life (EOL) on December 31st, 2021 (https://www.centos.org/centos-linux-eol/) *Interesting things in the Xena release include:* - The python-oslo-limit package has been added to RDO. This is the limit enforcement library which assists with quota calculation. Its aim is to provide support for quota enforcement across all OpenStack services. - The glance-tempest-plugin package has been added to RDO. This package provides a set of functional tests to validate Glance using the Tempest framework. - TripleO has been moved to an independend release model (see section TripleO in the RDO Xena release) The highlights of the broader upstream OpenStack project may be read via https://releases.openstack.org/xena/highlights.html *TripleO in the RDO Xena release:* - In the Xena development cycle, TripleO has moved to an Independent release model( https://specs.openstack.org/openstack/tripleo-specs/specs/xena/tripleo-inde… ) and will only maintain branches for selected OpenStack releases. In the case of Xena, TripleO will not support the Xena release. For TripleO users in RDO, this means that: - RDO Xena will include packages for TripleO tested at OpenStack Xena GA time. - Those packages will not be updated during the entire Xena maintenance cycle. - RDO will not be able to included patches required to fix bugs in TripleO on RDO Xena. - The lifecycle for the non-TripleO packages will follow the code merged and tested in upstream stable/xena branches. - There will not be any tripleoxena container images built/pushed, so interested users will have to do their own container builds when deploying xena. You can find details about this [in RDO webpage](https://www.rdoproject.org/documentation/tripleo-in-xena/) *Contributors* During the Xena cycle, we saw the following new RDO contributors: - Chris Sibbitt - Gregory Thiemonge - Julia Kreger - Leif Madsen Welcome to all of you and Thank You So Much for participating! But we wouldn’t want to overlook anyone. A super massive Thank You to all 41 contributors who participated in producing this release. This list includes commits to rdo-packages, rdo-infra, and redhat-website repositories: - Alan Bishop - Alan Pevec - Alex Schultz - Alfredo Moralejo - Amy Marrich (spotz) - Bogdan Dobrelya - Chandan Kumar - Chris Sibbitt - Damien Ciabrini - Dmitry Tantsur - Eric Harney - Gaël Chamoulaud - Giulio Fidente - Goutham Pacha Ravi - Gregory Thiemonge - Grzegorz Grasza - Harald Jensas - James Slagle - Javier Peña - Jiri Podivin - Joel Capitao - Jon Schlueter - Julia Kreger - Lee Yarwood - Leif Madsen - Luigi Toscano - Marios Andreou - Mark McClain - Martin Kopec - Mathieu Bultel - Matthias Runge - Michele Baldessari - Pranali Deore - Rabi Mishra - Riccardo Pittau - Sagi Shnaidman - Sławek Kapłoński - Steve Baker - Takashi Kajinami - Wes Hayutin - Yatin Karel *The Next Release Cycle* At the end of one release, focus shifts immediately to the next release i.e Yoga. *Get Started* To spin up a proof of concept cloud, quickly, and on limited hardware, try an All-In-One Packstack installation. You can run RDO on a single node to get a feel for how it works. Finally, for those that don’t have any hardware or physical resources, there’s the OpenStack Global Passport Program. This is a collaborative effort between OpenStack public cloud providers to let you experience the freedom, performance and interoperability of open source infrastructure. You can quickly and easily gain access to OpenStack infrastructure via trial programs from participating OpenStack public cloud providers around the world. *Get Help* The RDO Project has our users(a)lists.rdoproject.org for RDO-specific users and operators. For more developer-oriented content we recommend joining the dev(a)lists.rdoproject.org mailing list. Remember to post a brief introduction about yourself and your RDO story. The mailing lists archives are all available at https://mail.rdoproject.org. You can also find extensive documentation on RDOproject.org. The #rdo channel on OFTC IRC is also an excellent place to find and give help. We also welcome comments and requests on the CentOS devel mailing list and the CentOS and TripleO IRC channels (#centos, #centos-devel in Libera.Chat network, and #tripleo on OFTC), however we have a more focused audience within the RDO venues. *Get Involved* To get involved in the OpenStack RPM packaging effort, check out the RDO contribute pages, peruse the CentOS Cloud SIG page, and inhale the RDO packaging documentation. Join us in #rdo and #tripleo on the OFTC IRC network and follow us on Twitter @RDOCommunity. You can also find us on Facebook and YouTube.

1 0

[largescale-sig] Next meeting: Oct 27th, 15utc
by Thierry Carrez 27 Oct '21

27 Oct '21

Hi everyone, The Large Scale SIG meeting is back this Wednesday in #openstack-operators on OFTC IRC, at 15UTC. You can doublecheck how that time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20211027T15 A number of topics have already been added to the agenda, including discussing the topic of our next OpenInfra.Live show! Feel free to add other topics to our agenda at: https://etherpad.openstack.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

How to control data write into a multiattach volume
by open infra 27 Oct '21

27 Oct '21

Hi, I have created a multiattach volume and attached it to several Windows VMs/Instances. Is there away in OpenStack to drop all data written by each VM/instances? I am supposed to periodically detach and attach the multiattach volume. Regards, Danishka

2 1