Changes between Version 5 and Version 6 of GENIRacksAdministration/InstaGENIVMAllocation


Ignore:
Timestamp:
04/14/16 16:06:23 (6 years ago)
Author:
hdempsey@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIRacksAdministration/InstaGENIVMAllocation

    v5 v6  
    33== Memory allocation per VM ==
    44
    5 The default Xen VM memory allocation in an InstaGENI rack is 1GB for the default image. Each Physical Xen server host has 48GB of memory out of which 5GB is reserved for the server host itself and from the remaining memory, it is possible to allocate 43 VMs. Each rack has a 3 VM servers. There is one exception, Utah DDC IG has 15 VM servers.
     5The default Xen VM memory allocation in an InstaGENI rack is 1GB for the default image. Each physical Xen server host has 48GB of memory, out of which 5GB is reserved for the Xen server host itself.  From the remaining server memory, it is possible to allocate 43 VMs. Each standard InstaGENI rack has a 3 VM server hosts, but racks can be configured to support additional servers.  Currently the Utah DDC InstaGENI rack has 15 VM servers.  The Virginia Tech InstaGENI rack will have 10 VM servers.
    66
    77== Disk Space Allocation ==
    88
    9 Each InstaGENI rack has 1TB of disk space available.  Disk space allocation in the InstaGENI racks is as follows:
     9Each standard InstaGENI rack has 1TB of disk space available.  Disk space is allocated the InstaGENI racks as follows:
    1010
    11  1. There is the Disk image, which can be a user-created or a GENI/Emulab-provided images. These are standard compressed sized images that are less than 1GB in size for theGENI/Emulab-provided images. User-created images may be larger. When used, these images are cloned onto the space allocated to the VM.
     11 1. There is a disk image for each VM, which can be a user-created or a GENI/Emulab-provided image. The default GENI/Emulab provided compressed image requires less than 1GB of disk space. User-created images may be larger. When used, these images are cloned onto the space allocated to the VM.
    1212
    13  2. There is the default Xen VM Disk size that defaults to 20GB. This allocation started at 4GB, was then increased to 8GB and is now 20GB. This larger size was allocated to accommodate many experimenters that may want to run tools or generate logs that may generate large files. The goal is to avoid running out of disk space on a VM, which would be fatal for the VM instance.
     13 2. The default Xen VM disk space allocation is 20GB. This allocation started at 4GB in early deployments, increased to 8GB and is now 20GB. The allocation has increased to accommodate many experimenters who want to run tools or generate logs that require lots of disk space. (Running out of disk space on a VM is fatal for the VM instance.)
    1414
    15 Additionally the Logical Volume Manager (LVM) disk space is shared along with the disk images. Any new custom image when loaded by physical host server is mounted as a local volume from the same 1TB disk as the available images.  This is done so it may be possible to clone this new volume when a VM with the same disk image is requested at a later time. There is no reserved disk space for this feature, so it may vary across racks.
     15Additionally the Logical Volume Manager (LVM) disk space is shared with the disk image space.  Any new custom image loaded on the physical host server is mounted as a local volume from the same 1TB disk as the available images.  This is done so it may be possible to clone this new volume when a VM with the same disk image is requested at a later time. There is no reserved disk space for this feature, so it may vary across racks.