VIRTUALIZATION
MUHAMMAD ADNAN SOHAIL
52807
WHAT IS VIRTUAL
• Dictionary Definition:
Very close to being something without actually being it.
Being such in power or effect, though not actually such.
• ComputerTerms:
Opposite of physical.
Exist only in the memory of a computer.
METAPHOR
• Car-racingVideo Game:
No physical car.
Computer simulation of an engine, a transmission, brakes, tires and other parts.
• Virtual Server:
No physical computer parts.
Computer simulation of a processor, memory, disk, and network.
Accomplishes the same goals as a physical server.
HYPERVISOR
• A piece of computer software, firmware, or hardware that creates and runs
virtual machines.
• Generic term that doesn't apply to any particular vendor.
• Host  Actual physical server, that runs the Hypervisor software.
• Guest  Not exist physically, virtual machine hosted by hypervisor.
TYPES OF HYPERVISOR
• Type 1 Hypervisor (Native, or a Bare Metal):
• Runs directly on the physical hardware.There is no operating system separate from the
hypervisor, mean act as OS.
• Type 2 Hypervisor (Hosted):
• Runs as an application or service on separate OS.
THE CLOUD
• Different vendors define it differently.
• Some vendors running hypervisor software on their hardware.
• Some venders rent access to hypervisor.
• Not be exactly sure where your virtual server is running. It could be in one data center or
multiple data centers.
• Even if you knew what data center it was in, you wouldn't know what machine in that data
center it's running on.
• Typically draw a cloud on the network diagram to represent all of these things that we don't
know exactly where they're running.
PUBLIC, PRIVATE AND HYBRID CLOUD
• Public Cloud is owned by someone else and they rent access to it.
• Lots of different customers running on one set of physical hardware.
• Private Cloud is owned by the people that use it.
• Only one customer running on a private Cloud.
• Hybrid Cloud is a combination of public and private cloud.
• Option to move virtual machines to a public cloud in case their private cloud couldn’t
handle workload.
• E-Commerce retailer use this option during a busy time such as Christmas / Eids season.
TYPE OF SERVICE OFFERED BY VENDERS
• Infrastructure as a service(IaaS):
• Virtual processor, memory and disk and install virtual machines run almost any operating
system or any piece of software.
• Platform as a service (PaaS):
• Having an operating system, and possibly having some software on there, like a relational
database server, and a web server.
• Not have to worry about installing an operating system or maintaining that.
• Software as a service (SaaS):
• Get a predefined, fully functional piece of software.
• Little or no maintenance or administration that has to be done by the end user.
• For example: email provider that runs in the Google Cloud.
COMMON USES OF VIRTUALIZATION
• Virtualizing Desktop Computers.
• Running a Specific Program.
• Setting UpTest and Development Environments.
• Designing a Private Cloud.
• Utilizing a Public Cloud.
VIRTUALIZING DESKTOP COMPUTERS
• Challenges:
• Troubleshoot unique setups
• Upgrade applications
• Hardware refreshed
• Virtualization:
• Virtual Desktop Infrastructure (VDI)
• A central server pushes a copy ofVM to each user.
• Processing on thatVM will typically occur remotely.
• Desktop is a dumb terminal.
• User must save documents to network server
• Reducing Troubleshooting and Administration
• Help desk only ever has to troubleshoot one situation.
• Reduced hardware costs
• Expand quickly
• Top vendors forVDI solutions: 1) Citrix  XenServer. 2)VMware  Horizon 3) Microsoft  MSVDI
RUNNING A SPECIFIC PROGRAM
• Legacy applications
• 32bitVs. 64bit
• Different operating systems.
• Windows XP Vs.Windows 7
• MacVs. Windows
• WindowsVs. Linux
VIRTUALIZING TEST ENVIRONMENTS
• PermanentTest Environment:
• Example Ecommerce website have a test infrastructure before they roll changes to the production
website.
• Use to undo whatever something happens that doesn't go quite right.
• Use of snapshots and checkpoints to easy to roll back to where you were before.
• Scale hardware:
• how much hardware would we have to handle a certain load?
• Create test servers by cloning production server.
• TemporaryTesting:
• Example evaluating a new accounting system.
• No Need to buy new hardware.
• Use current virtualize environment.
• Use public cloud.
• The Cloud Provides:
• AmazonAWS – monthly
• Microsoft Azure – monthly
• Amazon Spot Instances – hourly
DESIGNING A PRIVATE CLOUD
• Large number of hosts and guests.
• Large percentage of the infrastructure.
• Run the main line of business applications.
• Private Cloud Considerations:
• Storage: Bottleneck in a private cloud consists of File SystemTypes (Read), Quantity (Space) and
Quality (Speed)
• Bandwidth: Local or Remote
• Uptime: Affect a lot of other decisions.
• Monitoring: the event of a disaster live migration
• Scalability: estimation for future
• Private CloudTools:
• Microsoft  Hyper-V and System CenterVirtual Machine Manager (SCVMM) (administration of a
large number ofVMs, live migration etc.)
• VMware  vCloud Suite consists of 1) vSphere ESXi (Type 1), 2) vMotion (live migration), 3) DRS
(Load balancing), 4) vCloud Director (Managing a private cloud)
UTILIZING A PUBLIC CLOUD
• Inexpensive to start
• Could be expensive to maintain.
• Not cheaper in the long run.
• Practically infinite scalability
• High availability
• More than small business can achieve on their own
• Significantly more secure than a server in a closet.
• May not secure blindly but need good Service Level Agreement (SLA):
• Read the SLA.
• Understand the SLA
• Negotiate the SLA
• Public Cloud Providers:
• Amazon  Amazon Web Services (AWS)
• Microsoft  Azure
• Rackspace  OpenCloud.
• Salesforce.com  CRM solutions
VIRTUALIZATION ADVANTAGES
• More efficient utilization of hardware
• Use what you need when you need it.
• Manually or Automatically adjust/resize resources
• Increase availability
• Manually or Automatically Live migration ofVMs
• Disaster recovery
• Snapshot or Checkpoint (Save the state of a virtual machine at a point in time)
• Just-in-time delivery of resources
• Processor (Fixed and speed can be Dynamic) and Memory (Dynamic and reclaim memory
by guest called ballooning)
• Saving energy
• Saving money
• Help scale data centers
VIRTUALIZATION DISADVANTAGES
• Increased complexity
• Network  Increased Load , Duplicate IP and MAC address
• Storage  Performance, Quality and Quantity problem with local storage
• Troubleshooting  Problem conflicting with Hypervisor/OS/ Hardware
• Expense
• Hypervisor best features is not free.
• Software load inVMs not free
• Special licensing forVMs environment
• Sprawl
• To manyVMs
• MoreVMs required more storage, bandwidth, administration, licenses and power
• Stopping Sprawl  Decommissioning unusedVMs, Identify temporaryVMs when created
and Audit productionVMs
That’s All
THANKYOU

