Browse Source

Add three more case studies

Include synopses for and links to new case studies covering Software
Factory, OpenStack Foundation and Packet Host.

Co-Authored By: Nicole Martinelli

Change-Id: I5501c4a86d50afac3a7f6767b2a9e84a2cddae26
Jeremy Stanley 6 months ago
parent
commit
a79cb815ec
1 changed files with 69 additions and 0 deletions
  1. 69
    0
      www/users.html

+ 69
- 0
www/users.html View File

@@ -143,6 +143,75 @@
143 143
 		    Read more about OpenLab at SuperUser.
144 144
 		  </a>
145 145
 		</p>
146
+
147
+		<h3>
148
+		  <a href="https://superuser.openstack.org/articles/zuul-case-study-software-factory/">
149
+		    Software Factory
150
+		  </a>
151
+		</h3>
152
+		<p>
153
+		Software Factory is a distribution that integrates all the
154
+		components as CentOS packages with an installer/operator named
155
+		sfconfig to manage service configuration, backup, recovery and
156
+		upgrades. The main Zuul advantages for their users are
157
+		customizable deployments and simplicity of use. The RDO project
158
+		has been using Software Factory successfully for about three
159
+		years now. The goal is to keep the same user experience from
160
+		upstream to downstream and to allow them to share
161
+		configurations, jobs, pipelines and easily run third party CI
162
+		jobs. With the addition of GitHub support to Zuul, Software
163
+		Factory can now be used without Gerrit and people are looking
164
+		into running their own gating CI/CD for GitHub organizations
165
+		with SF to use the log processing features.
166
+		</p><p>
167
+		  <a href="https://superuser.openstack.org/articles/zuul-case-study-software-factory/">
168
+		    Read more about Software Factory at SuperUser.
169
+		  </a>
170
+		</p>
171
+
172
+		<h3>
173
+		  <a href="http://superuser.openstack.org/articles/zuul-case-study-the-openstack-foundation/">
174
+		    OpenStack Foundation
175
+		  </a>
176
+		</h3>
177
+		<p>
178
+		OpenStack ended up in a situation where it wanted to keep gating
179
+		changes to OpenStack but have the ability to merge more than 24
180
+		changes a day. Running tests more quickly, or running fewer
181
+		tests were either not possible or less than ideal options.
182
+		Instead the infrastructure team set out to build a system (Zuul)
183
+		which could parallelize the serial testing of OpenStack.
184
+		Initially, Zuul was the coordinator for Jenkins and the two
185
+		systems worked together, and around April 2016, Jenkins was
186
+		replaced with an Ansible <https://www.ansible.com/>-based
187
+		execution system to improve performance and reliability. The
188
+		success of this Ansible-based system highly influenced the
189
+		decision to do the major Zuul v3 rewrite which also uses Ansible
190
+		to execute jobs.
191
+		</p><p>
192
+		  <a href="http://superuser.openstack.org/articles/zuul-case-study-the-openstack-foundation/">
193
+		    Read more about OpenStack Foundation at SuperUser.
194
+		  </a>
195
+		</p>
196
+
197
+		<h3>
198
+		  <a href="https://superuser.openstack.org/articles/zuul-case-study-packet-host/">
199
+		    Packet Host
200
+		  </a>
201
+		</h3>
202
+		<p>
203
+		Packet Host built a community cloud to support OpenStack with
204
+		100 concurrent VM instances each with 8 GB RAM, eight vCPUs and
205
+		80 GB storage running on 11 bare metal servers. Working with the
206
+		OpenStack Infra team has really opened my eyes up to the
207
+		capabilities of Zuul and the frameworks they’ve put together,
208
+		says John Studarus, who helped Packet Host put it together.
209
+		</p><p>
210
+		  <a href="https://superuser.openstack.org/articles/zuul-case-study-packet-host/">
211
+		    Read more about Packet Host at SuperUser.
212
+		  </a>
213
+		</p>
214
+
146 215
 	      </article>
147 216
 	    </div>
148 217
 	  </div>

Loading…
Cancel
Save