It’s been almost a year since I last looked at CloudBolt Software, and unfortunately other projects took me away from taking a deeper look at them at that time. After taking a day off from blogging and having wrapped up my vRealize Automation and Application Services series I thought I’d have another look, especially now having hands on with vRealize Automation to compare it to.
CloudBolt, as you’d expect comes as an OVF to deploy in vCenter or VMware Workstation, there are no OVF properties that are exposed in vCenter so the deployment process would be the same in either scenario.
- Deploy the OVF, this is a simple process since you are not setting anything during the setup
- While the VM is deploying, create your DNS records in AD
- Log in as root/cloudbolt; the CloudBOlt C2 Server Setup UI will open
- Set each of the options according to your network, then chose the Run option to configure CloudBolt. Here is what mine looks like before selecting run
- If you deploy the VMware Workstation, ensure your VM nic is set according to your desired configuration – NAT or Bridged
- Now, navigate to the IP address / FQDN of the server
- You will need a CloudBolt license key to continue; click on the Browse button to select your license file then click Upload License
- You will now be at the login screen, log in as admin / admin
- Accept the EULA and click Next
- Select your “resource handler” – in my case VMware vCenter (you can select others later if needed)
- Provide the IP address of your vCenter server along with a username and password, typically I’d create an administrative user specific for CloudBolt such as svc_vc_cb_bind so it could be identified.
- CloudBolt will identify your environment; give a name to your vCenter server, select your default datastore and which cluster to import
- Select which networks you want to be available for provisioning. This would be somewhat similar to selecting the port groups in the vCAC reservation – in my case I’ll select my vm port group (you can select more than one here)
- Select which templates you want to import
- Create a Cloud Bolt admin user, this is a local user account not tied to AD or LDAP services (all fields are required)
- Finally fill in SMTP information or just click Finish then click Start Using CloudBolt
The initial CloudBolt setup is done after that easy wizard, a few additional steps you will need to perform before turning this over to users that we will look at in future posts:
- Create new users or configure LDAP for your users to log in (Admin >> Users or Admin >> LDAP Authentication Settings >> New LDAP Utility)
- Create new groups (Groups >> Add a Group)
- Add portal (Admin >> CloudBolt Portals)
- Add a provisioning engine or confiugration manager (currently supports Puppet, Chef, Docker, Cobbler and HP Automation)
- Create a Service Catalog for users to access