CloudBees Jenkins运营中心的水平扩展

This article was sponsored by CloudBees. Thank you for supporting the sponsors who make SitePoint possible!

本文由 CloudBees 赞助 。 感谢您支持使SitePoint成为可能的赞助商！

Picture this: You start using Jenkins, probably with one machine. As both the number of projects and the size of the projects themselves start to grow, you start to add slaves. Slowly, your cluster of Jenkins servers grows, and you slowly start to lose your grip. What if your Jenkins master crashes? If you recognize this feeling or you want to avoid this, you definitely should read on.

想象一下：您可能在一台机器上开始使用Jenkins。 随着项目数量和项目本身大小的增长，您开始添加从站。 慢慢地，您的Jenkins服务器集群增长了，并且您开始逐渐失去控制力。 如果您的詹金斯大师崩溃了怎么办？ 如果您认识到这种感觉或想要避免这种感觉，则绝对应该继续阅读。

In this article we’ll take a small peak at CloudBees Jenkins Operation Center. CloudBees Jenkins Operation Center, created by CloudBees, offers you a lot of additional functionality to take your Jenkins cluster to the next level. The key features for CloudBees Jenkins Operation Center are:

在本文中，我们将在CloudBees Jenkins运营中心占据一个小高峰。 由CloudBees创建的CloudBees Jenkins操作中心为您提供了许多附加功能，可将您的Jenkins集群提升到一个新的水平。 CloudBees Jenkins操作中心的主要功能是：

• Consolidated navigation experience across all the client masters.
  跨所有客户端主站的合并导航体验。
• Shared build slave resources that can be used by any client masters.
  可以由任何客户端主服务器使用的共享构建从属资源。
• Control of authentication and authorization schemes used by client masters. This enables features such as: single sign-on and consolidated permission schemes.
  控制客户端主机使用的身份验证和授权方案。 这样可以启用以下功能：单点登录和合并权限方案。
• Management of update centers used by client masters.
  客户主使用的更新中心的管理。
• Consolidated management of Jenkins Enterprise licenses.
  统一管理Jenkins Enterprise许可证。
• Management and enforcement of certain key security settings on client masters.
  在客户端主服务器上管理和实施某些密钥安全设置。

Within this article we’ll just use a small amount of the available features. We’ll be creating a client master and a shared slave. For this we will be using three separate servers. The first one will run CloudBees Jenkins Operation Center, the second one will run Jenkins Enterprise and the third will be used as a shared slave. We will be explaining everything in the next couple of chapters.

在本文中，我们将仅使用少量可用功能。 我们将创建一个客户端主服务器和一个共享从服务​​器。 为此，我们将使用三个单独的服务器。 第一个将运行CloudBees Jenkins Operations Center，第二个将运行Jenkins Enterprise，第三个将用作共享从属。 在接下来的几章中，我们将解释所有内容。

制备 (Preparation)

I’ll be using three virtual machines on my local computer. If you want to follow along, you might want to make sure your own computer is powerful enough. If you happen to have three spare servers somewhere, you can also try it directly on those servers.

我将在本地计算机上使用三个虚拟机。 如果要继续学习，可能需要确保自己的计算机功能强大。 如果您恰好在某处有三个备用服务器，则也可以直接在这些服务器上尝试。

The three servers will be managed through Vagrant. I created a multi-machine Vagrant file which will boot all three servers. If you’re not familiar with Vagrant yet, you might want to read this article.

这三台服务器将通过Vagrant进行管理。 我创建了一个多计算机 Vagrant文​​件，它将引导所有三个服务器。 如果您还不熟悉Vagrant，则可能需要阅读这篇文章 。

Let’s start off with our Vagrant file. You can find the content here

让我们从我们的Vagrant文​​件开始。 您可以在这里找到内容

Note: All three boxes are running CentOS 7. You can easily replace them with Ubuntu boxes if you prefer, but do note that all commands below are meant for CentOS.

注意：所有这三个盒子都在运行CentOS7。如果愿意，您可以轻松地用Ubuntu盒子替换它们，但请注意，以下所有命令均适用于CentOS。

Three servers will be created when you run vagrant up. They each have a different IP:

当您运行vagrant up时，将创建三个服务器。 它们各自具有不同的IP：

• 192.168.56.105: CloudBees Jenkins Operation Center
  192.168.56.105：CloudBees Jenkins运营中心
• 192.168.56.106: Jenkins Enterprise – Client Master (master)
  192.168.56.106：Jenkins Enterprise –客户端管理员(管理员)
• 192.168.56.107: S