5. Hence we Understand:Virtualization is a very broad concept, which is certainly
applicable to so many aspects of computing.
The earliest uses of virtualization include the CompatibleTime Sharing System (CTSS)
developed by the Massachusetts Institute ofTechnology (MIT) on the IBM 704 in 1968
6.
7.
8. • There is a new version of this new OS, I want to
try it out.
• Specific application/Libraries available for a
specific OS.
• Using Snapshots to revert back to stable states
• Excellent to test risky/buggy stuff.
• Because I find it cool to virtualize stuff ! :P .
• Blah blah blah…. (many Justified and
unjustified reasons)
14. At an Average around 70% of Operational Costs of a Datacenter attributes to Power
and Cooling
15. Optimum Utilization of Resources
Cost of Power and Space.
Ease of manageability.
Easier Backups.
Faster Deployments.
Easy to relocate.
A whole lot flexibility.
+ countless benefits.
16.
17. A hypervisor or virtual machine manager (VMM) is a piece
of computer software, firmware or hardware that creates
and runs virtual machines.
The hypervisor presents the guest operating systems with
a virtual operating platform and manages the execution of
the guest operating systems
21. Abstraction of the Hardware Interfaces by
providing the multiple virtual interfaces and
mapping it to single Interface.
Similarly the concept to soft-switches. Ex
OpenvSwitch.
22.
23.
24. Where X=
▪ Infrastructure
▪ Network
▪ Identity
▪ Storage
▪ Software
▪ Platform
▪ Firewall
▪ Load-Balancer
▪ Email, etc,etc,…
So, X is a variable, which an infinite List.
25.
26. Anything as a service is a model of cloud based delivery.Where the person
is abstracted from the underlying layer and has a hypothetical unlimited
supply of the service being provided.
27. Cloud computing is the use of computing resources
(hardware and software) that are delivered as a ON-DEMAND
service over a network (typically the Internet).The name
comes from the use of a cloud-shaped symbol as an
abstraction for the complex infrastructure it contains in
system diagrams
28. It is an on–Demand Service.
User doesn’t know (he’s abstracted from where
the service resides)
User doesn’t maintain.
User Pays for as much as he uses. !
User has hypothetical inifite “value” of the
service he is using.
29. A very similar example in other domain which you could compare to could be
electricity department.
AfterYou build your house,You can generate your own electricity
depending on your usage and buying/setting up a Generator that could sustain
your needs.
Alternately ,You could avoid it and the maintenance and the running
cost, and all the other hassles associated with it by taking “electricity-as-a-
service” from any vendor. Pay him for the amount that you use.
30. Brings down initial Investment by loads.
No bothering of maintenance, support and
upgrades.
31. Scalability : Hypothetically… infinitely elastic.
Agile – In deployment
Application programming interface (API) :
based Interaction.
Cost : setup and operational expenses very low.
Location Independence : Provides ease of use
Fault-tolerence : as the infrastructure can be
geographically scattered. Better for disaster
recovery.
32. Multitenancy : having multiple customers (centralization) ,
still making sure they have their own address space and
privacy.
Security : Security is a major concern when you have multi-
tenancy.
Metering and Billing : It is needed according to the - Pay for
what you use – UseCase.
33. Public : Ex HP Cloud, Amazon , Rackspace
Private : VcloudDirector, Rackspace, etc.
Hybrid : ??? (when and where do we need it)
34. Ability of a cloud to provision (create
VMs) into the other compatible Clouds
This is where cloud-interoperability
comes into picture
35. The Base Level Node : Single “Host” server in a big cloud.
36.
37. The above example refers to Openstack Components : Other clouds too
would have similar building blocks and interactions.
38.
39. Wikipedia : for definitions
IBM Developerworks : For diagrams.