vRealize Automation 7.1 – Create a Blueprint, Configure Catalog Item & Provision VM (Part 6)

vRealize Automation 7.1 – Create a Service & Entitlement (Part 5)

1. Create a ‘vSphere’ Machine Blueprint

VMware Machine Blueprint Definition: A blueprint that contains a machine component specifies the workflow used to provision a machine and includes information such as CPU, memory, and storage. Machine blueprints specify the workflow used to provision a machine and include additional provisioning information such as the locations of required disk images or virtualization platform objects. Blueprints also specify policies such as the lease period and can include networking and security components such as security groups, policies, or tags. Blueprints can be specific to a business group or shared among groups in a tenant, depending on the entitlements that are configured for the published blueprint. More detail on Blueprints here.

To create the Blueprint Login as a user who has the ‘Infrastructure Architect’ role assigned (Machine Blueprint capabilities):

vracreatebp1b Continue reading

vRealize Automation 7.1 – Create a Service & Entitlement (Part 5)

vRealize Automation 7.1 – Create Machine Prefix, Business Group & Add Reservation (Part 4)

1. Create a Service

VMware Services Definition:  Services are used to organize catalog items into related offerings to make it easier for service catalog users to browse for the catalog items they need. You can entitle the service, which entitles business group users to all the associated catalog items. More details on Services here.

Login as a Tenant Admin or a user that holds the Catalog Admin role:

vraservicesentitlements

Continue reading

vRealize Automation 7.1 – Create Machine Prefix, Business Group & Add Reservation (Part 4)

vRealize Automation 7.1 – Create Endpoints & Fabric Groups (Part 3)

Before creating the Business Group we firstly need to create a Machine Prefix which can be used by the Business Group to create IaaS resources.

1. Create a Machine Prefix

VMware Machine Prefix Definition: You use machine prefixes to generate the names of provisioned machines. Machine prefixes are shared across all tenants. You should assign a default machine prefix to every business group that you expect to need IaaS resources. Every blueprint must have a machine prefix or use the group default prefix. Fabric administrators are responsible for managing machine prefixes. More detail on Machine Prefixes here.

Login as a Fabric Admin (which we created in the previous post) to create the machine prefix: Continue reading

vRealize Automation Blueprint Creation – vSphere Templates not Displaying

While in the process of creating a vRA blueprint, none of my vSphere templates were displaying as an option for selection. This led me to verify some of my previous config, which led to identifying the source of the problem to be a misplaced template. Thanks @HeagaSteve for pointing me in the right direction!

As you can see when I click on the ellipsis in order to select a template I receive ‘No data to display’ in the list box:

vrabptemplate1a Continue reading

vRealize Automation 7.1 – Create Endpoints & Fabric Groups (Part 3)

vRealize Automation 7.1 – Create Tenant & Configure Authentication (Part 2)

Following on from the tenant & authentication post above, the following steps detail the creation of an Endpoint & Fabric Group in vRA 7.1.

This post will show how to create a vCenter endpoint followed by a Fabric Group, a vRO endpoint and the credentials required to connect vRA to these endpoints.

Begin by logging into the new tenant with a user who has the IaaS Administrator privileges:

vra71endpoints0

Nice flow chart from vmware.com:

vra71endpoints01

1. Store Credentials:

Login into your tenant:

https://vipvra.ppsilver.lab.local/vcac/org/ehc/

vra71endpoints1

Continue reading

vRealize Automation 7.1 – Create Tenant & Configure Authentication (Part 2)

vRealize Automation 7.1 – Installation (Part 1)

Following on from the Install post above, the following steps detail the creation of a Tenant in vRA 7.1.

Begin by navigating to https://vRA-FQDN and logging into the default tenant using the Administrator account and password created during install:

vra71tenantauth1

Continue reading