The versions of CloudBolt below are currently supported. Click the Version title to expand the full release notes for that version.
As always, when upgrading CloudBolt, please review all Notes between the version of CloudBolt that you are currently using and the version you're upgrading to.
![]() | Upgrade Notes |
|
Improvements to Guided Setup:
Activate RDP/SSH Key authentication for a given server. When enabled, a private key is used in place of a username and password.
As always, when upgrading CloudBolt, please review all Notes between the version of CloudBolt that you are currently using and the version you're upgrading to.
As always, when upgrading CloudBolt, please review all Notes between the version of CloudBolt that you are currently using and the version you're upgrading to.
![]() |
We have upgraded some of the dashboard widgets in 9.4. Customized widgets will display below the upgraded widgets. For customized widgets to appear at the top of the dashboard, please contact support.
In addition, CloudBolt’s out-of-the-box widgets no longer use the following URL endpoints:
|
![]() |
If you've modified your out-of-the-box ServiceNOW CMDB plug-in, please reach out to support to update it.
|
With this release, you can now opt-in to using SELinux on your CloudBolt appliances. For set up instructions, see our SELinux documentation.
Enhancements
Bug Fixes
Security Improvements
As always, when upgrading CloudBolt, please review all Notes between the version of CloudBolt that you are currently running and the target version you're upgrading to.
![]() |
Secrets Stored in Remote Source Blueprints
If you have Remote Source Blueprints configured that contain Resource Actions with secrets, you will need to reconfigure them. Follow the Secrets Stored in Remote Source Blueprints docs to set up a password. This password encrypts and decrypts secrets when exporting and importing Blueprints. Without following these steps, any Resource Action secrets in your Remote Source Blueprint will become blank on its next refresh post. |
![]() |
Django 2.2 CloudBolt is upgrading Django to version 2.2 in CloudBolt version 9.3. This is a major update from Django 1.11.If you have written Plugins or UI Extensions for CloudBolt, you may need to update them to ensure they continue to work in versions 9.3+. Check Django’s list of backwards incompatible changes for more details. |
The Resource Group and Storage Account parameters are now being treated as tech-specific parameters in the Azure Parameters tab within the Azure Environment. It is now easier to make bulk changes to these parameters.
CloudBolt integrates with SSO natively. Identity Providers (IdP) authenticate users from a single source of truth. This allows enterprise organizations to control which users have access to which applications, all from one place. Users who want to access a CloudBolt linked to an SSO Identity Provider can choose to log in from CloudBolt’s UI or from their IdP.
Users can now import all images from an Azure Shared Image gallery that the selected Subscription has access to.
The CloudBolt UI has a new look and feel, including updates to the top level navigation, detailed descriptions for each header item, and quick actions for top level navigation items.
CloudBolt offers Veeam integration as a UI Extension. Veeam is a backup application for virtual environments. This integration allows for server backups and restoration to AWS and Azure. Download this XUI in the Content Library.
CloudBolt has added a Blueprint to support Cisco UCS Central. Use the Blueprint to provision Server Profiles from within CloudBolt’s UI.
SolarWinds IP Address Manager (IPAM) is a product offered by SolarWinds that allows enterprises to manage and control their DNS, DHCP, and IP Address operations within their private data centers and public clouds. CloudBolt now integrates with SolarWinds IPAM and offers the ability to configure a connection to your local SolarWinds IPAM and associate it with Networks with no scripting.
logrotate
for log rotation. Configuration can be modified to suit your needs at /etc/logrotate.d/cloudbolt
on your CloudBolt server. DEV-14899
/tmp/systemd-provite*
directory. DEV-12629
![]() |
Remote Source Blueprint Configuration: If you have Remote Source Blueprints configured that contain secrets, you will need to reconfigure them. Follow the Secrets Stored in Remote Source Blueprints documentation to set up a password that encrypts and decrypts secrets when exporting and importing Blueprints. Without following these steps, any secrets in your Remote Source Blueprint will become blank on its next refresh post-9.2. |
![]() |
CloudBolt is upgrading Django to version 2.2 in CloudBolt version 9.3. If you have written Plugins or UI Extensions for CloudBolt, you may need to update them to ensure they continue to work in versions 9.3+. Check Django’s list of backwards incompatible changes for more details. |
CloudBolt now supports deploying Kubernetes to multiple nodes. The Content Library contains a Kubernetes Cluster Blueprint available to import. This allows a Blueprint Admin to deploy a multi-node Kubernetes cluster. The Kubernetes Cluster Blueprint can be deployed to any Resource Handler. The Kubernetes Cluster Blueprint can also be used as a Sub-Blueprint to deploy Containerized Objects to dedicated Kubernetes clusters.
There are two main use cases for the Kubernetes Cluster Blueprint:
- Use it on its own to deploy a Kubernetes cluster. This is useful for IT Admins who want to provide multiple standalone clusters into which different apps can be deployed.
- Use it as a sub-Blueprint along with apps to be deployed into the new cluster.
See Container Orchestrators for set up and deployment. DEV-12361
The Create Blueprint Parameters (blueprint.create_parameters) permission allows non-Admin CloudBolt users to only create parameters for Blueprints they can access. See Blueprint-level Parameters for set up and use. DEV-13848
Added the ability to browse the Catalog by Blueprint Category in addition to the existing viewing options. Admin users can set the default viewing mode from Miscellaneous Settings. See Catalog Viewing Mode for more information. DEV-13612
A new third-party plugin allows Terraform users to make requests of CloudBolt and perform tasks such as server provisioning from Terraform. A new, open-source code base is accessible from the GitHub repository. Instructions to download and run the plugin can be found in the repository. DEV-12938
Previously, global parameter default values would only apply to servers. You can now configure global parameter default values to be set on Resources, by selecting from the new ‘Global Target’ field when creating or editing a global parameter default value. See Order Form Customization for more information. DEV-11808
The first time a user logs in to their account, they will be asked to choose a password reset challenge question from a dropdown list and provide an answer for that question. The answer to this question will be used when a password reset is initiated, and is not case sensitive. See Security.
The CloudBolt API has begun the transition to a new way to access objects called Global IDs. Global IDs will be consistent across different, similarly-configured CloudBolt instances. This makes it easier to reuse the same API calls, rather than modifying them to match the object IDs in each instance. The first objects to transition to this new Global ID are those referenced by a URL when ordering a Blueprint through the API: Blueprints, Environments, Groups, OS Builds, and Applications. The intent of this feature is to gradually replace the object IDs that are currently used. The old IDs will continue to be supported for all objects.
A new third-party plugin allows Terraform users to make requests of CloudBolt and perform tasks such as server provisioning from Terraform. A new, open-source code base is accessible from the GitHub repository. Instructions to download and run the plugin can be found in the repository.
We’ve added the ability to add Preconfigurations on Blueprint-level parameters. Like other parameters on Blueprints, Preconfigurations can be given a destination to be set on the deployed Resource, the build items, or both.
When set on the build items, Blueprint-level parameters will take precedence over any overlap set on the Environment of the Server Tier build items. If you define the same Preconfiguration on the Environment for a server, the Blueprint-level Preconfiguration and its options will override the Environment Preconfiguration. The same precedence will apply if you set Custom Fields on an Environment in a Server Tier that are defined in a Blueprint-level Preconfiguration.
CloudBolt 8.8 and earlier run on CentOS 6.6, but CloudBolt 9.0 runs on CentOS 7.6. This gives CloudBolt users access to all of the software supported by CentOS 7 that is not available on CentOS 6. Unfortunately, it is not possible to upgrade from CentOS 6 to CentOS 7 in place. We have prepared command line tools to make migrating your CloudBolt instance from CentOS 6 to CentOS 7 as painless as possible, but it is not completely automated. Please see Upgrading to 9.0 for details on how to upgrade.
We’ve made a number of improvements to the Terraform Integration that was introduced in 8.8
.tfstate
files for two-stage plan
then apply
Terraform run. DEV-12553
Centralized ServiceNow Management Page
CloudBolt now supports integration with one SIEM provider, Splunk, allowing users to configure their data forwarder from a new Admin page.
We’ve restored the ability to browse the Blueprints Catalog in table mode. You will now be able to switch between viewing your blueprints as a table or in tiles. This mode can be toggled with the button at the top right of the Catalog page.
We’ve also added the ability to skip to the first or last page in either viewing mode, and the ability to sort results by resource type.
In addition, there is a new Miscellaneous Setting under the Admin page where you can select a Catalog Viewing Mode as the default for all users.
We’ve extended CloudBolt’s ability to import and view billing data to GCP. Now, you can set up GCP Projects in CloudBolt to import billing information, and then view graphs summarizing the data on the GCP projects’ and resource handlers’ Billing tabs.
Detailed instructions to set up importing GCP billing data into CloudBolt can be found under the Google Cloud Platform section of the docs.
We’ve added the ability for CloudBolt users to access the consoles of servers under Nutanix Acropolis Resource Handlers CONTNT-234
Note that the Nutanix Hypervisor must be running the v3 API in order for the console to work.
The new Multi-Channel Alerts feature allows CB Admins to decide how to send notifications about different kinds of alerts from the product. They can now be sent to Slack and Email. Out-of-the-box alerts include security and administration events, and you can also send alerts from custom code such as an action or Recurring Job. See Multi-Channel Alerts.
Prior to 9.0, a unified view to import from the content library did not exist. Users had to know what kind of collection to look for, and go to each list view within the product for the type of collection they wanted to import (e.g. Blueprints, Orchestration Actions, etc).
Super Users can access importable content hosted by CloudBolt directly from the main menu. Browse, learn about and ultimately download Blueprints, Resource Actions, Server Actions, Orchestration Actions, Recurring Jobs, UI Extensions and Rules from a single page.
CloudBolt now integrates with Infoblox in a more robust, customizable way. We’ve given CloudBolt admins detailed control over which Networks use which IPAMs and how those IPAMs are used during the provisioning process. We have also added support for phpIPAM.
When you establish a new connection to an IPAM, you’ll see two new tabs: Networks, and Orchestration. Import the networks (expressed in CIDR notation) directly from your IPAM instance under the Networks tab.
In order to use the features in the Orchestration tab, you’ll need to import at least one. Once you’ve imported your IPAM Networks, you can view them in the data-table and click the pencil icon to assign them to one or more CloudBolt Network. In the Orchestration tab, enable or disable orchestration entirely. This is where you’ll find base-line Python code that allocates and deallocates IP addresses from your IPAMs during Server provisioning and decommissioning. CloudBolt administrators can modify this code to suit their needs, or revert to the basic version CloudBolt provides.
With this configuration complete, CloudBolt will execute Orchestration code to provide IP addresses to user-provisioned Servers that are associated with an IPAM whose Orchestration tab is enabled.
CloudBolt 9.0 includes important changes to the way we support Kubernetes. CloudBolt Admins can now associate a given Kubernetes Container Orchestrator with a CloudBolt Environment, and even have the option of making multiple Environments that support multiple Kubernetes clusters. This allows CloudBolt Admins to leverage CloudBolt’s existing role-based permissions: users that can deploy to a given Environment can deploy containerized objects to Container Orchestrators (Kubernetes Clusters) in that environment. Users without the permission cannot.
To set the association, Admins can: * Edit the Environment, selecting all relevant Container Orchestrators. * Edit the Container Orchestrator, selecting all relevant Environments.
CloudBolt displays associations in the List Views for Environments and for Container Orchestrators. Admins will need to edit Blueprints that deploy Containerized Objects to set their Environments.
More information about your Kubernetes clusters now shows: * Pod Details: Which Pods are running, their Images, Nodes and Statuses. * Node Details: Nodes that are members of the cluster, their statuses, and how heavily they are loaded.
False
and Integer 0
were not being passed to Actions. DEV-12868
git
repositories. DEV-12798
8.8 UPGRADE NOTES
When upgrading CloudBolt, please review all Upgrade Notes between the version of CloudBolt that you are presently running and the target version that you are upgrading to.
The next phase of this feature includes the following changes for improved user experience and support for more Blueprint features:
We’ve added a new action type that allows one to apply Terraform Plans in CloudBolt Blueprints. This action enables you to deploy CloudBolt resources containing Terraform-provided resources.
When a Blueprint containing Terraform Plan Actions is ordered, CloudBolt will discover servers provisioned by Terraform and add them to the resulting CloudBolt resource. These servers are later discovered by their associated Resource Handler and can be managed managed through the CloudBolt UI.
Read more about the Terraform integration under the Terraform Plan Action docs.
Job Engine worker processes are now started and managed via Supervisord, instead of by cron. You can check the status of worker processes on the status page at
, or on the command line with supervisorctl status.The following improvements have been made to order form validation:
Templates from any configured VMware content libraries are now available to be used within CloudBolt. VM Templates from local and subscribed content libraries can be imported into your VMware vCenter Resource Handlers and subsequently configured for any Environments. CloudBolt environments must have at least one Resource Pool configured to deploy Content Library Templates.
Cloudbolt’s IPAM page serves as something of a preview of what’s to come. You’ll find a new tab to allow you to import the networks you have configured in Infoblox. You’ll find a new, but disabled, Recurring Job which will, when you edit it, allow you to assign one or more IPAM networks to any or all of your CloudBolt networks and you’ll find a new Orchestration Action under the Pre-Create Resource hookpoint called, “IPAM Associations 01 - Allocate IP From Associated IPAM.” If you enable that Orchestration Action and associate an IPAM network with a CloudBolt network, it will allocate an IP address from your IPAM and use it as a static IP for that NIC.
See CloudBolt Plug-ins for more info.
Server and Resource Actions now give CloudBolt Admins the option to require approval before being run. When require_approval is set, the action will be added to an existing or new order.
Changes to the way CloudBolt models orders and groups allow users to write complex order approval Orchestration Actions that override the standard approval workflow.
collect_xui_apps
management command to index all UI Extensions on the users’ filesystem and add them to the database. DEV-12157
8.7 UPGRADE NOTES
When upgrading CloudBolt, please review all Upgrade Notes between the version of CloudBolt that you are presently running and the target version that you are upgrading to.
We’ve restructured our AWS restricted Resource Handlers to support multiple regions with the same account and handler. If you need help consolidating your environments into one Resource Handler, please consult CloudBolt Support.
CloudBolt can now resize VMs in Azure. Click, “Resize VM,” under Server Actions on the Server Details page. Note that the available sizes will be constrained by what Azure supports for that machine and by what sizes your CloudBolt admins have configured for the Environment.
CloudBolt will now limit the choices available for VM node size based on the choice made for disk type. If a user or blueprint designer selects Premium_LRS disks, only those VM node sizes that support those disks will be available.
CloudBolt now recommends reserved instances to save money by switching from On Demand costs to the discounted Reserved Instance rates on your ec2 instances. You can view these recommendations from an AWS Resource Handler’s Billing tab.
When synchronizing virtual machines to Servers from VMware VSphere to CloudBolt, we will now take note of IPv6 addresses in addition to IPv4 addresses. We have also added a new option under Miscellaneous Settings to tell CloudBolt which address to use for actions such as running remote scripts. Options are:
Virtual machines that are members of Azure Scale Sets will now be synchronized to CloudBolt
We’ve added the ability to set automated spelling corrections for tag values. CloudBolt Admins can specify mappings between misspelled values and the correct spelling. Then, whenever CloudBolt updates any tagged servers for that resource handler, then the spelling will be corrected based on what the admin has set to change. For example, an admin can specify that the misspelled value ‘poduction’ should be corrected to ‘production’. Then, if CloudBolt discovers a VM with that tag value, it will correct the value to ‘production’. This is supported on AWS, Azure, and VMWare resource handlers.
We’ve also added the ability for admins to enable bidirectional syncing on group and owner tags. The behavior will remain the same out of the box, but admins can enable bidirectional sync from the resource handler’s Tags tab. This will allow for tag values imported into CloudBolt to override the group and/or owner of the server.
CloudBolt now ships with improved Google Cloud support. The primary difference starting with this release is the support for multiple GCP Projects within one resource handler. Additional documentation on setting up the new and improved GCP handler can be found here.
CloudBolt can now take snapshot of an OpenStack instance and can revert back to a snapshot created by CB. To take a snapshot of an OpenStack server, click on ‘Create Snapshot’ server action available on the server details page. To revert the server back to a snapshot, click on ‘Revert To Snapshot’ server action on the server details page.
CloudBolt now offers the ability to have Blueprints populated from a definition stored in a remote source location, such as github, gitlab, or a filesystem. This is a beta feature that supports many of the core pieces of functionality, with some limitations. Please see the Catalog docs for more details. Feedback? Email the team: beta@cloudbolt.io.
Deleting
state are now marked Historical
. 165104806