- Create an Application Blueprint – Application Services Series Part 4
- Create a Logical Template – Application Services Series Part 3
- Create a Deployment Environment – Application Services Series Part 2
- Create a New Cloud Provider – Application Services Series Part 1
Application Services is configured, now its time to create and publish an Application Blueprint. During the installation I chose to install the sample content so I would have some an existing application blueprint available; I am going to take advantage of that sample content for my lab and edit one of the existing applications. If you are not already, log into Application Services as luke and use the pull down menu in the upper right to change to the Application view.
- Click on jPetStore
- In the Application Versions pane, click on the 1.0.0 version
- Click on the blueprint
- Click on CentOS32 v6.3
- Drag the CentOS64 v6.4 logical template into the application builder
- Drag the components from jPetStore to the CentOS64 operating sytem
- Delete the CentOS32 item and click the Save button
- Click the Deploy button in the upper right corner
- Name the new deployment profile and select the business group; Click the Deploy button
- Select the Deployment Environment, click the map details button then click Next
- Click into the hostname field and enter a name then click Next
- Review the execution plan and click next
- Click the publish button, name the item and click OK
Now we need to provide entitlements in vRealize Automation; log into vRA as tenantadmin:
- Click on the Administration tab >> Catalog Management >> Catalog Items
- Click on jPetStore (or whatever you named it), add it to the Clone Linux Template service and click Update
- Log out and log back in as luke
- Click on the Catalog tab; you should now have your basic VM template catalog item and the jPetStore catalog item.
You are now able to request Application Services blueprints through vRealize Automation!
This was a pretty basic example, and not likely to be replicated in real world use cases. In fact, I have seen projects to automate the installation of software take upwards of 6 months to complete. Remember with Application Services we have moved beyond installing an application and simply cloning it, as that doesn’t work or scale for many applications – they require connection strings, network information etc.. What you are doing now is leveraging a release engineering or application automation tool so building a solid Application Services blueprint will go through its own SDLC.