<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div id="magicdomid8" class=""><span
class="author-a-7xz85zrje6z79zvz83zffhz76zz84zz82z">Hello
everyone,</span>
<div id="magicdomid10" class=""><br>
</div>
<div id="magicdomid11" class=""><span
class="author-a-7xz85zrje6z79zvz83zffhz76zz84zz82z">This
sprint the team did:</span></div>
<div id="magicdomid508" class="ace-line"><br>
</div>
<span class="author-a-z65zi4l6z76zz81zz78zefz74zz81zroz77zz69z">About
Software Factory, the team is working on providing an event bus
for event</span><span
class="author-a-z88zfz75zz69z9kz86zcz122z3ecz80zz65zz89z5">s</span><span
class="author-a-z65zi4l6z76zz81zz78zefz74zz81zroz77zz69z">
occuring on the platform</span><span
class="author-a-z88zfz75zz69z9kz86zcz122z3ecz80zz65zz89z5">,
allowing closer monitoring and opening possibilities for
external add-ons</span><span
class="author-a-z65zi4l6z76zz81zz78zefz74zz81zroz77zz69z"> to be
written like Bugzilla ticket updater. During the sprint we
focused on the ACLs to connect and I/O to that bus and made
Gerrit publish its event into it.</span></div>
<div id="magicdomid9" class=""><br>
</div>
<div id="magicdomid11" class=""><span
class="author-a-z65zi4l6z76zz81zz78zefz74zz81zroz77zz69z">About
the Software Factory API, the node endpoint have been improved
to allow a user to easily trigger Nodepool image build and
retreive build logs</span><span
class="author-a-z88zfz75zz69z9kz86zcz122z3ecz80zz65zz89z5"> from
the CLI.</span></div>
<div id="magicdomid12" class=""><br>
</div>
<div id="magicdomid15" class=""><span
class="author-a-z65zi4l6z76zz81zz78zefz74zz81zroz77zz69z">We are
also working on improving the release process of Software
Factory by integrating the RPM packaging part in our CI process.
After some brainstormings about the workflow we end</span><span
class="author-a-z65zz67zuz72zz81zz86zz80z1kz75z4z79zvkdz84z">ed</span><span
class="author-a-z65zi4l6z76zz81zz78zefz74zz81zroz77zz69z"> up
with a toolbox that help us to create a convenient CI workflow.</span></div>
<div id="magicdomid16" class=""><br>
</div>
<div id="magicdomid21" class=""><span
class="author-a-z65zi4l6z76zz81zz78zefz74zz81zroz77zz69z">Now we
are</span><span
class="author-a-z88zfz75zz69z9kz86zcz122z3ecz80zz65zz89z5"> </span><span
class="author-a-z65zi4l6z76zz81zz78zefz74zz81zroz77zz69z">able
to functiona</span><span
class="author-a-z88zfz75zz69z9kz86zcz122z3ecz80zz65zz89z5">l</span><span
class="author-a-z65zi4l6z76zz81zz78zefz74zz81zroz77zz69z">ly
test Software Factory, installed with RPM packages, and gate
changes on packages and sources on that test. Also we were able
to, thanks to the tooling written, to create the next maint</span><span
class="author-a-z88zfz75zz69z9kz86zcz122z3ecz80zz65zz89z5">e</span><span
class="author-a-z65zi4l6z76zz81zz78zefz74zz81zroz77zz69z">nance
branch (2.4) of Software Factory by creating a working Koji
build target, Git branch on sources and distgit, tag built
packages from the Koji master target to the 2.4 target. This new
target enables the same CI workflow </span><span
class="author-a-z65zz67zuz72zz81zz86zz80z1kz75z4z79zvkdz84z">as
on</span><span
class="author-a-z65zi4l6z76zz81zz78zefz74zz81zroz77zz69z">
master.</span></div>
<div id="magicdomid23" class=""><span
class="author-a-z65zi4l6z76zz81zz78zefz74zz81zroz77zz69z">Finally
we created a working final repo with mash. This workflow will
need to be used and tested more but we are happy about it as we
successfuly started to use it on top of Zuul for building and
releasing Software Factory.</span></div>
<div id="magicdomid24" class=""><span
class="author-a-z65zi4l6z76zz81zz78zefz74zz81zroz77zz69z">In
addition</span><span
class="author-a-z65zz67zuz72zz81zz86zz80z1kz75z4z79zvkdz84z">,</span><span
class="author-a-z65zi4l6z76zz81zz78zefz74zz81zroz77zz69z"> more
Software Factory components ha</span><span
class="author-a-z88zfz75zz69z9kz86zcz122z3ecz80zz65zz89z5">ve</span><span
class="author-a-z65zi4l6z76zz81zz78zefz74zz81zroz77zz69z"> been
packaged and validated via that workflow.</span></div>
<div id="magicdomid25" class=""><span
class="author-a-z65zi4l6z76zz81zz78zefz74zz81zroz77zz69z">The
toolbox is available here: </span><span
class="author-a-z65zi4l6z76zz81zz78zefz74zz81zroz77zz69z url"><a
href="https://softwarefactory-project.io/r/gitweb?p=software-factory/sfinfo.git;a=tree;h=HEAD;hb=HEAD">https://softwarefactory-project.io/r/gitweb?p=software-factory/sfinfo.git;a=tree;h=HEAD;hb=HEAD</a></span></div>
<div id="magicdomid26" class=""><br>
</div>
<div id="magicdomid28" class=""><span
class="author-a-z65zi4l6z76zz81zz78zefz74zz81zroz77zz69z">As
Storyboard is now the Story tracker we bundle in Software
Factory we finally removed completly Redmine from the Software
Factory master branch.</span></div>
<div id="magicdomid29" class=""><br>
</div>
<div id="magicdomid31" class=""><span
class="author-a-z65zi4l6z76zz81zz78zefz74zz81zroz77zz69z">An
interesting blog post about Software Factory usage for deploying
and managing TripleO deployment have been published: </span><span
class="author-a-z65zi4l6z76zz81zz78zefz74zz81zroz77zz69z url"><a
href="https://www.rdoproject.org/resources/use-a-ci-cd-workflow-to-manage-tripleo-life-cycle-full/">https://www.rdoproject.org/resources/use-a-ci-cd-workflow-to-manage-tripleo-life-cycle-full/</a></span></div>
<div id="magicdomid32" class=""><br>
</div>
<div id="magicdomid36" class=""><span
class="author-a-z65zi4l6z76zz81zz78zefz74zz81zroz77zz69z">About
RDO,</span><span
class="author-a-4z76zpqz122zz80zz72zksz65zz82z1vz67zz85zz82z">
we completed the initial deployment of the DLRN API, which will
simplify our RDO CI process for trunk repos. There is further
work ahead and we are working on a Python client to make the
API easy to consume, as well as a redesigned architecture once
we migrate our instance to the RDO Cloud.</span></div>
<div id="magicdomid355" class="ace-line"><br>
</div>
<div id="magicdomid412" class="ace-line"><span
class="author-a-iz74zz82z6wz67zz87zhgjz78zz67zhkz81zy">We've
helped the rhos-ops team testing the RDO cloud beta by sending
different kind of real-life workloads from review.rdoproject.org
as well as ci.centos.org.</span></div>
<div id="magicdomid37" class=""><br>
</div>
<div id="magicdomid209" class="ace-line"><span
class="author-a-4z76zpqz122zz80zz72zksz65zz82z1vz67zz85zz82z">WeIRDO
</span><span
class="author-a-iz74zz82z6wz67zz87zhgjz78zz67zhkz81zy">jobs
running from ci.centos.org have successfully been tested against
the RDO Cloud beta environment.</span></div>
<div id="magicdomid429" class="ace-line"><span
class="author-a-iz74zz82z6wz67zz87zhgjz78zz67zhkz81zy">We are
planning to migrate WeIRDO jobs away from ci.centos.org since
they do not require bare metal hardware to run. This will free
up capacity there for TripleO-based jobs as well as for other
ci.centos.org tenants and everyone will be happier.</span></div>
<div id="magicdomid40" class=""><br>
</div>
<div id="magicdomid269" class="ace-line"><span
class="author-a-iz74zz82z6wz67zz87zhgjz78zz67zhkz81zy">A
complete UI refactor was released for ARA - Ansible Run
Analysis: </span><span
class="author-a-iz74zz82z6wz67zz87zhgjz78zz67zhkz81zy url"><a
href="https://github.com/openstack/ara">https://github.com/openstack/ara</a></span></div>
<div id="magicdomid314" class="ace-line"><span
class="author-a-iz74zz82z6wz67zz87zhgjz78zz67zhkz81zy">Users are
happy and gave great feedback! You can look at a demo of the new
interface here: </span><span
class="author-a-iz74zz82z6wz67zz87zhgjz78zz67zhkz81zy url"><a
href="http://ara-demo.dmsimard.com/">http://ara-demo.dmsimard.com/</a></span></div>
<div id="magicdomid353" class="ace-line"><span
class="author-a-iz74zz82z6wz67zz87zhgjz78zz67zhkz81zy">A spec
was also submitted to start discussing ARA implementation
directly in Zuul: </span><span
class="author-a-iz74zz82z6wz67zz87zhgjz78zz67zhkz81zy url"><a
href="https://review.openstack.org/#/c/444088/">https://review.openstack.org/#/c/444088/</a></span></div>
<div id="magicdomid354" class="ace-line"><br>
<div id="magicdomid573" class="ace-line"><span
class="author-a-7xz85zrje6z79zvz83zffhz76zz84zz82z">Sprint
review record:</span><span
class="author-a-4z70z2epz78zz80zz73zz79znqz87znlz73zy"> </span><span
class="author-a-4z70z2epz78zz80zz73zz79znqz87znlz73zy url"><a
href="https://bluejeans.com/s/vpLUp/">https://bluejeans.com/s/vpLUp/</a></span></div>
<div id="magicdomid18" class=""><span
class="author-a-7xz85zrje6z79zvz83zffhz76zz84zz82z">Sprint
review etherpad: </span><span
class="author-a-7xz85zrje6z79zvz83zffhz76zz84zz82z url"><a
href="http://softwarefactory-project.io/etherpad/p/sprint_review">http://softwarefactory-project.io/etherpad/p/sprint_review</a></span></div>
<div id="magicdomid19" class=""><br>
</div>
<div id="magicdomid20" class=""><span
class="author-a-7xz85zrje6z79zvz83zffhz76zz84zz82z">Next
public review will happen Friday Mar 24 at 14:00 UTC, feel
free to join us on #softwarefactory for the event details.</span></div>
<div id="magicdomid21" class=""><br>
</div>
<div id="magicdomid22" class=""><span
class="author-a-7xz85zrje6z79zvz83zffhz76zz84zz82z">The SF
team</span></div>
<br>
</div>
</body>
</html>