Blueprint information settings control who can access a blueprint, how many machines they can provision with it, and how long to archive a machine after the lease period is over.
Log in to the vRealize Automation console as a “Tenants administrator” or business group manager. In my case, I have created one already in my Active Directory with name “firstname.lastname@example.org” and gave permission to configure tenants during “create new tenants” process. Enter the “credentials” and click “Login”
Once you login. Either you follow the walkthrough screen on left side or go to “Infrastructure” tab -> Groups-> Blueprint > Click “Blueprint”.
In Blueprint ->Select “New Blueprint” -> Virtual and select the type of blueprint you are creating.in my case its “vSphere (vCenter)”
In “Buleprint Information” tab of blueprint. Enter the following information’s.
1-Enter a blueprint name in the “Name” text box and “description” (optional).
2- Select the “Master check box” to allow users to copy your blueprint (Optional)
3-Select the “Display location” on request check box to prompt users to choose a datacenter location when they submit a machine request (Optional).I leave it as unchecked as I will configure it later.
NOTE: This option requires additional configuration to add datacenter locations and associate compute resources with those locations.
4-Select the “Shared blueprint check box” to allow the blueprint to be entitled to users in any business group.
NOTE: If you “Deselect the Shared blueprint check box”, it will create a local blueprint, and then ask you to select a “business group” from the “Business group drop-down” menu to control access for a specific business group users.
5-Select a “reservation policy” from the Reservation policy drop-down menu (Optional). I already created once previous, so I am going to choose it.
6-Select a “machine prefix” from the Machine prefix drop-down menu.
7- Type a “number in the Maximum” per user text box to limit the number of machines that a single user can provision with this blueprint (Optional).I leave it as default
8-Specify the “number of days to archive” machines provisioned from this blueprint in the Archive (days) text box. Type “0” if you do not want to archive machines.
9-Set the daily cost of the machine by typing the amount in the Cost (daily) text box (Optional).
NOTE: This cost is added to any cost profiles that your fabric administrator sets up
In “Build Information” tab of blueprint. Enter the following information’s.
1-Select whether machines provisioned from this blueprint are classified as “Desktop” or “Server” from the Blueprint type drop-down menu.
NOTE: This information is for record-keeping and licensing purposes only.
Select your “Action” from drop-down as I am using “linked cloned” due to fast provisioned and storage space constraint in my lab.
Select “BasicVmWorkflow” from the Provisioning workflow drop-down menu, I choose “cloneworkflow”.
NOTE: If you are working with a KVM (RHEV) or Hyper-V (SCVMM) blueprint, you can provide an ISO for provisioning. For Hyper-V (SCVMM), you can also select additional profiles to attach to machines provisioned with your blueprint (Optional).
Next “clone from”, click on the “browse” button and select the “image” where you want to clone your blueprints
If you remembered my vRA baseline post, I had created a CentOS VM for this purpose. Select the VM machine and Click “Next”
Select a “snapshot” as I already created one in my CentOS VM. Because it is mandatory to create snapshot if you want to use linked clone technology. If you did not create the snapshot at start. then you have ability to create one right now. By choosing the “New Snapshot” button from right side of dialog box. Once done -> Click “Next”
NOTE: this step is only required in case of linked clone.
Confirm the snapshot selection by click on “OK” button
Now I choosed the snapshot whom I want to linked clone my blue print. Optionally “check delete snapshot after blueprint is deleted”. If you want.
In “Customization Spec”, enter the Customization specification name. It should be the same which you created in vCenter.
You can see it by login to vCenter from Classic or Web client.
In Classic Client-> Go to Home-> management ->Customization Specification Manager as shown below.
Next define your “minimum and maximum” Machine resources, which you want to allow your users to provision.
Next go to “Properties” tab. I have nothing to configure here right now.
Next in “Actions” Tab. Select your desired actions which you want to allow a machine owner to able to perform after provisioning the VM from this blueprint.
All actions are checked by default. Which is fine for me. Click “OK”
Now you blueprint is created. The next task is publish it