Changes between Version 28 and Version 29 of NEuca-overview

Show
Ignore:
Timestamp:
02/07/12 16:53:51 (7 years ago)
Author:
pruth (IP: 152.54.9.28)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NEuca-overview

    v28 v29  
    33== Overview == 
    44 
    5 NEuca (pronounced "nyoo-kah") is a set of patches for Eucalyptus and guest configuration scripts that enhance the functionality of a private Eucalyptus cloud without interfering with its traditional operations. NEuca allows VMs instantiated via Eucalyptus to 
    6   * Have additional network interfaces, not controlled by Eucalyptus. These interfaces can be connected on the host node to VLANs or physical interfaces. Eucalyptus continues to control and assign the address of eth0 of the VM. NEuca performs necessary operations on the node hosting the VM to make sure VLAN interfaces and extra bridges are created and torn down. This is consistent with the model of allowing Eucalyptus to control the 'management' interface of the VM, while the other interfaces are used for high-speed 'data-plane' interconnects although it may have other uses.  
     5NEuca (pronounced "nyoo-kah") is a set of patches for Eucalyptus and !OpenStack and guest configuration scripts that enhance the functionality of a private cloud without interfering with its traditional operations. NEuca allows VMs instantiated via Eucalyptus and !OpenStack to 
     6  * Have additional network interfaces, not controlled by the cloud management software. These interfaces can be connected on the host node to VLANs or physical interfaces. The cloud continues to control and assign the address of eth0 of the VM. NEuca performs necessary operations on the node hosting the VM to make sure VLAN interfaces and extra bridges are created and torn down. This is consistent with the model of allowing the cloud to control the 'management' interface of the VM, while the other interfaces are used for high-speed 'data-plane' interconnects although it may have other uses.  
    77  * Perform arbitrary post-boot actions using shell scripts.  
    88 
    9 The changes to Eucalyptus code base are limited to its Node Controller and do not impact on the other components or the user tools. The installation (described in a separate document) follows the traditional steps for installing Eucalyptus on a cluster with minor modifications for applying the NEuca patches. NEuca user tools can be [wiki:NEuca-guest-configuration installed on existing Eucalyptus-friendly images]. 
     9The changes to Eucalyptus and !OpenStack code base are limited to its Node Controller and do not impact on the other components or the user tools. The installation (described in a separate document) follows the traditional steps for installing Eucalyptus or !OpenStack on a cluster with minor modifications for applying the NEuca patches. NEuca user tools can be [wiki:NEuca-guest-configuration installed on existing images]. 
    1010 
    1111== Installation == 
     
    1313Installing NEuca has two basic steps:  
    1414 
    15  1. [wiki:Eucalyptus-2.0-Setup Installing Eucalyptus with NEuca patches] - (currently Eucalyptus 2.0.0 and 2.0.2) 
    16  2. [wiki:NEuca-guest-configuration Installing NEuca tools onto the images that the VMs will use in Eucalyptus] 
     15 1. Installing NEuca patchs ([wiki:Eucalyptus-2.0-Setup Eucalyptus (currently Eucalyptus 2.0.0 and 2.0.2) ], [wiki:OpenStack-Setup !OpenStack]) 
     16 2. [wiki:NEuca-guest-configuration Installing NEuca tools onto the images that the VMs] 
    1717 
    1818== License == 
     
    5959  * When specifying post-boot scripts, line continuation is indicated by the whitespace in the beginning of the line. Blank lines in post-boot scripts are not allowed.  '''WARNING:  BLANK LINES IN POST-BOOT SCRIPTS WILL CRASH THE WHOLE CLUSTER'''. 
    6060 
    61 Interfaces are specified in the [interfaces] section of the file, one at a time, starting with eth1. Eucalyptus 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: 
     61Interfaces 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: 
    6262{{{ 
    6363eth1=vlan:[host ethX]:[vlan tag on ethX]{:guest ip address/netmask length} 
     
    6767eth1=phys:[host ethX]{:guest ip address/netmask length} 
    6868}}} 
    69 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 Eucalyptus. 
     69for 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. 
    7070 
    71 IP 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 that Eucalyptus uses internally as this may interfere with communications with the host node. Which interface is being used by Eucalyptus on worker host nodes should be clear from Eucalyptus configuration ($EUCALYPTUS/etc/eucalyptus/eucalyptus.conf, see VNET_BRIDGE definition) #144. 
     71IP 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. Which interface is being used by Eucalyptus on worker host nodes should be clear from Eucalyptus configuration ($EUCALYPTUS/etc/eucalyptus/eucalyptus.conf, see VNET_BRIDGE definition) #144. 
    7272 
    7373The 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.