Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


 Image Added

 

 

Create Cluster

This activity creates a new cluster.

...

The Create Cluster activity parameters can be provided by manual inserted values or via IN arguments or variables:


Parameters:

  • Cluster Name (text box editor type) (type: string):

...

  • the name of the

...

  • Cluster.
  • Connection (text box editor type) (type: string): VMware host connection. The output from Connect to Host activity should be used as Input here.
  • Datacenter Name (text box editor type) (type: string):

...

  • the name of the Datacenter.

...

  • DRSAutomationLevel (combobox control editor type) (type: string): the DRS automation level for the

...

  • new created cluster. Flowster Studio provides the following options:
    • Manual: The DRS cluster will make recommendations to an administrator, but no automated actions will be taken.The administrator must manually carry out any recommendations.This is a good setting if you just want to see what impact DRS might have on your environment.
    • FullyAutomated:  Clusters configured for partial automation will automatically place new virtual machines on existing hosts based on performance and resource criteria.  However, after the initial placement event, which may result in recommendations to move other workloads to accommodate the new virtual machine, DRS operates the same way that it does when Manual DRS is use.
    • PartiallyAutomated:  When this option is selected, DRS will provide initial placement services as described earlier, but it will also move workloads around the cluster without administrator intervention if there is a chance to better balance workloads running inside the cluster.
  • DRSEnabled (combobox control editor type) (type: string):

...

  • enable the DRS property of the cluster. Flowster Studio provides the following options:
    • True: creates cluster with DRS property enabled.
    • False: creates cluster with DRS property disabled.
  • EnableHA (combobox control editor type) (type: string):

...

  • enable the HA property of the cluster. Flowster Studio provides the following options:
    • True: creates cluster with HA property enabled.
    • False: creates cluster with HA property disabled.


The Read Only Output variable are the possible output values that the activity will provide:

  • Output  (type: string):

...

  •  outputs the resulting Cluster ID.

...

  


Execution: The example below is an execution where a new cluster will be created:

Image Added

Delete Cluster

...

The Delete Cluster activity parameters can be provided by manual inserted values or via IN arguments or variables:

Image RemovedImage Added

Parameters:

  • Cluster ID ID (text box editor type) (type: string): the ID of the new Cluster. If this parameter is specified, the Datacenter Name and Cluster Name parameters are not needed.
  • Cluster Name (text box editor type) (type: string): the name of the Cluster.
  • Connection 'DatacenterName' and 'ClusterName' are ignored. E.g "domain-c99".
    The value can also be obtained from activities: Create Cluster or Get Cluster using the following steps:
    • use a Get Cluster/ Create Cluster activity to extract the ClusterID 
       Image AddedImage Added
    • bind the obtained ClusterID (stored in variable) to the Cluster ID field from Delete Cluster activity:   

                     Image Added

  • Cluster Name (text box editor type) (type: string): VMware host connection. The output from Connect to Host activity should be used as Input herethe name of the Cluster. E.g "DemoCluster".
  • Datacenter Name (text box editor type) (type: string): the name the name of the Datacenter. E.g. "Datacenter".

The Read Only Output variable are the possible output values that the activity will provide:

  • Output  (type: booleanstring): outputs the  outputs the result of the deleting operation.
 As mentioned above, the values for all the required parameters can be provided by IN arguments or variables. Below is an example of predefined arguments, ready to be used by the Delete Cluster activity:

Image Removed

 


Execution: The example below is an execution where a cluster will be deleted:

Image Added

Edit Cluster Properties

This activity edits cluster properties such as HA (enabled/disabled), DRS (enabled/disabled) and DRS Automation Level.

...

The Edit Cluster Properties activity parameters can be provided by manual inserted values or via IN arguments or variables:

Image RemovedImage Added

Parameters:

  • Cluster ID (text box editor type) (type: string):

...

  • the ID of the cluster whose properties are being

