The Eucalyptus 3.1 Compatibility Matrix below details supported platforms in the latest version of the IaaS software. The Eucalyptus 3.2 Compatibility Matrix will be coming soon.
- Eucalyptus 3.1 Compatibility Matrix.
- Looking for the latest Eucalyptus Compatibility Matrix?
Compute Compatibility
| Operating System and Hypervisors | Version | Architecture |
|---|---|---|
| CentOS+XEN | 5.x | x86_64 |
| CentOS+KVM | 6.x | x86_64 |
| Ubuntu+KVM | 10.04 | x86_64 |
| Ubuntu+KVM | 12.04 | x86_64 |
| RHEL+XEN | 5.x | x86_64 |
| RHEL+KVM | 6.x | x86_64 |
| VMWare ESX | 4.0, 4.1 | x86_64 |
| VMWare ESXi | 4.0, 4.1, 5.0 | x86_64 |
| VMware vCenter | 4.0, 4.1, 5.0 | x86_64 |
Guest Operating Systems
| Operating System Type | Version/Edition | Architecture |
|---|---|---|
| Windows Server 2003 | R2 | i386/x86_64 |
| Windows Server 2008 | Datacenter | i386/x86_64 |
| Windows Server 2008 | R2 | x86_64 |
| Windows 7 | Professional | i386/x86_64 |
| All Modern Linux Distributions | RedHat, CentOS, Ubuntu, Fedora, Debian, OpenSUSE, SLES, etc. | i386/x86_64 |
Network Compatibility by Eucalyptus Networking Modes
- Managed
- VM isolation, uses built-in DHCP service
- VLAN clean switches, no dynamic
- DHCP service on the network
- Managed (no VLAN)
- NO VM isolation, uses built-in DHCP service
- No dynamic DHCP service on the network
- Static
- No VM isolation, uses built-in DHCP service for static IP assignment
- No dynamic DHCP service on the network
- System
- No VM isolation, no automatic address handling
- Uses existing dynamic
Elastic Block Storage Compatibility
| Storage Array | Type and Series | Version | High Availability Support | Notes |
|---|---|---|---|---|
| NetApp (iSCSI) | FAS 2000 series FAS 6000 series |
OnTAPi 7.3.3 or higher ONTAPi 8.1 |
Yes | FlexClone license is required. No support for NetApp vFiler or vServer functionality. |
| EqualLogic | PS 4000 series PS 6000 series |
Compatible CLI versions | Yes | |
| Direct Attached Storage | Any JBOD | No | Linux SCSI Target Framework is required | |
| Local Disks | N/A | N/A | No | Linux SCSI Target Framework is required |
| Remote Disk | N/A | N/A | Linux SCSI Target Framework is required |
Minimum Hardware Requirements
- Front End Components
- Cloud Controller, Walrus, Storage Controller, Cluster Controller, VMware Broker
- 8 Cores, 2.4GHz, 8GB RAM, 500GB Disks (multiple disks).
- High Availability (HA) configurations must be equal in capacity.
- Node Controllers
- 4 Cores, 2.4GHz, 8GB RAM, 160GB Disks (multiple disks recommended).
- Note: Hardware virtualization must be enabled in the BIOS.
High Availability (HA) Recommendations
- Redundant Isolated Front End Components
- Redundant Network Switches
- Eucalyptus-supported SAN Adapter (Requirement for Storage Controller High Availability (HA))
- Redundant Disk Configuration (Requirement for Walrus High Availability (HA))
