Hello everyone,
This sprint the team did:
About Software Factory, the team is working on providing an event bus
for eventsoccuring on the platform, allowing closer monitoring and
opening possibilities for external add-onsto 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.
About the Software Factory API, the node endpoint have been improved to
allow a user to easily trigger Nodepool image build and retreive build
logsfrom the CLI.
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 endedup with a toolbox that help us
to create a convenient CI workflow.
Now we areable to functionally 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
maintenance 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 as onmaster.
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.
In addition,more Software Factory components havebeen packaged and
validated via that workflow.
The toolbox is available here:
https://softwarefactory-project.io/r/gitweb?p=software-factory/sfinfo.git;a=tree;h=HEAD;hb=HEAD
As Storyboard is now the Story tracker we bundle in Software Factory we
finally removed completly Redmine from the Software Factory master branch.
An interesting blog post about Software Factory usage for deploying and
managing TripleO deployment have been published:
https://www.rdoproject.org/resources/use-a-ci-cd-workflow-to-manage-tripleo-life-cycle-full/
About RDO,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.
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.
WeIRDO jobs running from ci.centos.org have successfully been tested
against the RDO Cloud beta environment.
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.
A complete UI refactor was released for ARA - Ansible Run Analysis:
https://github.com/openstack/ara
Users are happy and gave great feedback! You can look at a demo of the
new interface here: http://ara-demo.dmsimard.com/
A spec was also submitted to start discussing ARA implementation
directly in Zuul: https://review.openstack.org/#/c/444088/
Sprint review record:https://bluejeans.com/s/vpLUp/
Sprint review etherpad:
http://softwarefactory-project.io/etherpad/p/sprint_review
Next public review will happen Friday Mar 24 at 14:00 UTC, feel free to
join us on #softwarefactory for the event details.
The SF team
_______________________________________________
Softwarefactory-dev mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/softwarefactory-dev
