Troubleshooting Windows Azure Pack - Plans and Subscriptions

Hello Readers

Next topic on our Windows Azure Pack (WAP) Troubleshooting tour is "Plans and Subscriptions". Briefly Plan, Subscriptions and Resource Providers can be described in the following way:

Tenant: One or more individuals consuming services from the Windows Azure Pack via a subscription.

Plan: Contains one or more services (Resource Providers: VM, DB, Web, Service Bus) offered and the quota for each service. Subscriptions, Add-on and Resource Providers are all associated to a plan.

Subscription: The mapping between a tenant and one or more plans.

Resource Provider: Services offered within Windows Azure Pack with mapping to resources (e.g. Web Sites or Virtual Machines).

 

Pre-requisites for this blog post:

  • Windows Azure Pack is installed.
  • VM Cloud Resource Provider is configured.
  • Service Provider Foundation is installed and configured.
  • Virtual Machine Manager is installed and configured.

 

The areas we will walk over in the blog post are the following:

  • Gallery Item is part of a plan but is not showing in the Tenant Portal.
  • One or more VM Templates not showing in the list for a Plan.
  • No Networks are showing for a Plan.

 

Let's get started.

 

Gallery Item is part of a plan but is not showing in the Tenant Portal.

Error: A Gallery Item (Web Server (IIS)) is added to a plan but does not show in the tenant portal that is subscribed to the plan.

