First of all, many people believe that a cloud computing is an all-or-nothing “thing”, and that you either have it, or you don`t.

And this is – of course not true.

It`s not a secret that I work a lot with Microsoft technology. Both the products that embraces the public cloud, but most of the time, the private cloud.

Most of the people I speak with have some sort of understanding that Windows Azure is located in the public cloud – somewhere, and somehow. That is great, or at least a beginning. But if the talk moves toward the thing called “private cloud”, people seem to tune out.

Who should know what a Private Cloud is, and why should they care?

Recently, I got the honor to be made as a moderator In the SCVMM forum, and I`m now able to underline the important foundation of a private cloud for the persons who asks the questions. It may be an IT-pro, it may be a developer, it may also be a farmer – I don`t know, but they get their answers.

The most common misunderstanding is as follows:

“We got server virtualization, so yes, we have a Private Cloud”

Microsoft`s approach to a private cloud is much more than “just” server virtualization.

So far, this article may sound a bit disorderly, so once again I will try to start at the beginning.

Cloud computing is far more than server virtualization.

A highly virtualized infrastructure is not cloud computing, but an important stepping stone towards cloud computing. You can even do cloud computing without virtualization. But who has the money for that, and who does not want to use virtualization in the first place, even if they discard the entire cloud-extension?

For that`s what it is. A private cloud is an extension to your already highly virtualized datacenter. It brings in some important and useful mechanism into your organization.

We`re talking about being able to scale out and in, the users can provisioning their own resources – when they need it. Things are fault tolerant at many layers and most important – your business saves money because a cloud is optimizing the resources, and gives the organization a chance to respond to peaks, new business requirements, and new markets. And add automation to all the processes, and you`ll see that it`s far more than just server virtualization.

Tuesday, August 9, 2011

As I have stated before, SCVMM 2012 had some major improvements all over the place, and also in the Library.

Another interesting feature that I have found quite useful, is the possibility to create “Capability Profiles”.

For example; you have a Hyper-V Cluster that also plays a part in one of your defined clouds. You want to make sure that everything that is put onto that cloud, are configured as Highly Available.

There are many reasons for that, especially if you are dealing with Dynamic Optimization and Power Optimization – you want your resources to be available, and not directly attached to a physical server.

·Processor Range (This may vary from hypervisor to hypervisor. Hyper-V is currently limited to max 4 vCPU, while VMWare and Xen supports so much as 8 vCPU)

·Memory Range (This one also vary from hypervisor to hypervisor)

·Microsoft Synthetic Video Adapter (For Hyper-V only)

·DVD Drive Range (Number of DVD drivers)

·Shared Image Mode (For Hyper-V only)

·Bus Configuration (Contains configuration of the virtual disks, meaning if the profile should allow Fixed Disk Mode, Dynamic Disk Mode etc. You may for example not want your user to create VMs with differential disks on your cloud, so you can specify that it is not allowed)

·Network Adapters (Minimum and maximum vNICs)

·Network Optimization (For Hyper-V only)

·Advanced (Here you can configure the profile to enforce Highly Available VM Mode, and define it as required)

Create a Capability Profile for a Hyper-V Cloud, that requires VMs and services to be configured as Highly Available.

4.Name the profile with whatever you want, and remember to type a realese. Click “Next”

5.In the next window, select “Hyper-V virtualization host” in the “Fabric Compatibility”.

6.Scroll down to the last option located under the “Advanced” section, and mark the Highly available VM mode field as “Required”.

Now, you have created a Capability Profile that requires the resources to be Highly Available. But this profile needs to take place somewhere. To put it into action, we navigate further to one of our clouds.

In the “VMs and Services” pane, right click your cloud, and select “Properties”.

If you take a closer look, you will recognize the “Capability Profiles” option down to the left.

Click here, and mark the newly created Capability Profile you just created.

Once this is done, click “ok” and you have made the change.

What next?

You will need to modify your resources in the Library, to match this Capability Profile – as long as they should be placed on this cloud. This includes Hardware Profiles and VM/Service Templates.

I will provide you with a PowerShell script to update your resources one day, when I have a little more time to spend on this one.

Thursday, August 4, 2011

I am currently testing the SCVMM 2012 BETA, and I want to share how you collect SCVMM traces.

(This applies to both SCVMM 2008 R2 and SCVMM 2012)

I had an issue that when I added a WSUS server to the Fabric, the VMMservice crashed. It only crashed when it was properly configured. That means, if I configured the wrong TCP-port for the WSUS connection, I got a correct error message. But when I hit the high notes, it crashed with no mercy.

The recipe that Carmen Summers (the Program Manager of SCVMM) has made available:

From what computer should I collect the traces:

If it`s a console crash issue.

·Please collect the traces from both the computer where you run admin console, and your VMM Server.

If it’s an “Add Hosts” issue,

·Please collect the traces from the VMM server;

If it’s a host status (Needs Attention) or VM issue,

·Please collect the traces from both the VMM server and the host in question.

·In a command window on the machine that you want to capture VMM tracing, run “odson.reg” and “odsflags.cmd 255”. (If you need to collect traces for both VMM Server and the host or the Web server, make sure to run these commands on all computers.)

·Open DebugView and run it as administrator, make sure that in its Capture menu, you have both "Capture Win32" and "Capture Global Win32" checked. You should be able to see tracing from the VMM components showing up in the DebugView. (If you need to collect traces for both VMM Server and the host, make sure to do these steps on all computers.)

A Hyper-V Cluster is a major part of the private cloud, and is combination of the physical resources configured in the Fabric. As I have written several times before, SCVMM 2012 gives you the possibility to manage your entire virtual datacenter with a single console. This includes deep storage integration through the SMI-S protocol, out of band management so that you can deploy bare metal Hyper-V servers, and to use them in conjunction with Power Optimization and Dynamic Optimization (Dynamic Optimization does not require out of band management).

In a nutshell, you are able to do the following to get your private cloud ready:

1)Deploy SCVMM 2012

2)Deploy bare metal Hyper-V servers

3)Deploy Hyper-V Clusters

4)Assign LUN`s, CSV, and networking

5)Take portions of the physical resources in the Fabric, and assign it to a private cloud that you define

6)Assign the cloud to your users. (Normally after you have configured some available and usuable resources in the library)

Another thing to note, is that SCVMM 2008 R2 did not let you create stand-alone VM`s on the cluster, but you`re able to do this in SCVMM 2012. This is ideal when it comes to the domain controller-dilemma- since you should not locate your DC`s on a CSV only, but have them outside the cluster, so that the cluster would come online again after a complete shutdown. In other words, you can put them on dedicated LUN`s, or on DAS. For more information, see the Failover Clustering and Domain Requirements (by example) article.

Another feature that is worth mentioning, is the ability to patch your cluster with a dedicated WSUS server. This one will save you some serious amount of time, since there is no need for manual input.

Again, in a nutshell, this is what you would do:

1)Define a baseline of patches that WSUS should deploy

2)All the servers in the Fabric would be scanned to determine which hosts are not compliant

3)The non-compliant hosts are identified

4)An orchestrated patching workload will place a node into “maintenance mode”, live migrate the VMs to the other nodes in the cluster, patch the node, remote it from “maintenance mode”, and move the VM`s back

So, with SCVMM 2012 on its way, we can look forward to a more simplified day-to-day job.

From now on, this will be the tool, not just to manage your virtual infrastructure and clouds, but also the starting point when you are dealing with deployment of the various servers, storage, and networks you are in control of.