Microsoft has recently published their vision and plans for the future of Windows Azure Pack. This document called as “Windows Azure Pack Roadmap and Future Support” and must be taken into consideration by any service providers who has datacenters based on WAP and related components (SC, Windows Server).
You can download the full version of roadmap here.
Here I’m just citing the most important quotations:
Product support for WAP and the current version of System Center will continue to be available until the end of 2022. Table 1 summarizes the product support lifecycle for the main components in a WAP cloud deployment.
Microsoft Azure Stack brings Azure to service provider datacenters so that they can accelerate time to market and expand the addressable market for their services portfolio. Application developers can maximize their productivity using a ‘write once, deploy to Azure or Azure Stack’ approach. Microsoft Azure Stack will be launching in the fourth quarter of calendar year 2016
Service Providers should continue to use Windows Server Hyper-V for highly virtualized environments (for example, virtualizing their most demanding workloads) along with Windows Azure Pack and System Center for management. More importantly, they should sell and support what is available today that end customers understand and ask for, and then prepare for future evolution of technologies.
Finally, this is the third and last part of series of posts related with Windows Azure Pack (WAP) and VMM Clouds. Previously we’ve described installation of Windows Azure Pack and Service Provider Foundation. Now it’s time to implement the first cloud service. No doubt the most popular service is VM Cloud. Let’s describe what is it and how to deploy one with WAP.
Service Provider Foundation
Install and configure Service Provider Foundation
The VM Clouds service in Windows Azure Pack uses Service Provider Foundation to communicate with VMM. So, before provisioning VM Clouds Guide HOW TO
In the underlying VMM server that is associated with the Service Provider Foundation endpoint, you must have created a cloud and it’s associated components such as VM Templates, Hardware Profiles, VM Networks, Gallery Items
For clouds to work with Windows Azure Pack, you must ensure that the clouds are created with the following considerations:
You must create a cloud from host groups.
You must have already created logical networks that can be associated with the cloud
You must have already created a VM library share.
You must assign the right amount of capacity to the cloud. The capacity that you assign to the cloud governs the resources that will be available to the tenants while provisioning virtual machines using VM Clouds.
You must not select any of the available capability profiles (ESX Server, Hyper-V, XenServer) while creating the cloud. If you do so, tenants will not be able to deploy virtual machine roles using the VM Clouds service.
HOW-TO is described below
Service Provider Foundation service account
The Service Provider Foundation service account must be added to the administrator user role in the VMM server
To successfully complete all steps in this mini-guide
Create RunAsAccount in VMM and assign Administrator Role
In this section we create BASIC VMM cloud only for demo purposes.You have to carefully plan/design your cloud components.
Add hosts to host group (VMs and Services –> right click on host group name –> add hyper-v hosts and clusters“) or PS:
#In my case, host group called as All Hosts and 1 member hv01
$runAsAccount = Get-SCRunAsAccount -Name "Administrator"
$hostgroup = Get-SCVMHostGroup -Name "All Hosts"
Add-SCVMHost -ComputerName "hv01.domain.com" -VMHostGroup $hostgroup -Credential $runAsAccount