This article describes how to convert a RedHat Enterprise Linux server into a CloudBolt Appliance.
A RedHat Enterprise Linux 7 Server attached to your RedHat subscription and repos.
The server should be RHEL 7.6.
Other RHEL 7 versions may work.
The RHEL VM should meet these system requirements:
Hosted on vCenter 5.0+ or XenServer 6+
8+ GB memory
40+ GB storage (the initial VM will use ~2GB if thin provisioned, ~40GB if thick provisioned)
The server should be attached to your RedHat account and subscribed to the following repos or an equivalent subscription:
This should be a single-use VM. CloudBolt is not intended to run on a shared VM.
Download a copy of the CloudBolt 9.4+ Installer.
These instructions only work for CloudBolt 9.4+.
Find the latest installer at the CloudBolt Downloads Page.
Download a copy of the CloudBolt RHEL Setup Script
Copy the CloudBolt Installer and
install_cloudbolt_for_redhat.shscript to your RHEL server.
SSH into the CloudBolt server and escalate your privileges to be the
In this example, the soon-to-be CloudBolt server has the IP
[user@your-workstation]$ ssh firstname.lastname@example.org [email@example.com]$ sudo su - [firstname.lastname@example.org]#
3. Run the
install_cloudbolt_for_redhat.sh script with the path to the CloudBolt Installer
.tgzfile as the only argument.
Replace VERSION with the version of the downloaded file. For example, if you downloaded cloudbolt_installer_9.4.3_32b4145400.tgz. The VERSION component would be 9.4.3_32b4145400
[email@example.com]# sh install_cloudbolt_for_redhat.sh cloudbolt_installer_VERSION.tgz
This will unpack the installer and begin the installation process.
If the installation is successful you should see the following message at the end of the installer:
... ************** CloudBolt installer successfully finished! verbose log saved to: /var/log/cloudbolt/install/install_200601.1620.log ************** Please Reboot the VM and then visit https://10.11.12.13 to finish setting up your CloudBolt appliance.
If the installation fails, please file a ticket at firstname.lastname@example.org to resolve the issue.