Changes between Version 11 and Version 12 of virtual-machines

Show
Ignore:
Timestamp:
06/22/12 10:18:53 (7 years ago)
Author:
ibaldin (IP: 152.54.9.21)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • virtual-machines

    v11 v12  
    11= Virtual Machine Images = 
    22 
    3 Known ORCA images can be found here:  [wiki:neuca-images images] 
     3== Overview == 
    44 
    5 !ImageProxy: [wiki:image-proxy-with-orca Using ImageProxy with ORCA] 
    6  
    7 Instructions on building images with NEuca guest extensions are [wiki:NEuca-guest-configuration found here]. 
     5Orca-based installations require separate filesystem/kernel/ramdisk images (not a single bootable filesystem image). It is highly recommended to add [wiki:NEuca-guest-configuration NEuca guest extensions to your image]. Orca-based installations rely on KVM hypervisor so images must be compatible with it.  
    86 
    97== Miscellaneous instructions == 
    108 
    11  * '''NOTE1:''' For Orca-based installations the preferred method is to create a separate filesystem, kernel and ramdisk images and not a single bootable image. 
    12  * '''NOTE2:''' Orca-based installations use KVM hypervisor, 
    13  
     9 * Tested ORCA images with NEuca extensions can be found here:  [wiki:neuca-images images] 
     10 * Instructions on building images with NEuca guest extensions are [wiki:NEuca-guest-configuration found here]. 
    1411 * [http://docs.openstack.org/trunk/openstack-compute/admin/content/creating-a-linux-image.html OpenStack instructions on creating images] 
    1512 * [http://open.eucalyptus.com/wiki/creating-images-iso-kvm Eucalyptus instructions on creating images] 
     
    1714== !ImageProxy == 
    1815 
    19 Virtual Machine images can be made available to ORCA by placing them (and their metadata) at well known URLs.  An ORCA service called !ImageProxy will manage staging and caching all images at the appropriate cloud site(s).    !ImageProxy identifies each image by its URL and the SHA-1 hash of the image and requires an xml metadata file with the identifying information. 
     16Virtual Machine images can be made available to ORCA by placing them (and their metadata) at well known URLs.  An ORCA service called [wiki:image-proxy-with-orca ImageProxy] will manage staging and caching all images at the appropriate cloud site(s).    !ImageProxy identifies each image by its URL and the SHA-1 hash of the image and requires an xml metadata file with the identifying information. 
    2017 
    2118Sample metadata file. Node element names and keywords representing image type are case sensitive: