[Starlingx-discuss] Flock components python3 migration query on master.

Bailey, Henry Albert (Al) Al.Bailey at windriver.com
Mon Dec 14 22:55:20 UTC 2020


The containers typically install the python components they need using wheels
If the flock components are updated in their setup.cfg to be built universal wheels  (which are py2 and py3 compatible) then the wheels being generated from the spec should be able to be included.
That can be done in master, assuming the code  runs in both py2 and py3 without needing major changes.
Al

________________________________
From: Kalvala, Haridhar <haridhar.kalvala at intel.com>
Sent: Monday, December 14, 2020 6:12 AM
To: starlingx-discuss at lists.starlingx.io <starlingx-discuss at lists.starlingx.io>; Wensley, Barton <Barton.Wensley at windriver.com>; Wold, Saul <Saul.Wold at windriver.com>; Jones, Bruce E <bruce.e.jones at intel.com>; Sun, Austin <austin.sun at intel.com>
Cc: Mukherjee, Sanjay K <sanjay.k.mukherjee at intel.com>; Kumar, Sharath <sharath.kumar at intel.com>; Bhat, Gopalkrishna <gopalkrishna.bhat at intel.com>; Khalil, Ghada <Ghada.Khalil at windriver.com>
Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master.


[Please note this e-mail is from an EXTERNAL e-mail address]

Reminder for below request.



Thank You,

Haridhar Kalvala



From: Kalvala, Haridhar
Sent: Thursday, December 10, 2020 10:18 AM
To: starlingx-discuss at lists.starlingx.io; Wensley, Barton <Barton.Wensley at windriver.com>; Saul Wold <Saul.Wold at windriver.com>; Jones, Bruce E <bruce.e.jones at intel.com>; Sun, Austin <austin.sun at intel.com>
Cc: Mukherjee, Sanjay K <sanjay.k.mukherjee at intel.com>; Kumar, Sharath <sharath.kumar at intel.com>; Bhat, Gopalkrishna <gopalkrishna.bhat at intel.com>; Khalil, Ghada <Ghada.Khalil at windriver.com>
Subject: Flock components python3 migration query on master.



Hello All,



We are working on FM containerization (FM panel in open stack dashboard and backend pod service(fault)).

As part  of this activity, we are doing stx-horizon docker build. Which will include components from flock (for fm calls). As a reference example, please refer to this patch<https://review.opendev.org/c/starlingx/upstream/+/661423/4/openstack/python-horizon/centos/stx-horizon.stable_docker_image>.

The  front panel would be calling flock components fmclient, cgtsclient, distributedcloud etc.

These components are python2 build.  For FM panel to work we need migration of these components (seeing lot of dependency issues) from python2 to python3 on master branch.



Yesterday(9-Dec-2020) in non-openstack distro meeting, the discussion was flock python2 dependent components cannot  be migrated in master branch and will done in centos8 migration branch/stream.



So, I request for clarity/decision from community on this blocker for FM containerization.



Earlier in stx-3.0(stein’s openstack) as in above link, these component were part of stx-horizon docker build. But these were removed(as per patch below) as part of stx-4.0 migration (stein -->train --> Ussuri), as latest openstack only supports python3.



Patch details:

commit b8b897a028cda3936f17c5ac6b73af146c5de96b (tag: v4.0.0.rc0)

Author: yuchengde <yu.chengde at 99cloud.net<mailto:yu.chengde at 99cloud.net>>

Depends-on: https://review.opendev.org/#/c/731461/

Change-Id: I415ea75eb24d8b1c3151b63efd2e82075e68f26e

Signed-off-by: Yu Chengde yu.chengde at 99cloud.com<mailto:yu.chengde at 99cloud.com>





Thank you,

Haridhar Kalvala
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20201214/71e11c1b/attachment-0001.html>


More information about the Starlingx-discuss mailing list