<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<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:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Times New Roman \,serif";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
p.emailquote, li.emailquote, div.emailquote
{mso-style-name:emailquote;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:1.0pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle28
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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]-->
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:windowtext">Hi Penney and Scott<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">1, As I explained yesterday, you should update these file depending on your cenga setup<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">tools/centos-mirror-tools/config/centos/flock/required_build_tis_pkg.cfg<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">tools/centos-mirror-tools/config/centos/flock/yum.repos.d/StarlingX_cengn_compile_layer.repo<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">tools/centos-mirror-tools/config/centos/flock/yum.repos.d/</span>
<span style="color:windowtext">StarlingX_cengn_distro_layer.repo<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">tools/centos-mirror-tools/config/centos/distro/required_build_tis_pkg.cfg<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">tools/centos-mirror-tools/config/centos/distro/yum.repos.d/StarlingX_cengn_compile_layer.repo<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">root/build-tools/build_iso/centos_required_build_layer.cfg<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">2, I add a parameter for tools/toCOPY/generate-cgcs-centos-repo.sh, “—layer=<layer>”. Take attention.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">Thanks!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:windowtext">Martin, Chen<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">SSP, Software Engineer<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">021-61164330<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><a name="_____replyseparator"></a><b><span style="color:windowtext">From:</span></b><span style="color:windowtext"> Chen, Haochuan Z
<br>
<b>Sent:</b> Monday, October 21, 2019 10:20 PM<br>
<b>To:</b> 'Penney, Don' <Don.Penney@windriver.com>; 'Bailey, Henry Albert (Al)' <Al.Bailey@windriver.com>; 'Little, Scott' <Scott.Little@windriver.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io><br>
<b>Subject:</b> RE: [Starlingx-discuss] FW: [Build] Build layering reviews<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:windowtext">Hi<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">I have update patch again. Last week, I raise this concern<i><o:p></o:p></i></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">3, update script download_mirror.sh and generate-cgts-centos-repo<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">Currently all rpm name in lst is listed with fixed rpm version, which makes layer build easily to be corrupted. For example, any time TIS_PATCH_VER in build_srpm.data update, rpm name in lst should be updated.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">Prefer rpm named with “tis” should be query candidate on cenga, which request download_mirror.sh and generate-cgts-centos-repo update. Prefer we could finish such update in this story, as I think this is a
critical issue.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">So I update patch in stx-tools again to fix this issue. You can check download_mirror.sh<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">I add a step to generate rpm_tis.lst for layer build case. In such case, it will download tis_pkg.lst from cenga. What listed in tis_pkg.lst is distro or compile layer’s built rpm with named xxx.tis.xxx.rpm.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">So no matter src rpm or tarball upgrade, rpm_centos3party.lst is unnecessary to update.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">And I update build-iso, image.inc should concatenate with distro and compile layer’s image.in. As image.inc not only for install package, but also request for generate comps.xml.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">Please check my update and review my patch<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">Thanks!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:windowtext">Martin, Chen<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">SSP, Software Engineer<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">021-61164330<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:windowtext">From:</span></b><span style="color:windowtext"> Chen, Haochuan Z
<br>
<b>Sent:</b> Tuesday, October 15, 2019 10:27 PM<br>
<b>To:</b> Penney, Don <<a href="mailto:Don.Penney@windriver.com">Don.Penney@windriver.com</a>>; Bailey, Henry Albert (Al) <<a href="mailto:Al.Bailey@windriver.com">Al.Bailey@windriver.com</a>>; Little, Scott <<a href="mailto:Scott.Little@windriver.com">Scott.Little@windriver.com</a>>;
'starlingx-discuss@lists.starlingx.io' <<a href="mailto:starlingx-discuss@lists.starlingx.io">starlingx-discuss@lists.starlingx.io</a>><br>
<b>Subject:</b> RE: [Starlingx-discuss] FW: [Build] Build layering reviews<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:windowtext">Hi<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">I have updated patch for layer build<o:p></o:p></span></p>
<p class="MsoNormal"><a href="https://review.opendev.org/#/c/681821/">https://review.opendev.org/#/c/681821/</a><o:p></o:p></p>
<p class="MsoNormal"><a href="https://review.opendev.org/#/c/681823/">https://review.opendev.org/#/c/681823/</a><o:p></o:p></p>
<p class="MsoNormal"><a href="https://review.opendev.org/#/c/681824/">https://review.opendev.org/#/c/681824/</a><o:p></o:p></p>
<p class="MsoNormal"><a href="https://review.opendev.org/#/c/681828/">https://review.opendev.org/#/c/681828/</a><o:p></o:p></p>
<p class="MsoNormal"><a href="https://review.opendev.org/#/c/681832/">https://review.opendev.org/#/c/681832/</a><o:p></o:p></p>
<p class="MsoNormal"><a href="https://review.opendev.org/#/c/681834/">https://review.opendev.org/#/c/681834/</a><o:p></o:p></p>
<p class="MsoNormal"><a href="https://review.opendev.org/#/c/681835/">https://review.opendev.org/#/c/681835/</a><o:p></o:p></p>
<p class="MsoNormal"><a href="https://review.opendev.org/#/c/681836/">https://review.opendev.org/#/c/681836/</a><span style="color:windowtext"><o:p></o:p></span></p>
<p class="MsoNormal"><a href="https://review.opendev.org/#/c/681842/">https://review.opendev.org/#/c/681842/</a><o:p></o:p></p>
<p class="MsoNormal"><a href="https://review.opendev.org/#/c/681847/">https://review.opendev.org/#/c/681847/</a><o:p></o:p></p>
<p class="MsoNormal"><a href="https://review.opendev.org/#/c/681848/">https://review.opendev.org/#/c/681848/</a><span style="color:windowtext"><o:p></o:p></span></p>
<p class="MsoNormal"><a href="https://review.opendev.org/#/c/681851/">https://review.opendev.org/#/c/681851/</a><span style="color:windowtext"><o:p></o:p></span></p>
<p class="MsoNormal"><a href="https://review.opendev.org/#/c/681852/">https://review.opendev.org/#/c/681852/</a><o:p></o:p></p>
<p class="MsoNormal"><a href="https://review.opendev.org/#/c/681854/">https://review.opendev.org/#/c/681854/</a><o:p></o:p></p>
<p class="MsoNormal"><a href="https://review.opendev.org/#/c/681856/">https://review.opendev.org/#/c/681856/</a><o:p></o:p></p>
<p class="MsoNormal"><a href="https://review.opendev.org/#/c/681890/">https://review.opendev.org/#/c/681890/</a><o:p></o:p></p>
<p class="MsoNormal"><a href="https://review.opendev.org/#/c/681892/">https://review.opendev.org/#/c/681892/</a><span style="color:windowtext"><o:p></o:p></span></p>
<p class="MsoNormal"><a href="https://review.opendev.org/#/c/681894/">https://review.opendev.org/#/c/681894/</a><o:p></o:p></p>
<p class="MsoNormal"><a href="https://review.opendev.org/#/c/681898/">https://review.opendev.org/#/c/681898/</a><span style="color:windowtext"><o:p></o:p></span></p>
<p class="MsoNormal"><a href="https://review.opendev.org/#/c/681900/">https://review.opendev.org/#/c/681900/</a><o:p></o:p></p>
<p class="MsoNormal"><a href="https://review.opendev.org/#/c/681901/">https://review.opendev.org/#/c/681901/</a><o:p></o:p></p>
<p class="MsoNormal"><a href="https://review.opendev.org/#/c/681902/">https://review.opendev.org/#/c/681902/</a><o:p></o:p></p>
<p class="MsoNormal"><a href="https://review.opendev.org/#/c/681914/">https://review.opendev.org/#/c/681914/</a><o:p></o:p></p>
<p class="MsoNormal"><a href="https://review.opendev.org/#/c/688598/">https://review.opendev.org/#/c/688598/</a><span style="color:windowtext"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">And I think we still left three issue.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">1, request build-tools/build_iso/centos_required_build_layer.cfg
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">Current for self validation, we could add a file with such content. But we should create a file depending on cenga update<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">compile,file:///localdisk/loadbuild/martin/starlingx/centos_compile_iso_image.inc<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">distro,file:///localdisk/loadbuild/martin/distro/centos_distro_iso_image.inc<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">flock,file:///localdisk/loadbuild/martin/flock/centos_flock_iso_image.inc<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">2, propose use one copy of yum.conf.sample and yum.repo.d/*<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">Currently there is 4 copies of yum.conf.sample and yum.repo.d/*. 3 copies in stx-tools/centos-mirror-tools/config/centos/<layer>/ and 1 copy in stx-tools/centos-mirror-tools/<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"> Propose to remove 3 copies in stx-tools/centos-mirror-tools/config/centos/<layer>/. To avoid user confusing<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">3, update script download_mirror.sh and generate-cgts-centos-repo<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">Currently all rpm name in lst is listed with fixed rpm version, which makes layer build easily to be corrupted. For example, any time TIS_PATCH_VER in build_srpm.data update, rpm name in lst should be updated.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">Prefer rpm named with “tis” should be query candidate on cenga, which request download_mirror.sh and generate-cgts-centos-repo update. Prefer we could finish such update in this story, as I think this is a
critical issue.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">Thanks!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:windowtext">Martin, Chen<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">SSP, Software Engineer<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">021-61164330<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:windowtext">From:</span></b><span style="color:windowtext"> Penney, Don <<a href="mailto:Don.Penney@windriver.com">Don.Penney@windriver.com</a>>
<br>
<b>Sent:</b> Monday, September 30, 2019 11:33 PM<br>
<b>To:</b> Bailey, Henry Albert (Al) <<a href="mailto:Al.Bailey@windriver.com">Al.Bailey@windriver.com</a>>; Chen, Haochuan Z <<a href="mailto:haochuan.z.chen@intel.com">haochuan.z.chen@intel.com</a>>; Little, Scott <<a href="mailto:Scott.Little@windriver.com">Scott.Little@windriver.com</a>>;
'starlingx-discuss@lists.starlingx.io' <<a href="mailto:starlingx-discuss@lists.starlingx.io">starlingx-discuss@lists.starlingx.io</a>><br>
<b>Subject:</b> RE: [Starlingx-discuss] FW: [Build] Build layering reviews<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Is this the issue?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">openstack/python-horizon/centos/python-django-horizon.spec:BuildRequires: cgts-client<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I don’t see anything in this package that should need this dependency, and it should be safe to remove it.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:windowtext">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:windowtext"> Bailey, Henry Albert (Al) [<a href="mailto:Al.Bailey@windriver.com">mailto:Al.Bailey@windriver.com</a>]
<br>
<b>Sent:</b> Monday, September 30, 2019 10:56 AM<br>
<b>To:</b> Chen, Haochuan Z; Little, Scott; 'starlingx-discuss@lists.starlingx.io'<br>
<b>Subject:</b> Re: [Starlingx-discuss] FW: [Build] Build layering reviews<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="color:#1F497D">I think Cgts-client (renamed to system-client) should be in its own repo.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Al<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:windowtext">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:windowtext"> Chen, Haochuan Z [<a href="mailto:haochuan.z.chen@intel.com">mailto:haochuan.z.chen@intel.com</a>]
<br>
<b>Sent:</b> Monday, September 30, 2019 2:06 AM<br>
<b>To:</b> Little, Scott; 'starlingx-discuss@lists.starlingx.io'<br>
<b>Subject:</b> Re: [Starlingx-discuss] FW: [Build] Build layering reviews<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:windowtext">Hi Scott<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">I think have some question or concern.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">1, I find distro layer has dependency to cgts-client, as there is a addin for Horizon, which enables look up flock service info in Horizon.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">So there is task is must for layer building, which is out of my expectation. I begin to tackle these task.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:27.0pt;text-indent:-.25in;vertical-align:middle">
<span style="font-size:10.0pt;font-family:Symbol">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:12.0pt">Relocate from git 'config', subdir 'sysinv/cgts-client', to git 'utilities', subdir 'system-client',
<b>with full git history.</b></span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:27.0pt;text-indent:-.25in;vertical-align:middle">
<span style="font-size:10.0pt;font-family:Symbol">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:12.0pt">Rename rpm package from 'cgts-client' to 'system-client'</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:27.0pt;text-indent:-.25in;vertical-align:middle">
<span style="font-size:10.0pt;font-family:Symbol">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:12.0pt">Fix rpm packages that list cgts-client as a require or build require</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:27.0pt;text-indent:-.25in;vertical-align:middle">
<span style="font-size:10.0pt;font-family:Symbol">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:12.0pt">Rename python module from 'cgts-client' to 'system-client'</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:27.0pt;text-indent:-.25in;vertical-align:middle">
<span style="font-size:10.0pt;font-family:Symbol">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:12.0pt">Scan function names and/or variables for any that contain 'cgts' ... replace with 'system' ... can we do this in a backward compatible way?</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:27.0pt;text-indent:-.25in;vertical-align:middle">
<span style="font-size:10.0pt;font-family:Symbol">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:12.0pt">Fix users of the client to import using the new name, and reference any renamed functions/data.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:27.0pt;text-indent:-.25in;vertical-align:middle">
<span style="font-size:10.0pt;font-family:Symbol">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:12.0pt">Fix ISO and/or docker images that list this package for inclusion.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">2, “all” layer maybe doesn’t work, warning!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">For current patch for generate-cgts-centos-repo.sh, all layer’s rpms_lst_file is generated by merge “compiler/distro/flock” three layers, config/centos/all doesn’t be referenced, which is none sense. Which
means package such bash-4.2.46-31.el7.tis.4.x86_64.rpm, named with “tis” is also in mirror. This maybe interference source package building. I think request some fix in generate-cgts-centos-repo.sh to omit package with “tis” in name.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">3, Layered build introduces rpms_cemtos.lst dependency on TIS_PATCH_VER in build_srpm.data, which make developer easily disrupt layered building mechanism.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">For distro and flock layer, it has dependency to starlingX customized package, for example, distro layer require bash.tis.<tis patch version>.<version>.rpm, which will be add in config/centos/distro/rpms_centos3rdparty.lst<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">If new developer forget to update and build all package, it maybe disrupt layered building.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">BR!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:windowtext">Martin, Chen<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">SSP, Software Engineer<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">021-61164330<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:windowtext">From:</span></b><span style="color:windowtext"> Chen, Haochuan Z
<br>
<b>Sent:</b> Friday, September 27, 2019 4:40 PM<br>
<b>To:</b> Scott Little <<a href="mailto:scott.little@windriver.com">scott.little@windriver.com</a>>;
<a href="mailto:starlingx-discuss@lists.starlingx.io">starlingx-discuss@lists.starlingx.io</a><br>
<b>Subject:</b> RE: FW: [Starlingx-discuss] [Build] Build layering reviews<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:windowtext">Thanks, Scott. I have studied so much.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">BR!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:windowtext">Martin, Chen<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">SSP, Software Engineer<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">021-61164330<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:windowtext">From:</span></b><span style="color:windowtext"> Scott Little <<a href="mailto:scott.little@windriver.com">scott.little@windriver.com</a>>
<br>
<b>Sent:</b> Thursday, September 26, 2019 11:39 PM<br>
<b>To:</b> Chen, Haochuan Z <<a href="mailto:haochuan.z.chen@intel.com">haochuan.z.chen@intel.com</a>>;
<a href="mailto:starlingx-discuss@lists.starlingx.io">starlingx-discuss@lists.starlingx.io</a><br>
<b>Subject:</b> Re: FW: [Starlingx-discuss] [Build] Build layering reviews<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Returning this discussion to the mailing list.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If possible, join the Build call next week. <a href="https://wiki.openstack.org/wiki/Starlingx/Meetings">
https://wiki.openstack.org/wiki/Starlingx/Meetings</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">1)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">When mock installs for the first time. it uses rpms that have been download via lst file. The mock pseudo-layer lst files capture reflect the rpms needed by mock. The mock lst's are merged with the layers lst's. In this way, the mock
rpms don't have to be listed in each and every layer's lst.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">2)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Adding tools to generate an lst file reflacting the output of a build layer, and adding that lst for consumprion by higher layers, is indeed a possibility possibility I wanted to persue. Reference to that output lst could then be added
to as a new arg to the download script when invoked by a higher layer, or a config file could specify where to find it (cengn is the likely default supplier).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">compile layer)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">The compile layer is a true layer, built prior to the distro layer. Only a few build related packages go here. Compilers, language interpreters, rpm. I wanted those packages in place so that all distro layer packages build with the same
tools.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Scott<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">On 2019-09-25 10:24 p.m., Chen, Haochuan Z wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="color:windowtext">Still not clear about mock layer.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:windowtext"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:windowtext">1, In build container, mock is already installed, why request to download mock required package firstly?</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:windowtext">2, To build distro or flock layer, we could add compile layer’s tis rpm in distro and flock layer’s lst file. By download compile layer’s binary in mirror, it could also ensure user building package with same
tool.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:windowtext">Why introduces compile layer?</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:windowtext"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:windowtext">Thanks!</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:windowtext"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="color:windowtext">Martin, Chen</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:windowtext">SSP, Software Engineer</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:windowtext">021-61164330</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="color:windowtext"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:windowtext">From:</span></b><span style="color:windowtext"> Scott Little
<a href="mailto:scott.little@windriver.com"><scott.little@windriver.com></a> <br>
<b>Sent:</b> Thursday, September 26, 2019 12:25 AM<br>
<b>To:</b> Chen, Haochuan Z <a href="mailto:haochuan.z.chen@intel.com"><haochuan.z.chen@intel.com></a><br>
<b>Subject:</b> Re: FW: [Starlingx-discuss] [Build] Build layering reviews</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<p class="MsoNormal">See inline ...<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Scott<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">On 2019-09-23 11:00 a.m., Chen, Haochuan Z wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">Hi Scott<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I studied your patch and some questions.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">1, why there is mock and compile layer, what's usage or intention for these two layers?<o:p></o:p></p>
</div>
</blockquote>
<p class="MsoNormal">Build-pkgs uses a tool called mock to create a reproducible compilation sandbox. It is chroot like environmnet into which rpms are installed to construct a minimal build environment.<br>
<br>
The mock layer is not built. I created it as a placeholder for the lst files that downloads all the rpms that mock requires. Prior to building a layer, the lst files for both the layer being build, and the mock pseudo layer, need to be processed. Without
the mock pseudo layer, we would have to replicate that list of mock required rpms in each and ever layer's lst files.<br>
<br>
The concept ran into a bit of trouble because some of the rpms needed by mock are themselves built by the compile or distro layers (with a newer revision). So the
<br>
mock pseudo layer might actually omit those rpms from it's lst file, and they needed to be listed in the layer lst files instead.<o:p></o:p></p>
<p> <o:p></o:p></p>
<p>The compile layer is a true layer, built prior to the distro layer. Only a few build related packages go here. Compilers, language interpreters, rpm. I wanted those packages in place so that all distro layer packages build with the same tools.<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">2, for download_mirror.sh, it generate rpm list by merge file in config/centos/<layer>/<rpm list file name> and rpm list file in stx/<project name><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> But for generate-cgcs-centos-repo.sh, it use rpm list file in centos-mirror-tools folder. Rpm package should be added in two rpm list file.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> It is not good for maintenance. What about remove rpm list file in centos-mirror-tools folder<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <i>rpms_centos.lst/rpms_centos3rdparties.lst/rpms_3rdparties.lst/other_downloads.lst/ tarball-dl.lst</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
</blockquote>
<p>That was considered and debated. The concern was that the many git repos that make up the layer would list different versions of the same package. Then what do we do? Throw an error? Silently use the newest package? So we elected to keep binary rpms
needed to satisfy dependencies listed in a central place.<o:p></o:p></p>
<p>At some point we may want to explore allowing lst files specify required package but not version (beyond a possible minimum version) when on the master branch, and have a way to 'lock down' the versions only for a release branch.<o:p></o:p></p>
<p> <o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">3, Question about setup yum repo for rpm tailing with “tis” such as xxx.<b><span style="color:red">tis</span></b>.x86_64.rpm or xxx.<b><span style="color:red">tis</span></b>.noarch.rpm<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">In this patch <a href="https://review.opendev.org/#/c/681821/1">
<span style="color:#0563C1">https://review.opendev.org/#/c/681821/1</span></a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>There is such line in config/centos/flock/yum.repos.d/StarlingX_cengn_distro_layer.repo</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>[Starlingx-cengn_distro_layer]</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>name=Starlingx-cengn_distro_layer</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>baseurl=<a href="http://127.0.0.1:8088/localdisk/loadbuild/">http://127.0.0.1:8088/localdisk/loadbuild/</a></i><b><i><span style="color:red">slittle1/restructure3b</span></i></b><i>/std/rpmbuild/RPMS/</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>enabled=1</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>[Starlingx-cengn_distro_layer-rt]</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>name=Starlingx-cengn_distro_layer</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>baseurl=<a href="http://127.0.0.1:8088/localdisk/loadbuild/">http://127.0.0.1:8088/localdisk/loadbuild/</a></i><b><i><span style="color:red">slittle1/restructure3b</span></i></b><i>/rt/rpmbuild/RPMS/</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>enabled=1</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">also in<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">config/centos/flock/yum.repos.d/StarlingX_cengn_compile_layer.repo<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">config/centos/distro/yum.repos.d/StarlingX_cengn_compile_layer.repo<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">My understanding is rpm tailing with “tis” should also upload to cengn, rpm name listed in centos-mirror-tools/config/centos/flock/rpms_centos3rdparties.lst<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">So these three files should be unnecessary, with cengn update for layered build.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="text-indent:.5in">config/centos/flock/yum.repos.d/StarlingX_cengn_distro_layer.repo<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">config/centos/flock/yum.repos.d/StarlingX_cengn_compile_layer.repo<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">config/centos/distro/yum.repos.d/StarlingX_cengn_compile_layer.repo<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
</blockquote>
<p>For development testing, I had to hack together a simulated cengn by running lighttpd on 127.0.0.1:8088 and allowing it to serve up files from builds of lower layers<o:p></o:p></p>
<p>restructure3a == layer-comiler layer build<o:p></o:p></p>
<p>restructure3b == layer-distro layer build<o:p></o:p></p>
<p>restructure3c == layer-flock layer build (although there shouldn't be a repo entry referring to that one)<o:p></o:p></p>
<p>Finalizing the repo entries would have to wait until cengn was up an running.<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">4, In generate-cgcs-centos-repo.sh there is --layer-dir, and such content in your patch commit message<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>generate-cgcs-centos-repo.sh \</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>--layer-dir=/localdisk/loadbuild/slittle1/layer-compile/std/rpmbuild/RPMS/ \</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>--layer-dir=/localdisk/loadbuild/slittle1/layer-distro/std/rpmbuild/RPMS/ \</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>--layer-dir=/localdisk/loadbuild/slittle1/layer-distro/rt/rpmbuild/RPMS/ \</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>/import/mirrors/starlingx</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> For all rpm download from cengn, --layer-dir is unnecessary to generate link, correct?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
</blockquote>
<p>This is another way to do cross layer development testing without support from cengn. Again the goal is to allow an upper layer build to download rpms from a lower layer build on the same machine.<o:p></o:p></p>
<p> <o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">5, could you share build-tools/build-iso/centos_required_build_layer.cfg, share to me<o:p></o:p></p>
</div>
</blockquote>
<p> <o:p></o:p></p>
<p class="MsoNormal">Did that not get published in my reviews? Content is very simple.<br>
<br>
compile,<a href="file://localdisk/loadbuild/slittle1/restructure3a/centos_compile_iso_image.inc">file:///localdisk/loadbuild/slittle1/restructure3a/centos_compile_iso_image.inc</a><br>
distro,<a href="file://localdisk/loadbuild/slittle1/restructure3b/centos_distro_iso_image.inc">file:///localdisk/loadbuild/slittle1/restructure3b/centos_distro_iso_image.inc</a><br>
flock,<a href="file://localdisk/loadbuild/slittle1/restructure3c/centos_flock_iso_image.inc">file:///localdisk/loadbuild/slittle1/restructure3c/centos_flock_iso_image.inc</a><o:p></o:p></p>
<p> <o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">6, For distro/compiler/flock, all are separate layer?<o:p></o:p></p>
</div>
</blockquote>
<p>Yes<o:p></o:p></p>
<p> <o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">My current step<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>repo init -u <a href="https://opendev.org/starlingx/manifest.git">
https://opendev.org/starlingx/manifest.git</a></i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>apply this patch to .repo/manifests</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i><a href="https://review.opendev.org/#/c/681914/1">https://review.opendev.org/#/c/681914/1</a></i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>repo init -m compile.xml</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>repo sync</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>apply these to patch</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i><a href="https://review.opendev.org/#/c/681821/1">https://review.opendev.org/#/c/681821/1</a></i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i><a href="https://review.opendev.org/#/c/681828/1">https://review.opendev.org/#/c/681828/1</a></i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>./download_mirror.sh -n -g -l flock -c config/centos/compiler/yum.conf.sample -S
</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>./toCopy/generate-cgts-centos-repo output/stx-r1/CentOS/pike/</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>build-pkgs</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>build-iso</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">BR!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Martin, Chen<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">SSP, Software Engineer<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">021-61164330<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">-----Original Message-----<br>
From: Scott Little <a href="mailto:scott.little@windriver.com"><scott.little@windriver.com></a>
<br>
Sent: Thursday, September 19, 2019 9:54 PM<br>
To: Chen, Haochuan Z <a href="mailto:haochuan.z.chen@intel.com"><haochuan.z.chen@intel.com></a><br>
Subject: Re: FW: [Starlingx-discuss] [Build] Build layering reviews<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Most of the required changes were already merged.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I'll scan the spec when time permits to see if I missed anything.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Scott<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">On 2019-09-16 12:01 p.m., Chen, Haochuan Z wrote:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> Hi Scott<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> I read your patch for build layering, but could not find patch for build script.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> Description in spec <a href="https://review.opendev.org/#/c/672288/12/">
https://review.opendev.org/#/c/672288/12/</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> Modifications to package build scripts ... build-pkgs, <o:p>
</o:p></p>
</div>
<div>
<p class="MsoNormal">> build-srpms-parallel, build-srpms-serial, build-rpms-parallel, build-rpms-serial (cgcs-root):<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> Thanks<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> Martin, Chen<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> SSP, Software Engineer<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> 021-61164330<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> -----Original Message-----<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> From: Xie, Cindy<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> Sent: Friday, September 13, 2019 12:24 PM<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> To: Chen, Haochuan Z <<a href="mailto:haochuan.z.chen@intel.com">haochuan.z.chen@intel.com</a>><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> Cc: Hu, Yong <<a href="mailto:yong.hu@intel.com">yong.hu@intel.com</a>><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> Subject: FW: [Starlingx-discuss] [Build] Build layering reviews<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> Martin,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> I am wondering if you will be interested to working on this task. To me, having layering build and provide efficiency to developers are very important for StarlingX. It also provide a chance that you and work together w/ WR folks being
more close collaboration. Let me know your interested level.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> Thx. -cindy<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> -----Original Message-----<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> From: Scott Little <<a href="mailto:scott.little@windriver.com">scott.little@windriver.com</a>><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> Sent: Friday, September 13, 2019 4:55 AM<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> To: <a href="mailto:starlingx-discuss@lists.starlingx.io">
starlingx-discuss@lists.starlingx.io</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> Subject: [Starlingx-discuss] [Build] Build layering reviews<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> My prototype code for the layered build has been posted to gerrit.
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> (listed below)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> I was briefly able to build all layers, and produce an iso with the same package content as the cengn build. Then I was diverted by non-trivial changes to the restructuring work. What I have posted is now several weeks out of date and
will almost certainly will not work. The devil is in keeping the lst files in sync with the ever changing master branch.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> Other commitments will prevent me from resuming this work until November. If anyone wants to whip the lst files into shape and try to get the build working again, be my guest.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> Final delivery will require changes to the CENGN build scripts (Don or Myself), and a freeze on packaging changes will likely be required for aprox 3 days to finalize the lst files.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> Scott<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> ---------------- <Snip> ----------------<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> <a href="https://review.opendev.org/#/c/681821/1">https://review.opendev.org/#/c/681821/1</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> <a href="https://review.opendev.org/#/c/681914/1">https://review.opendev.org/#/c/681914/1</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> <a href="https://review.opendev.org/#/c/681823/1">https://review.opendev.org/#/c/681823/1</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> <a href="https://review.opendev.org/#/c/681824/1">https://review.opendev.org/#/c/681824/1</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> <a href="https://review.opendev.org/#/c/681828/1">https://review.opendev.org/#/c/681828/1</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> <a href="https://review.opendev.org/#/c/681832/2">https://review.opendev.org/#/c/681832/2</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> <a href="https://review.opendev.org/#/c/681834/1">https://review.opendev.org/#/c/681834/1</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> <a href="https://review.opendev.org/#/c/681836/1">https://review.opendev.org/#/c/681836/1</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> <a href="https://review.opendev.org/#/c/681835/1">https://review.opendev.org/#/c/681835/1</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> <a href="https://review.opendev.org/#/c/681842/1">https://review.opendev.org/#/c/681842/1</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> <a href="https://review.opendev.org/#/c/681847/1">https://review.opendev.org/#/c/681847/1</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> <a href="https://review.opendev.org/#/c/681848/1">https://review.opendev.org/#/c/681848/1</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> <a href="https://review.opendev.org/#/c/681851/1">https://review.opendev.org/#/c/681851/1</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> <a href="https://review.opendev.org/#/c/681852/1">https://review.opendev.org/#/c/681852/1</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> <a href="https://review.opendev.org/#/c/681854/1">https://review.opendev.org/#/c/681854/1</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> <a href="https://review.opendev.org/#/c/681856/1">https://review.opendev.org/#/c/681856/1</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> <a href="https://review.opendev.org/#/c/681890/1">https://review.opendev.org/#/c/681890/1</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> <a href="https://review.opendev.org/#/c/681892/1">https://review.opendev.org/#/c/681892/1</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> <a href="https://review.opendev.org/#/c/681892/1">https://review.opendev.org/#/c/681892/1</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> <a href="https://review.opendev.org/#/c/681898/1">https://review.opendev.org/#/c/681898/1</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> <a href="https://review.opendev.org/#/c/681900/1">https://review.opendev.org/#/c/681900/1</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> <a href="https://review.opendev.org/#/c/681901/1">https://review.opendev.org/#/c/681901/1</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> <a href="https://review.opendev.org/#/c/681902/1">https://review.opendev.org/#/c/681902/1</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><span style="font-size:12.0pt;font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> _______________________________________________<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> Starlingx-discuss mailing list<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> <a href="mailto:Starlingx-discuss@lists.starlingx.io">Starlingx-discuss@lists.starlingx.io</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">> <a href="http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss">
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman \,serif""> </span><o:p></o:p></p>
</div>
</blockquote>
<p> <o:p></o:p></p>
</blockquote>
<p><o:p> </o:p></p>
</div>
</body>
</html>