diff --git a/build.gradle b/build.gradle
index 5f352a1..399d3e3 100644
--- a/build.gradle
+++ b/build.gradle
@@ -28,7 +28,7 @@ repositories {
 
 group = "com.electriccloud"
 description = "Plugins : EC-OpenStack"
-version = "1.3.5"
+version = "1.3.6"
 
 apply plugin: 'groovy'
 apply plugin: 'flow-gradle-plugin'
diff --git a/help/help.adoc b/help/help.adoc
new file mode 100644
index 0000000..d1a40b0
--- /dev/null
+++ b/help/help.adoc
@@ -0,0 +1,905 @@
+
+Plugin Version @PLUGIN_VERSION@
+
+
+Revised on December 25, 2018
+
+== {CD} integration to OpenStack
+
+The plugin communicates with OpenStack through its application programming interface (API), which provides support for developers who are building interactive clients of OpenStack using a RESTful application development style. The EC-OpenStack plugin allows users to build a cloud by launching images and assigning metadata to instances, providing a more generic interface for managing resources.
+
+The plugin interact with OpenStack through the Compute API and Image API using PERL to perform the following tasks:
+
+* Create configurations with the connection information.
+* Perform actions on machines.
+* Deploy and delete servers.
+* Create and delete key pairs.
+* Create and delete floating IPs.
+* Create {CD} resources.
+* Create, attach, detach, extend, and delete volumes.
+* Create new images.
+* Create a snapshot of a server.
+* Do hard and soft reboots of a server.
+* Deploy, update, and delete HEAT orchestration templates.
+
+This plugin provides two primary actions: Deploy and Cleanup, which work as a pair within a job.
+
+== Integrated version
+
+This plugin was developed and tested against OpenStack IceHouse.
+
+The minimum {CD} supported version is ElectricCommander 3.6.
+
+IMPORTANT: For all parameter descriptions in this document, the required parameters are shown in [.required]#bold italics#.
+
+[[setupconfig]]
+== Setting up the plugin configuration
+
+[[CreateConfiguration]]
+
+
+Plugin configurations are sets of parameters that apply across some or all of the plugin procedures. They reduce repetition of common values, create predefined sets of parameters for end users, and store credentials securely. Each configuration has a unique name that is automatically entered in designated parameters in the procedures.
+
+The *Identity Service URL* must have http or https followed by your server hostname or IP address.
+
+==== Input
+
+. Go to *Administration* > *Plugins* to open the Plugin Manager.
+. Find the EC-OpenStack row.
+. Click *Configure* to open the OpenStack Configurations page.
+. Click *Create Configuration*.
+. To create an OpenStack configuration, enter the following information and click *OK*.
+
+Remember that you may need to create additional configurations later.
+
+==== Output
+
+The OpenStack Configurations page now shows the new configuration.
+
+You can also manage your OpenStack configurations on this page. Click *Edit* to modify an existing configuration or *Delete* to remove an existing configuration.
+
+[[procedures]]
+== Plugin procedures
+
+[[AllocateIP]]
+
+
+=== AllocateIP
+
+This procedure creates a new OpenStack floating IP address to use with your OpenStack account. The plugin stores properties on the {CD} server in the location in the *Results Location* and *Results tag* fields. The default location in the job directory called /myJob/Openstack/deployed/_Provision tag_ if the *Results Location* is blank.
+
+==== Input
+
+. Go to the AllocateIP procedure.
+. Enter the following parameters:
+
+
+[cols=",",options="header",]
+|===
+|Parameter |Description
+|Configuration |The name of a valid existing configuration with the connection information. (Required)
+|Results Location |The location in the {CD} server where the properties are stored. The default is _/myJob/OpenStack/deployed_.
+|Results tag |The unique tag for this provision to separate it from the other deployments stored in the same location. The default is _$[jobStepId]_. (Required)
+|===
+
+==== Output
+
+After the job runs, you can view the results on the Job Details page in {CD}.
+
+In the *AllocateIP* step, click the Log button to see the diagnostic information.
+
+[[AssociateFloatingIP]]
+
+
+=== AssociateFloatingIP
+
+This procedure associates a floating IP address to an existing instance.
+
+==== Input
+
+. Go to the AssociateFloatingIP procedure.
+. Enter the following parameters:
+
+
+[cols=",",options="header",]
+|===
+|Parameter |Description
+|Configuration |The name of a valid existing configuration with the connection information. (Required)
+|Server Id |The ID of the target server with the IP address. (Required)
+|===
+
+==== Output
+
+After the job runs, you can view the results on the Job Details page in {CD}.
+
+In the *AssociateFloatingIP* step, click the Log button to see the diagnostic information.
+
+[[AttachVolume]]
+
+
+=== AttachVolume
+
+This procedure attaches volumes that are created with the volume API to server instances. You can attach a volume to one instance.
+
+The plugin stores properties on the Commander server at the location specified the *Results Location* and *Results tag* fields. The default location in the job directory called /myJob/Openstack/deployed/_Provision tag_ if the *Results Location* is empty.
+
+==== Input
+
+. Go to the AttachVolume procedure.
+. Enter the following parameters:
+
+
+[cols=",",options="header",]
+|===
+|Parameter |Description
+|Configuration |The name of a valid existing configuration with the connection information. (Required)
+|Server ID |ID of the server to which the volume is attached. (Required)
+|Volume ID |ID of the volume to attach. (Required)
+|Name of device |Name of the device, such as _/dev/vdb_, set after the volume is attached to a server. If you do not specify a name, OpenStack automatically assigns the device a name.
+|Results Location |The location on the {CD} server where the properties are stored. The default is _/myJob/OpenStack/deployed_.
+|Results tag |The unique tag for this provision to separate it from other deployments stored in the same location. The default is _$[jobStepId]_. (Required)
+|===
+
+==== Output
+
+After the job runs, you can view the results on the Job Details page in ElectricCommander.
+
+In the *AttachVolume* step, click the Log button to see the diagnostic information.
+
+[[Cleanup]]
+
+
+=== Cleanup
+
+This procedure deletes an existing OpenStack server instance that was created using the Deploy procedure.
+
+==== Input
+
+. Go to the Cleanup procedure.
+. Enter the following parameters:
+
+
+[cols=",",options="header",]
+|===
+|Parameter |Description
+|Configuration |The name of a valid existing configuration with the connection information. (Required)
+|Server ID(s) |The IDs of one ore more servers to delete. Use a comma-separated list for more than one server. (Required)
+|Resource name(s) |The name of the resources to delete. Use a comma-separated list for more than one resource.
+|===
+
+==== Output
+
+After the job runs, you can view the results on the Job Details page in {CD}.
+
+In the *Cleanup* step, click the Log button to see the diagnostic information.
+
+[[CloudManagerGrow]]
+
+
+=== CloudManagerGrow
+
+This procedure allows the plugin to work with the CloudManager plugin. It calls the Deploy procedure and is run by the CloudManager.
+
+==== Input
+
+. Go to the CloudManagerGrow procedure.
+. Enter the following parameters:
+
+
+[cols=",",options="header",]
+|===
+|Parameter |Description
+|Configuration |The name of a valid existing configuration with the connection information. (Required)
+|Tenant ID |The ID of the tenant to use. (Required)
+|Number of Servers |The number of servers to deploy. If there are more than one, a suffix (_#) is added to server names. The default is 1. (Required)
+|Server name |Name of the new server. (Required)
+|Image ID |The ID of an existing image in Openstack. (Required)
+|Flavor ID |The ID for the flavor to use. (Required)
+|Results tag |The unique tag for this provision to separate it from other deployments stored in the same location. The default is _$[jobStepId]_. (Required)
+|Resource Pool(s) |The names of resource pools in {CD} that will be asssociated with the machines in this configuration if resources are created. For more than one resource pool, specify the names in a space-separated list. (Required)
+|Resource workspace |The {CD} workspace that the resource uses.
+|===
+
+==== Output
+
+After the job runs, you can view the results on the Job Details page in {CD}.
+
+In the *CloudManagerGrow* step, click the Log button to see the diagnostic information.
+
+[[CloudManagerShrink]]
+
+
+=== CloudManagerShrink
+
+This procedure allows the plugin to work with the CloudManager plugin. It calls the Cleanup procedure and is run by the CloudManager.
+
+==== Input
+
+. Go to the CloudManagerShrink procedure.
+. Enter the following parameters:
+
+
+[cols=",",options="header",]
+|===
+|Parameter |Description
+|Configuration |The name of a valid existing configuration with the connection information. (Required)
+|List of Deployments |A list of deployments that were previously created by the CloudManagerGrow procedure to stop. (Required)
+|===
+
+==== Output
+
+After the job runs, you can view the results on the Job Details page in {CD}.
+
+In the *CloudManagerShrink* step, click the Log button to see the diagnostic information.
+
+[[CloudManagerSync]]
+
+
+=== CloudManagerSync
+
+This procedure allows the plugin to work with CloudManager plugin. It verifies that the instances it has recorded as _alive_ are still alive. It is run by the CloudManager.
+
+==== Input
+
+. Go to the CloudManagerSync procedure.
+. Enter the following parameters:
+
+
+[cols=",",options="header",]
+|===
+|Parameter |Description
+|Configuration |The name of a valid existing configuration with the connection information. (Required)
+|List of Deployments |A list of deployments that were previously created by the CloudManagerGrow procedure to verify. (Required)
+|===
+
+==== Output
+
+After the job runs, you can view the results on the Job Details page in {CD}.
+
+In the *CloudManagerSync* step, click the Log button to see the diagnostic information.
+
+[[CreateImage]]
+
+
+=== CreateImage
+
+This procedure creates a virtual machine (VM) image. You can launch new instances from these images.
+
+The plugin stores properties on the {CD} server at the location specified in the *Results Location* and *Results tag* fields. The default location in the job directory called /myJob/Openstack/deployed/_Provision tag_ if the *Results Location* field is empty.
+
+==== Input
+
+. Go to the CreateImage procedure.
+. Enter the following parameters:
+
+
+[cols=",",options="header",]
+|===
+|Parameter |Description
+|Configuration |The name of a valid existing configuration with the connection information. (Required)
+|Image name |Display name of the new image. (Required)
+|Disk format |The disk format of a VM image. Valid values are AKI,AMI,ARI,Raw,iso, vhd, vdi, qcow2,and vmdk. (Required)
+|Container format |The container format for the new image. Valid values are aki, ari, ami, bare, and ovf. (Required)
+|Is image location a local file ? |Select this parameter in the check box if the source image file is on the local machine. (Required)
+|Image path |Path to the image on the local machine or a valid and direct URL to image location. (Required)
+|Size |Size of the raw image file from which the new image is generated.
+|Checksum |The checksum of the raw image file.
+|Min-Ram |The minimum RAM in megabytes (MBs) required to run this image on a server.
+|Min-Disk |The minimum disk space in gigabytes (GBs) required to run this image on a server.
+|Owner |The ID of the owner (tenant) of the image.
+|Results Location |The location on the {CD} server where the properties are stored. The default is _/myJob/OpenStack/deployed_.
+|Results tag |The unique tag for this provision to separate it from other deployments stored in the same location. The default is _$[jobStepId]_. (Required)
+|===
+
+==== Output
+
+After the job runs, you can view the results on the Job Details page in {CD}.
+
+In the *CreateImage* step, click the Log button to see the diagnostic information.
+
+[[CreateInstanceSnapshot]]
+
+
+=== CreateInstanceSnapshot
+
+This procedure creates a snapshot from the instance. You can launch an instance from a snapshot.
+
+The plugin stores properties on the {CD} server at the location specified in the *Results Location* and *Results tag* fields. The default location in the job directory called /myJob/Openstack/deployed/_Provision tag_ if the *Results Location* field is empty.
+
+==== Input
+
+. Go to the CreateImage procedure.
+. Enter the following parameters:
+
+
+[cols=",",options="header",]
+|===
+|Parameter |Description
+|Configuration |The name of a valid existing configuration with the connection information. (Required)
+|Instance snapshot name |The display name of the snapshot. (Required)
+|Server ID |The ID of the server instance for which a snapshot is created. (Required)
+|Metadata |Metadata for the snapshot in this format: key1,value1,key2,value2 ...
+|Results Location |The location on the {CD} server where the properties are stored. The default is _/myJob/OpenStack/deployed_.
+|Results tag |The unique tag for this provision to separate it from other deployments stored in the same location. The default is _$[jobStepId]_. (Required)
+|===
+
+==== Output
+
+After the job runs, you can view the results on the Job Details page in {CD}.
+
+In the *CreateImage* step, click the Log button to see the diagnostic information.
+
+image::cloudbees-common::cd-plugins/ec-openstack/parameters/create-instance-snapshot.png[image]
+
+[[CreateKeyPair]]
+
+
+=== CreateKeyPair
+
+This procedure creates a new OpenStack key pair. The public key is stored by OpenStack and the private key is returned to you. If a key with the specified name already exists, OpenStack returns an error.
+
+The plugin store properties on the {CD} server at the location in the *Results Location* and the *Results tag* fields. The default location is the job directory called /myJob/Openstack/deployed/_Provision tag value_ if *Results Location* field is empty.
+
+==== Input
+
+. Go to the CreateKeyPair procedure.
+. Enter the following parameters:
+
+
+[cols=",",options="header",]
+|===
+|Parameter |Description
+|Configuration |The name of a valid existing configuration wtih the connection information. (Required)
+|Key name |A unique name for the key pair. The default is _cmdr-$[jobStepId]_. (Required)
+|Results Location |The location on the {CD} server where the properties are stored. The default is _/myJob/OpenStack/deployed_.
+|Results tag |The unique tag for this provision to separate it from other deployments stored in the same location. The default is _$[jobStepId]_. (Required)
+|===
+
+==== Output
+
+After the job runs, you can view the results on the Job Details page in {CD}.
+
+In the *CreateKeyPair* step, click the Log button to see the diagnostic information.
+
+[[CreateStack]]
+
+
+=== CreateStack
+
+Heat is an OpenStack service to orchestrate multiple composite cloud applications using templates. This procedure creates a new HEAT stack from a specified HEAT template. You can enter the template (in JSON or YAML format)in the *Template* field or the URL of the template.
+
+The plugin stores properties on the {CD} server at the location specified in the *Results Location* and *Results tag* fields. The default location in the job directory called /myJob/Openstack/deployed/_Provision tag_ if the *Results Location* field is empty.
+
+==== Input
+
+. Go to the CreateStack procedure.
+. Enter the following parameters:
+
+
+[cols=",",options="header",]
+|===
+|Parameter |Description
+|Configuration |The name of a valid existing configuration with the connection information. (Required)
+|Stack Name |The display name for the new stack. (Required)
+|Template |The stack template to instantiate a HEAT stack in JSON or YAML format.
+|Template URL |A URI to the location containing the updated stack template to instantiate. You specify this parameter only if you are not entering the template in the *Template* field.
+|Results Location |The location on the {CD} server where the properties are stored. The default is _/myJob/OpenStack/deployed_.
+|Results tag |The unique tag for this provision to separate it from other deployments stored in the same location. The default is _$[jobStepId]_. (Required)
+|===
+
+==== Output
+
+After the job runs, you can view the results on the Job Details page in {CD}.
+
+In the *CreateStack* step, click the Log button to see the diagnostic information.
+
+[[CreateVolume]]
+
+
+=== CreateVolume
+
+This procedure creates a new OpenStack volume. A volume is a detachable block storage device. You can attach a volume to one instance at a time.
+
+The plugin stores properties on the {CD} server in the location in the *Results Location* and *Results tag* fields. The default location in the job directory called /myJob/Openstack/deployed/_Provision tag_ if the *Results location* is empty.
+
+==== Input
+
+. Go to the CreateVolume procedure.
+. Enter the following parameters:
+
+
+[cols=",",options="header",]
+|===
+|Parameter |Description
+|Configuration |The name of a valid existing configuration with the connection information. (Required)
+|Volume name |The name for the new volume that appears in the UI. (Required)
+|Size (in gigabytes [GBs]) |Size of the volume in GB. (Required)
+|Type of volume |The volume type. (Required)
+|Availability zone |The availability zone where the new zone is created.
+|Results Location |The location on the {CD} server where the properties are stored. The default is _/myJob/OpenStack/deployed_.
+|Results tag |The unique tag for this provision to separate it from the other deployments stored in the same location. The default is _$[jobStepId]_. (Required)
+|===
+
+==== Output
+
+After the job runs, you can view the results on the Job Details page in {CD}.
+
+In the *CreateVolume* step, click the Log button to see the diagnostic information.
+
+[[CreateVolumeSnapshot]]
+
+
+=== CreateVolumeSnapshot
+
+This procedure creates a snapshot of a volume, a point-in-time complete copy of the volume. You can create a volume from this snapshot.
+
+The plugin stores properties on the {CD} server at the location specified in the *Results Location* and *Results tag* fields. The default location in the job directory called /myJob/Openstack/deployed/_Provision tag_ if the *Results Location* field is empty.
+
+==== Input
+
+. Go to the CreateVolumeSnapshot procedure.
+. Enter the following parameters:
+
+
+[cols=",",options="header",]
+|===
+|Parameter |Description
+|Configuration |The name of a valid existing configuration with the connection information. (Required)
+|Name of volume snapshot |The display name of the snapshot. (Required)
+|Description |The description of the snapshot.
+|Create a snapshot forecefully? |Select this parameter (in the check box) to forcefully create a snapshot of a volume even if it is attached to an instance. Selecting this parameter sets it to _true_.
+
+The default is _false_; the parameter is not selected.
+|Volume ID |The ID of the volume from which to create a snapshot. (Required)
+|Results Location |The location on the {CD} server where the properties are stored. The default is _/myJob/OpenStack/deployed_.
+|Results tag |The unique tag for this provision to separate it from other deployments stored in the same location. The default is _$[jobStepId]_. (Required)
+|===
+
+=== Output
+
+After the job runs, you can view the results on the Job Details page in {CD}.
+
+In the *CreateVolumeSnapshot* step, click the Log button to see the diagnostic information.
+
+[[DeleteKeyPair]]
+
+
+=== DeleteKeyPair
+
+This procedure deletes an existing OpenStack key pair. The public key is removed from OpenStack. You must own the key pair.
+
+==== Input
+
+. Go to the DeleteKeyPair procedure.
+. Enter the following parameters:
+
+
+[cols=",",options="header",]
+|===
+|Parameter |Description
+|Configuration |The name of a valid existing configuration with the connection information. (Required)
+|Key name |Name of the key pair to delete. (Required)
+|===
+
+==== Output
+
+After the job runs, you can view the results on the Job Details page in {CD}.
+
+In the *DeleteKeyPair* step, click the Log button to see the diagnostic information.
+
+[[DeleteStack]]
+
+
+=== DeleteStack
+
+This procedure deletes an existing stack.
+
+The plugin stores properties on the {CD} server at the location specified in the *Results Location* and *Results tag* fields. The default location in the job directory called /myJob/Openstack/deployed/_Provision tag_ if the *Results Location* field is empty.
+
+==== Input
+
+. Go to the DeleteStack procedure.
+. Enter the following parameters:
+
+
+[cols=",",options="header",]
+|===
+|Parameter |Description
+|Configuration |The name of a valid existing configuration with the connection information. (Required)
+|Stack Name |The display name of the stack to delete. (Required)
+|Stack ID |The ID of the stack to delete. (Required)
+|Results Location |The location on the {CD} server where the properties are stored. The default is _/myJob/OpenStack/deployed_.
+|Results tag |The unique tag for this provision to separate it from other deployments stored in the same location. The default is _$[jobStepId]_. (Required)
+|===
+
+==== Output
+
+After the job runs, you can view the results on the Job Details page in {CD}.
+
+In the *DeleteStack* step, click the Log button to see the diagnostic information.
+
+[[DeleteVolume]]
+
+
+=== DeleteVolume
+
+This procedure deletes a volume. A volume is a detachable block storage device.
+
+The plugin stores properties on the {CD} server at the location specified in the *Results Location* and *Results tag* fields. The default location is the the job directory called /myJob/Openstack/deployed/_Provision tag_ fields if the *Results Location* is empty.
+
+==== Input
+
+. Go to the DeleteVolume procedure.
+. Enter the following parameters:
+
+
+[cols=",",options="header",]
+|===
+|Parameter |Description
+|Configuration |The name of a valid existing configuration with the connection information. (Required)
+|Volume ID |ID of the volume to delete. (Required)
+|===
+
+==== Output
+
+After the job runs, you can view the results on the Job Details page in {CD}.
+
+In the *DeleteVolume* step, click the Log button to see the diagnostic information.
+
+[[Deploy]]
+
+
+=== Deploy
+
+This procedure calls the CreateKey procedure and deploys one or more new instances. It store properties on the {CD} server at the location specified in the *Results Location* and the *Results tag* fields. The default location is in the directory for the job deployment results (/myJob/Openstack/deployed/_Results tag value_) if the *Results Location* field is empty.
+
+==== Input
+
+. Go to the Deploy procedure.
+. Enter the following parameters:
+
+
+[cols=",",options="header",]
+|===
+|Parameter |Description
+|Configuration |The name of a valid existing configuration with the connection information. (Required)
+|Key Pair Name |Name of an existing key pair. (Required)
+|Number of Servers |Number of servers to deploy. If there are more than one, a suffix (_#) is added to the server names. The default is 1. (Required)
+|Server name |Name of the new server. (Required)
+|Image ID |ID of an existing image in OpenStack. (Required)
+|Flavor ID |ID of the flavor to use. (Required)
+|Security Group(s) |One or more security groups in a newline delimited list.
+|Availability Zone |The availability zone in which to launch the server.
+|Customization Script |Configuration information or scripts to execute when the server is launched.
+|Results Location |The location on the {CD} server where the properties are stored. The default is _/myJob/OpenStack/deployed_.
+|Results tag |The unique tag for this provision to keep it separate from the other deployments stored in the same location. The default is _$[jobStepId]_. (Required)
+|Create Resource? |Select this parameter (in the check box) to create resources for deployed servers.
+|Associate IP? |Select this parameter in the check box to associate the IP address with the deployed instance.
+|Resource Pool |Name of the resource pool in {CD} that is associated with the machines in this configuration when resources are created.
+|Resource Port |Port that will be used when creating a resource.
+|Resource workspace |The {CD} workspace that the resources uses.
+|Resource Zone Name |The {CD} zone name for a resource. Used when creating a resource.
+|===
+
+==== Output
+
+After the job runs, you can view the results on the Job Details page in {CD}.
+
+In the *Deploy* step, click the Log button to see the diagnostic information.
+
+[[DetachVolume]]
+
+
+=== DetachVolume
+
+This procedure detaches a volume from a server. A volume is a detachable block storage device.
+
+The plugin store properties on the {CD} server at the location specified in the *Results Location* and *Results tag* fields. The default location is the job directory called /myJob/Openstack/deployed/_Provision tag_ if the *Results Location* field is empty.
+
+==== Input
+
+. Go to the DetachVolume procedure.
+. Enter the following parameters:
+
+
+[cols=",",options="header",]
+|===
+|Parameter |Description
+|Configuration |The name of a valid existing configuration with the connection information. (Required)
+|Server ID |ID of the server from which the volume is detached. (Required)
+|Volume ID |ID of the volume to detach. (Required)
+|Attachment ID |ID of the volume attachment. (Required)
+|===
+
+==== Output
+
+After the job runs, you can view the results on the Job Details page in {CD}.
+
+In the *DetachVolume* step, click the Log button to see the diagnostic information.
+
+[[ExtendVolume]]
+
+
+=== ExtendVolume
+
+This procedure extends the size of the specified volume. The volume must be in _available state_ before the size is extended.
+
+The plugin stores properties on the {CD} server at the location specified in the *Results Location* and *Results tag* fields. The default location in the job directory called /myJob/Openstack/deployed/_Provision tag_ if the *Results Location* field is empty.
+
+*Note:* Make sure that the ExtendVolume procedure is supported by the Openstack services before using this step.
+
+==== Input
+
+. Go to the ExtendVolume procedure.
+. Enter the following parameters:
+
+
+[cols=",",options="header",]
+|===
+|Parameter |Description
+|Configuration |The name of a valid existing configuration with the connection information. (Required)
+|Volume ID |ID of the volume to extend. (Required)
+|New size |New size of the volume. (Required)
+|Results Location |The location on the {CD} server where the properties are stored. The default is _/myJob/OpenStack/deployed_.
+|Results tag |The unique tag for this provision to separate it from other deployments stored in the same location. The default is _$[jobStepId]_. (Required)
+|===
+
+==== Output
+
+After the job runs, you can view the results on the Job Details page in {CD}.
+
+In the *ExtendVolume* step, click the Log button to see the diagnostic information.
+
+[[RebootInstance]]
+
+
+=== RebootInstance
+
+This procedure reboots a server instance.
+
+The plugin stores properties on the {CD} server at the location specified in the *Results Location* and *Results tag* fields. The default location in the job directory called /myJob/Openstack/deployed/_Provision tag_ if the *Results Location* field is empty.
+
+==== Input
+
+. Go to the RebootInstance procedure.
+. Enter the following parameters:
+
+
+[cols=",",options="header",]
+|===
+|Parameter |Description
+|Configuration |The name of a valid existing configuration with the connection information. (Required)
+|Server ID |ID of the server to reboot. (Required)
+|Reboot Type |Type of the reboot action (_Hard_ or _Soft_). (Required)
+|===
+
+==== Output
+
+After the job runs, you can view the results on the Job Details page in {CD}.
+
+In the *RebootInstance* step, click the Log button to see the diagnostic information.
+
+[[ReleaseIP]]
+
+
+=== ReleaseIP
+
+This procedure deletes an existing OpenStack floating IP address that is allocated to your account.
+
+==== Input
+
+. Go to the ReleaseIP procedure.
+. Enter the following parameters:
+
+
+[cols=",",options="header",]
+|===
+|Parameter |Description
+|Configuration |The name of a valid existing configuration with the connection information. (Required)
+|Floating Address ID |ID of the floating IP address to delete. (Required)
+|===
+
+==== Output
+
+After the job runs, you can view the results on the Job Details page in {CD}.
+
+In the *ReleaseIP* step, click the Log button to see the diagnostic information.
+
+[[Teardown]]
+
+
+=== Teardown
+
+This procedure deletes an existing OpenStack server.
+
+==== Input
+
+. Go to the Teardown procedure.
+. Enter the following parameters:
+
+
+[cols=",",options="header",]
+|===
+|Parameter |Description
+|Configuration |The name of a valid existing configuration with the connection information.
+|Resource name(s) |The names of the resources to delete. For more than one resource, use a comma-separated list. (Required)
+|===
+
+==== Output
+
+After the job runs, you can view the results on the Job Details page in {CD}.
+
+In the *Teardown* step, click the Log button to see the diagnostic information.
+
+[[UpdateStack]]
+
+
+=== UpdateStack
+
+This procedure updates an existing stack. You can enter the updated template (in JSON or YAML format)in the *Template* field or the URL of the template.
+
+The plugin stores properties on the {CD} server at the location specified in the *Results Location* and *Results tag* fields. The default location in the job directory called /myJob/Openstack/deployed/_Provision tag_ if the *Results Location* field is empty.
+
+==== Input
+
+. Go to the UpdateStack procedure.
+. Enter the following parameters:
+
+
+[cols=",",options="header",]
+|===
+|Parameter |Description
+|Configuration |The name of a valid existing configuration with the connection information. (Required)
+|Stack Name |The display name of the stack to update. (Required)
+|Stack ID |The ID of the stack to update. (Required)
+|Template |The template (in JSON or YAML format) with which to update the stack.
+|Template URL |A URI to the location containing the updated stack template to instantiate. You specify this parameter only if you are not entering the template in the *Template* field.
+|Results Location |The location on the {CD} server where the properties are stored. The default is _/myJob/OpenStack/deployed_.
+|Results tag |The unique tag for this provision to separate it from other deployments stored in the same location. The default is _$[jobStepId]_. (Required)
+|===
+
+==== Output
+
+After the job runs, you can view the results on the Job Details page in {CD}.
+
+In the *UpdateStack* step, click the Log button to see the diagnostic information.
+
+== Use cases and examples
+
+=== Use case: deploy, consume, and cleanup a job
+
+Deploy and cleanup work as a pair within a job.
+
+The most common use for this plugin is to create a server, create {CD} resources assigned to it, use the resources to run some operations, and then delete the resource and the server. To accomplish these tasks you must:
+
+. Create a plugin configuration.
+. Deploy an OpenStack server.
+. Create resources for this deployment.
+. Use the resources.
+. Delete the resources.
+. Delete the deployed server.
+
+=== Create a plugin configuration
+
+. Go to *Administration* > *Plugins* to open the Plugin Manager.
+. Find the EC-OpenStack row.
+. Click *Configure* to open the OpenStack Configurations page.
+. Click *Create Configuration*.
+. To create an OpenStack configuration, enter the following information and click *OK*.
+
+image::cloudbees-common::cd-plugins/ec-openstack/use-cases/case-1/create-config.png[image]
+
+=== Deploy an OpenStack server
+
+. Go to the Deploy procedure.
+. Enter the following parameters:
+
+=== Consume
+
+Create a new command step to use a resource that you created.
+
+In this example, add a resource from a resource pool using the ec-perl sleep command for 30 seconds:
+
+image::cloudbees-common::cd-plugins/ec-openstack/use-cases/case-1/consume-parameters.png[image]
+
+=== Clean up
+
+Create a Cleanup step as follows:
+
+image::cloudbees-common::cd-plugins/ec-openstack/use-cases/case-1/cleanup-parameters.png[image]
+
+=== Results and output
+
+After the job runs, you can view the results in {CD}:
+
+image::cloudbees-common::cd-plugins/ec-openstack/use-cases/case-1/job.png[image]
+
+image::cloudbees-common::cd-plugins/ec-openstack/use-cases/case-1/results.png[image]
+
+Deploy output:
+
+image::cloudbees-common::cd-plugins/ec-openstack/use-cases/case-1/deploy-log.png[image]
+
+Cleanup output:
+
+image::cloudbees-common::cd-plugins/ec-openstack/use-cases/case-1/cleanup-log.png[image]
+
+[[rns]]
+== Release notes
+
+=== EC-OpenStack 1.3.6
+
+* The documentation hahs been migrated to the main documentation site.
+
+=== EC-OpenStack 1.3.5
+
+* The plugin icon has been updated.
+
+=== EC-OpenStack 1.3.4
+
+* Added Rackspace support for Dynamic Environments
+* Configured the plugin to allow the {CD} UI to create configs inline of procedure form.
+* Configured the plugin to allow the {CD} UI to render the plugin procedure parameters entirely using the configured form XMLs.
+* Enabled the plugin for managing the plugin configurations in-line when defining an application process step or a pipeline stage task.
+
+=== EC-OpenStack 1.3.3
+
+* Added region field for create volume procedure
+
+=== EC-OpenStack 1.3.2
+
+* Added resource port field to the Dynamic Environments feature
+* Added resource port field to the Deploy procedure
+
+=== EC-OpenStack 1.3.1
+
+* Fixed issue with configurations being cached for IE.
+* Added validation to the CreateConfiguration procedure for the dynamic environments feature.
+* Added the "Tenant ID" parameter to the plugin configuration.
+* Removed tenant_id from all procedures except CreateConfiguration.
+* Added the ability to dynamically retrieve drop-down options such as image or flavor when creating resource templates for dynamic environments.
+* Added the ability to create a resource in non-default zone.
+
+=== EC-OpenStack 1.2.1
+
+* Fixed the issue that occurs when a resource was not created after provisioning it and the "Duplicate resource name" error message appears.
+* The Workspace parameter was removed from procedure to create an OpenStack configuration.
+
+=== EC-OpenStack 1.2.0
+
+The following procedures were added:
+
+* CreateVolume to create a new volume.
+* ExtendVolume to extend the size of a volume.
+* AttachVolume to attach the volume to a server instance.
+* DetachVolume to detach the volume from a server instance.
+* DeleteVolume to delete a volume from an OpenStack block storage.
+* CreateImage to create a virtual machine (VM) image on OpenStack Image Service Glance.
+* CreateInstanceSnapshot to create a snapshot of a server instance.
+* CreateVolumeSnapshot to create a snapshot of a volume.
+* CreateStack to create a HEAT stack from a HEAT template.
+* UpdateStack to update an existing stack with a template.
+* DeleteStack to delete an existing stack.
+
+The Deploy procedure was updated to add support for customization scripts, availability zones, security groups, and deployments using an instance snapshot.
+
+=== EC-OpenStack 1.1.2
+
+* Added properties in _ec_cloudprovisioning_plugin_ property sheet for {CD} Deploy.
+
+=== EC-OpenStack 1.1.1
+
+* Added support for Keystone v3 authorization.
+* Decoupled key pairs in creation and deletion operations from the Deploy and Cleanup procedures.
+* Added the AssociateFloatingIP procedure to associate floating IP addresses to existing VMs.
+* Fixed the *Create Resource?* parameter in the Deploy procedure.
+
+=== EC-OpenStack 1.0.0
+
+* Added the configuration management procedures.
+* Added the AllocateIP, Cleanup, CreateKeyPair, DeleteKeyPair, Deploy, and ReleaseIP procedures.
+* Implemented CloudManager support.
+* Implemented the XML parameter panel.
+* Added a Help link to each procedure.
+* Added the Help page.
+* Added use cases.
diff --git a/htdocs/images/parameters/allocate_ip_panel.png b/htdocs/images/parameters/allocate-ip-panel.png
similarity index 100%
rename from htdocs/images/parameters/allocate_ip_panel.png
rename to htdocs/images/parameters/allocate-ip-panel.png
diff --git a/htdocs/images/parameters/associate_floatingip.png b/htdocs/images/parameters/associate-floatingip.png
similarity index 100%
rename from htdocs/images/parameters/associate_floatingip.png
rename to htdocs/images/parameters/associate-floatingip.png
diff --git a/htdocs/images/parameters/attach_volume.png b/htdocs/images/parameters/attach-volume.png
similarity index 100%
rename from htdocs/images/parameters/attach_volume.png
rename to htdocs/images/parameters/attach-volume.png
diff --git a/htdocs/images/parameters/cleanup_panel.png b/htdocs/images/parameters/cleanup-panel.png
similarity index 100%
rename from htdocs/images/parameters/cleanup_panel.png
rename to htdocs/images/parameters/cleanup-panel.png
diff --git a/htdocs/images/parameters/cloudmanager_grow_panel.png b/htdocs/images/parameters/cloudmanager-grow-panel.png
similarity index 100%
rename from htdocs/images/parameters/cloudmanager_grow_panel.png
rename to htdocs/images/parameters/cloudmanager-grow-panel.png
diff --git a/htdocs/images/parameters/cloudmanager_shrink_panel.png b/htdocs/images/parameters/cloudmanager-shrink-panel.png
similarity index 100%
rename from htdocs/images/parameters/cloudmanager_shrink_panel.png
rename to htdocs/images/parameters/cloudmanager-shrink-panel.png
diff --git a/htdocs/images/parameters/cloudmanager_sync_panel.png b/htdocs/images/parameters/cloudmanager-sync-panel.png
similarity index 100%
rename from htdocs/images/parameters/cloudmanager_sync_panel.png
rename to htdocs/images/parameters/cloudmanager-sync-panel.png
diff --git a/htdocs/images/parameters/configuration_panel.png b/htdocs/images/parameters/configuration-panel.png
similarity index 100%
rename from htdocs/images/parameters/configuration_panel.png
rename to htdocs/images/parameters/configuration-panel.png
diff --git a/htdocs/images/parameters/create_image.png b/htdocs/images/parameters/create-image.png
similarity index 100%
rename from htdocs/images/parameters/create_image.png
rename to htdocs/images/parameters/create-image.png
diff --git a/htdocs/images/parameters/create_instance_snapshot.png b/htdocs/images/parameters/create-instance-snapshot.png
similarity index 100%
rename from htdocs/images/parameters/create_instance_snapshot.png
rename to htdocs/images/parameters/create-instance-snapshot.png
diff --git a/htdocs/images/parameters/create_key_panel.png b/htdocs/images/parameters/create-key-panel.png
similarity index 100%
rename from htdocs/images/parameters/create_key_panel.png
rename to htdocs/images/parameters/create-key-panel.png
diff --git a/htdocs/images/parameters/create_stack.png b/htdocs/images/parameters/create-stack.png
similarity index 100%
rename from htdocs/images/parameters/create_stack.png
rename to htdocs/images/parameters/create-stack.png
diff --git a/htdocs/images/parameters/create_volume_snapshot.png b/htdocs/images/parameters/create-volume-snapshot.png
similarity index 100%
rename from htdocs/images/parameters/create_volume_snapshot.png
rename to htdocs/images/parameters/create-volume-snapshot.png
diff --git a/htdocs/images/parameters/create_volume.png b/htdocs/images/parameters/create-volume.png
similarity index 100%
rename from htdocs/images/parameters/create_volume.png
rename to htdocs/images/parameters/create-volume.png
diff --git a/htdocs/images/parameters/delete_key_panel.png b/htdocs/images/parameters/delete-key-panel.png
similarity index 100%
rename from htdocs/images/parameters/delete_key_panel.png
rename to htdocs/images/parameters/delete-key-panel.png
diff --git a/htdocs/images/parameters/delete_stack.png b/htdocs/images/parameters/delete-stack.png
similarity index 100%
rename from htdocs/images/parameters/delete_stack.png
rename to htdocs/images/parameters/delete-stack.png
diff --git a/htdocs/images/parameters/delete_volume.png b/htdocs/images/parameters/delete-volume.png
similarity index 100%
rename from htdocs/images/parameters/delete_volume.png
rename to htdocs/images/parameters/delete-volume.png
diff --git a/htdocs/images/parameters/deploy_panel.png b/htdocs/images/parameters/deploy-panel.png
similarity index 100%
rename from htdocs/images/parameters/deploy_panel.png
rename to htdocs/images/parameters/deploy-panel.png
diff --git a/htdocs/images/parameters/detach_volume.png b/htdocs/images/parameters/detach-volume.png
similarity index 100%
rename from htdocs/images/parameters/detach_volume.png
rename to htdocs/images/parameters/detach-volume.png
diff --git a/htdocs/images/parameters/extend_volume.png b/htdocs/images/parameters/extend-volume.png
similarity index 100%
rename from htdocs/images/parameters/extend_volume.png
rename to htdocs/images/parameters/extend-volume.png
diff --git a/htdocs/images/parameters/release_ip_panel.png b/htdocs/images/parameters/release-ip-panel.png
similarity index 100%
rename from htdocs/images/parameters/release_ip_panel.png
rename to htdocs/images/parameters/release-ip-panel.png
diff --git a/htdocs/images/parameters/teardown_panel.png b/htdocs/images/parameters/teardown-panel.png
similarity index 100%
rename from htdocs/images/parameters/teardown_panel.png
rename to htdocs/images/parameters/teardown-panel.png
diff --git a/htdocs/images/parameters/update_stack.png b/htdocs/images/parameters/update-stack.png
similarity index 100%
rename from htdocs/images/parameters/update_stack.png
rename to htdocs/images/parameters/update-stack.png
diff --git a/htdocs/images/use_cases/Case_1/cleanup_log.png b/htdocs/images/use-cases/case-1/cleanup-log.png
similarity index 100%
rename from htdocs/images/use_cases/Case_1/cleanup_log.png
rename to htdocs/images/use-cases/case-1/cleanup-log.png
diff --git a/htdocs/images/use_cases/Case_1/cleanup_parameters.png b/htdocs/images/use-cases/case-1/cleanup-parameters.png
similarity index 100%
rename from htdocs/images/use_cases/Case_1/cleanup_parameters.png
rename to htdocs/images/use-cases/case-1/cleanup-parameters.png
diff --git a/htdocs/images/use_cases/Case_1/consume_parameters.png b/htdocs/images/use-cases/case-1/consume-parameters.png
similarity index 100%
rename from htdocs/images/use_cases/Case_1/consume_parameters.png
rename to htdocs/images/use-cases/case-1/consume-parameters.png
diff --git a/htdocs/images/use_cases/Case_1/create_config.png b/htdocs/images/use-cases/case-1/create-config.png
similarity index 100%
rename from htdocs/images/use_cases/Case_1/create_config.png
rename to htdocs/images/use-cases/case-1/create-config.png
diff --git a/htdocs/images/use_cases/Case_1/deploy_log.png b/htdocs/images/use-cases/case-1/deploy-log.png
similarity index 100%
rename from htdocs/images/use_cases/Case_1/deploy_log.png
rename to htdocs/images/use-cases/case-1/deploy-log.png
diff --git a/htdocs/images/use_cases/Case_1/deploy_parameters.png b/htdocs/images/use-cases/case-1/deploy-parameters.png
similarity index 100%
rename from htdocs/images/use_cases/Case_1/deploy_parameters.png
rename to htdocs/images/use-cases/case-1/deploy-parameters.png
diff --git a/htdocs/images/use_cases/Case_1/job.png b/htdocs/images/use-cases/case-1/job.png
similarity index 100%
rename from htdocs/images/use_cases/Case_1/job.png
rename to htdocs/images/use-cases/case-1/job.png
diff --git a/htdocs/images/use_cases/Case_1/results.png b/htdocs/images/use-cases/case-1/results.png
similarity index 100%
rename from htdocs/images/use_cases/Case_1/results.png
rename to htdocs/images/use-cases/case-1/results.png
diff --git a/pages/EC-OpenStack_help.xml b/pages/EC-OpenStack_help.xml
index c1dbe9f..d97fbfd 100644
--- a/pages/EC-OpenStack_help.xml
+++ b/pages/EC-OpenStack_help.xml
@@ -1,1813 +1,21 @@
-<?xml version="1.0"?>
+
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-  <meta name="generator" content="HTML Tidy for Windows (vers 25 March 2009), see www.w3.org" />
-  <meta content="text/html; charset=us-ascii" http-equiv="content-type" />
-
-  <title>ElectricFlow Plugin for OpenStack</title>
-  <link rel="stylesheet" href="../../plugins/@PLUGIN_KEY@/pluginhelp.css" type="text/css" media="screen" />
-</head>
-
-<body>
-  <div class="help">
-    <h1>OpenStack</h1>
-
-    <p>Plugin Version @PLUGIN_VERSION@</p>
-    <hr style="margin-left: -10px; margin-top: 10px; height: 1px; width: 100%; color: #5981BD;" noshade="noshade" />
-		
-		<p>Revised on December 25, 2018</p>
-
-	<h1>Contents</h1>
-				
-		<ul>
-				<li><p><a href="#overview">Overview</a></p></li>
-				<li><p><a href="#setupconfig">Setting Up the Plugin Configuration</a></p></li>
-				<li><p><a href="#ElectricFlow">Setting Up ElectricFlow</a></p></li>
-				<li><p><a href="#procedures">Plugin Procedures</a></p></li>
-				<ul>
-				<li><a href="#AllocateIP">AllocateIP</a></li>
-				<li><a href="#AssociateFloatingIP">AssociateFloatingIP</a></li>
-				<li><a href="#AttachVolume">AttachVolume</a></li>
-				<li><a href="#Cleanup">Cleanup</a></li>
-				<li><a href="#CloudManagerGrow">CloudManagerGrow</a></li>
-				<li><a href="#CloudManagerShrink">CloudManagerShrink</a></li>
-				<li><a href="#CloudManagerSync">CloudManagerSync</a></li>
-				<li><a href="#CreateImage">CreateImage</a></li>
-				<li><a href="#CreateInstanceSnapshot">CreateInstanceSnapshot</a></li>
-				<li><a href="#CreateKeyPair">CreateKeyPair</a></li>
-				<li><a href="#CreateStack">CreateStack</a></li>
-				<li><a href="#CreateVolume">CreateVolume</a></li>
-				<li><a href="#CreateVolumeSnapshot">CreateVolumeSnapshot</a></li>
-				<li><a href="#DeleteKeyPair">DeleteKeyPair</a></li>
-				<li><a href="#DeleteStack">DeleteStack</a></li>
-				<li><a href="#DeleteVolume">DeleteVolume</a></li>
-				<li><a href="#Deploy">Deploy</a></li>
-				<li><a href="#DetachVolume">DetachVolume</a></li>
-				<li><a href="#ExtendVolume">ExtendVolume</a></li>
-				<li><a href="#RebootInstance">RebootInstance</a></li>
-				<li><a href="#ReleaseIP">ReleaseIP</a></li>
-				<li><a href="#Teardown">Teardown</a></li>
-        <li><a href="#UpdateStack">UpdateStack</a></li>
-				</ul>
-				<li><p><a href="#example">Examples and Use Cases</a></p></li>
-				<li><p><a href="#rns">Release Notes</a></p></li>
-		</ul>
-					
-	<h1 id="overview">Overview</h1>
-
-  <p>OpenStack is an Infrastructure as a Service (IaaS) cloud computing project by Rackspace Cloud and NASA. It is free open-source software released under the terms of the Apache License.</p>
-
-  <p>The mission of the OpenStack project is to enable any organization to create and offer cloud computing services running on standard hardware. The community's first official release, code-named Austin, was made available just four months later with plans to release regular updates of the software every few months.</p>
-
-  <p>OpenStack integrates code from NASA's Nebula platform as well as Rackspace's Cloud Files platform.</p>
-
-  <p>For more information about OpenStack, go to </p>
-	<ul>
-	<li><a href="http://www.openstack.org/">OpenStack website</a></li>
-	<li><a href="http://docs.openstack.org/">OpenStack Manuals</a></li>
-	<li><a href="http://docs.openstack.org/api/quick-start/content/">OpenStack API Quick Start</a></li>
-  <li><a href="http://api.openstack.org/">OpenStack API Reference</a></li>
-	</ul>
-	
-  <h2>ElectricFlow Integration to OpenStack</h2>
-				
-	<!-- The integration description should answer the questions:
-How deep does our integration go? Why should I care? What general
-functionality does the plugin include? What functionality does
-the plugin omit?
--->
-
-    <p>The plugin communicates with OpenStack through its application programming interface (API), which provides support
-  for developers who are building interactive clients of OpenStack using a RESTful application development style. The EC-OpenStack 
-	plugin allows users to build a cloud by launching images and assigning metadata to instances, providing a more generic
-  interface for managing resources.</p>
-
-  <p>The plugin interact with OpenStack through the Compute API and Image API using PERL to perform the following tasks:</p>
-
-  <ul>
-    <li>Create configurations with the connection information.</li>
-    <li>Perform actions on machines.</li>
-    <li>Deploy and delete servers.</li>
-    <li>Create and delete key pairs.</li>
-    <li>Create and delete floating IPs.</li>
-    <li>Create ElectricFlow resources.</li>
-    <li>Create, attach, detach, extend, and delete volumes.</li>
-    <li>Create new images.</li>
-    <li>Create a snapshot of a server.</li>
-    <li>Do hard and soft reboots of a server.</li>
-    <li>Deploy, update, and delete HEAT orchestration templates.</li>
-  </ul>
-
-  <p>This plugin provides two primary actions: Deploy and Cleanup, which work as a pair within a job.</p>
-
-    <h2>Integrated Version</h2>
-
-    <p>This plugin was developed and tested against OpenStack IceHouse. </p>
-
-    <p>The minimum ElectricFlow supported version is ElectricCommander 3.6.</p>
-		
-		<p>IMPORTANT: For all parameter descriptions in this document, the required parameters are shown in 
-		<span class="required">bold italics</span>.</p>
-
-    <h1 id="setupconfig">Setting Up the Plugin Configuration</h1>
-		
-		<div id="CreateConfiguration"><a name="CreateConfiguration" id="CreateConfiguration"></a>
-
-    <p>Plugin configurations are sets of parameters that apply across some or all of the plugin procedures. 
-		They reduce repetition of common values, create predefined sets of parameters for end users, and store 
-		credentials securely. Each configuration has a unique name that is automatically entered in designated 
-		parameters in the procedures.</p>
-		
-		<p>The <b>Identity Service URL</b> must have http or https followed by your server hostname or IP address.</p>
-						
-		<h2>Input</h2>
-  
-    <ol>
-		  <li>Go to <b>Administration</b> &gt; <b>Plugins</b> to open the Plugin Manager.</li>
-		  <li>Find the EC-OpenStack row.</li>
-		  <li>Click <b>Configure</b> to open the OpenStack Configurations page.</li> 	
-		  <li>Click <b>Create Configuration</b>.</li>
-		  <li>To create an OpenStack configuration, enter the following information and click <b>OK</b>. 
-			<br /> Remember that you may need to create additional configurations later.</li>
-			
-			<table class="grid">
-      <thead>
-        <tr>
-          <th>Parameter</th>
-          <th>Description</th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-        <td class="required">Configuration Name</td>
-        <td>A unique name for the configuration. (Required)</td>
-      </tr>
-      <tr>
-        <td>Description</td>
-        <td>A description for this configuration.</td>
-      </tr>
-      <tr>
-          <td class="required">Identity Service URL</td>
-          <td>Provide the host name or IP address of the Identity Service for OpenStack.For example, http://192.168.100.134:8776. Do not include API version or tenant ID in URL here. (Required)</td>
-      </tr>
-	  <tr>
-          <td class="required">Login as</td>
-          <td>The OpenStack account user name and password. This
-        account must have enough privileges to perform API
-        functions. (Required)</td>
-      </tr>
-      <tr>
-          <td>Tenant ID</td>
-          <td>ID of the tenant to use.</td>
-      </tr>
-      <tr>
-        <td class="required">Compute Service URL</td>
-
-        <td>Provide the host name or IP address of the Compute Service for OpenStack.For example, http://192.168.100.134:8776. Do not include API version or tenant ID in URL here. (Required)</td>
-      </tr>
-
-
-          <tr>
-              <td class="required">Block Storage URL:</td>
-
-              <td>Provide the host name or IP address of the Block Storage Service for OpenStack.For example, http://192.168.100.134:8776. Do not include API version or tenant ID in URL here. (Required)</td>
-          </tr>
-
-          <tr>
-              <td class="required">Image Service URL</td>
-
-              <td>Provide the host name or IP address of the Image Service for OpenStack.For example, http://192.168.100.134:8776. Do not include API version or tenant ID in URL here. (Required)</td>
-          </tr>
-
-          <tr>
-              <td>Orchestration Service URL</td>
-
-              <td>Provide the host name or IP address of the Orchestration Service for OpenStack.For example, http://192.168.100.134:8776. Do not include API version or tenant ID in URL here.</td>
-          </tr>
-
-		  <tr>
-              <td class="required">Compute API version</td>
-
-              <td>The Compute Service API version. (Required)</td>
-          </tr>
-		  
-          <tr>
-              <td class="required">Keystone API version</td>
-
-              <td>The Keystone API version. (Required)</td>
-          </tr>
-
-          <tr>
-              <td class="required">Blockstorage API version</td>
-
-              <td>The OpenStack block storage API version. (Required)</td>
-          </tr>
-
-          <tr>
-              <td class="required">Image API version</td>
-
-              <td>The Image Service API version. (Required)</td>
-          </tr>
-
-        <tr>
-        <td class="required">Resource</td>
-        <td>The name of the resource (or pool) on which the integration steps can run. The default is <i>local</i>. (Required)</td>
-      </tr>
-      <tr>
-        <td class="required">Debug Level</td>
-        <td>The level for output: 0=errors only, 1=normal headers and responses, 2+=debugging information included.(Required)</td>
-      </tr>
-      </tbody>
-    </table>
-		
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/parameters/configuration_panel.png" />
-			
-		</ol>
-		
-		<h3>Output</h3>	 
-		
-		<p>The OpenStack Configurations page now shows the new configuration.</p>
-		
-		<p>You can also manage your OpenStack configurations on this page. Click <b>Edit</b> to modify an existing configuration or 
-		<b>Delete</b> to remove an existing configuration.</p>
-		
-		</div>
-			
-		<h1 id="procedures">Plugin Procedures</h1>
-		
-		<div id="AllocateIP"><a name="AllocateIP" id="AllocateIP"></a>
-
-    <h2>AllocateIP</h2>
-
-    <p>This procedure creates a new OpenStack floating IP address to use with your OpenStack account. The plugin stores properties 
-		on the ElectricFlow server in the location in the <b>Results Location</b> and <b>Results tag</b> fields. The default location 
-		in the job directory called /myJob/Openstack/deployed/<i>Provision tag</i> if the <b>Results Location</b> is blank.</p>
-		
-		<h3>Input</h3>
-		
-			<ol>
-			<li>Go to the AllocateIP procedure.</li>
-			<li>Enter the following parameters:<br />
-      <table class="grid">
-      <thead>
-        <tr>
-          <th>Parameter</th>
-          <th>Description</th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td class="required">Configuration</td>
-          <td>The name of a valid existing configuration with the connection information. (Required)</td>
-        </tr>
-        <tr>
-          <td>Results Location</td>
-          <td>The location in the ElectricFlow server where the properties are stored. The default is <i>/myJob/OpenStack/deployed</i>.</td>
-        </tr>
-        <tr>
-          <td class="required">Results tag</td>
-          <td>The unique tag for this provision to separate it from the other deployments stored in the same location. The default is <i>$[jobStepId]</i>. (Required)</td>
-        </tr>
-      </tbody>
-    </table>
-		</li>
-						
-		<br />
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/parameters/allocate_ip_panel.png" />
-		<br />
-
-		</ol>   
-						
-		<h3>Output</h3>
-						
-		<p>After the job runs, you can view the results on the Job Details page in ElectricFlow.</p>
-				
-		<p>In the <b>AllocateIP</b> step, click the Log button to see the diagnostic information.</p>	
-
-    </div>
-		
-		<div id="AssociateFloatingIP"><a name="AssociateFloatingIP" id="AssociateFloatingIP"></a>
-
-    <h2>AssociateFloatingIP</h2>
-
-    <p>This procedure associates a floating IP address to an existing instance.</p>
-		
-		<h3>Input</h3>
-		
-			<ol>
-			<li>Go to the AssociateFloatingIP procedure.</li>
-			<li>Enter the following parameters:<br />
-      <table class="grid">
-      <thead>
-        <tr>
-          <th>Parameter</th>
-          <th>Description</th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td class="required">Configuration</td>
-          <td>The name of a valid existing configuration with the connection information. (Required)</td>
-        </tr>
-        <tr>
-          <td class="required">Server Id</td>
-          <td>The ID of the target server with the IP address. (Required)</td>
-        </tr>
-      </tbody>
-    </table>
-		</li>
-						
-		<br />
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/parameters/associate_floatingip.png" />
-		<br />
-
-		</ol>   
-						
-		<h3>Output</h3>
-						
-		<p>After the job runs, you can view the results on the Job Details page in ElectricFlow.</p>
-				
-		<p>In the <b>AssociateFloatingIP</b> step, click the Log button to see the diagnostic information.</p>	
-
-    </div>
-		
-		<div id="AttachVolume"><a name="AttachVolume" id="AttachVolume"></a>
-
-    <h2>AttachVolume</h2>
-
-    <p>This procedure attaches volumes that are created with the volume API to server instances. You can attach a volume
-    to one instance.</p>
-    <p>The plugin stores properties on the Commander server at the location specified the <b>Results Location</b> and <b>Results tag</b>
-		fields. The default location in the job directory called /myJob/Openstack/deployed/<i>Provision tag</i> if the <b>Results Location</b> 
-		is empty.</p>
-		
-		<h3>Input</h3>
-
-			<ol>
-			<li>Go to the AttachVolume procedure.</li>
-			<li>Enter the following parameters:<br />
-      <table class="grid">
-              <thead>
-                  <tr>
-                      <th>Parameter</th>
-                      <th>Description</th>
-                  </tr>
-              </thead>
-              <tbody>
-                  <tr>
-                      <td class="required">Configuration</td>
-                      <td>The name of a valid existing configuration with the connection information. (Required)</td>
-                  </tr>
-                  <tr>
-                      <td class="required">Server ID</td>
-                      <td>ID of the server to which the volume is attached. (Required)</td>
-                  </tr>
-                  <tr>
-                      <td class="required">Volume ID</td>
-                      <td>ID of the volume to attach. (Required)</td>
-                  </tr>
-                  <tr>
-                      <td>Name of device</td>
-                      <td>Name of the device, such as <i>/dev/vdb</i>, set after the volume is attached to a server. If you do not
-											specify a name, OpenStack automatically assigns the device a name.</td>
-                  </tr>
-                  <tr>
-                      <td>Results Location</td>
-                      <td>The location on the ElectricFlow server where the properties are stored. The default is <i>/myJob/OpenStack/deployed</i>.</td>
-                  </tr>
-                  <tr>
-                      <td class="required">Results tag</td>
-                      <td>The unique tag for this provision to separate it from other deployments stored in the same location. The default is <i>$[jobStepId]</i>. (Required)</td>
-                  </tr>
-              </tbody>
-          </table>
-		</li>
-						
-		<br />
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/parameters/attach_volume.png" />
-		<br />
-
-		</ol>   
-						
-		<h3>Output</h3>
-						
-		<p>After the job runs, you can view the results on the Job Details page in ElectricCommander.</p>
-				
-		<p>In the <b>AttachVolume</b> step, click the Log button to see the diagnostic information.</p>	
-					
-		</div>
-		
-		<div id="Cleanup"><a name="Cleanup" id="Cleanup"></a>
-
-    <h2>Cleanup</h2>
-
-    <p>This procedure deletes an existing OpenStack server instance that was created using the Deploy procedure.</p>
-		
-		<h3>Input</h3>
-		
-		<ol>
-			<li>Go to the Cleanup procedure.</li>
-			<li>Enter the following parameters:<br />
-      <table class="grid">
-      <thead>
-        <tr>
-          <th>Parameter</th>
-          <th>Description</th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td class="required">Configuration</td>
-          <td>The name of a valid existing configuration with the connection information. (Required)</td>
-        </tr>
-        <tr>
-          <td class="required">Server ID(s)</td>
-          <td>The IDs of one ore more servers to delete. Use a comma-separated list for more than one server. (Required)</td>
-        </tr>
-        <tr>
-          <td>Resource name(s)</td>
-          <td>The name of the resources to delete. Use a comma-separated list for more than one resource.</td>
-        </tr>
-      </tbody>
-    </table>
-		</li>
-						
-		<br />
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/parameters/cleanup_panel.png" />
-		<br />
-
-		</ol>   
-						
-		<h3>Output</h3>
-						
-		<p>After the job runs, you can view the results on the Job Details page in ElectricFlow.</p>
-				
-		<p>In the <b>Cleanup</b> step, click the Log button to see the diagnostic information.</p>	
-
-    </div>
-		
-		<div id="CloudManagerGrow"><a name="CloudManagerGrow" id="CloudManagerGrow"></a>
-
-    <h2>CloudManagerGrow</h2>
-
-    <p>This procedure allows the plugin to work with the CloudManager plugin. It calls the Deploy procedure and is run by the 
-		CloudManager.</p>
-		
-		<h3>Input</h3>
-		
-		<ol>
-			<li>Go to the CloudManagerGrow procedure.</li>
-			<li>Enter the following parameters:<br />
-      <table class="grid">
-      <thead>
-        <tr>
-          <th>Parameter</th>
-          <th>Description</th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td class="required">Configuration</td>
-           <td>The name of a valid existing configuration with the connection information. (Required)</td>
-        </tr>
-        <tr>
-          <td class="required">Tenant ID</td>
-          <td>The ID of the tenant to use. (Required)</td>
-        </tr>
-        <tr>
-          <td class="required">Number of Servers</td>
-          <td>The number of servers to deploy. If there are more than one, a suffix (_#) is added to server names. The default is 1.
-          (Required)</td>
-        </tr>
-        <tr>
-          <td class="required">Server name</td>
-          <td>Name of the new server. (Required)</td>
-        </tr>
-        <tr>
-          <td class="required">Image ID</td>
-          <td>The ID of an existing image in Openstack. (Required)</td>
-        </tr>
-        <tr>
-          <td class="required">Flavor ID</td>
-          <td>The ID for the flavor to use. (Required)</td>
-        </tr>
-        <tr>
-            <td class="required">Results tag</td>
-            <td>The unique tag for this provision to separate it from other deployments stored in the same location. 
-						The default is <i>$[jobStepId]</i>. (Required)</td>
-				</tr>	
-        <tr>
-          <td class="required">Resource Pool(s)</td>
-          <td>The names of resource pools in ElectricFlow that will be asssociated with the machines in this configuration 
-					if resources are created. For more than one resource pool, specify the names in a space-separated list. (Required)</td>
-        </tr>
-        <tr>
-          <td>Resource workspace</td>
-          <td>The ElectricFlow workspace that the resource uses.</td>
-        </tr>
-      </tbody>
-    </table>
-		</li>
-						
-		<br />
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/parameters/cloudmanager_grow_panel.png" />
-		<br />
-
-		</ol>   
-						
-		<h3>Output</h3>
-						
-		<p>After the job runs, you can view the results on the Job Details page in ElectricFlow.</p>
-				
-		<p>In the <b>CloudManagerGrow</b> step, click the Log button to see the diagnostic information.</p>	
-			
-		</div>
-
-    <div id="CloudManagerShrink"><a name="CloudManagerShrink" id="CloudManagerShrink"></a>
-
-    <h2>CloudManagerShrink</h2>
-
-    <p>This procedure allows the plugin to work with the CloudManager plugin. It calls the Cleanup procedure and is run by 
-		the CloudManager.</p>
-		
-		<h3>Input</h3>
-		
-		<ol>
-			<li>Go to the CloudManagerShrink procedure.</li>
-			<li>Enter the following parameters:<br />
-      <table class="grid">
-      <thead>
-        <tr>
-          <th>Parameter</th>
-          <th>Description</th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td class="required">Configuration</td>
-          <td>The name of a valid existing configuration with the connection information. (Required)</td>
-        </tr>
-        <tr>
-          <td class="required">List of Deployments</td>
-          <td>A list of deployments that were previously created by the CloudManagerGrow procedure to stop. (Required)</td>
-        </tr>
-      </tbody>
-    </table>
-		</li>
-						
-		<br />
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/parameters/cloudmanager_shrink_panel.png" />
-		<br />
-
-		</ol>   
-						
-		<h3>Output</h3>
-						
-		<p>After the job runs, you can view the results on the Job Details page in ElectricFlow.</p>
-				
-		<p>In the <b>CloudManagerShrink</b> step, click the Log button to see the diagnostic information.</p>	
-
-   	</div>
-
-    <div id="CloudManagerSync"><a name="CloudManagerSync" id="CloudManagerSync"></a>
-
-    <h2>CloudManagerSync</h2>
-
-    <p>This procedure allows the plugin to work with CloudManager plugin. It verifies that the instances it has recorded as <i>alive</i>
-    are still alive. It is run by the CloudManager.</p>
-		
-		<h3>Input</h3>
-		
-		<ol>
-			<li>Go to the CloudManagerSync procedure.</li>
-			<li>Enter the following parameters:<br />
-       <table class="grid">
-      <thead>
-        <tr>
-          <th>Parameter</th>
-          <th>Description</th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td class="required">Configuration</td>
-           <td>The name of a valid existing configuration with the connection information. (Required)</td>
-        </tr>
-        <tr>
-          <td class="required">List of Deployments</td>
-          <td>A list of deployments that were previously created by the CloudManagerGrow procedure to verify. (Required)</td>
-        </tr>
-      </tbody>
-    </table>
-		</li>
-						
-		<br />
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/parameters/cloudmanager_sync_panel.png" />
-		<br />
-
-		</ol>   
-						
-		<h3>Output</h3>
-						
-		<p>After the job runs, you can view the results on the Job Details page in ElectricFlow.</p>
-				
-		<p>In the <b>CloudManagerSync</b> step, click the Log button to see the diagnostic information.</p>	
-
-		</div>
-
-		<div id="CreateImage"><a name="CreateImage" id="CreateImage"></a>
-
-     <h2>CreateImage</h2>
-
-     <p>This procedure creates a virtual machine (VM) image. You can launch new instances from these images.</p>
-     <p>The plugin stores properties on the ElectricFlow server at the location specified in the <b>Results Location</b> and
-			<b>Results tag</b> fields. The default location in the job directory called /myJob/Openstack/deployed/<i>Provision tag</i>
-			if the <b>Results Location</b> field is empty.</p>
-					
-			<h3>Input</h3>
-		
-		<ol>
-			<li>Go to the CreateImage procedure.</li>
-			<li>Enter the following parameters:<br />
-           <table class="grid">
-              <thead>
-                  <tr>
-                      <th>Parameter</th>
-                      <th>Description</th>
-                  </tr>
-              </thead>
-              <tbody>
-                  <tr>
-                      <td class="required">Configuration</td>
-                      <td>The name of a valid existing configuration with the connection information. (Required)</td>
-                  </tr>
-                  <tr>
-                      <td class="required">Image name</td>
-                      <td>Display name of the new image. (Required)</td>
-                  </tr>
-                  <tr>
-                      <td class="required">Disk format</td>
-                      <td>The disk format of a VM image. Valid values are AKI,AMI,ARI,Raw,iso, vhd, vdi, qcow2,and vmdk. (Required)</td>
-                  </tr>
-                  <tr>
-                      <td class="required">Container format</td>
-                      <td>The container format for the new image. Valid values are aki, ari, ami, bare, and ovf. (Required)</td>
-                  </tr>
-                  <tr>
-                      <td class="required">Is image location a local file ?</td>
-                      <td>Select this parameter in the check box if the source image file is on the local machine. (Required)</td>
-                  </tr>
-                  <tr>
-                      <td class="required">Image path</td>
-                      <td>Path to the image on the local machine or a valid and direct URL to image location. (Required)</td>
-                  </tr>
-                  <tr>
-                      <td>Size</td>
-                      <td>Size of the raw image file from which the new image is generated.</td>
-                  </tr>
-                  <tr>
-                      <td>Checksum</td>
-                      <td>The checksum of the raw image file.</td>
-                  </tr>
-                  <tr>
-                      <td>Min-Ram</td>
-                      <td>The minimum RAM in megabytes (MBs) required to run this image on a server.</td>
-                  </tr>
-                  <tr>
-                      <td>Min-Disk</td>
-                      <td>The minimum disk space in gigabytes (GBs) required to run this image on a server.</td>
-                  </tr>
-                  <tr>
-                      <td>Owner</td>
-                      <td>The ID of the owner (tenant) of the image.</td>
-                  </tr>
-                  <tr>
-                      <td>Results Location</td>
-                     <td>The location on the ElectricFlow server where the properties are stored. The default is <i>/myJob/OpenStack/deployed</i>.</td>
-                  </tr>
-                  <tr>
-                      <td class="required">Results tag</td>
-                      <td>The unique tag for this provision to separate it from other deployments stored in the same location. The default is <i>$[jobStepId]</i>. (Required)</td>
-                  </tr>
-              </tbody>
-          </table>
-    		</li>
-						
-		<br />
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/parameters/create_image.png" />
-		<br />
-
-		</ol>   
-						
-		<h3>Output</h3>
-						
-		<p>After the job runs, you can view the results on the Job Details page in ElectricFlow.</p>
-				
-		<p>In the <b>CreateImage</b> step, click the Log button to see the diagnostic information.</p>	
-						
-		</div>
-		
-		<div id="CreateInstanceSnapshot"><a name="CreateInstanceSnapshot" id="CreateInstanceSnapshot"></a>
-
-      <h2>CreateInstanceSnapshot</h2>
-
-      <p>This procedure creates a snapshot from the instance. You can launch an instance from a snapshot.</p>
-      <p>The plugin stores properties on the ElectricFlow server at the location specified in the <b>Results Location</b> and 
-			<b>Results tag</b> fields. The default location in the job directory called /myJob/Openstack/deployed/<i>Provision tag</i> 
-			if the <b>Results Location</b> field is empty.</p>
-			
-			<h3>Input</h3>
-		
-		<ol>
-			<li>Go to the CreateImage procedure.</li>
-			<li>Enter the following parameters:<br />
-            <table class="grid">
-              <thead>
-                  <tr>
-                      <th>Parameter</th>
-                      <th>Description</th>
-                  </tr>
-              </thead>
-              <tbody>
-                  <tr>
-                      <td class="required">Configuration</td>
-                      <td>The name of a valid existing configuration with the connection information. (Required)</td>
-                  </tr>
-                  <tr>
-                      <td class="required">Instance snapshot name</td>
-                      <td>The display name of the snapshot. (Required)</td>
-                  </tr>
-
-                  <tr>
-                      <td class="required">Server ID</td>
-                      <td>The ID of the server instance for which a snapshot is created. (Required)</td>
-                  </tr>
-
-                  <tr>
-                      <td>Metadata</td>
-
-                      <td>Metadata for the snapshot in this format: key1,value1,key2,value2 ... </td>
-                  </tr>
-									<tr>
-                      <td>Results Location</td>
-                      <td>The location on the ElectricFlow server where the properties are stored. The default is 
-											<i>/myJob/OpenStack/deployed</i>.</td>
-                  </tr>
-                  <tr>
-                      <td class="required">Results tag</td>
-                      <td>The unique tag for this provision to separate it from other deployments stored in the same location. The 
-											default is <i>$[jobStepId]</i>. (Required)</td>
-                  </tr>
-              </tbody>
-          </table>
-    		</li>
-						
-		<br />
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/parameters/create_image.png" />
-		<br />
-
-		</ol>   
-						
-		<h3>Output</h3>
-						
-		<p>After the job runs, you can view the results on the Job Details page in ElectricFlow.</p>
-				
-		<p>In the <b>CreateImage</b> step, click the Log button to see the diagnostic information.</p>	
-
-         
-					
-					<img alt="" src="../../plugins/@PLUGIN_KEY@/images/parameters/create_instance_snapshot.png" />
-					
-					</div>
-		
-		<div id="CreateKeyPair"><a name="CreateKeyPair" id="CreateKeyPair"></a>
-
-    <h2>CreateKeyPair</h2>
-
-    <p>This procedure creates a new OpenStack key pair. The public key is stored by OpenStack and the private key is returned to you. 
-		If a key with the specified name already exists, OpenStack returns an error.</p>
-    <p>The plugin store properties on the ElectricFlow server at the location in the <b>Results Location</b> and the <b>Results tag</b> fields.
-		The default location is the job directory called /myJob/Openstack/deployed/<i>Provision tag value</i> if <b>Results Location</b> field is 
-		empty.</p>
-		
-		<h3>Input</h3>
-		
-		<ol>
-			<li>Go to the CreateKeyPair procedure.</li>
-			<li>Enter the following parameters:<br />
-     <table class="grid">
-      <thead>
-        <tr>
-          <th>Parameter</th>
-          <th>Description</th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td class="required">Configuration</td>
-          <td>The name of a valid existing configuration wtih the connection information. (Required)</td>
-        </tr>
-        <tr>
-          <td class="required">Key name</td>
-          <td>A unique name for the key pair. The default is <i>cmdr-$[jobStepId]</i>. (Required)</td>
-        </tr>
-        <tr>
-          <td>Results Location</td>
-          <td>The location on the ElectricFlow server where the properties are stored. The default is <i>/myJob/OpenStack/deployed</i>.</td>
-        </tr>
-        <tr>
-          <td class="required">Results tag</td>
-          <td>The unique tag for this provision to separate it from other deployments stored in the same location. The default is <i>$[jobStepId]</i>. (Required)</td>
-        </tr>
-      </tbody>
-    </table>
-		</li>
-						
-		<br />
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/parameters/create_key_panel.png" />
-		<br />
-
-		</ol>   
-						
-		<h3>Output</h3>
-						
-		<p>After the job runs, you can view the results on the Job Details page in ElectricFlow.</p>
-				
-		<p>In the <b>CreateKeyPair</b> step, click the Log button to see the diagnostic information.</p>	
-
-   	</div>
-		
-		<div id="CreateStack"><a name="CreateStack" id="CreateStack"></a>
-
-       <h2>CreateStack</h2>
-
-       <p>Heat is an OpenStack service to orchestrate multiple composite cloud applications using templates. 
-			 This procedure creates a new HEAT stack from a specified HEAT template. You can enter the template (in JSON or YAML format)in the
-			 <b>Template</b> field or the URL of the template.</p>
-			 <p>The plugin stores properties on the ElectricFlow server at the location specified in the <b>Results Location</b> and 
-			 <b>Results tag</b> fields. The default location in the job directory called /myJob/Openstack/deployed/<i>Provision tag</i>
-			 if the <b>Results Location</b> field is empty.</p>
-							
-				<h3>Input</h3>
-		
-		  <ol>
-			<li>Go to the CreateStack procedure.</li>
-			<li>Enter the following parameters:<br />
-      <table class="grid">
-                  <thead>
-                      <tr>
-                          <th>Parameter</th>
-                          <th>Description</th>
-                      </tr>
-                  </thead>
-                  <tbody>
-                      <tr>
-                          <td class="required">Configuration</td>
-                           <td>The name of a valid existing configuration with the connection information. (Required)</td>
-                      </tr>
-                      <tr>
-                          <td class="required">Stack Name</td>
-                          <td>The display name for the new stack. (Required)</td>
-                      </tr>
-                      <tr>
-                          <td>Template</td>
-                          <td>The stack template to instantiate a HEAT stack in JSON or YAML format.</td>
-                      </tr>
-                      <tr>
-                          <td>Template URL</td>
-                          <td>A URI to the location containing the updated stack template to instantiate. You specify this parameter 
-													only if you are not entering the template in the <b>Template</b> field.</td>
-                      </tr>
-                     <tr>
-                      <td>Results Location</td>
-                      <td>The location on the ElectricFlow server where the properties are stored. The default is 
-											<i>/myJob/OpenStack/deployed</i>.</td>
-                  </tr>
-                  <tr>
-                      <td class="required">Results tag</td>
-                      <td>The unique tag for this provision to separate it from other deployments stored in the same location. The 
-											default is <i>$[jobStepId]</i>. (Required)</td>
-									</tr>	
-                  </tbody>
-              </table>
-		</li>
-						
-		<br />
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/parameters/create_stack.png" />
-		<br />
-
-		</ol>   
-						
-		<h3>Output</h3>
-						
-		<p>After the job runs, you can view the results on the Job Details page in ElectricFlow.</p>
-				
-		<p>In the <b>CreateStack</b> step, click the Log button to see the diagnostic information.</p>	
-
-    </div>
-		
-		<div id="CreateVolume"><a name="CreateVolume" id="CreateVolume"></a>
-
-   <h2>CreateVolume</h2>
-
-       <p>This procedure creates a new OpenStack volume. A volume is a detachable block storage device. You can attach a volume
-			  to one instance at a time.</p>
-       <p>The plugin stores properties on the ElectricFlow server in the location in the <b>Results Location</b> and <b>Results tag</b> fields.
-			 The default location in the job directory called /myJob/Openstack/deployed/<i>Provision tag</i> if the <b>Results location</b>
-			 is empty.</p>
-			 
-			<h3>Input</h3>
-			 
-			<ol>
-			<li>Go to the CreateVolume procedure.</li>
-			<li>Enter the following parameters:<br />
-      <table class="grid">
-              <thead>
-                  <tr>
-                      <th>Parameter</th>
-                      <th>Description</th>
-                  </tr>
-              </thead>
-              <tbody>
-                  <tr>
-                      <td class="required">Configuration</td>
-                      <td>The name of a valid existing configuration with the connection information. (Required)</td>
-                  </tr>
-                  <tr>
-                      <td class="required">Volume name</td>
-                      <td>The name for the new volume that appears in the UI. (Required)</td>
-                  </tr>
-                  <tr>
-                      <td class="required">Size (in gigabytes [GBs])</td>
-                      <td>Size of the  volume in GB. (Required)</td>
-                  </tr>
-                  <tr>
-                      <td class="required">Type of volume</td>
-                      <td>The volume type. (Required)</td>
-                  </tr>
-                  <tr>
-                      <td>Availability zone</td>
-                      <td>The availability zone where the new zone is created. </td>
-                  </tr>
-                  <tr>
-                      <td>Results Location</td>
-                      <td>The location on the ElectricFlow server where the properties are stored. The default is <i>/myJob/OpenStack/deployed</i>.</td>
-                  </tr>
-                  <tr>
-                      <td class="required">Results tag</td>
-                      <td>The unique tag for this provision to separate it from the other deployments stored in the same location. The 
-											default is <i>$[jobStepId]</i>. (Required)</td>
-                  </tr>
-              </tbody>
-          </table>
-		</li>
-						
-		<br />
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/parameters/create_volume.png" />
-		<br />
-
-		</ol>   
-						
-		<h3>Output</h3>
-						
-		<p>After the job runs, you can view the results on the Job Details page in ElectricFlow.</p>
-				
-		<p>In the <b>CreateVolume</b> step, click the Log button to see the diagnostic information.</p>	
-
-		</div>
-
-		<div id="CreateVolumeSnapshot"><a name="CreateVolumeSnapshot" id="CreateVolumeSnapshot"></a>
-
-          <h3>CreateVolumeSnapshot</h3>
-
-          <p>This procedure creates a snapshot of a volume, a point-in-time complete copy of the volume. 
-					You can create a volume from this snapshot.</p>
-          <p>The plugin stores properties on the ElectricFlow server at the location specified in the <b>Results Location</b> and 
-					<b>Results tag</b> fields. The default location in the job directory called /myJob/Openstack/deployed/<i>Provision tag</i>
-					if the <b>Results Location</b> field is empty.</p>
-					
-					<h3>Input</h3>
-			 
-			<ol>
-			<li>Go to the CreateVolumeSnapshot procedure.</li>
-			<li>Enter the following parameters:<br />
-      <table class="grid">
-              <thead>
-                  <tr>
-                      <th>Parameter</th>
-                      <th>Description</th>
-                  </tr>
-              </thead>
-              <tbody>
-                  <tr>
-                      <td class="required">Configuration</td>
-                      <td>The name of a valid existing configuration with the connection information. (Required)</td>
-                  </tr>
-                  <tr>
-                      <td class="required">Name of volume snapshot</td>
-                      <td>The display name of the snapshot. (Required)</td>
-                  </tr>
-                  <tr>
-                      <td>Description</td>
-                      <td>The description of the snapshot.</td>
-                  </tr>
-                  <tr>
-                      <td>Create a snapshot forecefully?</td>
-                      <td>Select this parameter (in the check box) to forcefully create a snapshot of a volume even if it is 
-											attached to an instance. Selecting this parameter sets it to <i>true</i>. <br />
-											The default is <i>false</i>; the parameter is not selected.</td>
-									</tr>
-                  <tr>
-                      <td class="required">Volume ID</td>
-                      <td>The ID of the volume from which to create a snapshot. (Required)</td>
-                  </tr>
-                 <tr>
-                      <td>Results Location</td>
-                      <td>The location on the ElectricFlow server where the properties are stored. The default is 
-											<i>/myJob/OpenStack/deployed</i>.</td>
-                  </tr>
-                  <tr>
-                      <td class="required">Results tag</td>
-                      <td>The unique tag for this provision to separate it from other deployments stored in the same location. The 
-											default is <i>$[jobStepId]</i>. (Required)</td>
-									</tr>	
-              </tbody>
-          </table>
-		</li>
-						
-		<br />
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/parameters/create_volume_snapshot.png" />
-		<br />
-
-		</ol>   
-						
-		<h3>Output</h3>
-						
-		<p>After the job runs, you can view the results on the Job Details page in ElectricFlow.</p>
-				
-		<p>In the <b>CreateVolumeSnapshot</b> step, click the Log button to see the diagnostic information.</p>	
-					
-		</div>
-		
-		<div id="DeleteKeyPair"><a name="DeleteKeyPair" id="DeleteKeyPair"></a>
-
-    <h2>DeleteKeyPair</h2>
-
-    <p>This procedure deletes an existing OpenStack key pair. The public key is removed from OpenStack. You must own the key pair.</p>
-		
-		<h3>Input</h3>
-		
-		<ol>
-			<li>Go to the DeleteKeyPair procedure.</li>
-			<li>Enter the following parameters:<br />
-       <table class="grid">
-      <thead>
-        <tr>
-          <th>Parameter</th>
-          <th>Description</th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td class="required">Configuration</td>
-          <td>The name of a valid existing configuration with the connection information. (Required)</td>
-        </tr>
-        <tr>
-          <td class="required">Key name</td>
-          <td>Name of the key pair to delete. (Required)</td>
-        </tr>
-      </tbody>
-    </table>
-		</li>
-						
-		<br />
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/parameters/delete_key_panel.png" />
-		<br />
-
-		</ol>   
-						
-		<h3>Output</h3>
-						
-		<p>After the job runs, you can view the results on the Job Details page in ElectricFlow.</p>
-				
-		<p>In the <b>DeleteKeyPair</b> step, click the Log button to see the diagnostic information.</p>	
-
-    </div>
-		
-		<div id="DeleteStack"><a name="DeleteStack" id="DeleteStack"></a>
-
-          <h2>DeleteStack</h2>
-
-              <p>This procedure deletes an existing stack.</p>
-              <p>The plugin stores properties on the ElectricFlow server at the location specified in the <b>Results Location</b> and
-							<b>Results tag</b> fields. The default location in the job directory called /myJob/Openstack/deployed/<i>Provision tag</i>
-							if the <b>Results Location</b> field is empty.</p>
-							
-							<h3>Input</h3>
-		
-		<ol>
-			<li>Go to the DeleteStack procedure.</li>
-			<li>Enter the following parameters:<br />
-       <table class="grid">
-                  <thead>
-                      <tr>
-                          <th>Parameter</th>
-                          <th>Description</th>
-                      </tr>
-                  </thead>
-                  <tbody>
-                      <tr>
-                          <td class="required">Configuration</td>
-                           <td>The name of a valid existing configuration with the connection information. (Required)</td>
-                      </tr>
-                      <tr>
-                          <td class="required">Stack Name</td>
-                          <td>The display name of the stack to delete. (Required)</td>
-                      </tr>
-                      <tr>
-                          <td class="required">Stack ID</td>
-                          <td>The ID of the stack to delete. (Required)</td>
-                      </tr>
-                     <tr>
-                          <td>Results Location</td>
-                          <td>The location on the ElectricFlow server where the properties are stored. The default is 
-											    <i>/myJob/OpenStack/deployed</i>.</td>
-                  </tr>
-                  <tr>
-                          <td class="required">Results tag</td>
-                          <td>The unique tag for this provision to separate it from other deployments stored in the same location. The 
-											    default is <i>$[jobStepId]</i>. (Required)</td>
-									</tr>	
-                  </tbody>
-              </table>
-		</li>
-						
-		<br />
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/parameters/delete_stack.png" />
-		<br />
-
-		</ol>   
-						
-		<h3>Output</h3>
-						
-		<p>After the job runs, you can view the results on the Job Details page in ElectricFlow.</p>
-				
-		<p>In the <b>DeleteStack</b> step, click the Log button to see the diagnostic information.</p>	
-
-		</div>
-		
-		<div id="DeleteVolume"><a name="DeleteVolume" id="DeleteVolume"></a>
-
-    <h2>DeleteVolume</h2>
-
-   <p>This procedure deletes a volume. A volume is a detachable block storage device.</p>
-   <p>The plugin stores properties on the ElectricFlow server at the location specified in the <b>Results Location</b> and
-	 <b>Results tag</b> fields. The default location is the the job directory called /myJob/Openstack/deployed/<i>Provision tag</i>
-	 fields if the <b>Results Location</b> is empty.</p>
-
-		<h3>Input</h3>
-		
-		<ol>
-			<li>Go to the DeleteVolume procedure.</li>
-			<li>Enter the following parameters:<br />
-      <table class="grid">
-              <thead>
-                  <tr>
-                      <th>Parameter</th>
-                      <th>Description</th>
-                  </tr>
-              </thead>
-              <tbody>
-                  <tr>
-                      <td class="required">Configuration</td>
-                      <td>The name of a valid existing configuration with the connection information. (Required)</td>
-                  </tr>
-                  <tr>
-                      <td class="required">Volume ID</td>
-                      <td>ID of the volume to delete. (Required)</td>
-                  </tr>
-              </tbody>
-          </table>
-		</li>
-						
-		<br />
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/parameters/delete_volume.png" />
-		<br />
-
-		</ol>   
-						
-		<h3>Output</h3>
-						
-		<p>After the job runs, you can view the results on the Job Details page in ElectricFlow.</p>
-				
-		<p>In the <b>DeleteVolume</b> step, click the Log button to see the diagnostic information.</p>	
-					
-    </div>
-    
-    <div id="Deploy"><a name="Deploy" id="Deploy"></a>
-
-    <h2>Deploy</h2>
-
-    <p>This procedure calls the CreateKey procedure and deploys one or more new instances. It store properties on the ElectricFlow 
-		server at the location specified in the <b>Results Location</b> and the <b>Results tag</b> fields. The default location is in the 
-		directory for the job deployment results (/myJob/Openstack/deployed/<i>Results tag value</i>) if the <b>Results Location</b> field 
-		is empty.</p>
-		
-		<h3>Input</h3>
-		
-		<ol>
-			<li>Go to the Deploy procedure.</li>
-			<li>Enter the following parameters:<br />
-     <table class="grid">
-      <thead>
-        <tr>
-          <th>Parameter</th>
-          <th>Description</th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td class="required">Configuration</td>
-          <td>The name of a valid existing configuration with the connection information. (Required)</td>
-        </tr>
-        <tr>
-          <td class="required">Key Pair Name</td>
-          <td>Name of an existing key pair. (Required)</td>
-        </tr>
-        <tr>
-          <td class="required">Number of Servers</td>
-          <td>Number of servers to deploy. If there are more than one, a suffix (_#) is added to the server names. The default is 1.
-          (Required)</td>
-        </tr>
-        <tr>
-          <td class="required">Server name</td>
-          <td>Name of the new server. (Required)</td>
-        </tr>
-        <tr>
-          <td class="required">Image ID</td>
-          <td>ID of an existing image in OpenStack. (Required)</td>
-        </tr>
-        <tr>
-          <td class="required">Flavor ID</td>
-          <td>ID of the flavor to use. (Required)</td>
-        </tr>
-				 <tr>
-          <td>Security Group(s)</td>
-          <td>One or more security groups in a newline delimited list.</td>
-        </tr>
-        <tr>
-           <td>Availability Zone</td>
-           <td>The availability zone in which to launch the server.</td>
-          </tr>
-          <tr>
-              <td>Customization Script</td>
-              <td>Configuration information or scripts to execute when the server is launched.</td>
-          </tr>
-          <tr>
-          <td>Results Location</td>
-          <td>The location on the ElectricFlow server where the properties are stored. The default is <i>/myJob/OpenStack/deployed</i>.</td>
-        </tr>
-        <tr>
-          <td class="required">Results tag</td>
-          <td>The unique tag for this provision to keep it separate from the other deployments stored in the same location. The default is <i>$[jobStepId]</i>. (Required)</td>
-        </tr>
-        <tr>
-          <td>Create Resource?</td>
-          <td>Select this parameter (in the check box) to create resources for deployed servers.</td>
-        </tr>
-        <tr>
-          <td>Associate IP?</td>
-          <td>Select this parameter in the check box to associate the IP address with the deployed instance.</td>
-        </tr>
-        <tr>
-          <td>Resource Pool</td>
-          <td>Name of the resource pool in ElectricFlow that is associated with the machines in this configuration when resources are created.</td>
-        </tr>
-        <tr>
-            <td>Resource Port</td>
-            <td>Port that will be used when creating a resource.</td>
-        </tr>
-        <tr>
-          <td>Resource workspace</td>
-          <td>The ElectricFlow workspace that the resources uses.</td>
-        </tr>
-        <tr>
-            <td>Resource Zone Name</td>
-            <td>The ElectricFlow zone name for a resource. Used when creating a resource.</td>
-        </tr>
-        </tbody>
-    </table>
-		</li>
-						
-		<br />
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/parameters/deploy_panel.png" />
-		<br />
-
-		</ol>   
-						
-		<h3>Output</h3>
-						
-		<p>After the job runs, you can view the results on the Job Details page in ElectricFlow.</p>
-				
-		<p>In the <b>Deploy</b> step, click the Log button to see the diagnostic information.</p>	
-
-    </div>
-
-   <div id="DetachVolume"><a name="DetachVolume" id="DetachVolume"></a>
-
-   <h2>DetachVolume</h2>
-
-   <p>This procedure detaches a volume from a server. A volume is a detachable block storage device.</p>
-   <p>The plugin store properties on the ElectricFlow server at the location specified in the <b>Results Location</b> and <b>Results tag</b>
-	 fields. The default location is the job directory called /myJob/Openstack/deployed/<i>Provision tag</i> if the <b>Results Location</b> 
-	 field is empty.</p>
-					
-	 <h3>Input</h3>
-		
-		<ol>
-			<li>Go to the DetachVolume procedure.</li>
-			<li>Enter the following parameters:<br />
-          <table class="grid">
-              <thead>
-                  <tr>
-                      <th>Parameter</th>
-                      <th>Description</th>
-                  </tr>
-              </thead>
-              <tbody>
-                  <tr>
-                      <td class="required">Configuration</td>
-                      <td>The name of a valid existing configuration with the connection information. (Required)</td>
-                  </tr>
-                  <tr>
-                      <td class="required">Server ID</td>
-                      <td>ID of the server from which the volume is detached. (Required)</td>
-                  </tr>
-									 <tr>
-                      <td class="required">Volume ID</td>
-                      <td>ID of the volume to detach. (Required)</td>
-                  </tr>
-                  <tr>
-                      <td class="required">Attachment ID</td>
-    
-                  <td>ID of the volume attachment. (Required)</td>
-                  </tr>
-              </tbody>
-          </table>
-		</li>
-						
-		<br />
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/parameters/detach_volume.png" />
-		<br />
-
-		</ol>   
-						
-		<h3>Output</h3>
-						
-		<p>After the job runs, you can view the results on the Job Details page in ElectricFlow.</p>
-				
-		<p>In the <b>DetachVolume</b> step, click the Log button to see the diagnostic information.</p>
-					
-		</div>
-		
-    <div id="ExtendVolume"><a name="ExtendVolume" id="ExtendVolume"></a>
-
-    <h2>ExtendVolume</h2>
-
-    <p>This procedure extends the size of the specified volume. The volume must be in <i>available state</i> before the 
-		size is extended.</p>
-    <p>The plugin stores properties on the ElectricFlow server at the location specified in the <b>Results Location</b> and <b>Results tag</b>
-		fields. The default location in the job directory called /myJob/Openstack/deployed/<i>Provision tag</i> if the <b>Results Location</b>
-		field is empty.</p>
-					
-		<p><b>Note:</b> Make sure that the ExtendVolume procedure is supported by the Openstack services before using this step.</p>
-
-		<h3>Input</h3>
-		
-		<ol>
-			<li>Go to the ExtendVolume procedure.</li>
-			<li>Enter the following parameters:<br />
-      <table class="grid">
-              <thead>
-                  <tr>
-                      <th>Parameter</th>
-                      <th>Description</th>
-                  </tr>
-              </thead>
-              <tbody>
-                  <tr>
-                      <td class="required">Configuration</td>
-                      <td>The name of a valid existing configuration with the connection information. (Required)</td>
-                  </tr>
-                  <tr>
-                      <td class="required">Volume ID</td>
-                      <td>ID of the volume to extend. (Required)</td>
-                  </tr>
-                  <tr>
-                      <td class="required">New size</td>
-                      <td>New size of the volume. (Required)</td>
-                  </tr>
-                  <tr>
-                      <td>Results Location</td>
-                      <td>The location on the ElectricFlow server where the properties are stored. The default is 
-											<i>/myJob/OpenStack/deployed</i>.</td>
-                  </tr>
-                  <tr>
-                      <td class="required">Results tag</td>
-                      <td>The unique tag for this provision to separate it from other deployments stored in the same location. The 
-											default is <i>$[jobStepId]</i>. (Required)</td>
-                  </tr>
-              </tbody>
-          </table>
-		</li>
-						
-		<br />
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/parameters/extend_volume.png" />
-		<br />
-
-		</ol>   
-						
-		<h3>Output</h3>
-						
-		<p>After the job runs, you can view the results on the Job Details page in ElectricFlow.</p>
-				
-		<p>In the <b>ExtendVolume</b> step, click the Log button to see the diagnostic information.</p>	
-					
-		</div>
-		
-		<div id="RebootInstance"><a name="RebootInstance" id="RebootInstance"></a>
-
-      <h2>RebootInstance</h2>
-
-      <p>This procedure reboots a server instance.</p>
-      <p>The plugin stores properties on the ElectricFlow server at the location specified in the <b>Results Location</b> and 
-			<b>Results tag</b> fields. The default location in the job directory called /myJob/Openstack/deployed/<i>Provision tag</i> 
-			if the <b>Results Location</b> field is empty.</p>
-			
-			<h3>Input</h3>
-		
-		  <ol>
-			<li>Go to the RebootInstance procedure.</li>
-			<li>Enter the following parameters:<br />
-      <table class="grid">
-              <thead>
-                  <tr>
-                      <th>Parameter</th>
-                      <th>Description</th>
-                  </tr>
-              </thead>
-              <tbody>
-                  <tr>
-                      <td class="required">Configuration</td>
-                      <td>The name of a valid existing configuration with the connection information.  (Required)</td>
-                  </tr>
-                  <tr>
-                      <td class="required">Server ID</td>
-                      <td>ID of the server to reboot. (Required)</td>
-                  </tr>
-                  <tr>
-                      <td class="required">Reboot Type</td>
-                      <td>Type of the reboot action (<i>Hard</i> or <i>Soft</i>). (Required)</td>
-                  </tr>
-              </tbody>
-          </table>
-		</li>
-						
-		<br />
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/parameters/reboot.png" />
-		<br />
-
-		</ol>   
-						
-		<h3>Output</h3>
-						
-		<p>After the job runs, you can view the results on the Job Details page in ElectricFlow.</p>
-				
-		<p>In the <b>RebootInstance</b> step, click the Log button to see the diagnostic information.</p>	
-
-    </div>
-
-    <div id="ReleaseIP"><a name="ReleaseIP" id="ReleaseIP"></a>
-
-    <h2>ReleaseIP</h2>
-
-    <p>This procedure deletes an existing OpenStack floating IP address that is allocated to your account.</p>
-		
-		<h3>Input</h3>
-		
-		<ol>
-			<li>Go to the ReleaseIP procedure.</li>
-			<li>Enter the following parameters:<br />
-      <table class="grid">
-      <thead>
-        <tr>
-          <th>Parameter</th>
-          <th>Description</th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td class="required">Configuration</td>
-          <td>The name of a valid existing configuration with the connection information. (Required)</td>
-        </tr>
-        <tr>
-          <td class="required">Floating Address ID</td>
-          <td>ID of the floating IP address to delete. (Required)</td>
-        </tr>
-      </tbody>
-    </table>
-		</li>
-						
-		<br />
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/parameters/release_ip_panel.png" />
-		<br />
-
-		</ol>   
-						
-		<h3>Output</h3>
-						
-		<p>After the job runs, you can view the results on the Job Details page in ElectricFlow.</p>
-				
-		<p>In the <b>ReleaseIP</b> step, click the Log button to see the diagnostic information.</p>	
-    		
-		</div>
-		
-		   <div id="Teardown"><a name="Teardown" id="Teardown"></a>
-
-              <h2>Teardown</h2>
-
-              <p>This procedure deletes an existing OpenStack server.</p>
-              							
-							<h3>Input</h3>
-		
-		<ol>
-			<li>Go to the Teardown procedure.</li>
-			<li>Enter the following parameters:<br />
-      <table class="grid">
-                  <thead>
-                      <tr>
-                          <th>Parameter</th>
-                          <th>Description</th>
-                      </tr>
-                  </thead>
-                  <tbody>
-                      <tr>
-                          <td>Configuration</td>
-                           <td>The name of a valid existing configuration with the connection information.</td>
-                      </tr>
-                      <tr>
-                          <td class="required">Resource name(s)</td>
-                          <td>The names of the resources to delete. For more than one resource, use a comma-separated list. (Required)</td>
-                      </tr>
-                   </tbody>
-              </table>
-		</li>
-						
-		<br />
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/parameters/teardown_panel.png" />
-		<br />
-
-		</ol>   
-						
-		<h3>Output</h3>
-						
-		<p>After the job runs, you can view the results on the Job Details page in ElectricFlow.</p>
-				
-		<p>In the <b>Teardown</b> step, click the Log button to see the diagnostic information.</p>	
-
-		</div>
-
-   <div id="UpdateStack"><a name="UpdateStack" id="UpdateStack"></a>
-
-              <h2>UpdateStack</h2>
-
-              <p>This procedure updates an existing stack. You can enter the updated template (in JSON or YAML format)in the
-                  <b>Template</b> field or the URL of the template.</p>
-              <p>The plugin stores properties on the ElectricFlow server at the location specified in the <b>Results Location</b> and
-							<b>Results tag</b> fields. The default location in the job directory called /myJob/Openstack/deployed/<i>Provision tag</i>
-							if the <b>Results Location</b> field is empty.</p>
-							
-							<h3>Input</h3>
-		
-		<ol>
-			<li>Go to the UpdateStack procedure.</li>
-			<li>Enter the following parameters:<br />
-      <table class="grid">
-                  <thead>
-                      <tr>
-                          <th>Parameter</th>
-                          <th>Description</th>
-                      </tr>
-                  </thead>
-                  <tbody>
-                      <tr>
-                          <td class="required">Configuration</td>
-                           <td>The name of a valid existing configuration with the connection information. (Required)</td>
-                      </tr>
-                      <tr>
-                          <td class="required">Stack Name</td>
-                          <td>The display name of the stack to update. (Required)</td>
-                      </tr>
-                      <tr>
-                          <td class="required">Stack ID</td>
-                          <td>The ID of the stack to update. (Required)</td>
-                      </tr>
-                      <tr>
-                          <td>Template</td>
-                          <td>The template (in JSON or YAML format) with which to update the stack.</td>
-                      </tr>
-                      <tr>
-                          <td>Template URL</td>
-                          <td>A URI to the location containing the updated stack template to instantiate. You specify this parameter 
-													only if you are not entering the template in the <b>Template</b> field.</td>
-                      </tr>
-                      <tr>
-                         <td>Results Location</td>
-                         <td>The location on the ElectricFlow server where the properties are stored. The default is 
-											   <i>/myJob/OpenStack/deployed</i>.</td>
-                      </tr>
-                      <tr>
-                         <td class="required">Results tag</td>
-                         <td>The unique tag for this provision to separate it from other deployments stored in the same location. The 
-											   default is <i>$[jobStepId]</i>. (Required)</td>
-									   </tr>	
-                  </tbody>
-              </table>
-		</li>
-						
-		<br />
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/parameters/update_stack.png" />
-		<br />
-
-		</ol>   
-						
-		<h3>Output</h3>
-						
-		<p>After the job runs, you can view the results on the Job Details page in ElectricFlow.</p>
-				
-		<p>In the <b>UpdateStack</b> step, click the Log button to see the diagnostic information.</p>	
-
-		</div>
-
-          
-		
-    <h1>Use Cases and Examples</h1>
-    <!-- This section is for examples and use cases, including screenshots of the new Parameter Panel with example values filled in.
-Unfortunately, I can't tell you what exactly to put here, but it's OK to put what seems like too much! Include both parameter
-values and output where appropriate. Use a separate 'h2' header for each example. Under the h2 header try to stay with the style
-outline used above where possible.
--->
-
-    <h2 id="overview">Use Case: Deploy, Consume, and Cleanup a Job</h2>
-
-    <p>Deploy and cleanup work as a pair within a job.</p>
-
-    <p>The most common use for this plugin is to create a server, create ElectricFlow resources assigned to it, 
-		use the resources to run some operations, and then delete the resource and the server. To accomplish these tasks you must:</p>
-
-    <ol>
-      <li>Create a plugin configuration.</li>
-      <li>Deploy an OpenStack server.</li>
-      <li>Create resources for this deployment.</li>
-      <li>Use the resources.</li>
-      <li>Delete the resources.</li>
-      <li>Delete the deployed server.</li>
-    </ol>
-
-    <h4>Create a Plugin Configuration</h4>
-		
-		 <ol>
-		  <li>Go to <b>Administration</b> &gt; <b>Plugins</b> to open the Plugin Manager.</li>
-		  <li>Find the EC-OpenStack row.</li>
-		  <li>Click <b>Configure</b> to open the OpenStack Configurations page.</li> 	
-		  <li>Click <b>Create Configuration</b>.</li>
-		  <li>To create an OpenStack configuration, enter the following information and click <b>OK</b>. 
-      <br />
-      <img alt="" src="../../plugins/@PLUGIN_KEY@/images/use_cases/Case_1/create_config.png" />
-			</li>
-      <p>After the configuration is created, you can now see it in the <b>OpenStack Configurations</b> page.</p>.
-			</ol>
-
-    <h4>Deploy an OpenStack Server</h4>
-		
-		<ol>
-			<li>Go to the Deploy procedure.</li>
-			<li>Enter the following parameters:</li>
-      <img alt="" src="../../plugins/@PLUGIN_KEY@/images/use_cases/Case_1/deploy_parameters.png" />
-			
-		</ol>
-
-    <h4>Consume</h4>
-
-    <p>Create a new command step to use a resource that you created.</p>
-		<p>In this example, add a resource from a resource pool using the ec-perl sleep command for 30 seconds:</p>
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/use_cases/Case_1/consume_parameters.png" />
-
-    <h4>Clean Up</h4>
-
-    <p>Create a Cleanup step as follows:</p>
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/use_cases/Case_1/cleanup_parameters.png" />
-
-    <h4>Results and Output</h4>
-
-    <p>After the job runs, you can view the results in ElectricFlow:</p>
-		
-	  <img alt="" src="../../plugins/@PLUGIN_KEY@/images/use_cases/Case_1/job.png" />
-		<br />
-		
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/use_cases/Case_1/results.png" />
-
-    <p>Deploy output:</p>
-		<img alt="" src="../../plugins/@PLUGIN_KEY@/images/use_cases/Case_1/deploy_log.png" />
-
-    <p>Cleanup output:</p>
-    <img alt="" src="../../plugins/@PLUGIN_KEY@/images/use_cases/Case_1/cleanup_log.png" />
-
-
-    <h1 id="rns">Release Notes</h1>
-    <h2>@PLUGIN_KEY@ 1.3.5</h2>
-    <ul>
-        <li>The plugin icon has been updated.</li>
-    </ul>
-    <h2>@PLUGIN_KEY@ 1.3.4</h2>
-    <ul>
-        <li>Added Rackspace support for Dynamic Environments</li>
-        <li>Configured the plugin to allow the ElectricFlow UI to create configs inline of procedure form.</li>
-        <li>Configured the plugin to allow the ElectricFlow UI to render the plugin procedure parameters entirely using the configured form XMLs.</li>
-        <li>Enabled the plugin for managing the plugin configurations in-line when defining an application process step or a pipeline stage task.</li>
-    </ul>
-      <h2>@PLUGIN_KEY@ 1.3.3</h2>
-      <ul>
-          <li>Added region field for create volume procedure</li>
-      </ul>
-
-      <h2>@PLUGIN_KEY@ 1.3.2</h2>
-      <ul>
-          <li>Added resource port field to the Dynamic Environments feature</li>
-          <li>Added resource port field to the Deploy procedure</li>
-      </ul>
-
-      <h2>@PLUGIN_KEY@ 1.3.1</h2>
-    <ul>
-        <li>Fixed issue with configurations being cached for IE.</li>
-        <li>Added validation to the CreateConfiguration procedure for the dynamic environments feature.</li>
-        <li>Added the "Tenant ID" parameter to the plugin configuration.</li>
-        <li>Removed tenant_id from all procedures except CreateConfiguration.</li>
-        <li>Added the ability to dynamically retrieve drop-down options such as image or flavor when creating resource templates for dynamic environments.</li>
-        <li>Added the ability to create a resource in non-default zone.</li>
-	</ul>
-    <h2>@PLUGIN_KEY@ 1.2.1</h2>
-    <ul>
-      <li>Fixed the issue that occurs when a resource was not created after provisioning it and the "Duplicate resource name" error message appears.</li>
-      <li>The Workspace parameter was removed from procedure to create an OpenStack configuration.</li>
-    </ul>
-    <h2>@PLUGIN_KEY@ 1.2.0</h2>
-    <p>The following procedures were added:</p>
-    <ul>
-      <li>CreateVolume to create a new volume.</li>
-      <li>ExtendVolume to extend the size of a volume.</li>
-      <li>AttachVolume to attach the volume to a server instance.</li>
-      <li>DetachVolume to detach the volume from a server instance.</li>
-      <li>DeleteVolume to delete a volume from an OpenStack block storage.</li>
-      <li>CreateImage to create a virtual machine (VM) image on OpenStack Image Service Glance.</li>
-      <li>CreateInstanceSnapshot to create a snapshot of a server instance.</li>
-      <li>CreateVolumeSnapshot to create a snapshot of a volume.</li>
-      <li>CreateStack to create a HEAT stack from a HEAT template.</li>
-      <li>UpdateStack to update an existing stack with a template.</li>
-      <li>DeleteStack to delete an existing stack.</li>
-    </ul>
-    <p>The Deploy procedure was updated to add support for customization scripts, availability zones, security groups,
-			and deployments using an instance snapshot.</p>
-      
-			
-    <h2>@PLUGIN_KEY@ 1.1.2</h2>
-    <ul>
-      <li>Added properties in <i>ec_cloudprovisioning_plugin</i> property sheet for ElectricFlow Deploy.</li>
-    </ul>
-		
-  <h2>@PLUGIN_KEY@ 1.1.1</h2>
-  <ul>
-    <li>Added support for Keystone v3 authorization.</li>
-    <li>Decoupled key pairs in creation and deletion operations from the Deploy and Cleanup procedures.</li>
-    <li>Added the AssociateFloatingIP procedure to associate floating IP addresses to existing VMs.</li>
-    <li>Fixed the <b>Create Resource?</b> parameter in the Deploy procedure.</li>
-  </ul>
-	
-	<h2>@PLUGIN_KEY@ 1.0.0</h2>
-
-    <ul>
-      <li>Added the configuration management procedures.</li>
-      <li>Added the AllocateIP, Cleanup, CreateKeyPair, DeleteKeyPair, Deploy, and ReleaseIP procedures.</li>
-      <li>Implemented CloudManager support.</li>
-      <li>Implemented the XML parameter panel.</li>
-      <li>Added a Help link to each procedure.</li>
-      <li>Added the Help page.</li>
-      <li>Added use cases.</li>
-    </ul>
-		
-  </div>
-	
-</body>
-
+    <head>
+        <meta content="text/html; charset=us-ascii" http-equiv="content-type"/>
+        <title>@PLUGIN_KEY@</title>
+        <link rel="stylesheet" href="../../plugins/@PLUGIN_KEY@/pluginhelp.css" type="text/css" media="screen" />
+    </head>
+    <body>
+        <div class="help">
+            <h1>@PLUGIN_KEY@</h1>
+            <p>
+                Version @PLUGIN_VERSION@
+            </p>
+            <p>
+                Documentation for this plugin is now  available <a href="https://docs.cloudbees.com/docs/cloudbees-cd/latest/plugins/ec-openstack" target="_blank">here</a>.
+            </p>
+        </div>
+        </body>
 </html>
+
diff --git a/src/main/resources/META-INF/plugin.xml b/src/main/resources/META-INF/plugin.xml
index b4bd69e..359ec83 100644
--- a/src/main/resources/META-INF/plugin.xml
+++ b/src/main/resources/META-INF/plugin.xml
@@ -33,4 +33,7 @@
             <javascript>war/ecplugins.openstack.ConfigurationManagement/ecplugins.openstack.ConfigurationManagement.nocache.js</javascript>
         </component>
     </components>
+    <hasAdoc>true</hasAdoc>
+    <catalogLabel>OpenStack</catalogLabel>
+    <detailedDescription>OpenStack is an Infrastructure as a Service (IaaS) cloud computing project by Rackspace Cloud and NASA. It is free open-source software released under the terms of the Apache License. This plugin allows users to build a cloud by launching images and assigning metadata to instances, providing a more generic interface for managing resources.</detailedDescription>
 </plugin>
diff --git a/src/main/resources/project/ui_forms/allocate.ip.xml b/src/main/resources/project/ui_forms/allocate.ip.xml
index 2e82db8..4638bf6 100644
--- a/src/main/resources/project/ui_forms/allocate.ip.xml
+++ b/src/main/resources/project/ui_forms/allocate.ip.xml
@@ -16,7 +16,7 @@
 
 -->
 <editor>
-    <help>/commander/pages/@PLUGIN_NAME@/@PLUGIN_KEY@_help?s=Administration&amp;ss=Plugins#AllocateIP</help>
+    <help>https://docs.cloudbees.com/docs/cloudbees-cd/latest/plugins/ec-openstack#AllocateIP</help>
     <formElement>
         <label>Configuration:</label>
         <!-- Improvements for CEV-18687 -->
diff --git a/src/main/resources/project/ui_forms/associate_ip.xml b/src/main/resources/project/ui_forms/associate_ip.xml
index 74e89a8..9a6cb29 100644
--- a/src/main/resources/project/ui_forms/associate_ip.xml
+++ b/src/main/resources/project/ui_forms/associate_ip.xml
@@ -16,7 +16,7 @@
 
 -->
 <editor>
-    <help>/commander/pages/@PLUGIN_NAME@/@PLUGIN_KEY@_help?s=Administration&amp;ss=Plugins#AssociateFloatingIP</help>
+    <help>https://docs.cloudbees.com/docs/cloudbees-cd/latest/plugins/ec-openstack#AssociateFloatingIP</help>
     <formElement>
         <label>Configuration:</label>
         <!-- Improvements for CEV-18687 -->
diff --git a/src/main/resources/project/ui_forms/attach_volume.xml b/src/main/resources/project/ui_forms/attach_volume.xml
index dc61f1d..b6168df 100644
--- a/src/main/resources/project/ui_forms/attach_volume.xml
+++ b/src/main/resources/project/ui_forms/attach_volume.xml
@@ -16,7 +16,7 @@
 
 -->
 <editor>
-    <help>/commander/pages/@PLUGIN_NAME@/@PLUGIN_KEY@_help?s=Administration&amp;ss=Plugins#AttachVolume</help>
+    <help>https://docs.cloudbees.com/docs/cloudbees-cd/latest/plugins/ec-openstack#AttachVolume</help>
     <formElement>
         <label>Configuration:</label>
         <!-- Improvements for CEV-18687 -->
diff --git a/src/main/resources/project/ui_forms/cleanup.xml b/src/main/resources/project/ui_forms/cleanup.xml
index a04b073..8f48079 100644
--- a/src/main/resources/project/ui_forms/cleanup.xml
+++ b/src/main/resources/project/ui_forms/cleanup.xml
@@ -16,7 +16,7 @@
 
 -->
 <editor>
-    <help>/commander/pages/@PLUGIN_NAME@/@PLUGIN_KEY@_help?s=Administration&amp;ss=Plugins#Cleanup</help>
+    <help>https://docs.cloudbees.com/docs/cloudbees-cd/latest/plugins/ec-openstack#Cleanup</help>
     <formElement>
         <label>Configuration:</label>
         <!-- Improvements for CEV-18687 -->
diff --git a/src/main/resources/project/ui_forms/create.key.xml b/src/main/resources/project/ui_forms/create.key.xml
index d2d33fb..6eb2e72 100644
--- a/src/main/resources/project/ui_forms/create.key.xml
+++ b/src/main/resources/project/ui_forms/create.key.xml
@@ -16,7 +16,7 @@
 
 -->
 <editor>
-    <help>/commander/pages/@PLUGIN_NAME@/@PLUGIN_KEY@_help?s=Administration&amp;ss=Plugins#CreateKeyPair</help>
+    <help>https://docs.cloudbees.com/docs/cloudbees-cd/latest/plugins/ec-openstack#CreateKeyPair</help>
     <formElement>
         <label>Configuration:</label>
         <!-- Improvements for CEV-18687 -->
diff --git a/src/main/resources/project/ui_forms/create_image.xml b/src/main/resources/project/ui_forms/create_image.xml
index 6ab0b8d..231a081 100644
--- a/src/main/resources/project/ui_forms/create_image.xml
+++ b/src/main/resources/project/ui_forms/create_image.xml
@@ -16,7 +16,7 @@
 
 -->
 <editor>
-    <help>/commander/pages/@PLUGIN_NAME@/@PLUGIN_KEY@_help?s=Administration&amp;ss=Plugins#CreateVolume</help>
+    <help>https://docs.cloudbees.com/docs/cloudbees-cd/latest/plugins/ec-openstack#CreateVolume</help>
     <formElement>
         <label>Configuration:</label>
         <!-- Improvements for CEV-18687 -->
diff --git a/src/main/resources/project/ui_forms/create_instancesnapshot.xml b/src/main/resources/project/ui_forms/create_instancesnapshot.xml
index 98ca9d7..4f01507 100644
--- a/src/main/resources/project/ui_forms/create_instancesnapshot.xml
+++ b/src/main/resources/project/ui_forms/create_instancesnapshot.xml
@@ -16,7 +16,7 @@
 
 -->
 <editor>
-    <help>/commander/pages/@PLUGIN_NAME@/@PLUGIN_KEY@_help?s=Administration&amp;ss=Plugins#CreateInstanceSnapshot</help>
+    <help>https://docs.cloudbees.com/docs/cloudbees-cd/latest/plugins/ec-openstack#CreateInstanceSnapshot</help>
     <formElement>
         <label>Configuration:</label>
         <!-- Improvements for CEV-18687 -->
diff --git a/src/main/resources/project/ui_forms/create_stack.xml b/src/main/resources/project/ui_forms/create_stack.xml
index 28f8eee..0d31ccb 100644
--- a/src/main/resources/project/ui_forms/create_stack.xml
+++ b/src/main/resources/project/ui_forms/create_stack.xml
@@ -16,7 +16,7 @@
 
 -->
 <editor>
-    <help>/commander/pages/@PLUGIN_NAME@/@PLUGIN_KEY@_help?s=Administration&amp;ss=Plugins#CreateStack</help>
+    <help>https://docs.cloudbees.com/docs/cloudbees-cd/latest/plugins/ec-openstack#CreateStack</help>
     <formElement>
         <label>Configuration:</label>
         <!-- Improvements for CEV-18687 -->
diff --git a/src/main/resources/project/ui_forms/create_volume.xml b/src/main/resources/project/ui_forms/create_volume.xml
index 6c007b0..60ca877 100644
--- a/src/main/resources/project/ui_forms/create_volume.xml
+++ b/src/main/resources/project/ui_forms/create_volume.xml
@@ -16,7 +16,7 @@
 
 -->
 <editor>
-    <help>/commander/pages/@PLUGIN_NAME@/@PLUGIN_KEY@_help?s=Administration&amp;ss=Plugins#CreateVolume</help>
+    <help>https://docs.cloudbees.com/docs/cloudbees-cd/latest/plugins/ec-openstack#CreateVolume</help>
     <formElement>
         <label>Configuration:</label>
         <!-- Improvements for CEV-18687 -->
diff --git a/src/main/resources/project/ui_forms/create_volumesnapshot.xml b/src/main/resources/project/ui_forms/create_volumesnapshot.xml
index fd51f68..888c0a2 100644
--- a/src/main/resources/project/ui_forms/create_volumesnapshot.xml
+++ b/src/main/resources/project/ui_forms/create_volumesnapshot.xml
@@ -16,7 +16,7 @@
 
 -->
 <editor>
-    <help>/commander/pages/@PLUGIN_NAME@/@PLUGIN_KEY@_help?s=Administration&amp;ss=Plugins#CreateVolumeSnapshot</help>
+    <help>https://docs.cloudbees.com/docs/cloudbees-cd/latest/plugins/ec-openstack#CreateVolumeSnapshot</help>
     <formElement>
         <label>Configuration:</label>
         <!-- Improvements for CEV-18687 -->
diff --git a/src/main/resources/project/ui_forms/delete.key.xml b/src/main/resources/project/ui_forms/delete.key.xml
index 1291730..e490d81 100644
--- a/src/main/resources/project/ui_forms/delete.key.xml
+++ b/src/main/resources/project/ui_forms/delete.key.xml
@@ -16,7 +16,7 @@
 
 -->
 <editor>
-    <help>/commander/pages/@PLUGIN_NAME@/@PLUGIN_KEY@_help?s=Administration&amp;ss=Plugins#DeleteKeyPair</help>
+    <help>https://docs.cloudbees.com/docs/cloudbees-cd/latest/plugins/ec-openstack#DeleteKeyPair</help>
     <formElement>
         <label>Configuration:</label>
         <!-- Improvements for CEV-18687 -->
diff --git a/src/main/resources/project/ui_forms/delete_stack.xml b/src/main/resources/project/ui_forms/delete_stack.xml
index 943e540..04c0238 100644
--- a/src/main/resources/project/ui_forms/delete_stack.xml
+++ b/src/main/resources/project/ui_forms/delete_stack.xml
@@ -16,7 +16,7 @@
 
 -->
 <editor>
-    <help>/commander/pages/@PLUGIN_NAME@/@PLUGIN_KEY@_help?s=Administration&amp;ss=Plugins#DeleteStack</help>
+    <help>https://docs.cloudbees.com/docs/cloudbees-cd/latest/plugins/ec-openstack#DeleteStack</help>
     <formElement>
         <label>Configuration:</label>
         <!-- Improvements for CEV-18687 -->
diff --git a/src/main/resources/project/ui_forms/delete_volume.xml b/src/main/resources/project/ui_forms/delete_volume.xml
index 3077489..4b61145 100644
--- a/src/main/resources/project/ui_forms/delete_volume.xml
+++ b/src/main/resources/project/ui_forms/delete_volume.xml
@@ -16,7 +16,7 @@
 
 -->
 <editor>
-    <help>/commander/pages/@PLUGIN_NAME@/@PLUGIN_KEY@_help?s=Administration&amp;ss=Plugins#DeleteVolume</help>
+    <help>https://docs.cloudbees.com/docs/cloudbees-cd/latest/plugins/ec-openstack#DeleteVolume</help>
     <formElement>
         <label>Configuration:</label>
         <!-- Improvements for CEV-18687 -->
diff --git a/src/main/resources/project/ui_forms/deploy.xml b/src/main/resources/project/ui_forms/deploy.xml
index c0ed138..351af3e 100644
--- a/src/main/resources/project/ui_forms/deploy.xml
+++ b/src/main/resources/project/ui_forms/deploy.xml
@@ -16,7 +16,7 @@
 
 -->
 <editor>
-    <help>/commander/pages/@PLUGIN_NAME@/@PLUGIN_KEY@_help?s=Administration&amp;ss=Plugins#Deploy</help>
+    <help>https://docs.cloudbees.com/docs/cloudbees-cd/latest/plugins/ec-openstack#Deploy</help>
     <formElement>
         <label>Configuration:</label>
         <!-- Improvements for CEV-18687 -->
diff --git a/src/main/resources/project/ui_forms/deploy_DE.xml b/src/main/resources/project/ui_forms/deploy_DE.xml
index 2d8e627..d89797d 100644
--- a/src/main/resources/project/ui_forms/deploy_DE.xml
+++ b/src/main/resources/project/ui_forms/deploy_DE.xml
@@ -16,7 +16,7 @@
 
 -->
 <editor>
-    <help>/commander/pages/@PLUGIN_NAME@/@PLUGIN_KEY@_help?s=Administration&amp;ss=Plugins#_DeployDE</help>
+    <help>https://docs.cloudbees.com/docs/cloudbees-cd/latest/plugins/ec-openstack#_DeployDE</help>
     <formElement>
         <label>Configuration:</label>
         <!-- Improvements for CEV-18687 -->
diff --git a/src/main/resources/project/ui_forms/detach_volume.xml b/src/main/resources/project/ui_forms/detach_volume.xml
index 14efc6c..08d6f40 100644
--- a/src/main/resources/project/ui_forms/detach_volume.xml
+++ b/src/main/resources/project/ui_forms/detach_volume.xml
@@ -16,7 +16,7 @@
 
 -->
 <editor>
-    <help>/commander/pages/@PLUGIN_NAME@/@PLUGIN_KEY@_help?s=Administration&amp;ss=Plugins#DetachVolume</help>
+    <help>https://docs.cloudbees.com/docs/cloudbees-cd/latest/plugins/ec-openstack#DetachVolume</help>
     <formElement>
         <label>Configuration:</label>
         <!-- Improvements for CEV-18687 -->
diff --git a/src/main/resources/project/ui_forms/extend_volume.xml b/src/main/resources/project/ui_forms/extend_volume.xml
index a3b60e9..0608316 100644
--- a/src/main/resources/project/ui_forms/extend_volume.xml
+++ b/src/main/resources/project/ui_forms/extend_volume.xml
@@ -16,7 +16,7 @@
 
 -->
 <editor>
-    <help>/commander/pages/@PLUGIN_NAME@/@PLUGIN_KEY@_help?s=Administration&amp;ss=Plugins#ExtendVolume</help>
+    <help>https://docs.cloudbees.com/docs/cloudbees-cd/latest/plugins/ec-openstack#ExtendVolume</help>
     <formElement>
         <label>Configuration:</label>
         <!-- Improvements for CEV-18687 -->
diff --git a/src/main/resources/project/ui_forms/grow.xml b/src/main/resources/project/ui_forms/grow.xml
index 9c578b9..6005193 100644
--- a/src/main/resources/project/ui_forms/grow.xml
+++ b/src/main/resources/project/ui_forms/grow.xml
@@ -16,7 +16,7 @@
 
 -->
 <editor>
-    <help>/commander/pages/@PLUGIN_NAME@/@PLUGIN_KEY@_help?s=Administration&amp;ss=Plugins#CloudManagerGrow</help>
+    <help>https://docs.cloudbees.com/docs/cloudbees-cd/latest/plugins/ec-openstack#CloudManagerGrow</help>
     <formElement>
         <label>Configuration:</label>
         <!-- Improvements for CEV-18687 -->
diff --git a/src/main/resources/project/ui_forms/reboot.xml b/src/main/resources/project/ui_forms/reboot.xml
index 2bca198..83f3263 100644
--- a/src/main/resources/project/ui_forms/reboot.xml
+++ b/src/main/resources/project/ui_forms/reboot.xml
@@ -16,7 +16,7 @@
 
 -->
 <editor>
-    <help>/commander/pages/@PLUGIN_NAME@/@PLUGIN_KEY@_help?s=Administration&amp;ss=Plugins#Reboot</help>
+    <help>https://docs.cloudbees.com/docs/cloudbees-cd/latest/plugins/ec-openstack#Reboot</help>
     <formElement>
         <label>Configuration:</label>
         <!-- Improvements for CEV-18687 -->
diff --git a/src/main/resources/project/ui_forms/release.ip.xml b/src/main/resources/project/ui_forms/release.ip.xml
index dc3f6d0..be65f64 100644
--- a/src/main/resources/project/ui_forms/release.ip.xml
+++ b/src/main/resources/project/ui_forms/release.ip.xml
@@ -16,7 +16,7 @@
 
 -->
 <editor>
-    <help>/commander/pages/@PLUGIN_NAME@/@PLUGIN_KEY@_help?s=Administration&amp;ss=Plugins#ReleaseIP</help>
+    <help>https://docs.cloudbees.com/docs/cloudbees-cd/latest/plugins/ec-openstack#ReleaseIP</help>
     <formElement>
         <label>Configuration:</label>
         <!-- Improvements for CEV-18687 -->
diff --git a/src/main/resources/project/ui_forms/shrink.xml b/src/main/resources/project/ui_forms/shrink.xml
index 63aedf1..25ab1cc 100644
--- a/src/main/resources/project/ui_forms/shrink.xml
+++ b/src/main/resources/project/ui_forms/shrink.xml
@@ -16,7 +16,7 @@
 
 -->
 <editor>
-    <help>/commander/pages/@PLUGIN_NAME@/@PLUGIN_KEY@_help?s=Administration&amp;ss=Plugins#CloudManagerShrink</help>
+    <help>https://docs.cloudbees.com/docs/cloudbees-cd/latest/plugins/ec-openstack#CloudManagerShrink</help>
     <formElement>
         <type>entry</type>
         <label>Configuration:</label>
diff --git a/src/main/resources/project/ui_forms/sync.xml b/src/main/resources/project/ui_forms/sync.xml
index 16cab56..bb9ebbb 100644
--- a/src/main/resources/project/ui_forms/sync.xml
+++ b/src/main/resources/project/ui_forms/sync.xml
@@ -16,7 +16,7 @@
 
 -->
 <editor>
-    <help>/commander/pages/@PLUGIN_NAME@/@PLUGIN_KEY@_help?s=Administration&amp;ss=Plugins#CloudManagerSync</help>
+    <help>https://docs.cloudbees.com/docs/cloudbees-cd/latest/plugins/ec-openstack#CloudManagerSync</help>
     <formElement>
         <type>entry</type>
         <label>Configuration:</label>
diff --git a/src/main/resources/project/ui_forms/teardown.xml b/src/main/resources/project/ui_forms/teardown.xml
index a8ab41f..5cb607d 100644
--- a/src/main/resources/project/ui_forms/teardown.xml
+++ b/src/main/resources/project/ui_forms/teardown.xml
@@ -16,7 +16,7 @@
 
 -->
 <editor>
-  <help>/commander/pages/@PLUGIN_NAME@/@PLUGIN_KEY@_help?s=Administration&amp;ss=Plugins#Teardown</help>
+  <help>https://docs.cloudbees.com/docs/cloudbees-cd/latest/plugins/ec-openstack#Teardown</help>
   <formElement>
     <label>Configuration:</label>
     <!-- Improvements for CEV-18687 -->
diff --git a/src/main/resources/project/ui_forms/update_stack.xml b/src/main/resources/project/ui_forms/update_stack.xml
index e1b5e29..eef825a 100644
--- a/src/main/resources/project/ui_forms/update_stack.xml
+++ b/src/main/resources/project/ui_forms/update_stack.xml
@@ -16,7 +16,7 @@
 
 -->
 <editor>
-    <help>/commander/pages/@PLUGIN_NAME@/@PLUGIN_KEY@_help?s=Administration&amp;ss=Plugins#UpdateStack</help>
+    <help>https://docs.cloudbees.com/docs/cloudbees-cd/latest/plugins/ec-openstack#UpdateStack</help>
     <formElement>
         <label>Configuration:</label>
         <!-- Improvements for CEV-18687 -->