[Starlingx-discuss] [OpenStack Ussuri Upgrade Task] Call for patch review!!
Saul Wold
sgw at linux.intel.com
Mon Jun 22 20:02:51 UTC 2020
On 6/22/20 11:57 AM, Scott Little wrote:
> In short, ussuri should not be merged.
>
So, your saying that the 5 or so patches that merged to
openstack-armada-app need to be reverted? I don't think the build will
succeed with a partial set of Ussuri related patches merged..
Sau!
> Scott
>
>
> On 2020-06-22 1:32 p.m., Scott Little wrote:
>> The ussuri build only passed because I created customized build
>> scripts for that feature branch. This was to prove that the python2/3
>> issues were the only issues with the build. I was in no way
>> committing to deliver those customizations into the master branch build.
>>
>> 1) We would loose the ability to build on older branches without
>> significant extra effort.
>>
>> 2) It would be very fragile. It relies on hard code list of packages
>> that are to be compiled for python3 vs python2. I'm sure that list
>> will be changing over time.
>>
>> What I would like to see is build-stx-images.sh modified to look for
>> and consume a config file that tells it how to partition wheels and
>> images into two separate builds. Externally, the command remains a
>> single invocation with no new arguments. The config file could then be
>> modified to individually shift images from python2 to python3 build
>> method without having to tinker with cengn build scripts every time
>> there is a change.
>>
>> Scott
>
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
More information about the Starlingx-discuss
mailing list