Changes between Version 33 and Version 34 of NEuca-overview

Show
Ignore:
Timestamp:
01/29/13 14:33:22 (6 years ago)
Author:
ibaldin (IP: 152.54.9.21)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NEuca-overview

    v33 v34  
    1616 2. [wiki:NEuca-guest-configuration Installing NEuca tools onto the images that the VMs] (Same process for Eucalyptus and !OpenStack) 
    1717 
    18  
    19  
    20 == License == 
    21  
    22 NEuca patches to Eucalyptus are released under GPLv3 consistent with the Eucalyptus license. NEuca guest configuration scripts are released under the MIT/GENI Public License. Updated version of the iniparser library is released under the MIT license. 
    23  
    2418== The details == 
    2519 
    26 NEuca functionality leverages the --user-data{-file} option of the euca-run-instances command. By default user data is free-formatted. NEuca imposes a INI format on this data. The user can pass a .ini-formatted configuration file that describes the desired interface configuration of the VM and includes the optional script to be executed by the VM at boot time. Here is an example of the configuration file: 
    27 {{{ 
    28 [global] 
    29  
    30 slice_id=6D3DE7CC-7188-49B2-AF48-F21497450D84 ; optional slice identifier 
    31  
    32 [interfaces] 
    33  
    34 ; Interface specification has the form of either 
    35 ; eth1=vlan:[host ethX]:[vlan tag on ethX]{:guest ip address} or 
    36 ; eth1=phys:[host ethX]{:guest ip address} 
    37 ; interfaces must start at eth1 and can be named in any order, however numbering gaps are not allowed 
    38 ; e.g. if configuration file specified eth1, eth2 and eth4 only eth1 and eth2 will be processed 
    39  
    40 eth1=vlan:eth0:20:192.168.1.3/24 ; eth1 attaches to eth0.20 on host and has IP 192.168.1.3/24 
    41 eth2=vlan:eth0:19:192.168.2.3/24 ; eth2 attaches to eth0.19 on host and has IP 192.168.2.3/24 
    42  
    43 [instanceConfig] 
    44 ; The script must not have any blank lines 
    45 ; use tab or spaces in the beginning of the line to indicate the continuation 
    46 ; of the script 
    47  
    48 script=#!/bin/sh  
    49     # Test script  
    50     yum install make 
    51  
    52 }}} 
     20NEuca functionality leverages the --user-data{-file} option of the euca-run-instances command. By default user data is free-formatted. NEuca imposes a INI format on this data. The user can pass a .ini-formatted configuration file that describes the desired interface configuration of the VM and includes the optional script to be executed by the VM at boot time. Here is an [https://code.renci.org/gf/project/networkedclouds/wiki/?pagename=Essex+NEuca example of the configuration file]. 
    5321 
    5422To use this file it can be passed on to the standard euca-run-instances command as follows: 
     
    6331Interfaces are specified in the [interfaces] section of the file, one at a time, starting with eth1. The cloud software manages eth0 of the VM and it is not possible to affect that interface inside the guest using standard NEuca tools (except for doing it via the post-boot script). Each interface specification has one of the two forms: 
    6432{{{ 
    65 eth1=vlan:[host ethX]:[vlan tag on ethX]{:guest ip address/netmask length} 
     33<mac address>=vlan:[host ethX]:[vlan tag on ethX]{:guest ip address/netmask length} 
    6634}}} 
    6735for attaching VMs eth1 to a tagged interface on the host or 
    68 {{{ 
    69 eth1=phys:[host ethX]{:guest ip address/netmask length} 
    70 }}} 
    71 for attaching VMs eth1 to a physical interface on the host. Interfaces enumerated one by one in any order, however numbering gaps are not allowed. A configuration file that defines eth1, eth2 and eth4 will result in VM only having eth1 and eth2 configured in addition to eth0 that is managed by the cloud. 
     36 
     37Interfaces enumerated one by one in any order, however numbering gaps are not allowed. A configuration file that defines eth1, eth2 and eth4 will result in VM only having eth1 and eth2 configured in addition to eth0 that is managed by the cloud. 
    7238 
    7339IP address specification for an interface is optional. NEuca guest tools will ignore interfaces without IP addresses and leave them unconfigured. '''CAUTION:''' do not attempt to attach VM interfaces to the interface/bridge used by the cloud management software internally as this may interfere with communications with the host node.   The interface/bridge to be avoided can be found in the could configuration files.  In Eucalyptus $EUCALYPTUS/etc/eucalyptus/eucalyptus.conf, see VNET_BRIDGE definition.  In !OpenStack /etc/nova/nova.conf. 
    7440 
    75 The post-boot script, specified in [instanceConfig] section can perform any actions consistent with the capabilities of the OS installed in the image. It is executed at priority 99 of rc scripts in LSB for the appropriate runlevel.  
     41The [wiki:velocity-templates post-boot script], specified in [instanceConfig] section can perform any actions consistent with the capabilities of the OS installed in the image. It is executed at priority 99 of rc scripts in LSB for the appropriate runlevel.  
    7642 
    7743== Using NEuca guest tools ==