Showing posts with label virtualization. Show all posts
Showing posts with label virtualization. Show all posts

Friday, October 31, 2014

Cloud Computing: Origins

Ph. D. Julio Fernandez Vilas
¿Any comments? jfvilas@gmail.com



The arrival of cloud computing technologies to the IT market has not happened in the big bang mode.
Unlike other technologies more directly related to the research and innovative activities that manufacturers in the world of IT (as might be the use of flash technology in storage systems, higher recording densities on tape, or FCoE), Cloud Computing is not is a technology in itself, but is rather a "way of doing".

In my view, it all started in the mid-90s, with the emergence of ISPs (Internet Service Providers) and ASP (Application Service Providers). These were the years of the birth of the Internet Age. The need of an Internet connection to be a consumer of content, and the need to have "presence" on the Internet to become a content generator was quickly covered with ISPs (those that provided access) and ASP's (those that provided the infrastructure needed to publish content).

Thereafter, as a result of the acquisition of knowledge in the new technologies of the Internet by businesses, Service Providers began to lose focus, and were the companies themselves, seeing the potential of the Internet as a new channel to open new lines of business (or expand existing), which took care of personally managing its online presence. In fact, web applications that were only mere information portals, became sites where e-commerce activities can be done, both B2C (the most successful business of all time) and B2B.
 
Obviously, these business execution capabilities may be beyond the any business capabilities, leaving a margin of existence to the ASP (ISPs were gradually eliminated by the telcos). But in the second era of the Internet, where "being on the internet" was not only for disseminating information (it was mainly for doing business), the ASP had to evolve, did not come to stay static websites, which eventually generate a new way of working, and therefore a new way of doing online business. Then we came to the "dot.com" era.

Everyone wanted to do business very quickly, so there was no time to create departments, or build a datacenter, time-to-market was critical. How is this problem of getting quicker deployments resolved? A new type of service providers appeared: the hosters (as a continuation of the story we might call them HSP, Hosting Service Provider).

With HSP, companies no longer have to worry about the more purely technological side. They just need to focus on defining a good business strategy. Once defined, if a company has some development capacity, it can implement the solution and it is ready. If not, it just has to find a company that will make the development and deploy it to the HSP chosen.

Alongside all the evolution we have been living in recent years in all that relates to "the web" and mobile, the world's infrastructure has also undergone major changes. From the IBM mainframe virtualizer (now renamed to zVM) of the 60s, to the current KVM, Xen, vSphere, Hyper-V, etc., the world of virtualization has evolved in dizzying, provided a new vision and a new way of managing the infrastructure.

Workload consolidation, cost reduction, simplification of the datacenter, high availability, and a right utilization of the installed resources are some of the concepts to which we have been migrating almost without realizing the fact that we have just virtualized our hardware.

But virtualization is not only a valuable asset for companies with own datacenter. Those who are taking greater advantage of developments in virtualization technologies are undoubtedly the HSP.

HSPs have been able to finally get rid of dealing a big problem, the "power and cooling." At the time of the birth of the HSP, one operating system instance was installed in one physical machine (they were the years that became popular pizza servers, 1 server = 1U, ie, 42 servers per standard rack), and powering and cooling hosters’ datacenters was a real headache.

With virtualization the HSP consolidate operating system instances one far fewer physical machines, allowing them to lower their costs exponentially, and improve their service offerings.

And not just talking about physical space. The power consumption decreases dramatically, which also makes it also decreases the need for refrigeration. That is, virtualization has a double impact on the cost savings, as well as everything that is in itself by consolidating services, also helps reduce datacenter PUE.

HSP's as Rackspace, Softlayer, Terremark, etc ..., can offer hosting services at a much lower price, and also a very quicker provisioning process.

Infrastructure virtualization has changed the way we manage our hardware infrastructure, and the next step is here knocking on doors of datacenters: network virtualization.

We ourselves see it in our datacenters: provisioning a virtual machine software takes minutes to set up, but the configuration of the network part is a series of manual tasks that must be added to the total provisioning time.

New trends in what is known as "software-defined" are called to finish simplifying all procurement processes and operations, at the same time that it will mean the next step in the design and management of systems high Availability (HA) and disaster recovery (DR).

Software-Defined Networks (SDN), Software-Defined Data Center (SDDC), or Software-Defined Storage (SDS) are some of the initiatives (definable as best as pure technology strategies) that begin to fill the tables of CIOs and datacenter architects, and where the next battle for control of the datacenter between computer hardware manufacturers and communications hardware manufacturers as long as the software-defined trends will be responsible for completing the process of virtualization, to lead us to what I call the Virtual Datacenter.

Wednesday, October 14, 2009

Cloud Computing Definition #2

Ph. D. Julio Fernandez Vilas
¿Any comments? jfvilas@gmail.com

If we think that “cloud servicing” is not a kind of cloud computing, what should be considered cloud computing? There are still 2 parts of our cloud computing stack: applications and cloud infrastructure. Let’s talk about cloud infrastructure, a.k.a. IaaS (Infrastructure as a Service). EMC (the storage giant famous by its Symmetrix boxes) bought VMWare several years ago. As it occurred with no other companies bought by EMC, VMWare has not been included into the EMC Corp., and it has been kept as a separate company instead. It’s just a bit of history.

EMC sees IaaS as a “double-cloud infrastructure” built by the private cloud and the public cloud. What EMC thinks about “clouding the infrastructure” is closely related to what its award winning ESX is designed for. According to EMC view, companies using virtualization infrastructure (I think EMC’s theories are right for ESX or even for Xen) should enter in a “virtualize-everything” mode. This way, the virtualized infrastructure can hold all the infrastructure needs of the company.

