Windows Azure Pack–Creating a Plan for VM Clouds
After you set up the connection from the Windows Azure Pack to the Service Provider Foundation and the the Virtual Machine Manager (VMM) you need to create a plan that your customers can subscribe to. The plan defines the capacity boundaries and specifies on which VMM cloud the VMs should be placed.
To create a plan start the WAP Admin Portal go to Plan and click on Create a new Hosting Plan
Enter a name for the plan and select the previous configured VM cloud service.
Finish the Plan wizard. Now the created plan appears on in the plans list.
Next the plan needs to be configured. Click on the plan name, here VM Server Plan. This will open the dash board for the plan. In the middle of the page you find the plan services:
Click on the name of the plan service, in my example Virtual Machine Clouds. This will open the virtual machine clouds configuration page where you select the VMM server and the VMM cloud that you want to include in the plan.
In the usage limit section you can configure the usage limit for the plan:
In the networks section you need to add the network that the plan will use:
In the hardware profile section add the hardware profiles from VMM that you want to offer in the plan:
In the template section add the template you want to make available. You can offer multiple templates:
Finally you can add additional settings that define what action on the VMs can be executed:
Now save the plan.
The final step in your virtual machine service is to create a plan where you configure the capacity and capability settings of the virtual machine you want to offer to your users. You should name the plan in a way that is self describing to your users or customers to help them choose the right plan. Plan should make it easy to your customers to find the right service for their needs.
Gunter Danzeisen hat einen Abschluss in Informatik der Technischen Schule. Zusätzlich ist er zertifizierter Microsoft System Engineer (MCSE 2003) sowie zertifizierter Microsoft IT Professional (MCITP 2008).