Monthly archives "January 2014"

Building Private Cloud – Part 3

Now we have the Hyper-V Clusters ready. We have the Fabric Configured to have a Logical Switch and VM Networks for each group.

The next step is to create a Cloud for each subsidiary group. The high level steps are as below.

1) Create Private Cloud for each subsidiary group with the appropriate network for each Cloud

2) Create Self Service User Role for each Group

Lets go in detail.

1) Create Private Cloud for each subsidiary group

Private Cloud will be the logical boundary for the consumer. Consumer will not be seeing anything beyond this stage. End user will create VMs on the private cloud.

Navigate to SCVMM -> VMs and Services – > Clouds

Click on Create Cloud

Create Private Cloud

Create Private Cloud

 

In the next page, Select the appropriate host group which will be used by this Cloud.

Create Private Cloud - Select host group

Create Private Cloud – Select host group

 

Create Private Cloud - Select Logical Network

Create Private Cloud – Select Logical Network

 

Proceed with the next steps and configure the optional components.

Select the Storage Classification.

Create Private Cloud - Select Storage

Create Private Cloud – Select Storage

 

In the next page, Select the Library Share which will be used by this cloud.

Create Private CLoud- Select Library

Create Private Cloud- Select Library

 

In the next page, Set the maximum capacity for the entire cloud.

Create Private Cloud - Set Capacity

Set  the maximum capacity

 

Select the appropriate capability profile.

Create Private Cloud - Set capability profile

Create Private Cloud – Set capability profile

 

Finally, Verify the summary and proceed.

Similarly, we need to create a Private Cloud for S2-IT and S3-IT. While creating S2-IT-PriviateCloud, We need to select the appropriate Logical Network we created for S2-IT and while creating S3-IT-PriviateCloud, we need to select the appropriate Logical Network we created for S3-It.

 

With this, We are done with the creation of a Private cloud. Now we need to set up the access using a Self Service User Role, allocate the templates, Hardware Profiles, Gust OS Profile etc which will be covered in the next part. The below illustration gives a brief on the different fabric components which are getting linked to form a Private Cloud.

illustration - Linking the network componet with cloud

 

 

Building Private Cloud – Part 2

I have detailed on create a Hyper-V Cluster using SCVMM 2012 R2 in one of my previous posts (Part1 and Part2). However, Don’t configure anything related with Fabric based on those posts.

The critical part of the configuration is fabric – especially Network. Hence, I would like to detail about that on this part.

At this stage, I had my Hyper-V cluster built using SCVMM 2012 R2. I will be completing the fabric configuration specific to Private Cloud now. Based on the requirement we had on the Part-1, I am allocating one VLAN per S-IT.

S-IT GROUP VLAN
S1-IT 10.0.21.0/24
S2-IT 10.0.22.0/24
S3-IT 10.0.23.0/24

Individual VLAN will give us the flexibility to have strict network level restrictions based on the requirements. Each VLAN is configured with a DHCP scope of 10 IPs, so that the VMs deployed through a template will get an IP and be joined to the domain. Once deployed, The S-IT team should be able to change the IP to a static IP with in their assigned range.

The high level steps which will be preformed are

1) Creating Logical Network for S1-IT, S2-IT and S3-IT with site/VLAN information

2) Creating UpLink Port Profile which will be used for the Logical Switch

3) Creating Logical Switch and select the UpLink Port Profile

4) Creating VM Networks for S1-IT, S2-IT and S3-IT and link with the corresponding Logical Network

5) Assigning Logical Switch for the Phyical Hosts

6) Creating Virtual Network Adapters for S1-IT, S2-IT and S3-IT on top of the Logical Switch and link them to the corresponding VM Network

Here is a quick illustration for you to relate each different components involved.

 

Network Components for building private cloud

Network Components for building private cloud

 

So lets go in detail.

1) Creating Logical Network for S1-IT, S2-IT and S3-IT with site/VLAN information

As we planned, each S-IT will be defined as an independent Logical Network.

Navigate to Fabric -> Networking -> Logical Network

Create a new Logical Network for S1-IT and define the Site with the assigned subnet and VLAN.

SCVMM 2012 R2 Fabric Configuration

LOGICAL NETWORK for S1-IT

On the Network Site page, create a new site for S1-IT , Link with the correct host group which has the HyperV Physical hosts and then enter the Subnet /VLAN details.