To verify the error do the following:

  1. Open WAP Admin portal as administrator. (e.g. https://wap01.fabrikam.com:30091)

  2. Select Plans and click on the Plan for which you want to add a VM Role (e.g. Contoso) .

  3. Under the plan services select Virtual Machine Clouds.

  4. Scroll down to Gallery

  5. Verify that the Gallery Item shows in the list of Gallery Items.

     

    Figure 1: List of Gallery Items that is added to a plan in the WAP Admin Portal

  6. Login into the WAP Tenant Portal with a subscription that has access to the plan that was just updated with IIS Server Gallery Item. (e.g. admins@contoso.com @ https://wap01.fabrikam.com:30081)

  7. Click New

  8. Select Virtual Machine Role

  9. Select From Gallery

  10. Verify that the Web Server (IIS) is not showing in the list:

     

    Figure 2: List of Gallery Items available in the WAP Tenant Portal

 

Cause: TheGallery Item has not been made public and can therefore it cannot be seen in the WAP Tenant Portal.

 

Solution: Make the Gallery Item public in the WAP Admin Portal.

To make the Gallery Item public do the following:

  1. Open WAP Admin portal as administrator. (e.g. https://wap01.fabrikam.com:30091)

  2. Select VM Clouds and Gallery Items.

  3. In the list of Gallery Items, check that the Web Server state is set to Private, as this would explain why it's not showing in the tenant VM Role list.

     

    Figure 3: Shows a full list of Gallery Item in the WAP Admin Portal

    Note that Web Server is set to Private.

  4. Select Web Server and click and select Yes

  5. Verify that Web Server has changed from Private to Public

    Figure 4: Shows a Gallery Item being set to Public state

  6. Login into the WAP Tenant Portal with a subscription that has access to the plan that was just updated with IIS Server Gallery Item. (e.g. admins@contoso.com @ https://wap01.fabrikam.com:30081)

  7. Click New.

  8. Select Virtual Machine Role.

  9. Select From Gallery.

  10. Verify that Web Server now shows in the Gallery List

     

    Figure 5: Showing a Web Server Gallery (IIS) in the WAP Tenant Portal

 

One or more VM Templates are not showing in the list for a plan

Error: One or more VM Templates are not showing in the list of templates that can be added to a plan, but is listed in VMM Library.

Cause: The VM Template is not "tagged" with an Operating System Profile and therefore it does not show up in the list of VM templates that can be added to a plan.

To verify the issue do the following:

  1. Logon to the VMM Server as Administrator.

  2. Open the Virtual Machine Manager Console.

  3. Select Library.

  4. Under Templates Select VM Templates.

  5. Locate the VM Template you want to add to a Plan in WAP.

     

    Figure 6: List of VM Templates in Virtual Machine Manager

     

  6. Open the WAP Admin Portal.

  7. Select Plans.

  8. Click on a Plan (e.g Contoso).

  9. Under the Plan Select Virtual Machine Clouds.

  10. Under Templates click Add Template.

     

    Figure 7: List of VM Templates that can be added to a plan.

    Note: You might see that the VM Template is not in the list.

     

Solution: Update the VM Template in VMM with an Operating System Profile.

  1. Logon to the VMM Server as Administrator.

  2. Open the Virtual Machine Manager Console.

  3. Select Library

  4. Under Templates Select VM Templates.

  5. Locate the VM Template you want to add to a Plan in WAP.

  6. Double click on the VM Template.

  7. Verify that the VM Template has an Operating System.

     

Figure 8: VM Template with an OS Profile Selected

Figure 9: VM Template with no OS Profile

 

Note: Only VM Templates with a defined Operating System can be listed in WAP.

 

  1. Create a new VM Template pointing to the same resources where an Operating System profile is selected.

     

    Figure 10: List of OS Profiles that can be selected when creating a VM Template in the VMM Console.

     

  2. Save the template.

  3. Go to the WAP Admin portal.

  4. Select Plans.

  5. Select Virtual Machine Clouds.

  6. Click Add Template.

  7. Select the New template from the list.

     

    Figure 11: List of VM Templates that can be added to a plan in the WAP Admin Portal

     

  8. Save the Plan

 

No Networks are showing for a Plan

Error: No Networks are showing when creating a new plan or adding networks to an existing plan.

Figure 12: No Networks can be added under the Northwind Plan in the WAP admin Portal

 

Cause: Only VM Networks can be added to a plan and only VM Networks that are connected to a logical network that is associated to a VMM Cloud for which the Plan uses, can be added to a plan.

To verify the issue do the following:

  1. Open the VMM Console.

  2. Select VMs & Services.

  3. Expand Clouds, Right click on the cloud that a Plan is mapped to in WAP for which a network should be added. (e.g. Northwind)

  4. Select Logical Networks

  5. Verify that at least one logical network is selected.

     

    Figure 13: List of Logical Networks that can be used for Northwind cloud

    Note: If no Networks are selected this would be the reason why no VM Networks can be selected in the WAP Plan for Northwind.

     

Solution: Verify that the logical network (on which the VM Network has been created) is added to the VMM cloud.

The following requirements must be true before VM Networks can be added to a plan:

  • Logical Network must have minimum one binding to a physical host adapter before it can be added to a VMM Cloud.
  • VMM Logical Network must be assigned to the VMM Cloud that the WAP plan is using.
  • VM Network must be connected to a Logical Network that is assigned to the same VMM Cloud used in the statement above.

In the scenario we want to add a VM Network called Nortwind VM Network to a Plan and then have a tenant login to the WAP Tenant portal and select the Network for a VM.

To do this, do the following:

  1. Open the VMM Console.

  2. Select Fabric.

  3. Select a logical network that Northwind Tenant can use (E.g. Northwind PA) and verify that it has an IP Pool.

     

    Figure 14: Logical network and IP Pool shown in the Virtual Machine Manager console

     

  4. Right click, select View Dependent Resources and verify that the logical network has minimum one host assigned.

     

    Figure 15: List of Dependent Resources for a Logical Network in the Virtual Machine Manager Console

     

  5. Select VMs and Services.

  6. Right click on the Cloud used by the WAP Plan and select properties.

  7. Click Logical Networks and select a logical network identified above (e.g. Northwind PA), Click OK to save the change.

  8. Right Click on VM Networks and select Create VM Network.

  9. Assign a name for the VM Network (e.g. Northwind Tenant Network) Select the Logical Network just added to the VMM Cloud (e.g. Northwind PA), Click Next.

  10. Select Isolate using Hyper-v… and click Next.

  11. Provide an IP Subnet and click Next.

  12. Click Next to Connectivity and Click Finish.

  13. Right Click on the newly created Network and select Create IP Pool.

  14. Specify a name (e.g. Northwind CA IP Pool) and click Next.

  15. Click Next to IP address range, Click next to gateway, DNS WINS and Click Finish under Summary.

  16. A VM Network with an assigned IP Pool should show in the VM Network list.

     

    Figure 16: VM network and IP Pool shown in the Virtual Machine Manager console

     

  17. Open the WAP Admin Portal.

  18. Select Plans and Select the plan that uses the VMM Cloud for which the VM network was created (e.g. Northwind).

  19. Click Virtual Machine Clouds.

  20. Verify that the Plan maps to the VMM Cloud where the logical network was added.

     

    Figure 17: VMM Server and Cloud mapping for a plan in the WAP Admin portal

     

  21. Scroll down to networks and verify that Add networks now shows.

  22. Click on Add Networks and Select the VM Network created earlier.

  23. Verify that at least one Template is added to the plan.

     

    Figure 18: List of Templates that is added to a plan in the WAP Admin Portal

     

  24. Save the plan.

  25. Login to the WAP Tenant Portal as a subscribed user to the plan (e.g. admin@northwind.com).

  26. Click New.

  27. Select Standalone Virtual Machine > From Gallery.

  28. Select a Template.

  29. Specify VM Name, Password and click Next.

  30. Verify that the new added network can be selected from the drop down list.

    Figure 19: List of networks a VM can be connected to, during provisioning of a VM in the WAP Tenant Portal

  31. Click Ok to provision the VM.

     

Summary

In this blog post we learned how we can troubleshoot Windows Azure Pack & Plans and Subscriptions.

We looked at the following examples:

  • Gallery Item is part of a plan but is not showing in the Tenant Portal.
  • One or more VM Templates not showing in the list for a Plan.
  • No Networks are showing for a Plan

Hope this blog post has been helpful.

As always let me know if you have run into any challenges which are not described here and I'll be happy to add for others to consume.

Happy deploying Windows Azure Pack with Plan and Subscriptions.