Initial vRealize Automation (vRA) Configuration Part 5 - Create A Blueprint

Skip to Part:

 

Create a Blueprint and Publish It

Blueprints are the mechanism by which repeatable service offerings are defined in vRealize Automation.  A blueprint contains information about the types of virtual machine instances, networks, resources, software, and XaaS blueprints required to create a service.  Once a blueprint has been defined, it must be published to the service catalog in order for it to be requestable by users.  A user can then request the blueprint, if they’re so entitled, to receive the service defined by the blueprint.

Use the following procedures to create a blueprint:

  1. Click the Design tab.
    Click the Design tab
  2. Click the “New” button.
    Click the New button
  3. Enter a valid name for the blueprint. In our example, we’re building a RedHat Enterprise Linux (RHEL) 7 blueprint, so we named it RedHat 7.
  4. Enter a valid description for the blueprint. This description appears in the service catalog when a user is browsing available catalog items to request.
  5. Click the “OK” button.
    Click the OK button
  6. In the blueprint canvas, click and drag the vSphere (vCenter) Machine item from the left to the center of the canvas on the right.
    Click and drag vSphere Machine to the canvas
    vSphere machine on canvas
  7. Enter a valid name for the blueprint component. This is going to be a RedHat 7 vSphere machine so we name it “RedHat7_vSphere_VM”.  It’s important to change this from the default and make it a friendly name because the end-user can see it in the request form.  Additionally, if you submit a request using the REST API, this component name will be referenced in the request and will make it easier to distinguish programmatically if the name makes sense.
    Enter a name for the component
  8. Click the Build Information tab.
    Click the Build Information tab
  9. Change the Action type to Linked Clone.
    Change the action ttype to linked clone
  10. Click the ellipsis button next to the “Clone from” field.
  11. Select the base machine from which to make a linked clone. Note that only the list of virtual machines that have at least one snapshot on them will be displayed.  No templates will be shown here, as they are used for full clones not linked clones.  If an expected item is missing from the list, it may be because data collection has not happened since the snapshot was made.  Be sure to initiate data collection on the appropriate compute resources before going to this screen if you’ve recently made changes a VM snapshot.
  12. Click the “OK” button.
  13. Select a valid snapshot from the “Clone from snapshot” list. Do not select Use current snapshot, as this will induce an unnecessary delay in the provisioning process.  Always make a snapshot of the desired linked clone state and reference it directly.
  14. Consult the vSphere Client for a list of valid VM Customization Specifications. Find one that applies to the appropriate kind of VM blueprint you’re creating.  Note the name and use it in the next step.  In our example, we have an enterprise linux customization spec intended for use in vRA, named VRA7.  So this is the name we’ll copy for the next step.
  15. Enter the customization spec name in the build information for the blueprint.
  16. Click the Machine Resources tab.
  17. Enter the desired minimum and maximum CPU, memory, and storage values, and click the “Finish” button to create the blueprint.
  18. Select the newly created blueprint in the list by clicking it. Be sure not to click on the name of the blueprint as this is a link to edit it. 
  19. Click the “Publish” button to publish this blueprint to the catalog.

Skip to Part:

 


Leave a comment