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

 

Comments

comments