Changes between Version 4 and Version 5 of GENIRacksAdministration/InstaGENIVMAllocation


Ignore:
Timestamp:
04/11/16 11:31:02 (5 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIRacksAdministration/InstaGENIVMAllocation

    v4 v5  
    66
    77== Disk Space Allocation ==
     8
    89Each InstaGENI rack has 1TB of disk space available.  Disk space allocation in the InstaGENI racks is as follows:
    910
    10  1. There is the Disk image, which can be a user-created or a GENI/Emulab-provided images. These are standard compressed sized images . These images 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 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.
    1112
    12  2. There is the default Xen VM Disk size. with a default of 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 tcpdumps or generate large log files. The goal is to avoid running out of disk space on a VM, which would be fatal for the VM instance.
     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.
    1314
    1415Additionally 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.