Hello ! Here is a summary of what the team did from November 16 to November 30.
Regarding Software Factory: * We released the version 2.7: https://www.redhat.com/archives/softwarefactory-dev/2017-November/msg00014.html * We upgraded softwarefactory-project.io to version 2.7 and setup a zuulv3 services * We fixed issues found when running the new version in production * We setup a new nodepool tenant for zuulv3 and created dib-centos-7 and dib-fedora-25 labels * We setup a hypervisor-oci hosts for zuulv3 and created centos-oci and f27-oci labels * We migrated a few projects to zuulv3: logreduce, restfuzz, debtor, repoxplorer * Our migration experience will then be shared with other users (DCI, RDO), we're preparing a document to ease the migration: https://softwarefactory-project.io/etherpad/p/zuul3_migration_notes * We worked on fix for job console streaming not working corectly when containers are running concurrently * We created a GitHub Application: https://github.com/apps/softwarefactory-project-zuul * We started to improve our preprod nightly deployment to use a distributed arch with zuul3/nodepool3 (without zuul2/nodepool2 and jenkins) * We wrote "Getting Started With Software Factory And Zuul3" https://github.com/redhat-openstack/website/pull/1119/ * We added a Zuulv3 pipeline for Github to Software Factory: https://softwarefactory-project.io/r/#/c/10366/ * We wrote "Gate Repositories On Github With Software Factory And Zuul3" https://softwarefactory-project.io/r/#/c/10438/ Regarding RDO: * We have updated our infrastructure systems to the latest CentOS patches. * We have identified an issue with our version of the python-cryptography library, working to fix it * We are working on a nodepool issue at review.rdo, where it gets stuck and stalls the Zuul queues. Additional monitoring has been proposed and debug logs has been enabled. * We are working on a plan to transition to a new logserver in an attempt to fix ongoing I/O performance issues: https://etherpad.openstack.org/p/rdo-logserver-replacement * We have started planning the logistics for a new experiment for the upcoming RDO test day where we will have a ready-to-use cloud for people to test things on: https://dmsimard.com/2017/11/29/come-try-a-real-openstack-queens-deployment/ Regarding DLRN: * We have added an audit trail for CI votes and promotions, storing which user initiated them Regarding openstack-infra: * We investigated a k8s Nodepool driver that could be a starting point to use OpenShift as a resource provider for Software Factory: https://review.openstack.org/521356 * We proposed to create openstack-infra/log-classify project to improve the current crm114 script and converge with the logreduce project: https://review.openstack.org/522166 * We proposed an improvement to the zookeeper interface to avoid raise exception on ConnectionLost and SessionExpired: https://review.openstack.org/523640 * We updated the zuul-dashboard patch, some are now merged \o/ https://review.openstack.org/#/q/topic:zuul-web * We proposed to run third party CI checks on zuul-jobs: http://lists.openstack.org/pipermail/openstack-infra/2017-November/005688.html * We proposed a MQTT reporter driver in zuulv3: https://review.openstack.org/#/c/518279/ * We contributed Github application documentation: https://review.openstack.org/522420 * We've spent time trying to troubleshoot, understand and document recurrent DNS lookup failures * We are trying to enforce minimum TTLs to see if it helps with recurrent DNS lookup failures: https://review.openstack.org/#/q/topic:unbound-ttl Regarding ARA: * We've landed a significant API refactor to improve performance which splits "list" and "detail" into different calls: https://review.openstack.org/#/c/516172/ * We've landed a significant refactor which removes static HTML generation, cleans up configuration and splits the configuration into logical parts: https://review.openstack.org/#/c/523013/ * We've started (what will be) a significant refactor around unit, functional and integration tests in order to stop mocking Ansible, improve coverage and performance while being easier to write and maintain: https://review.openstack.org/#/c/522710/ * We've started scheduling tweets for the @ara_community twitter account to share blog posts, news and FAQs about ARA * We've made the web application import the views, API and configuration "just-in-time" in order to prevent loading them needlessly if the app context is available: https://review.openstack.org/#/c/522983/ * We've made a blog post to give an update on the status of ARA 1.0: https://dmsimard.com/2017/11/22/status-update-ara-1.0/ * We've presented a quick update about ARA 1.0 at the Ansible Montreal meetup Regarding rdopkg: * We added a utility to include feature spec files into the documentation automatically * We updated docs and improved doc file naming consistency * We added action alias support * We refactored patch/update-patches to use same code path * We added additional feature tests and extended old ones * We fixed state file handling regression Regarding repoxplorer: * We have refactored the info boxes for projects, groups and contributors to use the REST API * We refactored the output format of top/projects/*.json endpoint to make them compatible with the CSV format, then we added the CSV output format to them Regarding other things: * We follow-up on OSSA-2017-005 and wrote an ERRATA about regressions caused by the initial fix. * We triaged a couple of other OSSA bug to be disclosed in the following weeks * We're hitting the quota limits on our production tenant on rdocloud, so we asked for an extension for christmas * We have met a customer to describe the OpenStack release management process, and how it can help them for their internal products * We did a presentation at ansible montreal meetup to explain how to use CI/CD workflow with Software-Factory to devellop ansible roles and playbooks For a detailed view of what was done, you can check this sprint's taskboard: https://tree.taiga.io/project/morucci-software-factory/taskboard/2017-48 Our review meeting can be watched at https://bluejeans.com/s/k64ny The next public review will happen Thursday Dec 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