LOGICAL NETWORK - DEFINE SITE - SITE-S1-IT

LOGICAL NETWORK – DEFINE SITE – SITE-S1-IT

 

Click on next and Confirm after verifying the summary.

Similarly, We need a Logical Network for S2-IT.

SCVMM 2012 R2 Fabric Configuration

LOGICAL NETWORK – S2-IT

On the Network Site page, create a new site for S2-IT , Link with the correct host group which has the HyperV Physical hosts and then enter the Subnet /VLAN details.

SCVMM 2012 R2 fabric configuration

LOGICAL NETWORK – DEFINE SITE – SITE-S2-IT

Click on next and Confirm after verifying the summary. Create a similar Logical Network for S3-IT and set the right subnet/VLAN details.

2) Creating UpLink Port Profile which will be used for the Logical Switch

As you know, Uplink Port Profile will be used along with the logical switch and define the teaming mode and algorithm used.

Navigate to SCVMM -> Fabric -> Networking -> Port Profiles

Create a new Port Profile. Configure the Port Profile as an Uplink Port profile. Set the teaming mode as Switch Independent and Algorithm as Dynamic.

PortProfile-Cloud-Uplink

PortProfile-Cloud-Uplink

In the network configuration page, Select the appropriate sites where this Port Profile will be used. We need to select the Sites which has been created for S1-IT, S2-IT and S3-IT.

PortProfile-Cloud-Uplink-NetworkSites

PortProfile-Cloud-Uplink-NetworkSites

Click on Next and proceed after verifying the summary.

3) Creating Logical Switch and select the UpLink Port Profile

Logical Switch is an equivalent to HyperV switch. While Logical Switch is configured on the host, The network interfaces allocated for the logical switch will be used to create a HyperV Switch. The teaming mode of interfaces is defined in the Port Profile which will be linked with the Logical Switch.

 

SCVMM 2012 R2 Priviate Cloud

Logical Switch Creation

On the next screen, We need to add the UpLink profile. Select the one which has been created for the Private Cloud. Verify the site names and host group again.

 

LOGICAL-SWITCH-PRIVIATECLOUD-UPLINK

Proceed with further steps.

4) Creating VM Networks for S1-IT, S2-IT and S3-IT and link with the corresponding Logical Network

VM Networks will be used for to create Virtual Networks on top of the Logical Switch. Each S-IT group will need a VM Network which will be linked with the Logical Network we defined in Step 1.

Navigate to SCVMM ->VMs and Services -> VM Networks

Create a New VM Network and assign the corresponding Logical Network.

Configuring SCVMM 2012 R2 Fabric

VM Network for S1-IT

Click on NEXT and then Finish after reviewing the Summary.

Similarly, Create VM Network for S2-IT and link with the respective logical network for S2-IT.

Virtual Netowrk SCVMM 2012 R2 Fabric

Virtual Network for S2-IT

Similarly, Create one for S3-IT and link with the logical network of S3-IT.

5) Assigning Logical Switch for the Physical Hosts

On each Hyper-V host in the cluster or each stand alone host, the Logical Switch needs to be configured. Logical Switch will create a HyperV Switch with the defined Network Interfaces and also take care of teaming based on the Uplink port profile, if multiple interfaces are present.

Navigate to SCVMM -> Fabric ->Servers -> HostGroup -> Cluster ->

Select a node and navigate to Properties -> Virtual Switches

Click on New Virtual Switch -> New Logical Switch

Select the correct logical switch from the drop down list.

Select the Network Adapters which will be used for HyperV data.

Select the appropriate UpLink Profile.

 

Adding Logical Switch to HyperV host

Adding Logical Switch

Once done, Click on OK.

Do this activity on all HyperV Hosts which will be part of this Cloud.

6) Creating Virtual Network Adapters for S1-IT, S2-IT and S3-IT on top of the Logical Switch and link them to the corresponding VM Network

Next step is to Link the VM Network created for each S-IT with the Logical Switch. This is done using the option of Virtual Network Adapter which will be created on top of the logical switch.

Navigate to SCVMM -> Fabric ->Servers -> HostGroup -> Cluster ->

Select a node and navigate to Properties -> Virtual Switches

Select the Virtual Switch  and Click on New Virtual Adapter.

Enter the appropriate name for the virtual adapter.

