Exporting and Importing Bright Objects – See What’s Coming!

page_header_divider_line

By Martijn de Vries | March 24, 2020 | Bright Cluster Manager, Bright 9.0

   

 

Exporting and importing Bright objects is a topic that comes up very often, and we have an exciting enhancement on the horizon that I wanted to tell you about.

This new import capability will be available for Bright Cluster Manager 9.0, and we will be adding the export capability to Bright Cluster Manager 8.2, 8.1, and 8.0.

If you have a Bright cluster, this new capability will allow you to export most objects that exist in the Bright management infrastructure to JSON format. When you export an object - or multiple objects - to JSON, you will get a directory of files where each file represents one object in Bright. You will have the opportunity to tweak those files before importing the objects into a new Bright cluster.

How might this be useful?

For example, you might have defined a group of node objects in your current cluster that you want to migrate to a new Bright cluster. With this new functionality, it’s no longer necessary to write scripts to recreate those node objects in your new cluster; you can simply export them from the old cluster and import them into the new cluster.

Or, you may wish to carry out a parallel upgrade of Bright. Instead of doing an in-place upgrade which always has some risks associated with it, you can now carry out a parallel upgrade where you take a new head node and a new installation of Bright and import all of the objects from your old cluster, rather than building the configuration from scratch.

Or, you may have many different Bright clusters, and you want to take an object from one particular Bright cluster and push it to lots of others. For example, to replicate a particular disk setup, or to keep cluster objects under version control. In this case, you could define the object and update it in a central place and then push it out to a group of clusters, selectively.

This is much quicker and far more efficient, and the word “selective” is so important here. The previous method to carry out an import or export would be to export the entire configuration of a Bright cluster and import it onto another cluster, blasting away anything that was previously there.

Now, you can import and export in a much more refined and selective manner. And, because we use JSON, there are a host of tools to manipulate or modify the definitions, before import.

If you would like to find out more about this functionality, please get in touch.

resource_asset_divider_image

COMMENTS