Innovation at Your fingertips: new features of WebSphere Cloudburst V2.0

Each innovative line of the article will introduce you to information and discussion on emerging technologies from the perspective of developers and other practitioners, as well as behind-the-scenes insights into cutting-edge ibm®websphere® products.

New firmware, new features

IBM WebSphere Cloudburst Appliance firmware V2.0 does not lack new features. To inspire your interest in this new version, this article will give you a general overview of some of the most important new features. These new features will be covered in more detail in subsequent articles.

So, let's start now!

Dynamic Virtual machine Operations

Prior to version 2.0, the composition of the virtual system in the WebSphere Cloudburst was defined by its schema. In this version, this concept has not changed, but now you can tailor or delete a single virtual machine based on changing workload requirements.

Cloning

Clone a virtual opportunity to create a new virtual machine and add the virtual machine to the virtual system. There are many things that happen when you create a clone:

WebSphere Cloudburst creates a new virtual machine and assigns a new IP address.

The tool executes any script package that is marked "on virtual system creation" from the source virtual machine on the new virtual machine.

An emergency patch from the source virtual machine is installed to the new virtual machine.

If this is a custom node, WebSphere Cloudburst will join and start the node.

In this case, using the term "clone" is not very accurate. Cloning means exact replication (one copy), which is not the case in this example. To further illustrate this point, imagine that if manual changes were made to the virtual system after deployment, the changes would not be reflected in the clone because they were not encapsulated in your schema.

To create a clone of an existing virtual machine, find virtual Systems > Your_virtualsystem. Expand virtual Machines, and then click the View link next to the VM you want to clone. Figure 1 shows the clone icon, which is circled with a red line.

Figure 1. Virtual machine cloning operation.

Delete

Removing a virtual machine removes the virtual machine from the virtual system. Any script that is marked to be executed when "on virtual system deletion" is run, and the WebSphere Cloudburst removes the node from the cell. One warning about deleting a node is that the automatic deletion process must run the node sequentially. If the node is turned off when the virtual machine is deleted, the deletion of the node cannot take place, and you need to manually delete the node using the Cleannode command.

To remove an existing virtual machine, find virtual Systems > Your_virtualsystem. Expand virtual Machines, and then click the View link next to the VM you want to delete. Figure 2 shows the part of the delete icon that is circled with the red line.

Figure 2. Virtual Machine Delete operation