<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Zhipemg <br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Can you provide a method to generate an
updated <a
href="http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/stx-centos-py2_stable-wheels.tar">stx-centos-py2_stable-wheels.tar</a></div>
<div class="moz-cite-prefix">that I can implement on the CENGN side?</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">In this way, we can have the tarball
automatically update when new updates arrive.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Scott</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">\</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 2020-08-14 10:47 a.m., Liu, ZhipengS
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:DM6PR11MB301972093634E104286F902B85400@DM6PR11MB3019.namprd11.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Microsoft YaHei";
panose-1:2 11 5 3 2 2 4 2 2 4;}
@font-face
{font-family:"\@Microsoft YaHei";}
@font-face
{font-family:"MS PGothic";
panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
{font-family:"\@MS PGothic";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:JA;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:JA;}
span.EmailStyle19
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:58213764;
mso-list-type:hybrid;
mso-list-template-ids:-1622371212 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1
{mso-list-id:490490636;
mso-list-template-ids:-1800218006;}
@list l1:level1
{mso-level-start-at:3;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l2
{mso-list-id:979766693;
mso-list-template-ids:1029756472;}
@list l3
{mso-list-id:1042680222;
mso-list-template-ids:1147572040;}
@list l3:level1
{mso-level-start-at:2;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">Hi Frank and Don,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This is exactly a workaround for 4 python2
base images build after I discussed with Scott and Chant in
mailing list.<o:p></o:p></p>
<p class="MsoNormal">Please see my attached email for more
detail.<o:p></o:p></p>
<p class="MsoNormal">We cannot revert this patch directly as it
will block ussuri openstack image build.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Chant and I also tried several solutions
before, including<o:p></o:p></p>
<ol style="margin-top:0cm" start="1" type="1">
<li class="MsoListParagraph"
style="margin-left:0cm;mso-list:l0 level1 lfo3">Try to find
all python2 dependent wheels
<o:p></o:p></li>
</ol>
<p class="MsoNormal" style="margin-left:18.0pt"> Need add
almost all old python2 wheels and fix conflict and dependency
issues.
<o:p></o:p></p>
<ol style="margin-top:0cm" start="2" type="1">
<li class="MsoListParagraph"
style="margin-left:0cm;mso-list:l0 level1 lfo3">Try to find
wheels support both python2 and python3<o:p></o:p></li>
</ol>
<p class="MsoListParagraph">Some wheels could not support both.<o:p></o:p></p>
<ol style="margin-top:0cm" start="3" type="1">
<li class="MsoListParagraph"
style="margin-left:0cm;mso-list:l0 level1 lfo3">Try to build
these 4 images with python3 enabled<o:p></o:p></li>
</ol>
<p class="MsoListParagraph">But these local packages have
several local dependencies, which are all python2 based.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">stx-nova-api-proxy (This one can be
upgraded to py3)<o:p></o:p></p>
<p class="MsoNormal">stx-fm-rest-api <o:p></o:p></p>
<p class="MsoNormal">stx-keystone-api-proxy<o:p></o:p></p>
<p class="MsoNormal">stx-platformclients<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks!<o:p></o:p></p>
<p class="MsoNormal">Zhipeng<o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>From:</b> Miller, Frank
<a class="moz-txt-link-rfc2396E" href="mailto:Frank.Miller@windriver.com"><Frank.Miller@windriver.com></a> <br>
<b>Sent:</b> 2020<span style="font-family:"Microsoft
YaHei",sans-serif;mso-fareast-language:ZH-CN"
lang="ZH-CN">年</span>8<span
style="font-family:"Microsoft
YaHei",sans-serif;mso-fareast-language:ZH-CN"
lang="ZH-CN">月</span>14<span
style="font-family:"Microsoft
YaHei",sans-serif;mso-fareast-language:ZH-CN"
lang="ZH-CN">日</span> 4:07<br>
<b>To:</b> Khalil, Ghada
<a class="moz-txt-link-rfc2396E" href="mailto:Ghada.Khalil@windriver.com"><Ghada.Khalil@windriver.com></a>; Penney, Don
<a class="moz-txt-link-rfc2396E" href="mailto:Don.Penney@windriver.com"><Don.Penney@windriver.com></a>;
'<a class="moz-txt-link-abbreviated" href="mailto:starlingx-discuss@lists.starlingx.io">starlingx-discuss@lists.starlingx.io</a>'
<a class="moz-txt-link-rfc2396E" href="mailto:starlingx-discuss@lists.starlingx.io"><starlingx-discuss@lists.starlingx.io></a>; Liu,
ZhipengS <a class="moz-txt-link-rfc2396E" href="mailto:zhipengs.liu@intel.com"><zhipengs.liu@intel.com></a><br>
<b>Subject:</b> RE: [build]: py2 starlingx images locked
to python modules from June build?<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Zhipeng:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Please suggest a solution to this issue.
One option is to back out the commit that introduced this
issue. Can you identify a solution that doesn’t require you
to back out your commit?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Frank<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>From:</b> Khalil, Ghada <<a
href="mailto:Ghada.Khalil@windriver.com"
moz-do-not-send="true">Ghada.Khalil@windriver.com</a>>
<br>
<b>Sent:</b> Wednesday, August 12, 2020 10:06 PM<br>
<b>To:</b> Penney, Don <<a
href="mailto:Don.Penney@windriver.com"
moz-do-not-send="true">Don.Penney@windriver.com</a>>;
'<a class="moz-txt-link-abbreviated" href="mailto:starlingx-discuss@lists.starlingx.io">starlingx-discuss@lists.starlingx.io</a>' <<a
href="mailto:starlingx-discuss@lists.starlingx.io"
moz-do-not-send="true">starlingx-discuss@lists.starlingx.io</a>>;
Liu, ZhipengS (<a href="mailto:zhipengs.liu@intel.com"
moz-do-not-send="true">zhipengs.liu@intel.com</a>) <<a
href="mailto:zhipengs.liu@intel.com"
moz-do-not-send="true">zhipengs.liu@intel.com</a>>;
Miller, Frank <<a
href="mailto:Frank.Miller@windriver.com"
moz-do-not-send="true">Frank.Miller@windriver.com</a>><br>
<b>Subject:</b> RE: [build]: py2 starlingx images locked
to python modules from June build?<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The launchpad is: <a
href="https://bugs.launchpad.net/starlingx/+bug/1891416"
moz-do-not-send="true">
https://bugs.launchpad.net/starlingx/+bug/1891416</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>From:</b> Penney, Don <<a
href="mailto:Don.Penney@windriver.com"
moz-do-not-send="true">Don.Penney@windriver.com</a>>
<br>
<b>Sent:</b> Wednesday, August 12, 2020 9:21 PM<br>
<b>To:</b> '<a class="moz-txt-link-abbreviated" href="mailto:starlingx-discuss@lists.starlingx.io">starlingx-discuss@lists.starlingx.io</a>' <<a
href="mailto:starlingx-discuss@lists.starlingx.io"
moz-do-not-send="true">starlingx-discuss@lists.starlingx.io</a>>;
Liu, ZhipengS (<a href="mailto:zhipengs.liu@intel.com"
moz-do-not-send="true">zhipengs.liu@intel.com</a>) <<a
href="mailto:zhipengs.liu@intel.com"
moz-do-not-send="true">zhipengs.liu@intel.com</a>>;
Miller, Frank <<a
href="mailto:Frank.Miller@windriver.com"
moz-do-not-send="true">Frank.Miller@windriver.com</a>><br>
<b>Subject:</b> [Starlingx-discuss] [build]: py2 starlingx
images locked to python modules from June build?<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi folks,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It was discovered that the recent
stx-platformclients image was not picking up recent changes
made to the distributedcloud-client package (I believe a
Launchpad will be raised shortly). Tracing back through the
CENGN build logs, the problem appears to stem from the changes
introduced by:<o:p></o:p></p>
<p class="MsoNormal"><a
href="https://review.opendev.org/#/c/737456/11/build-tools/build-docker-images/docker-image-build.cfg"
moz-do-not-send="true">https://review.opendev.org/#/c/737456/11/build-tools/build-docker-images/docker-image-build.cfg</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So for specific images, including
stx-platformclients, the image build is now using a reference
to a presumably static tarball:<o:p></o:p></p>
<p class="MsoNormal"><a
href="http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/stx-centos-py2_stable-wheels.tar"
moz-do-not-send="true">http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/stx-centos-py2_stable-wheels.tar</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Looking at the dir listing, we can see this
tarball is dated June 23<sup>rd</sup>:<o:p></o:p></p>
<p class="MsoNormal"><a
href="http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/"
moz-do-not-send="true">http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">What this means is that these particular
images will be using this locked tarball for installing python
modules from the wheels (ie. The PIP_PACKAGES list)… which
means that an image like stx-platformclients, which is getting
various starlingx clients from wheels, will only ever have
content from that June 23<sup>rd</sup> build.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Was this the intended behavior? Instead of
this “alternate wheels tarball”, shouldn’t we be generating a
wheels tarball with both py2 and py3 support, as long as we’re
building any py2 images?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal">Don.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Starlingx-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Starlingx-discuss@lists.starlingx.io">Starlingx-discuss@lists.starlingx.io</a>
<a class="moz-txt-link-freetext" href="http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss">http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>