Tuesday, June 14, 2011

Cloud Computing… obviously…

Ok, let‘s have a go. 2011 started well. I remember the PDC back in the autumn of 2010, where Microsoft announced some new features on the Windows Azure platform. –The VMRole, along with remote desktop connection and Azure Connect. Let‘s raise our flags, and celebrate the possibility to use Microsoft‘s datacenters as an IaaS (Infrastructure – as a Service). No, it was not the intention by Microsoft. It should be a simplified way to move your legacy application to their cloud. Microsoft Public Cloud is nothing else but a PaaS (Platform – as a Service). The reasons for this, are is some cases very complex, and in other cases very simple. To work with Windows Azure, you should have a decent understanding of the behavior of the different roles ‘up there’.
(you can read several post that I have previously written on this subject on my blog)
To summarize a bit: I spent the most of my time in the beginning of 2011, explaining the new features to IT-pro‘s, developers, and also decision makers. Windows Azure = PaaS, write your code, and run it up there, where it should run. Do not move your VM containing infrastructure roles, and rely on that the configuration would last.
We are now almost half through the year of 2011, and everything is all about the cloud.
Sometimes I‘m very excited on the subject, and sometimes I‘m sick and tired of it.
The reason why I‘m sick and tired of it, is because of all the misunderstanding out there, and that everyone seems to know what it is, without really have a clue. And that‘s an interesting statement from me, right? Why the heck should I claim that I have a clue, anyway?
The tendency is that as long as you have some server virtualization, you‘ve already fulfilled the ‘requirements’ to call your datacenter for a private cloud. Really? Actually, to confuse you more, you could have a private cloud without virtualization. But virtualization makes it more achievable and also a lot more cost effective and so on. Let`s take a look at some definitions.

The cloud itself is a set of hardware, networks, storage, services, and interfaces that enable the delivery of computing as a service. Cloud services include the delivery of software, infrastructure, and storage over the internet (either as a separate components or a complete platform) based on user demand.
Overall, the cloud embodies the following four basic characteristics:

·         Elasticity and the ability to scale up and down
·         Billing and metering of service usage in a pay-as-you-go model
·         Self-service provisioning and automatic deprovisioning
·         Virtualization (Yes I know, I mentioned that it`s not necessary, but would you really create a cloud without virtualization?)

We have now some sort of basic information about what`s defining the cloud. (Hopefully you would agree with this so far).

But everybody is talking about cloud. Managers, IT-pro`s, developers, and even consumers – the end-users. Should this really be necessary?

In a dynamic economic environment, your company`s survival may depend on your ability to focus on core business and adapt quickly. Yesterday`s profitable business model can`t be counted on to translate into future growth and profits. As your business adapts to changing government and industry regulations, evaluates the new business partnerships, and anticipates competitive threats, IT needs to help the business find new ways to respond.
At the same time, plans for change must often be made in the context of limited resources for finances, people, technology, and power.
While there are a lot of technical considerations, keep in mind the fundamental truth: cloud computing – what it is and how it helps companies rethink how they deploy technology.
The IT-pro`s, or at least the IT-manager should have an in-depth knowledge by now, on the cloud terms. What he/she/they should do with it, and how, why, and when. One of their responsibilities is to bring this information to the CEO, or someone else that has a function as a decision maker. It`s most of all a business model. The technicians should know how to plan for, develop, test, and build the cloud (private), and also have an understanding on how they should move to the public cloud, if that`s an option.

And the end user should not have a clue. The end user doesn`t really have to know anything about the underlying technology. In small businesses, for example, the cloud provider becomes the de facto datacenter. In larger organizations, the IT organization oversees the inner workings of both the internal resources and external cloud resources. Business management needs to take responsibility for overall governance of data or services living in a public cloud. Cloud service providers must provide a predictable and guaranteed service level and security to all their constituents.

So as an IT-pro, how should you ‘attack’ the cloud?
You can consider the Saas (Software – as a Service) offering from Microsoft, as an option if you want to move your Exchange, Sharepoint and Lync servers to the public cloud. If you`re sniffing on the Windows Azure platform, take some time to know how it works, how it works in conjunction with SQL Azure, and AppFabric, and discuss it with your developers.

What about the private cloud?
Microsoft has done a great job on the term ‘cloud’, with their next versions of the System Center suite. The main product that reflects the cloud is System Center Virtual Machine Manager 2012. Yes, it even contains a button that says ‘create Cloud’. Spend some time with it. It`s not only a fantastic tool to manage the entire virtual infrastructure, along with bare metal deployment of Hyper-V servers, clusters, load balancing, storage, networking and so on. It`s even careless if your hypervisor is Hyper-V, VMware, or/and XenServer. It just works. You`ll get a great visual overview of some of the buzz words in our business, along with many useful features. Remember the four characteristics when you`re playing around with VMM 2012:

·         Elastiity and the ability to scale up and down
·         Billing and metering of service usage in a pay-as-you-go model
·         Self-service provisioning and automatic deprovisioning
·         Virtualization (Yes I know, I mentioned that it`s not necessary, but would you really create a cloud without virtualization?)

To add some extra features, take a closer look at System Center Operation Manager, System Center Configuration Manager, System Center Service Manager, and System Center Opalis.

Hurry up, the cloud-train is about to leave the station, and you do not want to miss it! J


No comments: