Create vRealize Automation 7.3 Blueprints
From Notes_Wiki
<yambe:breadcrumb>VRealize_Automation_or_VMWare_Cloud|VRealize Automation or VMWare Cloud</yambe:breadcrumb>
Create vRealize Automation 7.3 Blueprints
Once appliance is deployed and configured for endpoints, fabric groups, AD integration, reservation, etc. then blueprint creation can be started. To create and use a blueprint in vRA 7.3 use following steps:
- Ensure that desired templates are available at vCenter level. The template should be connected to desired networks so that we do not have to worry about adding network in blueprint. We can change the VM network to something else using properties or property groups later.
- Ensure that "Customization specification" for DHCP (or static IPs if using network profiles) are available for required OS (Windows or Linux) in vCenter.
- Go to "Home" -> "Customization Specification Manager" and create specification in vCenter (eg suse), if not created already.
- Login into vra and Infrastructure -> Compute Resources -> Compute Resources.
- Against the cluster where template is created, click right arrow and select "Data Collection".
- Click all "Request now" buttons for immediate data collection one by one - Inventory, State, Performance. Without these the new templates may not show up in the blueprint design phase in next steps.
- Click ok to close data collection diaglog box.
- Go to "Design -> Blueprints".
- Click on New to create new blueprint.
- Give desired blueprint name (eg suse12sp3) and set archive (days) to 0.
- Click ok to go to Blueprint Design page.
- Drag and drop vSphere (vCenter )Macihne to canvas. Make following modifications:
- Under General:
- ID
- Desired (eg suse12sp3_vm1)
- Instances
- Minimum (1), Maximum (1)
- Under Build Information:
- Blueprint type
- Server
- Action
- Clone
- Provisioning workflow
- CLoneWorkflow
- Clone from
- Select appropriate template using selection menu
- Customization spec
- Required (Eg suse)
- Machine Resources:
- Give appropriate min and max for resources
- Storage, Network, Security, Properties and Profiles leave as it is and click save.
- Click "Finish" to finish creating blueprint.
- Select the created blueprint and click "Publish" to publish blueprint.
- Go to Administration tab –> Catalog Management –> Entitlements and create new entitlement with following values:
- Under Genral use:
- Name
- Give desired name (eg rndbg1_suse_1 )
- Status
- Active
- Business Group
- rndbg1
- Users and Groups
- All users and groups
- and click next.
- On Items & Approvals use:
- Select required entitled services (Eg Suse)
- Entitled Items
- (Eg suse12sp3)
- Entitled Actions
- Required (Eg: all actions. Click '+' to list actions and select all)
- and click Finish to complete creating entitlement for selected services for selected business groups.
- Ensure that created blueprint belongs to correct service.
- Go to Administration -> Catalog Management -> Catalog Items.
- Select blueprint created above (Eg suse12sp3) and configure it to be part of desired service (Eg suse).
- Login as user of created business group (eg user). Go to Catalog and Services and blueprint should be visible.
- Make a request of created blueprint with appropriate values and click submit. Finally click ok.
- Go to Requests. Select current request and click "View Details".
- Click "Execution Information" on top right to see progress of blueprint execution. Once blueprint is provisioned the status on "Requests" page would reflect the same. Once Request status is Successful we can proceed.
- Go to Items -> Deployments or Items -> Machines to see various VMs deployment wize or as a consolidated list.
- For any VM click VM name and then click "View Details" to get various VM details. We can also go to Deployment and choose action "Destroy" to destroy this deployment.
- Login as configuration admin and go to Catalog.
- Click 'X' at top and see things on behalf of user.
- Similarly go to Items and see Items owned by desired business group.
- Also go to Infrastructure -> Managed Machines to see list of all machines managed by vra and there reservation. We can also change reservation and ownership of already deployed machines from here.
Refer:
<yambe:breadcrumb>VRealize_Automation_or_VMWare_Cloud|VRealize Automation or VMWare Cloud</yambe:breadcrumb>