This repository has been archived by the owner on Aug 30, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 24
vmtypes 3.3 spec
Steve Jones edited this page Sep 6, 2017
·
5 revisions
VM Type support in Eucalyptus has two disjoint aspects:
- AWS compatibility as determined by published VM type names (but not necessarily characteristics).
- Private cloud administrator control over vm type definitions.
Currently (09/18/12) the vm type definitions used by AWS are:
| Micro | t1.micro | |||
|---|---|---|---|---|
| Standard | m1.small | m1.medium | m1.large | m1.xlarge |
| High CPU | c1.medium | c1.xlarge | ||
| High Mem | m2.xlarge | m2.2xlarge | m2.4xlarge | |
| Cluster Compute | cc1.4xlarge | cc2.8xlarge | ||
| High I/O | hi1.4xlarge | |||
| GPU | cg1.4xlarge |
- Small Instance (Default) 1.7 GB of memory, 1 EC2 Compute Unit (1 virtual core with 1 EC2 Compute Unit), 160 GB of local instance storage, 32-bit or 64-bit platform
- Medium Instance 3.75 GB of memory, 2 EC2 Compute Units (1 virtual core with 2 EC2 Compute Units each), 410 GB of local instance storage, 32-bit or 64-bit platform
- Large Instance 7.5 GB of memory, 4 EC2 Compute Units (2 virtual cores with 2 EC2 Compute Units each), 850 GB of local instance storage, 64-bit platform
- Extra Large Instance 15 GB of memory, 8 EC2 Compute Units (4 virtual cores with 2 EC2 Compute Units each), 1690 GB of local instance storage, 64-bit platform
- Micro Instance 613 MB of memory, up to 2 ECUs (for short periodic bursts), EBS storage only, 32-bit or 64-bit platform
- High-Memory Extra Large Instance 17.1 GB memory, 6.5 ECU (2 virtual cores with 3.25 EC2 Compute Units each), 420 GB of local instance storage, 64-bit platform
- High-Memory Double Extra Large Instance 34.2 GB of memory, 13 EC2 Compute Units (4 virtual cores with 3.25 EC2 Compute Units each), 850 GB of local instance storage, 64-bit platform
- High-Memory Quadruple Extra Large Instance 68.4 GB of memory, 26 EC2 Compute Units (8 virtual cores with 3.25 EC2 Compute Units each), 1690 GB of local instance storage, 64-bit platform
- High-CPU Medium Instance 1.7 GB of memory, 5 EC2 Compute Units (2 virtual cores with 2.5 EC2 Compute Units each), 350 GB of local instance storage, 32-bit or 64-bit platform
- High-CPU Extra Large Instance 7 GB of memory, 20 EC2 Compute Units (8 virtual cores with 2.5 EC2 Compute Units each), 1690 GB of local instance storage, 64-bit platform
- Cluster Compute Quadruple Extra Large 23 GB memory, 33.5 EC2 Compute Units, 1690 GB of local instance storage, 64-bit platform, 10 Gigabit Ethernet
- Cluster Compute Eight Extra Large 60.5 GB memory, 88 EC2 Compute Units, 3370 GB of local instance storage, 64-bit platform, 10 Gigabit Ethernet
- Cluster GPU Quadruple Extra Large 22 GB memory, 33.5 EC2 Compute Units, 2 x NVIDIA Tesla “Fermi” M2050 GPUs, 1690 GB of local instance storage, 64-bit platform, 10 Gigabit Ethernet
- High I/O Quadruple Extra Large 60.5 GB memory, 35 EC2 Compute Units, 2* 1024 GB of SSD-based local instance storage, 64-bit platform, 10 Gigabit Ethernet
- MVP is a larger number of vm types
- Having an arbitrary number is not in MVP
- Create and Delete become optional if the number of VMTypes are fixed
- MVP precludes requiring admin to login via to adjust the VMTypes
- MVP includes an admin API for controlling vm type definitions
- Create and Delete are optional
- Don't allow for removal of default AWS types
- Deleting would involve invalidating existing references
- t1.micro doesn't have instance store option
- MVP includes a euca-describe-vmtypes
- Ephemeral disk configurations
- UserConsole changes related to removing config file for vmtypes
- Use the new UI instead
- Change the presentation to accommodate the larger number of vmtypes
- Changing ephemeral configuration changes the
- Admin UI
- Presentation of existing types
- Create and delete mutable types
- Authorization and authentication are required in
- Constraints on legitimate values
- Restrict naming to [:alnum:] period
tag:rls-3.3 tag:vmtypes