![]() ![]() That means that we will use the same type of build job throughout the entire course of this blog, but we will vary the different configurations and tuning to find the best fit for our specific build. In order to get a measurement of the performance of Jenkins we need to establish a baseline. Below is a view from the AWS console showing the EC2 instances and how they are placed in the us-east-2 AZs. This means the OCS storage cluster is stretched across these 3 AZs. The AWS region us-west-2 has availability zones (AZs) us-west-2a, us-west-2b, and us-west-2c, and the 6 worker nodes are spread across the 3 AZs, 2 nodes in each AZ. As shown in the following, the OpenShift Container Storage worker nodes are of instance type m5.2xlarge with 8 vCPUs, 32 GB Mem, and 3x100GB gp2 volumes attached to each node for OCP and one 1TB gp2 volume for the OCS storage cluster. The 6 worker nodes are basically the storage provider and persistent storage consumers (Jenkins). ![]() OpenShift on AWS Test EnvironmentĪll posts in this series use a Red Hat OpenShift Container Platform on AWS setup that includes 8 EC2 instances deployed as 1 master node, 1 infra node, and 6 worker nodes that also run Red Hat OpenShift Container Storage Gluster and Heketi pods. This second post will deal with different approaches for improving the performance of Jenkins on OpenShift. The first post illustrated the deployment of a Jenkins master instance and a typical workload. This blog series will take a close look at Jenkins running on Red Hat OpenShift 3.11 and the various possibilities we have to improve its performance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |