Filters

CLEAR ALL

Search Results ()

Filter Icon

Search Results ()

    All Plugins (172)

    Filter Icon

    Quick Info

    Product icon
    Product
    DevOps Deploy (HCL Launch)
    Plugin type icon
    Type
    plugin
    Compatibility icon
    Compatibility
    DevOPs Deploy version 8.0.0 or later
    created by icon
    Created by
    HCL Software
    Website icon
    Website
    Published Date
    April 17th, 2024
    Last Updated
    June 7th, 2024

    Description

    HCL DRYiCE MyCloud is a hybrid-cloud lifecycle management plug-in that offers optimal governance and monitoring of your cloud infrastructure. With intuitive data visualization and actionable insights, you are always one step ahead. Intelligent insights that help effectively visualize, manage, and optimize multi-cloud spends, improve governance and strengthen the multi-cloud security posture can be gained with, MyCloud FinOps.

    Quick Info

    Product icon
    Product
    DevOps Deploy (HCL Launch)
    Plugin type icon
    Type
    plugin
    Compatibility icon
    Compatibility
    DevOPs Deploy version 8.0.0 or later
    created by icon
    Created by
    HCL Software
    Website icon
    Website
    Published Date
    April 17th, 2024
    Last Updated
    June 7th, 2024

    Deploy-MyCloud-2.1168407.zip

    Uploaded: 04-Jun-2024 06:08

    Deploy-MyCloud-1.1167478.zip

    Uploaded: 18-Apr-2024 11:20

    Release Notes

    Initial release.

    Summary

    Executes a VM provision in My-cloud, installs Deploy agent in it, and updates that agent resource in an Environment of this launch instance.

    This plug-in includes one or more steps. Click Process Steps for step details and properties.

    Compatibility

    This plug-in requires version 8.0.0 or later of HCL DevOps Deploy.

    Installation

    See Installing plugins in HCL Deploy for installing and removing plugins.

    History

    The following table describes the changes made in each plug-in versions.

    Plugin history details
    Version Description
    2 Supports multiple VM creation.
    Removed feature of the plugin which was failing after 40 minutes if VMs weren’t created.
    Payload object is replaced with multiple properties.
    1 Initial release of the plug-in.

    Process Steps

    The single process step in this plugin is:

    MyCloud Instance provision

    Execute a VM provision in My-cloud, install Deploy agent in it and updates that agent resource in an Environment of this launch instance.
    Configuration properties below.

    Name Type Description Required
    MyCloud Api Url
    String
    The API url associated with the my cloud
    account Ex-https://demo.domain.com.
    Yes
    Username
    String
    The username associated with the my cloud account.
    Yes
    Password
    Secured
    The password associated with the my cloud account.
    Yes
    Component Name
    String
    The launch component name associated with the deployment.
    Yes
    Tag Name
    String
    The tag name to add with the component Ex- windows_tag.
    Yes
    Appliction Name
    String
    The launch application name which will deploy the component version Ex- application-mycloud-launch.
    Yes
    Env Name
    String
    The launch environment name under the application provided. In this environment the deployment will be done Ex- DEV, PROD etc.
    Yes
    VM Counts
    String
    Number of VMs required to be created in this step.
    Yes
    VM OS Type
    String
    Select the OS type of the VM.
    Yes
    Instance Size
    String
    Select the Instance size according to the OS type.
    Yes
    Data Center Name
    String
    Select the Data Center.
    Yes
    Network
    String
    Select the Network.
    Yes
    Cluster Name
    String
    Select the Cluster Name.
    Yes
    Storage Name
    String
    Select the Storage Name.
    Yes

     

    For Initial release of the plugin, the VM provision data are described below. This payload is not required in v2. All these values has been converted into properties

    Requesting for Windows VM:

    {
    “items”: [
    {
    “businessparameters”: {
    “ddlInstanceSize”: “Large_L1”,
    “ddlNetwork”: “OTZ-IDMZ-WEB-SRVS”,
    “hdnDataCenterName”: “VMWPOD-PROD”,
    “hdnClusterName”: “Management-Prod”,
    “hdnStorageName”: “NetApp_VMW_SharedDataStore01”,
    “launchAgentURL”: “Place Your launch Agent Server IP Address”
    }
    }
    ],
    “serviceCatalogId”: “103”
    }

    Requesting for Linux VM:

    {
    “items”: [
    {
    “businessparameters”: {
    “ddlInstanceSize”: “Medium_M1”,
    “ddlNetwork”: “OTZ-IDMZ-DTB-SRVS”,
    “hdnDataCenterName”: “VMWPOD-PROD”,
    “hdnClusterName”: “Management-Prod”,
    “hdnStorageName”: “NetApp_VMW_SharedDataStore01”,
    “launchAgentURL”: “Place Your launch Agent Server IP Address”
    }
    }
    ],
    “serviceCatalogId”: “102”
    }

     

    Usage

    The My Cloud plug-in provides the features that can be used for the following purposes:

    • Visualize and manage multi-cloud spends.
    • Improve governance and strengthen the multi-cloud security through MyCloud FinOps.

    Perform the following steps to use MyCloud plug-in:

  • Create a generic process.
  • Search for MyCloud plugin in the search palette and add it to the step as shown below.
    Add MyCloud to process step screen
  • Configure the step, as shown below, with all the properties required

  • Execute the process. It typically requires 25-30 minutes to finish. Refer to the images
    below to track the progress from initiation to completion.
    The plugin step involves creating a VM and installing a Deploy agent in it. The agent will
    then appear as Online in the resource tab.
    A resource group will be created to host the agent and then the tagged accordingly.
    This resource group will be added to our Environment (DEV of application MY-APP) provided in the plugin step UI.
    Additionally, the tag will be applied to the component (MY-COMP).
    Output log 2
  • The agent is successfully created and is currently Online (win-14785-1-web.agent-1). It was deployed on the VM with the IP address 172.30.13.53.
  • Component tag

  • The tag name provided in the plugin is automatically applied to the component.
    Component tag
  • The created Resource is added to the environment.Resource added to Environment
  • This environment is now ready for deploying any version of the MY-COMP component. Deployment will target the machine created earlier, specifically the VM with the IP address 172.30.13.53.