Hello,

Here is a summary of what the team did from Jan 12 to Jan 25.

Sprint taskboard:
https://tree.taiga.io/project/morucci-software-factory/taskboard/2018-04


Regarding Software Factory:
* we fixed a bug in sfconfig that duplicated zuul3's local gerrit
connection in its config file under certain circumstances.
* we migrated the remaining job to ansible playbook, e.g. DCI and rdopkg
* we cutover zuulv2 and removed all the legacy service from sf-project.io
* We worked on fixing some small issues on the sf-2.7-release
especially an entry were missing from the zuul.conf template and path
to CSS/JS for zuul-web were wrong. Our release process help a lot to
publish new version quickly.
* We worked on restoring the artifact export to logstash with zuul3 (a
feature we add with zuul2 but that was broken with zuul3) we used the
same zuul3 role as upstream.
* We worked on having some protecting at upgrade 2.7 -> 3.0 to make
sure removed services zuul2/nodepool2/jenkins are removed from the
arch and stopped.
* We worked on an implementation of graphite to allow user to use the
same query used to create dashboards upstream for zuul and nodepool on
grafana
* We wrote a blog post about CI/CD of sf-project.io:
http://rdoproject.org/blog/2018/01/CICD-workflow-with-zuul/
* We discussed the opportunity of merging review.rdoproject.org with
softwarefactory-project.io in order to improve, amongst other things,
our resource usage efficiency (both human and CI)
http://eavesdrop.openstack.org/meetings/rdo_meeting___2018_01_17/2018/rdo_meeting___2018_01_17.2018-01-17-15.00.log.html#l-76
* We also discussed the opportunity to host the Zuul and Nodepool for
the Ansible GitHub projects so they don't have to run their own


Regarding openstack-infra:
* we cherry-picked our feature/v3 changes that were automatically
abandoned after the upstream branch was merged into master.
* we contributed to nodepool, zuul-jobs and zuul to prepare ground for
allowing users to access held test nodes in SF (see epic
https://tree.taiga.io/project/morucci-software-factory/epic/937 ). A
PoC demo video is here: https://sendvid.com/nlwhl0xa
* we worked on visualisation of jobs and projects pipeline using
d3.js: https://review.openstack.org/537871 and
https://review.openstack.org/537869
* the third-party-ci effort on zuul-jobs catch a couple of errors:
https://review.openstack.org/#/c/534431/
* We proposed a patch upstream to zuul to document a working feature
that were missing from the doc https://review.openstack.org/#/c/535730
* We proposed a patch upstream to zuul to prevent zuul to run
'merger:cat' gearman task on a project if all loading class are
excluded https://review.openstack.org/#/c/535509/
* We proposed a patch upstream to zuul to extend the tenant definition
format in order that a python script can be used to populate
dynamically the project of a tenant
https://review.openstack.org/#/c/535878/
* We merged feature/zuulv3 into master branches for zuul and nodepool,
one step closer to 3.0 tags
* Split nl01.o.o and nl02.o.o nodepool configuration into nl01.o.o /
nl02.o.o / nl3.o.o / nl04.o.o due to nodepool-launcher CPU usage. Also
changed flavor from 8GB -> 2GB instances.
* zuulv3.o.o replaced with zuul01.o.o, RAM increased to 60GB.
* Infracloud is dead, either we lost HDDs on controllers or HPE has
started to reclaim hardware.
* Removing tripleo-test-cloud-rh1 from nodepool-launchers upstream,
jobs now running in RDOCloud and basically zero maintenance happening
on cloud (meltdown patches not applied). No longer safe for us to be
running jobs there.
* We implemented backups for Zuul Scheduler:
https://review.openstack.org/#/c/532955/
* We proposed an improvement to zuul-changes in order to be able to
dump queues from a file instead:
https://review.openstack.org/#/q/topic:zuul-changes
* We troubleshooted an odd issue around variable precedence in the
zuul-jobs integration tests: https://review.openstack.org/#/c/536615/


Next public review will happen Thursday Feb 8 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