Create a Deployment Environment - Application Services Series Part 2

Nov 23, 2014 • Jonathan Frappier

In my last post we created the Cloud Provider, now we need to setup a Deployment Environment. We are really setting up logical constructs here to map to to services and resources we already have. So far we mapped a Cloud Provider to vRealize Automation Center and to our business group. Now we are going to create a deployment environment for Application Services that maps to the cloud provider we created, that maps to vRealize resources… If you are not already, log in as Luke and perform the following.

Click on the Cloud Provider pull down menu in the top right corner (short aside, that menu name will change to show the context you are currently working in so if you logged out this may be different) and select Deployment Environments

Click the Create A Deployment Environment button

Provide a name

Select a Cloud Provider from the pull down menu

Click the Select button to select a reservation policy; click OK then Save

You screen should look similar to what is pictured below. Since Application Services is now part of vRealize Automation, most of the work we are doing here will map to what has already been configured in vRealize Automation. Next we need to create a logical template.

Related Posts

VMware Application Services (formerly Application Director) is now deployed, but we need to do a bit more integration with vRealize Automation / vCloud Automation Center so we can publish Application Services blueprints to the vRealize Automation catalog. First we need to define a cloud provider;

While logged in as Luke, the user we gave all of the Application Services roles to, click on the Applications pull down menu and select Cloud Providers

Click the Create Cloud Provider button/box

Click the Cloud Provider Type pull down and notice what options are available - vCloud 5.x, vCAC and EC2. What about vCloud Air - can we use that? If you said yes you are correct because vCloud Air is based on vCloud Director.

Enter the information like so (note some of the boxes appear "greyed out" - they are not, just a poor choice for background colors) and click the Validate Connection button

Notice that you have to use an upper case domain, I'm curious as to why but in any case its the only way that worked for me

Next in the lower half of the screen (not pictured above) in the templates section, click the green plus icon

You should see the CentOS-Template catalog item we previously published in the vRealize Automation catalog; click the check mark next to the desired template and click OK

Click the Save button in the upper right hand corner

We now have the first step in setting up Application Services complete, up next we will create a Deployment Enviornment

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: