Virtualization progress

From GO Wiki
Jump to: navigation, search

Overview

Page for keeping track of the progress towards implementing a virtualization infrastructure.

Also see rationale and overview at Virtualization.

Target Design

It seems likely at this point that OpenStack will replace Eucalyptus as the UEC driver (slated for next release). With that, we'll be able to bridge and continue progress.

  • Dedicated manager machine(s) (manager(s) may or may not be a VM).
  • Dedicated worker machines.
    • Two machines dedicated to single database VM instances.
    • Two machines holding a varying number web/server instances.
  • All machines tied to dedicated storage accordingly.
  • Ability make use of remote infrastructure
    • Share workers with similar infrastructure remotely.
    • Push VM instances and storage to 3rd-party "cloud" (pay-for service, remote site) as necessary.

Current Design

  • Various equal compute nodes with various VMs running; no centralized operation.
  • Offsite bridging not possible. Offsite handled by system copy--nasty.

It seems likely at this point that OpenStack will replace Eucalyptus as the UEC driver (slated for next release). With that, we'll be able to bridge and continue progress.

Software

Because KVM (preferred VM) is not compatible with Xen/AWS, there is currently an issue with bridging our systems with pay-for third parties.

  • Ubuntu 10.04/10 nodes handled locally--kvm/libvirt. Any host machine can act as manager.
  • Remote infrastructure handled separately--Xen/AWS.

Past Designs/Trials

Various combinations of:

  • UEC/Eucalyptus
  • Open Nebula
  • XenServer
  • CentOS
  • Debian
  • openSUSE