Changes between Version 1 and Version 2 of EcualyptusNetworking

Show
Ignore:
Timestamp:
10/19/08 17:51:27 (10 years ago)
Author:
sayler (IP: 152.3.136.30)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • EcualyptusNetworking

    v1 v2  
    123123}}} 
    124124 
    125 If we go ahead and assign addresses to the interfaces on each VM, it looks like eth0 (attached to eucabr3) is a restricted interface and eth1 (attached to eth0) is a public interface. 
     125Further understanding of just how this is set up requires looking at how Eucalyptus sets up VDE ([http://wiki.virtualsquare.org/index.php/VDE]). 
    126126 
    127 The dom0 can communicate with the domUs via a private link. 
     127On each guest VM instance, eth0 is a "public" interface, and eth1 is a "private" interface.   
     128 
     129The cloud controller runs DHCP for both interfaces in our setup.  We answer requests on eth0 of shirako029 (connected to the cluster network) with 10.128.1.x "public" addresses.  Theoretically, we answer requests on eucadev3 of shirako029 for the private interfaces' virtual bridged vlan.  Packets don't seem to make it from the NCs to the CC.. so this doesn't work presently.