You can design blueprints that deploy Heat stacks when consumed as a service.


  • Verify that you have service architect user privileges to access the plug-in.

  • Verify that the OpenStack Keystone service is connected to an Active Directory server for automatic synchronization. This configuration automatically synchronizes user accounts in Keystone


  1. Log in to the vRealize Automation tenant as a service architect.
  2. Select Design > XaaS > XaaS Blueprints.
  3. Click New.
  4. Select the workflow Orchestrator > Library > VMware Integrated OpenStack > Deploy a Heat stack or Delete a Heat stack, and click Next.
  5. Select the template to be published and click Next.

    The blueprint form appears.

  6. Complete the text boxes in the blueprint form.

    You must enter custom labels for all parameters. Parameters listed below are specific for this blueprint. Keystone URL, Project name, Keystone domain name, User name, and Password parameters are mandatory for all blueprints. For the delete blueprint you only need the first parameter from the table and the mandatory ones.




    Visibility to user


    New Stack Name

    Specify the name for the new Heat stack. You can leave this value empty to allow the catalog user to specify the new stack name.



    Template Content

    Provide the Heat template file content to be published. Configure as text area.

    A Heat template is a static architectural design of the orchestrated application, and are written in the HOT (Heat Orchestration Template) format.



    Environment Content

    Provide the Heat environment file content. Configure as text area.

    The Heat environment file contains values for specific parameters in the Heat template.

    For authoring information, see the OpenStack documentation.



    timeout in minutes

    Specify the timeout period for this service in minutes.


  7. Click Finish.

    The newly created blueprint appears in the list of XaaS blueprints.

  8. To publish the blueprint, select it from the list and click Publish.

    A blueprint becomes available for consumption only after you publish it.