Hello,

Here is a summary of what the team did from June 19 to June 30

Regarding Software Factory:
* We restored latest deployment using heat templates and new image built with dib: https://preprod.softwarefactory-project.io/. Job to deploy it daily remains to be merged
* We re-packaged zuul3 using rh-python35 SCL
* We Rewrote the create_release documentation to take into acount edeploy removal
* We worked on two RDO stories:
** Adding the capability to use an external log server for ci logs
** Adding the capability to run multiple zuul-merger
* We added a new dashboard for jobs using managesf API V2, based on zuul sql reporter [DEMO] * We started work on managesf's API v2. It brings the following improvements:

 * - pagination and sorting of results

 * - better inter connectivity between endpoints

** currently implemented endpoints: builds (from zuul), buildsets (from zuul) and jobs (zuul): GET ** todo: plug policy engine back (need to rework on users & resources api first) * we added a dynamic grafana dashboard for system metrics (a new server will be automatically added * we started to create zuul and nodepool dashboards using grafyaml to be able to manage these dashboards in the config repo * We inproved the ELK stack by reducing index size and adding retention policies * We investigated Kibana dashboard for by project CI stats https://goo.gl/ZdL6TR
* We worked on the part two of the SF intro blog post
* We worked and discussed on the backup system for SF

Regarding RDO:
* The centos-7 image from upstream is now available in review.rdoproject.org for use in TripleO-based jobs * Initial groundwork in getting TripleO-based jobs to work on the upstream-centos-7 image
* TripleO jobs have started running successfully against upstream
* Drafted documentation on how TripleO on review.rdo works: https://review.rdoproject.org/etherpad/p/upstream-tripleo-tweaks * Implemented logging collection from review.rdoproject.org to logs.rdoproject.org * Added a second zuul-merger (with a third on standby) to review.rdoproject.org to cope with load generated by upstream

Regarding DLRN:
* The DLRN infrastructure update has been completed. All workers are now using MariaDB for their databases, and the DLRN API has bene enabled on https://trunk.rdoproject.org. Documentation update is under review: https://github.com/redhat-openstack/website/pull/961

 * -
   https://trunk.rdoproject.org/api-centos-master-uc/api/civotes.htmlto
   check the CI Votes for the centos7-master builder

* DLRN 0.2.0 has been released
* We have added patches to run git clones in parallel, improved locking for remote import operations, and improved our CI coverage with a Tripleo CI-based job
* Created a PoC to use DLRN to build packages for Fedora Atomic CI Project

Regarding ARA:
* Fixed a regression introduced in 0.13.2 that caused files to be displayed incorrectly (double-escaped HTML) and released 0.13.3

Regarding rdopkg:
* We researched python BDD frameworks and selected python-behave to implement rdopkg behavior tests. * We implemented first WIP versions of new rdopkg behavior tests to cover core actions: https://softwarefactory-project.io/r/#/c/8679/

Also:
* Invesgated a logreduce utility to extract anomalies from failed job based on success jobs results. [DEMO] Code is available here: git clone https://softwarefactory-project.io/r/logreduce

The full meeting and demos can be seen here: https://bluejeans.com/s/OHdr1


Next public review will happen Friday July 14 at 13: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

Reply via email to