Tristan Cacqueray tdecacqu@redhat.com writes:

On March 30, 2018 8:02 am, Antoine Musso wrote:

...

On 29/03/2018 12:33, Tristan Cacqueray wrote:

...

Greeting folks,

We are pleased to announce the release of Software Factory version 3.0: http://www.softwarefactory-project.io/releases/3.0

It is a software development forge that integrates the last version of Zuul and Nodepool along with a few patches that couldn't make it into the upstream release:

• Ansible-2.4 support: https://review.openstack.org/535839
• Dynamic tenant configuration: https://review.openstack.org/535878
• MQTT reporter: https://review.openstack.org/535543
• Job and Projects dashboard: https://review.openstack.org/550979
• Broken config protection: https://review.openstack.org/535511
• Zookeeper auto-retry: https://review.openstack.org/535537
• OpenContainer Nodepool provider: https://review.openstack.org/535556
• Kubernetes Nodepool provider: https://review.openstack.org/535557

Hello,

It seems those patches were proposed to the v3 feature branch which eventually got mass abandoned on the v3 branch got merged into master.

Is there any plan to get them reviewed/merged and added in the next Zuul/Nodepool versions?

Hi Antoine,

It's unclear what is the scope of the next versions. We integrated the above patches in Software Factory packages as they improve the user experience without changing the services interface. They are up for review on the master branch and we are available to update them if needed.

I think the most important one is the broken config protection as it prevents a single commit to break every tenants.

...

I am specially interested in the Kubernetes Nodepool provider. Wikimedia is planning to migrate its CI stack to Kubernetes and surely we will have time/budget/brains to work on enhancing and maintaining it. Though for now we are still on Zuul v2 and an obsolete Nodepool version.

The proposed Kubernetes driver relies on a containerized openssh service so that zuul-jobs can work seemlessly on OpenStack or Kubernetes resources. Note that it's not a true native Kubernetes driver, for example it doesn't create speculative container images nor use specific Kubernetes workflow. This driver just let you run job in a container instead of a fully fledge instance.

Perhaps the driver should be renamed k8s-ssh if other #zuul users want to leverage Nodepool to truely test container based projects. Anyway that deserves a thread on its own :-)

There's been a lot of research and discussion around this -- it's a complex topic. Now that v3 is released, I plan on writing up the notes we have and laying out a plan for us to discuss. Hopefully I'll be able to do that next week.

-Jim