<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">All three layers have built
successfully on cengn.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Compier layer: 52 min: <a
moz-do-not-send="true"
href="http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200211T210351Z/">http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200211T210351Z/</a><br>
</div>
<div class="moz-cite-prefix">Distro Layer: 152 min: <a
moz-do-not-send="true"
href="http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200211T215536Z/">http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200211T215536Z/</a><br>
</div>
<div class="moz-cite-prefix">Flock Layer: 54 min: <a
moz-do-not-send="true"
href="http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200211T234731Z/">http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200211T234731Z/</a><br>
</div>
<div class="moz-cite-prefix"> - This build includes iso but not
docker containers</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">The layered build iso can be found
here:<br>
</div>
<div class="moz-cite-prefix"> <a moz-do-not-send="true"
href="http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/latest_build/outputs/iso/">http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/latest_build/outputs/iso/</a></div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">I hope you will take it out for a test
drive.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">The monolithic build will continue to
run for a few weeks, and it can still be found here for now:</div>
<div class="moz-cite-prefix"> <a moz-do-not-send="true"
href="http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_build/outputs/iso/">http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_build/outputs/iso/</a><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">The old path will likely be removed or
symlinked to point to the flock build.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">How do I recognize the layer content in
my build?</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On cengn<br>
</div>
<div class="moz-cite-prefix">
<a class="moz-txt-link-freetext" href="http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/latest_build/outputs/ISO_BUILD_INFO.txt">http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/latest_build/outputs/ISO_BUILD_INFO.txt</a></div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">After install</div>
<div class="moz-cite-prefix"> /etc/build.info</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">The expected content is something like:</div>
<div class="moz-cite-prefix">
<pre>OS="centos"
SW_VERSION="20.01"
BUILD_TARGET="Host Installer"
BUILD_TYPE="Formal"
BUILD_ID="20200211T234731Z"
JOB="STX_build_layer_flock_master_master"
BUILD_BY=<a class="moz-txt-link-rfc2396E" href="mailto:starlingx.build@cengn.ca">"starlingx.build@cengn.ca"</a>
BUILD_NUMBER="16"
BUILD_HOST="starlingx_mirror"
BUILD_DATE="2020-02-11 23:47:31 +0000"
FLOCK_OS="centos"
FLOCK_JOB="STX_build_layer_flock_master_master"
FLOCK_BUILD_BY=<a class="moz-txt-link-rfc2396E" href="mailto:starlingx.build@cengn.ca">"starlingx.build@cengn.ca"</a>
FLOCK_BUILD_NUMBER="16"
FLOCK_BUILD_HOST="starlingx_mirror"
FLOCK_BUILD_DATE="2020-02-11 23:47:31 +0000"
DISTRO_OS="centos"
DISTRO_JOB="STX_build_layer_distro_master_master"
DISTRO_BUILD_BY=<a class="moz-txt-link-rfc2396E" href="mailto:starlingx.build@cengn.ca">"starlingx.build@cengn.ca"</a>
DISTRO_BUILD_NUMBER="16"
DISTRO_BUILD_HOST="starlingx_mirror"
DISTRO_BUILD_DATE="2020-02-11 21:55:36 +0000"
COMPILER_OS="centos"
COMPILER_JOB="STX_build_layer_compiler_master_master"
COMPILER_BUILD_BY=<a class="moz-txt-link-rfc2396E" href="mailto:starlingx.build@cengn.ca">"starlingx.build@cengn.ca"</a>
COMPILER_BUILD_NUMBER="30"
COMPILER_BUILD_HOST="starlingx_mirror"
COMPILER_BUILD_DATE="2020-02-11 21:03:51 +0000"
</pre>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">However I note cengn didn't generate
the content as expected. I'll be working to fix this today.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Next steps:</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">1) Set up the layered jobs to run
nightly</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">2) Modify the layered build jobs to
only run if there is a code change.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"> There is some question as to should an
upper layer rebuild occur if a lower layer was rebuilt, even
though there is no code delta. <br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">I argue yes, If a compiler layer
component changes, I think everything should be rebuilt with the
new tools. Also a flock layer component might change an api, an
include file, etc. and publish it via a dev package. We could try
to tease out if the upper layer is using a dev package that has
been upversioned by a lower layer, but for a first pass I'd
suggest we just rebuild of a lower layer has been updated.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">The argument against hinges largely on
the flock layer containing little if any compiled code. e.g.
Python and Go rather than C or C++. I'll concede that point. <br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">However a change to compile layer, say
'rpm' or 'python' should be picked up right away. All layers
should use the same packaging tools. All python packages should
be validated vs the updated interpreter.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">3) There has been a suggestion to move
iso and container builds out of the flock layer job into an
independent job. <br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">The argument for moving the iso build
into a separate job hinges on the assumption that a lower layer
can be rebuilt without triggering a rebuild of the upper layer.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">The argument to move docker images into
an independent layer is a much stronger one. Most images are
pulling a lot, if not all, of there content from external
sources. We might want to pick up new content in a docker image
even though the flock layer is unchanged.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 2020-02-11 6:47 p.m., Jones, Bruce E
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:9A85D2917C58154C960D95352B22818BF166F9C9@fmsmsx123.amr.corp.intel.com">
<pre class="moz-quote-pre" wrap="">This is very cool. I just merged the Docs changes.
brucej
-----Original Message-----
From: Saul Wold [<a class="moz-txt-link-freetext" href="mailto:sgw@linux.intel.com">mailto:sgw@linux.intel.com</a>]
Sent: Tuesday, February 11, 2020 3:51 PM
To: <a class="moz-txt-link-abbreviated" href="mailto:starlingx-discuss@lists.starlingx.io">starlingx-discuss@lists.starlingx.io</a>
Subject: Re: [Starlingx-discuss] [important] Build layering has merged
Thanks to Scott and Martin along with a cast of other merged. This should be a major improvement for folks working on building and testing changes in StarlingX.
Sau!
On 2/11/20 2:10 PM, Scott Little wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">The build layering feature has merged.
The documentation review is still outstanding, hopefully merged soon:
<a class="moz-txt-link-freetext" href="https://review.opendev.org/#/c/705092/5">https://review.opendev.org/#/c/705092/5</a>
CENGN will build in both layered and non-layered mode for a few days.
The one are where things are significantly different is the location
of lst files, and the fact that each layer carries an independent set
of lst files. Read the doc. I'll try to incorporate any Q/A into
future revisions to the document.
Scott
_______________________________________________
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>
<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>
_______________________________________________
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>