Changes between Version 17 and Version 18 of virtual-machines

Show
Ignore:
Timestamp:
01/24/14 15:13:26 (5 years ago)
Author:
ibaldin (IP: 152.54.9.21)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • virtual-machines

    v17 v18  
    55Orca-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. The most straightforward way to build an image is to start with a 'pre-cursor' image from !OpenStack, Eucalyptus or EC2 and modify it to your needs. 
    66 
    7 == Miscellaneous instructions == 
     7== Workflow == 
    88 
    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]. 
    11  * [http://docs.openstack.org/image-guide/content/ch_modifying_images.html OpenStack instructions on how to modify images] 
     9 1 Start with [wiki:neuca-images existing image] and modify it, for example using [http://docs.openstack.org/image-guide/content/ch_modifying_images.html OpenStack instructions on how to modify images] or see below. 
     10 2 Install [wiki:NEuca-guest-configuration NEuca tools into the image] 
     11 3 Make the image sparse (see below)  
     12 4 Test if it boots  
     13 5 Create !ImageProxy image descriptor file and calculate the hash (see below) 
    1214 
    1315== Resizing an existing image filesystem ==