Virtualization

  • 1.
  • 2.
    WHAT IS VIRTUAL •Dictionary Definition: Very close to being something without actually being it. Being such in power or effect, though not actually such. • ComputerTerms: Opposite of physical. Exist only in the memory of a computer.
  • 3.
    METAPHOR • Car-racingVideo Game: Nophysical car. Computer simulation of an engine, a transmission, brakes, tires and other parts. • Virtual Server: No physical computer parts. Computer simulation of a processor, memory, disk, and network. Accomplishes the same goals as a physical server.
  • 4.
    HYPERVISOR • A pieceof computer software, firmware, or hardware that creates and runs virtual machines. • Generic term that doesn't apply to any particular vendor. • Host  Actual physical server, that runs the Hypervisor software. • Guest  Not exist physically, virtual machine hosted by hypervisor.
  • 5.
    TYPES OF HYPERVISOR •Type 1 Hypervisor (Native, or a Bare Metal): • Runs directly on the physical hardware.There is no operating system separate from the hypervisor, mean act as OS. • Type 2 Hypervisor (Hosted): • Runs as an application or service on separate OS.
  • 6.
    THE CLOUD • Differentvendors define it differently. • Some vendors running hypervisor software on their hardware. • Some venders rent access to hypervisor. • Not be exactly sure where your virtual server is running. It could be in one data center or multiple data centers. • Even if you knew what data center it was in, you wouldn't know what machine in that data center it's running on. • Typically draw a cloud on the network diagram to represent all of these things that we don't know exactly where they're running.
  • 7.
    PUBLIC, PRIVATE ANDHYBRID CLOUD • Public Cloud is owned by someone else and they rent access to it. • Lots of different customers running on one set of physical hardware. • Private Cloud is owned by the people that use it. • Only one customer running on a private Cloud. • Hybrid Cloud is a combination of public and private cloud. • Option to move virtual machines to a public cloud in case their private cloud couldn’t handle workload. • E-Commerce retailer use this option during a busy time such as Christmas / Eids season.
  • 8.
    TYPE OF SERVICEOFFERED BY VENDERS • Infrastructure as a service(IaaS): • Virtual processor, memory and disk and install virtual machines run almost any operating system or any piece of software. • Platform as a service (PaaS): • Having an operating system, and possibly having some software on there, like a relational database server, and a web server. • Not have to worry about installing an operating system or maintaining that. • Software as a service (SaaS): • Get a predefined, fully functional piece of software. • Little or no maintenance or administration that has to be done by the end user. • For example: email provider that runs in the Google Cloud.
  • 9.
    COMMON USES OFVIRTUALIZATION • Virtualizing Desktop Computers. • Running a Specific Program. • Setting UpTest and Development Environments. • Designing a Private Cloud. • Utilizing a Public Cloud.
  • 10.
    VIRTUALIZING DESKTOP COMPUTERS •Challenges: • Troubleshoot unique setups • Upgrade applications • Hardware refreshed • Virtualization: • Virtual Desktop Infrastructure (VDI) • A central server pushes a copy ofVM to each user. • Processing on thatVM will typically occur remotely. • Desktop is a dumb terminal. • User must save documents to network server • Reducing Troubleshooting and Administration • Help desk only ever has to troubleshoot one situation. • Reduced hardware costs • Expand quickly • Top vendors forVDI solutions: 1) Citrix  XenServer. 2)VMware  Horizon 3) Microsoft  MSVDI
  • 11.
    RUNNING A SPECIFICPROGRAM • Legacy applications • 32bitVs. 64bit • Different operating systems. • Windows XP Vs.Windows 7 • MacVs. Windows • WindowsVs. Linux
  • 12.
    VIRTUALIZING TEST ENVIRONMENTS •PermanentTest Environment: • Example Ecommerce website have a test infrastructure before they roll changes to the production website. • Use to undo whatever something happens that doesn't go quite right. • Use of snapshots and checkpoints to easy to roll back to where you were before. • Scale hardware: • how much hardware would we have to handle a certain load? • Create test servers by cloning production server. • TemporaryTesting: • Example evaluating a new accounting system. • No Need to buy new hardware. • Use current virtualize environment. • Use public cloud. • The Cloud Provides: • AmazonAWS – monthly • Microsoft Azure – monthly • Amazon Spot Instances – hourly
  • 13.
    DESIGNING A PRIVATECLOUD • Large number of hosts and guests. • Large percentage of the infrastructure. • Run the main line of business applications. • Private Cloud Considerations: • Storage: Bottleneck in a private cloud consists of File SystemTypes (Read), Quantity (Space) and Quality (Speed) • Bandwidth: Local or Remote • Uptime: Affect a lot of other decisions. • Monitoring: the event of a disaster live migration • Scalability: estimation for future • Private CloudTools: • Microsoft  Hyper-V and System CenterVirtual Machine Manager (SCVMM) (administration of a large number ofVMs, live migration etc.) • VMware  vCloud Suite consists of 1) vSphere ESXi (Type 1), 2) vMotion (live migration), 3) DRS (Load balancing), 4) vCloud Director (Managing a private cloud)
  • 14.
    UTILIZING A PUBLICCLOUD • Inexpensive to start • Could be expensive to maintain. • Not cheaper in the long run. • Practically infinite scalability • High availability • More than small business can achieve on their own • Significantly more secure than a server in a closet. • May not secure blindly but need good Service Level Agreement (SLA): • Read the SLA. • Understand the SLA • Negotiate the SLA • Public Cloud Providers: • Amazon  Amazon Web Services (AWS) • Microsoft  Azure • Rackspace  OpenCloud. • Salesforce.com  CRM solutions
  • 15.
    VIRTUALIZATION ADVANTAGES • Moreefficient utilization of hardware • Use what you need when you need it. • Manually or Automatically adjust/resize resources • Increase availability • Manually or Automatically Live migration ofVMs • Disaster recovery • Snapshot or Checkpoint (Save the state of a virtual machine at a point in time) • Just-in-time delivery of resources • Processor (Fixed and speed can be Dynamic) and Memory (Dynamic and reclaim memory by guest called ballooning) • Saving energy • Saving money • Help scale data centers
  • 16.
    VIRTUALIZATION DISADVANTAGES • Increasedcomplexity • Network  Increased Load , Duplicate IP and MAC address • Storage  Performance, Quality and Quantity problem with local storage • Troubleshooting  Problem conflicting with Hypervisor/OS/ Hardware • Expense • Hypervisor best features is not free. • Software load inVMs not free • Special licensing forVMs environment • Sprawl • To manyVMs • MoreVMs required more storage, bandwidth, administration, licenses and power • Stopping Sprawl  Decommissioning unusedVMs, Identify temporaryVMs when created and Audit productionVMs
  • 17.