On Connectivity – Click on Browse and select the appropriate VM Network. VLAN details will be listed by default based on the information on VM Network.

SCVMM 2012 R2 Fabric Configuration

Virtual Network Adapter

Add Virtual Network Adapter for each S-IT.

Virtual Network Adapter

Virtual Network Adapter

Similarly, Create one Virtual Network Adapter for S-IT3 and link with the appropriate VM Network.

Thats the end of Part-2.

 

 

Building a private cloud – Part 1

Its almost three months I installed SCVMM 2012 R2. I had invested atlest 10 hours a day on learning this product. And today when I look back, I am happy to see the progress which I made. I would like to share my experience how I made a private cloud. As I always say, I am still learning this product. My intention is not to say that you should do like this, but to share that this is how I made it working – though it may not be the optimal way.

The ultimate AIM I had in my mind for using SCVMM are

  • Building a private cloud
  • Make use of Network Virtualization

I am still trying to see how to get network virtualizaiton working and will post the details once I am successful.

Lets go to the first part in detail.

Definition of Cloud Computing

A computing capability that provides an abstraction between the computing resource and its underlying technical architecture (e.g., servers, storage, networks), enabling convenient, on-demand network access to a shared pool of configurable computing resources that can be rapidly provisioned and released with minimal management effort or service provider interaction.” This definition states that clouds have five essential characteristics: on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service. Narrowly speaking, cloud computing is client-server computing that abstract the details of the server away;one requests a service (resource), not a specific server (machine).

Definition of a private cloud

Private cloud is virtualized cloud data centers inside your company’s firewall. It may also be a private space dedicated to your company within a cloud provider’s data center. An internal cloud behind the organization’s firewall. The company’s IT department provides software and hardware as a service to its customers — the people who work for the company. Vendors love the words “private cloud.”

 

Source – http://cloudtimes.org/glossary/

That being said, My goal on building a private cloud is to have the five defined characters. On-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service. Out of this, Measuring service will come while we plan for a charge back – which I didn’t plan. I had Microsoft Azure in my mind which gave me a feel of a Cloud. From an consumer standpoint, Its not mandatory to know where the service is hosted, what technology is behind the solution, what hardware is being used etc. Consumer should get a pool of compute resource which can be used using a self service mechanism.

 

Flow - Cloud 1

 

To visualize this, I made a scenario here. InsideVirtualization.com is a company who is into some business. Company has three subsidiaries. Management don’t want to invest on dedicated IT Infrastructure for the subsidiaries. However, the IT team in the subsidiary should be able to create/manage without depending of the main IT Team. At the same time, Management enforce that the IT team in the subsidiaries should be only accessing/managing the resources entitled to them. The Finance team would like to have the service allocated based on the budget allocated for IT Infrastructure for each subsidiary. The IT security team dont want the servers/services provisioned for subsidiaries to communicate with each other, but should be able to communicate with a minimal set of servers/services in the Core IT.

😀 , The scenario tends towards question asked in Microsoft certification.

To make this requirement working, I am building a private cloud.

Once we have a successful private cloud, here is what we can achieve.

  • S1-IT (Subsidary1 IT Team) will get a cloud name S1-Priviate-Cloud
  • S1-IT will be able to use a self service console to create/manage the VMs provisioned
  • S1-IT will only be able to manage a Virtual Server entitled to the S1-Priviate-Cloud
  • S1-IT will only be able to use the compute resources allocated for their cloud
  • S1-IT will be only seeing the components up to the Private cloud. Everything behind will be hidden.
  • S1-IT will heave the flexibility to mix and match the total resources allocated for the cloud. Based on approvals, S1-IT could request to get more resources allocated to the cloud.

Similarly, S2-IT and S3-IT will also get an private cloud.

I will come up with more details in the next part.

Keep watching my blog. If you feel that I am wrong on any of the statements, Please feel free to put a comment or use Contact page.

Cheers

 

Expanding a CSV Volume

Recently, I had a challenge with free space on one of the CSV Volume. The immediate idea is to expand the volume.  Is that viable?

Yes. Here is how I did.

Expand the volume on storage side first.

As CSV is a cluster resource, The Owner of the resource will have the privilege to perform most of the tasks. So identify the owner of this CSV Disk from fail over cluster. It should be definitely one among the servers in the group. Perform the next steps from the Owner node.

Once the volume is successfully expanded on storage side, we should be seeing the change in disk management like below. The added space will be marked as unallocated space.

 

