Get Started with Bitnami Multi-Tier Blueprints on VMware vRealize Automation
VMware vRealize Automation is an automation platform that helps IT companies to accelerate the complete and effective delivery of IT services. This platform manages, in a single place, IT requests for infrastructure, applications, containers, etc., and processes them in a common catalog. This way, IT companies can deliver a consistent user experience for on-demand services they provide.
The latest version of this platform has adopted the converged blueprint model so developers can request the incorporation of custom blueprints to the service catalog or create new ones by simply cloning the existing templates. Administrators can enable and import as many blueprints as they like to the catalog. This helps companies simplify their release processes and automate their software deployments. Bitnami offers VMware users a set of blueprints ready to be deployed in any datacenter using VMware vRealize Automation.
In this tutorial you will learn how to configure a Bitnami Multi-Tier Blueprint for publishing in the catalog and how to create a Jenkins cluster on the VMware vRealize Automation platform using its blueprint template.
In this tutorial, you will learn, step by step, the process for editing a Bitnami Multi-Tier Blueprint template to add it to your catalog and show you, as an example, how to create a Jenkins cluster running the recently added blueprint.
Here are the steps you will follow in this tutorial:
- Configure the Bitnami Multi-Tier Blueprint template
- Deploy a Bitnami Jenkins cluster using VMware vRealize Automation
- Access the cluster
Now, let’s walk you through these steps in detail.
Step 1: Configure the Bitnami Multi-Tier Blueprint template
: At the end of this step, you will have edited and prepared a Multi-Tier blueprint template for publishing in the catalog.
NOTE: This step assumes that the administrators have already uploaded the Bitnami Multi-Tier Blueprint template to the VMware vRealize Automation platform.
Administrators are able to create and manage blueprints directly from the VMware vRealize Automation platform. When the admin user publishes a blueprint, it becomes available on the catalog so it can be reused easily. Administrators can create templates and upload them as blueprints, create new ones directly from the design canvas or clone an existing one.
Once the Jenkins Bitnami Blueprint has been uploaded, the administrator needs to make some changes both at master node and at slave node level to configure the template for publishing it to the catalog. To make this happen, navigate to the “Design -> Blueprints” section and select the recently uploaded Multi-Tier blueprint (in this example we will use the Bitnami Jenkins Blueprint for vRealize Automation template):
The next screen is the “Design Canvas” view. There you will find the Multi-Tier blueprint, (in this example, the Jenkins Bitnami Blueprint, which comprises a master and slave nodes) as you can see below:
To configure the blueprint for publishing in the catalog, you need to edit some server and application software values both in the master and slave nodes.
Edit the “Master_Server” values
To edit the “Master_Server” values, click on the “Master_Server” tag in the blueprint:
Then, edit the following information:
In the “Build Information” tab, edit the “Clone from” and the “Customization spec” fields:
In the “Machine Resources” tab, check that the values shown in the “Minimum” column match with the minimum requirements detailed in the “General -> Description” section. If everything is correct, click “Save” to apply the changes.
By default, Bitnami set the minimum requirements for the virtual machines in its templates. To check these requirements navigate to the “General -> Description” section as shown below:
Edit the application software values
NOTE: The configuration of the following parameter is optional. It is only required in case that the datacenter is not connected to internet or can’t access the VMware marketplace server. Refer to the Known issues section for more information on this.
To configure the software parameters, navigate to the “Design -> Blueprints” section and select the blueprint. You will see the “Design Canvas” view. Follow these instructions to set the application software parameters:
On the upper-left side of the screen you will see a configuration icon. Click on it to see the Blueprint Properties.
Navigate to the “Properties -> Custom Properties” tab. You will find the BITNAMI_BUNDLE_URL which indicates from where the Bitnami bundle should be downloaded from. The bundle contains scripts for the installation of essential services.
Click the “Edit” icon to replace this value with the URL that points to the repository in which the downloaded software has been stored. Click “OK” to save the changes.
Edit the “Slave_Server” values
To complete the configuration of the blueprint you need to repeat the same process described above for the master node but in the slaves. To edit the “Slave_Server” values, click on the “Slave_Server” tag in the blueprint:
Publish the blueprint in the catalog, after this you should see your blueprint published in the “Catalog” tab.
Step 2: Deploy a Bitnami Jenkins cluster using VMware vRealize Automation
: At the end of this step, you will have created a Jenkins cluster running on the VMware vRealize Automation platform using a blueprint template.
Once you have logged in to the VMware vRealize Automation platform, follow these steps to deploy a Bitnami Jenkins cluster using its blueprint template:
Navigate to the “Catalog” tab to select the Bitnami Drupal template for vRealize. Click “Request” to continue the process.
To complete the deployment request, you need to specify some information both at cluster and master/slave level:
- Jenkins Cluster deployment information
- “Master_Server” deployment parameters
- “Slave_Server” deployment parameters
Edit the Jenkins Cluster deployment information
- In the Jenkins Cluster deployment section, select the “General” tab and enter a description for the deployment, a reason for the request, the number of the deployments you want to request, and the password you want to set for the application.
NOTE: The default username to access the application is user.
Edit the “Master_Server” deployment parameters
In the left-side menu, select the “Master_Server” section and in the “General” tab, enter the value for the master node virtual machine “CPUs” and “Memory” (remeber that these values must match to the minimum requirements indicated in the “Description” field).
Edit the “Slave_Server” deployment parameters
In the left-side menu, select the “Slave_Server” section and in the “General” tab, add the number of slave nodes you want to deploy by changing the value shown in “Instances”.
Enter the value for the slave nodes virtual machines “CPUs” and “Memory” (remeber that these values must match to the minimum requirements indicated in the “Description” field).
Click “Save” for the changes to take effect.
Click “Submit” to send your request to the system administrator.
The system will confirm you that your request has been sent successfully:
To check the status of your request, navigate to the “Requests” tab and check the status of your last request:
Once the deployment has finished, you will see the following status:
Step 3: Access the cluster
: At the end of this step you will have obtained the IP address of the server to access the application via web browser.
Once the deployment has been completed successfully, the IP address you need to access the application should be available. To access the application:
Select the “Requests” tab.
Select your deployment from the resulting list and click on it.
In the “Deployment -> General” screen, click the “Execution Information” link:
In the resulting screen you will see the status of the cluster deployment. Clicking “[…]” button beside the master and each of the slave nodes, you can check the deployment logs.
To access Jenkins, click the “[…]” button beside the master node and scroll down until you find the application credentials and the server IP address (you can also find the server IP address by checking the slave nodes deployment logs):
NOTE: Remember that the application password is the one you have entered during the deployment. Check the step 2 for more details.
Enter the IP address in a browser. Enter your application credentials and click “log in” to start with Jenkins:
To learn more about the topics discussed in this tutorial, use the links below: