Part 7: vRA 7.5 Infrastructure and XaaS Blue Prints Creation
This post will cover creation of Blue prints for Virtual machines and Any thing as a service (XaaS). We had created the backbone for vRA till now from blog 1 to blog6 but in this blog will create the actual blue prints.
Please find the links for all the posts in this series below.
- Introduction and Design : Installing and Configuring vRealize Automation (vRA) 7.5
- Part 1: Deploying vRealize Automation (vRA) 7.5 Appliance
- Part 2: Installing SQL for vRealize Automation (vRA) 7.5
- Part 3: vRealize Automation (vRA) 7.5 Installation and IIS server Configuration
- Part 4: vRA 7.5 Initial Configuration of Default tenant and AD Directory Sync
- Part 5: vRA 7.5 Sub tenant Creation and Branding
- Part 6: vRA 7.5 Custom Groups, End points and Reservation Configuration
- Part 7: vRA 7.5 Infrastructure and XaaS Blue Prints Creation
- Part 8: vRA 7.5 Approvals, Catalog Management and Testing Blue Prints
- Part 9: vRA 7.5 fixing installation errors and configuration issues
Please click on the left side social share icons to share this post if you feel its useful to others.
Contents of the Post
Blue Print Creation
Login to the tenant as vraadmin ( https://vra.sslab.com/vcac/org/sslab)
- Select Design – Blue Prints – Add new (+)
- provide Name and unique ID will created automatically which can be changed.
- Deployment limit: how many VM’s or blue print requests users can request using this blue print.
- Lease Days : minimum days vm will be active, maximum days the vm deployed by blue print will be valid.
- Archive days: By default after max days VM will be deleted, instead if can be archived by shutting down for those days.
Now Blue prints are opened, Select Machine type – drag vSphere VM –
General : provide VM ID, Machine Prefix, instance min, max
in Blue Print information page.
- Type: Server
- action: clone
- Clone VM : select VM Template.
Machine Resources
Provide min and Max cpu, ram and storage the VM can have.
Review and Finish
Once the blue print is done – it will be in draft mode – select and Publish
XaaS Blue Print
XaaS blur print will use default vRO instance installed on the vRA appliance. we can have external vRO as well. In our case its in built.
Select New to create new blue print.
navigate through all the folders and select Create a Snapshot or what ever action.
Provide Name and next
Review and Next
Review and next
Select Category Xaas, so that it will display in XaaS folder.
Select and publish the blue print.
With this part 7 is completed. Now will move to the final step of testing in part 8 of this series..!!
Please find the links for all the posts in this series below. Click on the link below for the next post in this series.
- Introduction and Design : Installing and Configuring vRealize Automation (vRA) 7.5
- Part 1: Deploying vRealize Automation (vRA) 7.5 Appliance
- Part 2: Installing SQL for vRealize Automation (vRA) 7.5
- Part 3: vRealize Automation (vRA) 7.5 Installation and IIS server Configuration
- Part 4: vRA 7.5 Initial Configuration of Default tenant and AD Directory Sync
- Part 5: vRA 7.5 Sub tenant Creation and Branding
- Part 6: vRA 7.5 Custom Groups, End points and Reservation Configuration
- Part 7: vRA 7.5 Infrastructure and XaaS Blue Prints Creation
- Part 8: vRA 7.5 Approvals, Catalog Management and Testing Blue Prints
- Part 9: vRA 7.5 fixing installation errors and configuration issues
Please click on the left side social share icons to share this post if you feel its useful to others.
Hope this post is useful, please leave your comments below.
Great series on vra
Hi Siva, great blog! I am trying to create an iis server farm with vra using puppet . I already have puppet integrated in my vra.