Hi everyone, Alaks Sevugan here. So, have been following my previous posts on
? If not, this will be a good time to review the blog posts. In this post, I will be covering how to customize and deploy a Service in VMM 2012.
Let’s say that you have created a service template using the service designer and you are ready to deploy the service. You need to select which Cloud or Host group, you want the service to be deployed to. VMM will run the intelligent placement algorithm for placing multiple VMs in the service on the most appropriate hosts in the host group or cloud in the environment - this will be based on VM requirements and available host resources.
· When the
, you will be given a preview of each VM in the service and the suitable host it be deployed to. And as part of customizing the deployment, you can choose a different host if you need to.
· When the
, hosts are hidden from the preview and you can customize any of the settings for the deployment or change some of the VM properties.
Ability to provide overrides as a part of Service deployment enables you to author a Service Template once and deploy it to multiple environments – test, dev, production etc., without having to change the Service Template for each environment.
Service Deployment Preview
This is the Service deployment preview in VMM. You can see that this Service has been deployed to the Seattle Test Cloud and none of the host information is shown.
, like database name, connection string etc. that need to be provided as a part of deployment can be provided here as shown.
Once you have customized and you are happy with the preview, you can go ahead and deploy the service. Here is a typical flowchart that explains Service Deployment:
Tier is selected based on the deployment order of the tier.
For each machine in the tier, VMM will copy all the VHDs, apps, scripts etc. to the destination host.
It will create VMs, customize the OS and install a guest agent that will be used for app deployment, OS Roles and Features
Once the guest agent install is complete, OS roles, features are installed and any custom EXEs provided will be run before app installs followed by the installation of the application.
VMM will then run the post install EXEs for the machine and once that is complete, the machine will be added to the Load Balancer.
This process is repeated for each of the tiers.
Job Trail for Service Deployment
As the service is being deployed in VMM, the job trail in the Jobs views gives you the current status of the deployment. All the VMs in each tier are deployed in parallel. Once the VMs are deployed, the applications in each tier are deployed in parallel based on the deployment order.
If the job fails for any reason, the job can be restarted and the job will continue from where it left off. If the job continues to fail, then the specific VMs can be deleted and the job restarted, so the VM get recreated.
If the service deployment job fails, the system does not roll back any changes. You need to delete the failed service and redeployed the service, if the service has to be deployed from the beginning.
Here is a typical Service Deployment Job Trail:
Deployed Service in VMM
When the Service is being deployed or the Service is deployed successfully, the Service can be viewed in the “VM and Services” navigation bar. Here is a typical screenshot for the Services deployed to the host groups:
Deployed Service in OpsMgr
Once a service is deployed, here is a typical layout of what a deployed Service diagram looks like in OpsMgr. This layout is for a Petshop service - Petshop service has 3 tiers Web Tier, Mid Tier and a SQL Tier. This Service Diagram is generated as the Service is being deployed in VMM.
This completes the Service authoring and deployment blogs. In the next blog we will look at how to manage the updates to the Service.
Until next time…enjoy creating, customizing and deploying Services in your environment.