267 lines
10 KiB
HTML
267 lines
10 KiB
HTML
<!DOCTYPE HTML>
|
||
<!--
|
||
Arcana by HTML5 UP
|
||
html5up.net | @ajlkn
|
||
Free for personal and commercial use under the CCA 3.0 license (html5up.net/license)
|
||
-->
|
||
<html>
|
||
<head>
|
||
<title>Zuul: Users</title>
|
||
<meta charset="utf-8" />
|
||
<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png">
|
||
<link rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png">
|
||
<link rel="icon" type="image/png" sizes="16x16" href="/favicon-16x16.png">
|
||
<link rel="manifest" href="/site.webmanifest">
|
||
<link rel="mask-icon" href="/safari-pinned-tab.svg" color="#071d49">
|
||
<meta name="msapplication-TileColor" content="#00aba9">
|
||
<meta name="theme-color" content="#ffffff">
|
||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||
<!--[if lte IE 8]><script src="assets/js/ie/html5shiv.js"></script><![endif]-->
|
||
<link rel="stylesheet" href="assets/css/main.css" />
|
||
<!--[if lte IE 8]><link rel="stylesheet" href="assets/css/ie8.css" /><![endif]-->
|
||
<!--[if lte IE 9]><link rel="stylesheet" href="assets/css/ie9.css" /><![endif]-->
|
||
</head>
|
||
<body>
|
||
<div id="page-wrapper">
|
||
|
||
<!-- Header -->
|
||
<div id="header">
|
||
|
||
<!-- Logo -->
|
||
<h1>
|
||
<a href="/"><img id="logo" src="images/logo.svg" alt="Zuul"/></a>
|
||
</h1>
|
||
|
||
<!-- Nav -->
|
||
<nav id="nav">
|
||
<ul>
|
||
<li><a href="index.html">Home</a></li>
|
||
<li class="current"><a href="users.html">Users</a></li>
|
||
<li>
|
||
<a href="docs/">Documentation</a>
|
||
<ul>
|
||
<li><a href="docs/zuul/">Zuul</a></li>
|
||
<li><a href="docs/nodepool">Nodepool</a></li>
|
||
<li><a href="docs/zuul-jobs">Zuul Jobs</a></li>
|
||
<li><a href="docs/zuul-base-jobs">Base Jobs</a></li>
|
||
<li><a href="docs/zuul-sphinx/">Zuul Sphinx</a></li>
|
||
<li><a href="docs/faq.html">Zuul FAQ</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="community.html">Community</a></li>
|
||
</ul>
|
||
</nav>
|
||
</div>
|
||
|
||
<section class="wrapper style1">
|
||
<div class="container">
|
||
<div id="content">
|
||
<article>
|
||
<header class="major">
|
||
<h2>Zuul Users</h2>
|
||
</header>
|
||
|
||
<h3>
|
||
<a href="http://superuser.openstack.org/articles/zuul-case-study-bmw/">
|
||
BMW
|
||
</a>
|
||
</h3>
|
||
<p>
|
||
BMW has been preparing a centrally hosted CI/CD
|
||
instance based on Zuul V3 and many of the projects
|
||
using previous CI/CD solutions are already in the
|
||
progress of migrating to the new Zuul V3
|
||
instance. Hosting many projects on one central
|
||
platform has many advantages for operation overhead
|
||
and resource sharing in the cloud, but hosting many
|
||
projects on one CI/CD instance directly translates to
|
||
high stability and availability.
|
||
|
||
To maximize the availability of their central CI/CD
|
||
service, BMW is running
|
||
Zuul, <a href="https://zuul-ci.org/docs/nodepool.html">Nodepool</a>
|
||
and <a href="https://zookeeper.apache.org/">Zookeeper</a>
|
||
services in
|
||
an <a href="https://openshift.com/">OpenShift</a>
|
||
cluster, hosted on OpenStack. In addition to improved
|
||
availability, they have seen several development and
|
||
operation benefits for their internal CI/CD
|
||
development team.
|
||
</p><p>
|
||
<a href="http://superuser.openstack.org/articles/zuul-case-study-bmw/">
|
||
Read more about BMW at SuperUser.
|
||
</a>
|
||
</p>
|
||
|
||
<h3>
|
||
<a href="http://superuser.openstack.org/articles/zuul-case-study-godaddy">
|
||
GoDaddy
|
||
</a>
|
||
</h3>
|
||
<p>
|
||
Zuul is in a pilot phase for GoDaddy, primarily in use
|
||
for testing their OpenStack deployment automation and also for
|
||
managing changes to some of their Kubernetes deployment
|
||
automation. They also uses Zuul to test and deploy itself.
|
||
</p><p>
|
||
GoDaddy has replaced a lot of slow, brittle
|
||
Jenkins jobs with highly parallelized, more realistic Zuul test
|
||
jobs. They've also been able to accelerate development on some
|
||
new projects by setting up rapid proof-of-concepts in PRs to
|
||
GitHub. Some of these go nowhere, and some of them eventually become
|
||
the deployment automation that goes into production.
|
||
</p><p>
|
||
<a href="http://superuser.openstack.org/articles/zuul-case-study-godaddy">
|
||
Read more about GoDaddy at SuperUser.
|
||
</a>
|
||
</p>
|
||
|
||
<h3>
|
||
<a href="http://superuser.openstack.org/articles/openlab-zuul/">
|
||
OpenLab
|
||
</a>
|
||
</h3>
|
||
<p>
|
||
Zuul is currently being used as an offering within OpenLab for
|
||
projects, applications and tools that need CI gating and/or automation
|
||
around testing. With the companion tool Nodepool, they are able to keep
|
||
OpenStack virtual machines available, speeding up the process for
|
||
developers of testing code changes.
|
||
</p><p>
|
||
With the introduction of Zuul-based CI/CD instances, projects were
|
||
able to use the cloud resources for their automation in a very dynamic
|
||
way. As a result, projects can do much more excessive testing in less
|
||
time, which directly results in higher quality software, while being
|
||
faster in development and integration.
|
||
</p><p>
|
||
With the introduction of Zuul V3, OpenLab also sees a
|
||
lot of benefits from the operator's perspective by
|
||
providing a centrally hosted CI/CD instance, as
|
||
opposed to many small ones that require managing
|
||
individually.
|
||
</p><p>
|
||
<a href="http://superuser.openstack.org/articles/openlab-zuul/">
|
||
Read more about OpenLab at SuperUser.
|
||
</a>
|
||
</p>
|
||
|
||
<h3>
|
||
<a href="https://superuser.openstack.org/articles/zuul-case-study-software-factory/">
|
||
Software Factory
|
||
</a>
|
||
</h3>
|
||
<p>
|
||
Software Factory is a distribution that integrates all the
|
||
components as CentOS packages with an installer/operator named
|
||
sfconfig to manage service configuration, backup, recovery and
|
||
upgrades. The main Zuul advantages for their users are
|
||
customizable deployments and simplicity of use. The RDO project
|
||
has been using Software Factory successfully for about three
|
||
years now. The goal is to keep the same user experience from
|
||
upstream to downstream and to allow them to share
|
||
configurations, jobs, pipelines and easily run third party CI
|
||
jobs. With the addition of GitHub support to Zuul, Software
|
||
Factory can now be used without Gerrit and people are looking
|
||
into running their own gating CI/CD for GitHub organizations
|
||
with SF to use the log processing features.
|
||
</p><p>
|
||
<a href="https://superuser.openstack.org/articles/zuul-case-study-software-factory/">
|
||
Read more about Software Factory at SuperUser.
|
||
</a>
|
||
</p>
|
||
|
||
<h3>
|
||
<a href="http://superuser.openstack.org/articles/zuul-case-study-the-openstack-foundation/">
|
||
OpenStack Foundation
|
||
</a>
|
||
</h3>
|
||
<p>
|
||
OpenStack ended up in a situation where it wanted to keep gating
|
||
changes to OpenStack but have the ability to merge more than 24
|
||
changes a day. Running tests more quickly, or running fewer
|
||
tests were either not possible or less than ideal options.
|
||
Instead the infrastructure team set out to build a system (Zuul)
|
||
which could parallelize the serial testing of OpenStack.
|
||
Initially, Zuul was the coordinator for Jenkins and the two
|
||
systems worked together, and around April 2016, Jenkins was
|
||
replaced with an Ansible <https://www.ansible.com/>-based
|
||
execution system to improve performance and reliability. The
|
||
success of this Ansible-based system highly influenced the
|
||
decision to do the major Zuul v3 rewrite which also uses Ansible
|
||
to execute jobs.
|
||
</p><p>
|
||
<a href="http://superuser.openstack.org/articles/zuul-case-study-the-openstack-foundation/">
|
||
Read more about OpenStack Foundation at SuperUser.
|
||
</a>
|
||
</p>
|
||
|
||
<h3>
|
||
<a href="https://superuser.openstack.org/articles/zuul-case-study-packet-host/">
|
||
Packet Host
|
||
</a>
|
||
</h3>
|
||
<p>
|
||
Packet Host built a community cloud to support OpenStack with
|
||
100 concurrent VM instances each with 8 GB RAM, eight vCPUs and
|
||
80 GB storage running on 11 bare metal servers. Working with the
|
||
OpenStack Infra team has really opened my eyes up to the
|
||
capabilities of Zuul and the frameworks they’ve put together,
|
||
says John Studarus, who helped Packet Host put it together.
|
||
</p><p>
|
||
<a href="https://superuser.openstack.org/articles/zuul-case-study-packet-host/">
|
||
Read more about Packet Host at SuperUser.
|
||
</a>
|
||
</p>
|
||
|
||
</article>
|
||
</div>
|
||
</div>
|
||
</section>
|
||
|
||
<!-- Footer -->
|
||
<div id="footer">
|
||
<div class="container">
|
||
<div class="row">
|
||
<section class="3u 6u(narrower) 12u$(mobilep)">
|
||
<h3>Get Zuul</h3>
|
||
<ul class="links">
|
||
<li><a href="https://opendev.org/zuul/zuul/">Source</a></li>
|
||
<li><a href="https://pypi.org/project/zuul/">Install</a></li>
|
||
<li><a href="https://zuul-ci.org/docs/">Documentation</a></li>
|
||
<li><a href="https://zuul-ci.org/docs/faq.html">FAQ</a></li>
|
||
</ul>
|
||
</section>
|
||
<section class="3u 6u$(narrower) 12u$(mobilep)">
|
||
<h3>Get Involved</h3>
|
||
<ul class="links">
|
||
<li><a href="http://lists.zuul-ci.org/cgi-bin/mailman/listinfo">Mailing lists</a></li>
|
||
<li><a href="http://webchat.freenode.net/?channels=%23zuul">IRC</a> #zuul on Freenode</li>
|
||
<li><a href="https://storyboard.openstack.org/#!/project/679">Bugs</a></li>
|
||
<li><a href="https://review.opendev.org/#/q/status:open+project:zuul/zuul">Code Review</a></li>
|
||
</ul>
|
||
</section>
|
||
</div>
|
||
</div>
|
||
|
||
<!-- Copyright -->
|
||
<div class="copyright">
|
||
<ul class="menu">
|
||
<li>© Zuul Contributors. Licensed under Creative Commons Attribution 3.0</li><li>Zuul is collaboratively developed under the Apache 2 license and managed by the OpenStack Foundation.</li><li>Design based on Arcana from: <a href="http://html5up.net">HTML5 UP</a></li><li><a href="https://opendev.org/zuul/zuul-website/">Browse page source</a></li>
|
||
</ul>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
</div>
|
||
|
||
<!-- Scripts -->
|
||
<script src="assets/js/jquery.min.js"></script>
|
||
<script src="assets/js/jquery.dropotron.min.js"></script>
|
||
<script src="assets/js/skel.min.js"></script>
|
||
<script src="assets/js/util.js"></script>
|
||
<!--[if lte IE 8]><script src="assets/js/ie/respond.min.js"></script><![endif]-->
|
||
<script src="assets/js/main.js"></script>
|
||
|
||
</body>
|
||
</html>
|