The infrastructure can grow or decrease according to business needs. The benefits of virtualization are clear: changing the capabilities of the infrastructure is as easy as adding a new server to the virtualized farm. Companies will be positioning this year and next one in this “virtualized datacenter stage”. In fact, the private or internal cloud is an evolution of the virtualization of the whole datacenter.


How can datacenters prepare for the IaaS? I´ll point out just three guidelines:
  1. Create (or expand) a virtual infrastructure to support the running business services.
  2. Prepare your systems to be run in the cloud, that is:
    1. Reduce the number of different cluster you manage.
    2. Create the fewest number of different clusters that support your business.
    3. Expand your cluster(s) with all the nodes you need.
    4. Deploy all the software you use to run your business to all the nodes.
    5. Use a load balancer to specialize the workload of each node or group of nodes.
  3. Manage your virtual infrastructure.
Nowadays I don’t see an easy way to move (i.e., LiveMigration, VMotion or whatever) an OS image running in your private cloud to the public cloud (is there any public reliable ESX service?).

What would you do with your storage?
  • Suppose you use FC: you should have a very clear extended SAN that crosses your private SAN boundaries (maybe with FC-IP) and expands to a hypothetic public SAN service, so when you move your OS images to the public cloud, FC access should be provided to the nodes of the ESX farm.
  • Suppose you use iSCSI: you show work with communications staff in order to create alternative routes to your storage when you move OS images to the public cloud.
  • You may use CNA's: you have a problem.
There are several beta experiences related with the VMware ecosystem: bluelock, hosting.com, Logica, melbourneIT… It is very important to note that they are all beta services. So, going back to our main discussion, can virtualization be considered cloud computing? We can say, without a doubt that virtualization is the base for IaaS. But I prefer to restrict the term cloud computing to other things more closely related to what computing means.

Finally, in Cloud Computing Definition #2 we exclude virtualization as a main objective and we think of it as a booster of IaaS. In future articles we will talk about XaaS (Everything as a Service) ans its relation with cloud computing.

Friday, October 9, 2009

Cloud Computing Definition #1

Ph. D. Julio Fernandez Vilas
¿Any comments? jfvilas@gmail.com

So, why do you need a definition of what Cloud Computing is? Do you really need it? Ok, maybe you still don’t know what does Cloud Computing means. Maybe you are an IT specialist of any kind and Cloud Computing is something vague for you. So it is for me, too.

First of all: forget about finding an exact definition of Cloud Computing (CC). There is no standard or publicly coined definition about what CC is. I will try to define it by using several analogies.

Everybody knows what Web 2.0 (W2) is. Right? W2 is an evolution from what can be defined as “dynamic web” (that is: rich web sites where users and companies can perform some kind of e-commerce). I use the words “dynamic web” in order to make a distinction of what in its origin was called “The Web”, just a static web where companies can publish information. Let’s call it web 0.9, or even “Web beta”. Several years after the initial use of web beta, big companies entered the Internet to make business. They saw the web as a new channel to produce new income.

At that moment, “web beta” evolved to a dynamic web, web 1.0, where users can buy goods and services from “web-enabled companies”. Travel agencies, flight companies, books, music, gifts, auctions… Lots of companies came up at an era finally defined as the dot com era.

Ok… What a nice story!!! Let’s continue.

Several years after the web reinvented itself evolving to W2. W2 means free user interaction, means social networks, in general, W2 means freedom to people’s thoughts.

But… what does it happen to web applications? Here is where CC comes into. It can be said that W2 relates to social networks as CC relates to web-enabled companies. That is, CC is the Web 2.0 of business. Or even, one could say that CC is the evolution of B2B.

All these assertions can be accepted. But the problem here is that there is a lot of confusion about CC because of marketing messages.

In order to separate authentic CC approaches from marketing messages coming from companies who wants to stay on the wave, we first build a stratified decomposition of CC. Let’s look at this first picture, with CC three levels.


At the top, “Cloud Services” are services offered to customers (via Internet connections) to different kind of devices. Typically printing services, like HP’s CloudPrinting or SnapFish are being offered like “Cloud Services”.

At the very bottom, cloud infrastructure enclose a set of services that can be used to, for instance, host an application, a server, or any kind of hardware or base software you use these days in your datacenter. Cloud infrastructure has a lot to do with virtualization. For example, VMware, and the EMC’s theories about Public and Private clouds walk this way.

In the middle, applications developed by companies can now benefit from re-using external services (typically exposed as web services) in a pay-per-use model. For example, AWIS (Amazon Web Information Services) or SimpleDB are base software services offered by Amazon Web Services.

From my point of view: Cloud Services, as they are known these days, have no relation with the desired Cloud Computing stack. In fact, most of the cloud services that are being announced everywhere mean taking one step back in Internet evolution. I would rename Cloud Services as Web 1.5. Why?

Printing a picture from your BlackBerry or iPhone via 3G/GPRS and receiving your photos at home is a “cloud service”? No, surely no. Why do I say “no”? Just think about developing such a printing application and try to answer these questions:

  • Do I need any kind of virtualization infrastructure to run my application?
  • Do I need to use a service from another company to build the application?
  • Finally, do I need 2009’s technology to develop my application? Could I have developed my application 8 or 10 years ago?
I expect you to agree with me that a printing application over Internet has nothing to do with Cloud. This is only “Cloud Marketing”.