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

[ptl][release][stable][EM] Extended Maintenance - Ussuri
by Előd Illés 03 Nov '21

03 Nov '21

Hi, As Xena was released last week and we are in a less busy period, now it is a good time to call your attention to the following: In a month Ussuri is planned to transition to Extended Maintenance phase [1] (planned date: 2021-11-12). I have generated the list of the current *open* and *unreleased* changes in stable/ussuri for the follows-policy tagged repositories [2] (where there are such patches). These lists could help the teams who are planning to do a *final* release on Ussuri before moving stable/ussuri branches to Extended Maintenance. Feel free to edit and extend these lists to track your progress! * At the transition date the Release Team will tag the *latest* Ussuri releases of repositories with *ussuri-em* tag. * After the transition stable/ussuri will be still open for bug fixes, but there won't be official releases anymore. *NOTE*: teams, please focus on wrapping up your libraries first if there is any concern about the changes, in order to avoid broken (final!) releases! Thanks, Előd [1] https://releases.openstack.org/ [2] https://etherpad.opendev.org/p/ussuri-final-release-before-em

1 1

[horizon][dev]Handle multiple login sessions from same user in Horizon
by Luz de Avila, Arthur 01 Nov '21

01 Nov '21

Hi everyone, In order to improve the system my colleagues and I would like to bring up a new feature to Horizon. We found out that an user is able to login in Horizon with the same credentials in multiple devices or/and browsers. This may be not very secure as the user can login in many different devices or/and browsers with the same credential. Thinking on that, we would like bring up more control to the admin of the system in a way that the admin can enable or disable the multiple login sessions according to the needs of the system. For a better follow up of this propose, a blueprint has been opened with more details about the idea and concepts of this and we would like the onion of the community whether this feature make sense to implement or not. The blueprint opened on launchpad: https://blueprints.launchpad.net/horizon/+spec/handle-multiple-login-sessio… Kind regards, Arthur Avila

2 1

Openstack ansible VS kolla ansible
by A Monster 01 Nov '21

01 Nov '21

Openstack-ansible uses LXC containers to deploy openstack services , while Kolla uses docker containers instead, which of these two deployment tools should I use for an Openstack deployment, and what are the differences between them.

3 2

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 30 Oct '21

30 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 29 Oct '21

29 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 29 Oct '21

29 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