<Insert Picture Here>
Enterprise Virtualization With Xen
Frank Martin – Sr. Architect.
EDCS Advanced Architecture Team
SAFE HARBOR STATEMENT
The following is intended to outline our general product
direction. It is intended for information purposes only,
and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or
functionality, and should not be relied upon in making
purchasing decisions.
The development, release, and timing of any features or
functionality described for Oracle’s products remains at
the sole discretion of Oracle.
Early Stages – “Statelessness”
• Breaking the logical/physical
relationship between workload
and its placement on
hardware
• Key to automation and
modernization of a true “lights
out Data Center and remote
facilities management
techniques
• “Statelessness” The key to the
adaptation of virtualization in
the enterprise
Early Stages – Network Storage
• In a stateless system, Network Storage is key to the
architecture.
• No local disk usage – everything is remotely mounted.
• Most activity is concentrated on Server Virtualization,
but the migration of data to a network storage-centric
approach is crucial
Early Stages – Configuration
Repository
• “Statelessness” places the attributes of all workload
into an outside repository.
• Red Hat 5 – uses LDAP for this
• EDCS uses an Oracle Database
• Interfaces into Linux for all OS specifics ( hostname,
network configs, mountpoints, users and software)
EDCS Standard Provisioning “Grid”
• Stateless
• PXE Booted
• Network Disk Centric
• All workload encapsulated into System Repository
• BUT….
• Single OS to a single server (Server proliferation)
• No Windows support
• Big Flat Network
Enter: Server Virtualization
Project DAKOTA
• Encapsulation of the computing environment
• Network, Server, Disk all “Disposable”
• Support of Windows alongside of Solaris and Linux
Project Dakota
• Network Encapsulation:
• SSL-VPN Tunnels and ACLS
• Disk Encapsulation
• Net Apps “Flex Cloning”
• Server Virtualization
• Xen