Expanding a CSV Volume

Verifying DISK on Disk Management

 

The increase in capacity will be visible on the Failover Cluster Manager. However, the usable space will still be the old until we expand.

Expanding CSV Volume

Verifying DISK capacity fro Failover Cluster Manager

 

The next step is to extend the volume from Disk Management. Please note – this option will be grayed out if not logged into the Owner node.

Expand CSV Volume

Extend Volume

 

Go ahead with extending.

Extend Volume - Size Available

Extend Volume – Size Available

 

Expanding CSV Volume

Disk Expanded

 

Great ! This change should be reflected even in Fail-over Cluster manager as well as SCVMM.

Expand CSV Volume

Verifying after Expanding CSV

 

 

Expand CSV VOlume

After Disk Expansion – Change reflected on SCVMM

 

I had VMs running on the CSV Volume and all was safe ! However, I did the testing only for expansion. Shrinking the disk even throws a warning that data may erased and hence, couldn’t try. Will test it shortly :D.

 

Windows Server 2012 – Windows update failed due to issues with KB2871690

Few days back, I did faced issues on Windows Server 2012 failing on Windows Update and put a post on my blog on it.

Further investigation made me to conclude that the issue is specific to one particular patch – KB2871690. While we select the entire updates, KB2871690 fails which revert the entire updates.

If we exclude this single update, the entire set of updates can get installed successfully in one stretch.

 

Exclude KB2871690

Exclude KB2871690

 

All went well with out KB2871690.

Update successful without KB2871690

Update successful without KB2871690

 

I even tried the standalone installer, but no luck.

Standalone Installation KB2871690

Standalone Installation KB2871690

 

Standalone Installation KB2871690 Failed

Standalone Installation KB2871690 Failed

 

Here is the error I see for stand alone installer.

Standalone installation - error

Standalone installation – error

This may be specific to my VM. But I did tested on a second fresh VM and was sucessfull on updates after excluding  KB2871690.

I am checking this further and will update if I get some clue.

 

Windows Server 2012 – Failure configuring windows updates. Reverting changes.

I was trying to create a Windows 2012 Template for SCVMM 2012 R2. As the normal process I follow, Started a full Windows update just after the OS installation.

~75 updates was present including optional updates. The first attempt failed and it took few minutes to revert the changes and get the server rebooted.

Failure configuring windows update

The next attempt was to go for a partial update. First, I only opted optional update which went successful and server got rebooted.

The second attempt was to take half of the updates which was even successful.

The third attempt was to use the entire pending list which again failed. Suspecting one of the update in the list is having some trouble.

Investigating more and update here if I find some issues.

———————————————————————————————————

Please check my latest post for update on this issue.

 

SCVMM 2012 R2 – VLAN Information missing on the Network Adapter Configuration

Observed this issue last week. The VLAN ID in the Network Interface details inside the properties of a VM is not showing up as expected.

Here is the scenario.

SCVMM 2012 R2 with Windows Server 2012 R2 HyperV.

VMs are deployed and all works well. The Virtual Switch is configured as a Trunk and each VM needs to specify the VLAN ID. All well, However the VLAN ID of a VM is not getting displayed in the VMM console.

VLAN ID Missing on VM Properties

VLAN ID Missing on VM Properties

 

However, If we verify the VLAN ID of the same VM over this command let, its properly configured.

VLAN ID through command

VLAN ID through commandlet

 

Now lets try to change the VLAN ID through SCVMM Console.

VLAN ID Change through SCVMM

VLAN ID Change through SCVMM

I changed the VLAN ID to 66 and here is the confirmation of the job status.

Change VLAN through SCVMM - Job successful

Change VLAN through SCVMM – Job successful

 

After this change, I verified that the new VLAN got updated on the VM using the commandlet.

 

VLAN ID Change - Confirmation over Commandlet

VLAN ID Change – Confirmation over Commandlet

 

Going back to the SCVMM, The VM properties still don’t show that VLAN id is enabled and configured.

 VLAN-ID-CHANGE-Still-missing


VLAN ID CHANGE – Still missing

 

However, if we go to the connection details, VLAN ID is displayed.

VLAN ID Change - Connection details

VLAN ID Change – Connection details

 

This may be a minor bug. I have opened a case with the Microsoft support. I will update once I get more details on this.