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

Wed Jan 6 00:01:19 UTC 2021

Just some input based on the experience of CentOS 8 supporting, hope to help you.
For "python-pbr/python3-pbr" ,  though don't know the detailed migrate issue you have,  what I did is just adding 'python3-pbr-<version>.noarch.rpm' into 'flock/rpms_centos.lst',
and change all 'BuildRequires: python-pbr'  to 'BuildRequires: python3-pbr',  'Requires:       python-pbr'   to 'Requires:       python3-pbr',  then at least I can build ok and no dependency
issue during deployment.

B,R
Haiqing Bai
From: Kalvala, Haridhar <haridhar.kalvala at intel.com>
Sent: Tuesday, December 15, 2020 1:58 PM
To: Bailey, Henry Albert (Al) <Al.Bailey at windriver.com>; 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.
Importance: High

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

Thank you for response.
I tried the same approach(spec and setup configuration file changes) on master branch for few flock components related with fault containerization.
After changing few requires to python3, I observe below issues. Which I am not clear how to solve.
Below are the few more blocker we are facing:
è Starlingx-dashboard :
o   can't migrate python-pbr to python3-pbr.
o   Cephclient is throwing errors on trying to migrate to py3.
è Fmclient  :
o   Nfv components migration is a issue.

So I am looking for some inputs here who have done it earlier.

Sample error log:

INFO: pip is looking at multiple versions of horizon to determine which version is compatible with other requirements. This could take a while.
INFO: pip is looking at multiple versions of distributedcloud-client to determine which version is compatible with other requirements. This could take a while.
INFO: pip is looking at multiple versions of coverage to determine which version is compatible with other requirements. This could take a while.
INFO: pip is looking at multiple versions of cgtsclient to determine which version is compatible with other requirements. This could take a while.
^[[91mERROR: Cannot install pylint==1.4.0, pylint==1.4.1, pylint==1.4.2, pylint==1.4.3, pylint==1.4.4 and pylint==1.4.5 because these package versions have conflicting dependencies.
^[[0m
The conflict is caused by:
    pylint 1.4.5 depends on logilab-common>=0.53.0
    pylint 1.4.4 depends on logilab-common>=0.53.0
    pylint 1.4.3 depends on logilab-common>=0.53.0
    pylint 1.4.2 depends on logilab-common>=0.53.0
    pylint 1.4.1 depends on logilab-common>=0.53.0
    pylint 1.4.0 depends on logilab-common>=0.53.0

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

^[[91mERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies
^[[0m^[[91mWARNING: You are using pip version 20.3.1; however, version 20.3.2 is available.
You should consider upgrading via the '/var/lib/openstack/bin/python -m pip install --upgrade pip' command.
^[[0mThe command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1
Command (docker) failed, attempt 1 of 1.
Max command attempts reached. Aborting...

Thank you,
Haridhar Kalvala
From: Bailey, Henry Albert (Al) <Al.Bailey at windriver.com<mailto:Al.Bailey at windriver.com>>
Sent: Tuesday, December 15, 2020 4:25 AM
To: Kalvala, Haridhar <haridhar.kalvala at intel.com<mailto:haridhar.kalvala at intel.com>>; starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>; Wensley, Barton <Barton.Wensley at windriver.com<mailto:Barton.Wensley at windriver.com>>; Wold, Saul <Saul.Wold at windriver.com<mailto:Saul.Wold at windriver.com>>; Jones, Bruce E <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>; Sun, Austin <austin.sun at intel.com<mailto:austin.sun at intel.com>>
Cc: Mukherjee, Sanjay K <sanjay.k.mukherjee at intel.com<mailto:sanjay.k.mukherjee at intel.com>>; Kumar, Sharath <sharath.kumar at intel.com<mailto:sharath.kumar at intel.com>>; Bhat, Gopalkrishna <gopalkrishna.bhat at intel.com<mailto:gopalkrishna.bhat at intel.com>>; Khalil, Ghada <Ghada.Khalil at windriver.com<mailto:Ghada.Khalil at windriver.com>>
Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master.

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<mailto:haridhar.kalvala at intel.com>>
Sent: Monday, December 14, 2020 6:12 AM
To: starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io> <starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>>; Wensley, Barton <Barton.Wensley at windriver.com<mailto:Barton.Wensley at windriver.com>>; Wold, Saul <Saul.Wold at windriver.com<mailto:Saul.Wold at windriver.com>>; Jones, Bruce E <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>; Sun, Austin <austin.sun at intel.com<mailto:austin.sun at intel.com>>
Cc: Mukherjee, Sanjay K <sanjay.k.mukherjee at intel.com<mailto:sanjay.k.mukherjee at intel.com>>; Kumar, Sharath <sharath.kumar at intel.com<mailto:sharath.kumar at intel.com>>; Bhat, Gopalkrishna <gopalkrishna.bhat at intel.com<mailto:gopalkrishna.bhat at intel.com>>; Khalil, Ghada <Ghada.Khalil at windriver.com<mailto: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<mailto:starlingx-discuss at lists.starlingx.io>; Wensley, Barton <Barton.Wensley at windriver.com<mailto:Barton.Wensley at windriver.com>>; Saul Wold <Saul.Wold at windriver.com<mailto:Saul.Wold at windriver.com>>; Jones, Bruce E <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>; Sun, Austin <austin.sun at intel.com<mailto:austin.sun at intel.com>>
Cc: Mukherjee, Sanjay K <sanjay.k.mukherjee at intel.com<mailto:sanjay.k.mukherjee at intel.com>>; Kumar, Sharath <sharath.kumar at intel.com<mailto:sharath.kumar at intel.com>>; Bhat, Gopalkrishna <gopalkrishna.bhat at intel.com<mailto:gopalkrishna.bhat at intel.com>>; Khalil, Ghada <Ghada.Khalil at windriver.com<mailto: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/20210106/603ceef2/attachment-0001.html>