Wednesday, February 27, 2013

Windows Azure Services for Windows Server 2012 - We're getting there!


Windows Azure Services for Windows Server 2012 – Useful

A couple of months ago, I blogget about project “Katal” – or Windows Azure Services for Windows Server 2012 as it’s officially called.


I’ve been working close with a couple of service providers lately, and many of them have shown deep interest of this beautiful portal with such a rich user experience.

To get it straight, it is the same experience as you get on windowsazure.com

This blog post is just a teaser to get you interested to play with it on your own, showing how the tenant portal presents stuffs to the tenant administrator, while Orchestrator with SPF, Virtual Machine Manager and Windows Server 2012 with Hyper-V are running the show in the background.

First of all, the tenants access the portal and signs-up using one of my available stamps that I have made public.
They will get an e-mail with logon information – and yes, I can secure this so that they would have to authenticate themselves prior to getting access.

Once this is done, they can logon to the portal, getting the same guidance as you would get the first time you logon to windowsazure.com
As an experienced cloud guy, I would start by creating a virtual network before I deploy some virtual machines.


As you can see, I am planning to scale a bit, so I got just a few IP addresses there ;-)
 

Next, I’ll deploy a virtual machine based on a template I have created in VMM and made available as part of my stamp.

As you can see, I have created VM network and is currently deploying a virtual machine.
 

What’s going on under the hood?

If we take a look at the VMM side, we can first look for some new user roles.

The portal creates these when the tenants have signed up for a stamp.

Next, we can see at our VM networks. We have now a new VM network that is based on a logical network. This is something the VMM administrator will configure during the network fabric setup.
 

And last, the virtual machine is deployed to the cloud we have made available in the portal.
 
That's all for now, but I will cover the details over the next blog posts, to hopefully get you started with Windows Azure Services for Windows Server 2012. If you have any questions, feel free to comment on this post.
 
-kn

4 comments:

Anonymous said...

Kristian,

Can you explain why you have created VM Networks (Cluster Vm Networks, Iscsi Network, live Migration, SMB VM Network) which are only visible to your Hyper-V hosts?
From what I read on technet the VM network's are only used by virtual machines

What I have found out is that the SMB VM network will need to have a DNS/GW and allow clients to connect in Failover Cluster, is this correct?

Kristian Nese said...

Yes. I have created thos VM networks since they are related to the virtual network adapter (created with the logical switch) as well, and connected there. Is an additional layer of abstraction, and is associated with a logical network.
By creating these VM networks, I can map each virtual network adapter on the host to the right network, and also apply my QoS settings for the traffic.
SMB wit multi-channel will require DNS yes and allow clients to connect in failover cluster.

Matt White said...

Hi. Is there any news of a network virtualisation gateway that can effectively route traffic from an NVGRE isolated LAN to the wider world? This is the missing link!

Kristian Nese said...

Nexus v1000 from Cisco, and other vendors are working on something here. Will post something asap, when it's ready.

-kn