...

  • edited. E.g "domain-c99".

    The value can also be obtained from activities: Create Cluster or Get Cluster using the following steps:

    • use a Get Cluster/ Create Cluster activity to extract the ClusterID:   
      Image AddedImage Added
    • bind the obtained ClusterID (stored in variable) to the Cluster ID field from Delete Cluster activity:   

              Image Added

  • DRSAutomationLevel (combobox control editor type) (type: string):

...

  • only choose a value if you want to change this property. If left empty, this property will not be changed.
  • DRSEnabled (combobox control editor type) (type: string):

...

  • only choose a value if you want to change this property. If left empty, this property will not be changed.
  • EnableHA (combobox control editor type) (type: string):

...

  • only choose a value if you want to change this property. If left empty, this property will not be changed.

The Read Only Output variable are the possible output values that the activity will provide:

  • Output  (type: string):

...

  •  outputs the result of the execution status.
 

 

 

 

 




Get All Clusters

This activity all the clusters.

...

The Get All Clusters activity parameters can be provided by manual inserted values or via IN arguments or variables:

Image RemovedImage Added

Parameters:

  • Connection (text box editor type) (type: string): VMware host connection. The output from Connect to Host activity should be used as Input here.
  • Datacenter Name (text box editor type) (type: string): the name of the datacenter where the cluster will be searched for.

...

  • Output  (type: list<string>): outputs the resulting Clusters.
  • Output Details  (type: collection<collection<string>>): outputs a collection containing the resulting cluster names and IDs.


In order to extract the values from the Output Clusters collection (in our case the output is a List (Of String) ), 

 

For Each and Log Track Data activities should be used:

Image AddedImage Added


Execution: The example below is an execution where all clusters with their details are returned:

Image Added 


Get Cluster

This activity returns the specified Cluster ID.

...

The Get Cluster activity parameters can be provided by manual inserted values or via IN arguments or variables:

Image RemovedImage Added

Parameters:

  • Cluster Name (text box editor type) (type: string): the name the name of the Cluster.
  • Datacenter Name (text box editor type) (type: string): the name the name of the Datacenter.

The Read Only Output variable are the possible output values that the activity will provide:

  • Output  (type: string): outputs the  outputs the resulting Cluster ID. If the Cluster is not found, value is empty.
 As mentioned above, the values for all the required parameters can be provided by IN arguments or variables. Below is an example of predefined arguments, ready to be used by the Get Cluster activity:

Image Removed

 

 

 


 Execution: The example below is an execution where the cluster id for Cluster "DemoCluster_Flowster" is returned:

 Image Added


 

Get Cluster Properties

This activity returns the properties of the specified Cluster.

Activity Parameters

The Get Cluster Properties activity parameters can be provided by manual inserted values or via IN arguments or variables:

...

Image Added

Parameters:

  • Cluster ID (text box editor type) (type: string):

...

  • the ID of the cluster whose properties are being

...

  • edited. E.g "domain-c99".

    The value can also be obtained from activities: Create Cluster or Get Cluster using the following steps:

    • use a Get Cluster/ Create Cluster activity to extract the ClusterID:   
       Image AddedImage Added
    • bind the obtained ClusterID (stored in variable) to the Cluster ID field from Delete Cluster activity:   

              Image Added

          

The Read Only Output variable are the possible output values that the activity will provide:

  • Output  (type: collection<string>):

...

  •  outputs a collection of Properties and their corresponding values.

...

  • Output Automation

...

  • Level  (type:

...

  • string): outputs the state of the

...

  • Automation Level.
  • Output

...

  • DRS  (type:

...

  • string): outputs

...

  • true/false if DRS is enabled.
  • Output HA  (type:

...

  • string):

...

  •  outputs true/false if HA is enabled.

 In order to extract the values from the output collection (in our case the output is a Collection(Of String) ), For Each and Log Track Data activities should be used:

Image Added


Execution: The example below is an execution where the properties for Cluster "DemoCluster_Flowster" are returned:

Image Added