We have previously looked at how we enable application self-service, a standardized approach to deploying applications, and how we monitor applications across private and public clouds. And today we are going to explore the various application deployment models that are available when you have a private cloud.
In todays datacenter, you are most likely deploying individual virtual (or physical) machines by leveraging either a standardized installation routine, a vanilla (sysprep) OS image or a virtual machine template. This is a great start to leverage virtualization and standardized deployments, however even a well-managed virtualization solution has its limitations and requires you to continue operating within the practices you use today for the configuration, deployment, monitoring and operating of your applications.
As you move to a private cloud, one of the things we focus on is the standardization of service deployment, and we provide a way to transition from where you are today and leverage these new opportunities for consistency and standardization.
There are 3 potential options that are provided for in the Microsoft private cloud for deploying the underlying OS components for the application, or the application as a service. These can be considered a progression, however you can pick the one that best suits your needs!
The screenshots below show visual representations of each of these:
The diagram below shows an example of a service template and how all the components come together to form the service. Capturing the specifications for the hardware, OS and application profiles means that you drive consistency in the model and also allow you to leverage these profiles across applications for reuse of the information.
I look at this model, and believe in the very near future that this will be the preferred method of developers and ISVs handing off applications to their customers. Imaging receiving a service template like this that is all configured and ready to go, and all you have to do is enter your company or business unit specific information at deployment time!
So now that we have looked at the different underlying structures for deploying our applications, lets take a look at the configuration and deployment models for the applications themselves.
As in the graphic below, we look at application deployment modes being in one of three models:
And with that, we have covered this topic on the application deployment models in a private cloud!
There are several things you can be doing today to get started with applications in your private cloud:
I hope that was useful for you.