Kernel and Ramdisk Management in Eucalyptus

Follow

Eucalyptus versions:  3.3.0 and 3.4.2

Eucalyptus supports the legacy AWS model regarding kernel and ramdisk image association to machine images.  Kernel and ramdisk images can be registered only by users under the eucalyptus account.  The kernel and ramdisk images can be made available to all the users on the cloud by changing the launch permission to all using euca-modify-image-attribute.

Setting Default Kernel (EKI) and Ramdisk (ERI) For The Cloud

Eucalyptus has the following cloud properties that display the default kernel and ramdisk for the cloud:

  • cloud.images.defaultkernelid
  • cloud.images.defaultramdiskid

Setting the default kernel and ramdisk images for a Eucalyptus cloud can be done by using the following methods:

  • If cloud.images.defaultkernelid and cloud.images.defaultramdiskid are set to <unset>, the first kernel and/or ramdisk image that is bundled, uploaded and registered will populate these values. 
  • Manually, by using the Admin UI 

  • Manually, by using euca-modify-property to set cloud.images.defaultkernelid and/or cloud.images.defaultramdiskid.

Associating Kernel (EKI) and Ramdisk (ERI) Images to Machine Images (EMI)

EKIs and ERIs can be associated to EMIs by using the following methods below.  Each of these methods contain a description of how the default cloud EKI and/or ERI will be used if kernel and/or ramdisk options are not leveraged.

      • If either the kernel ID or ramdisk ID is passed in by --kernel or --ramdisk options with an incorrect prefix, then both cloud default kernel and ramdisk IDs are used. 
      • If two of the same parameter (either --kernel or --ramdisk) are passed in and the kernel/ramdisk IDs both have the correct prefix, then the second one is used. 
      • If either the kernel ID or ramdisk ID is passed in by --kernel or --ramdisk options with an incorrect prefix, then both cloud default kernel and ramdisk are used. 
      • If two of the same parameter (either --kernel or --ramdisk) are passed in and the kernel/ramdisk IDs both have the correct prefix, then the second one is used. 
      • If either the kernel ID or ramdisk ID is passed in with an incorrect prefix, then and error is thrown.  
      • If two of the same parameter (i.e. --kernel or --ramdisk) are passed in and the kernel/ramdisk IDs both have the correct prefix, then the second one is used. 
      • If no valid kernel ID or ramdisk ID is associated by using either of the two methods mentioned above, then the cloud default kernel/ramdisk ID is used for the undefined parameter.
Have more questions? Submit a request

Comments

Powered by Zendesk