Changes between Version 61 and Version 62 of flukes

Show
Ignore:
Timestamp:
05/31/12 16:40:12 (7 years ago)
Author:
ibaldin (IP: 152.54.9.21)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • flukes

    v61 v62  
    9292Nodes are accessed by users over the management IP network which has access to the public Internet. In addition nodes may have other interfaces connecting them to other nodes, which are created by ORCA from Layer 2 circuits either within one domain or between domains, depending on the requested topology. IP address assignment on the primary/management interfaces is the responsibility of the hosting domain and these IP addresses are reported as part of the manifest (they cannot be set or determined at request time by the user). IP addresses for all other interfaces can be specified by the user. When IP addresses are left unspecified, the interfaces in the hosts are created, but remain unconfigured. 
    9393 
    94 Two node types are possible - plain node (a VM with either a default image or an image specified by the user) or a node group. A node group is a set of nodes with common attributes (e.g. size, boot image, post boot script, binding). A node group can be connected to other node groups or individual nodes over a Layer 2 connection (e.g. a VLAN). A node group may have an internal bus/vlan. Nodes within a node group that has a connection to another node or node group will be put on the same vlan. 
     94Two node types are possible - plain node (a VM with either a default image or an image specified by the user) or a node group. A node group is a set of nodes with common attributes (e.g. size, boot image, post boot script, binding). A node group can be connected to other node groups or individual nodes over a Layer 2 connection (e.g. a VLAN). Nodes within a node group that has a connection to another node or node group will be put on the same vlan. 
    9595 
    9696Similar parameters can be specified for nodes and node groups. For node groups, the number of nodes should be specified. The IP address specified for the node group is the address to be assigned to the '''first node''' in the node group, with other addresses sequentially selected from the same address set  limited by the netmask. E.g. if there are 3 nodes in a cluster and a user specifies 172.16.1.10/16 then the first node will have 172.16.1.10/16, second 172.16.1.11/16 etc. 
     97 
     98=== Links === 
     99 
     100There are two types of links in Flukes - point-to-point and broadcast. Point-to-point links can connect nodes and nodegroups to each other. In the case of a nodegroup, a point-to-point link leading to another node or node group implies that all nodes in the nodegroup must have an interface on this link.  
     101 
     102Broadcast links can be used to create isolated VLANs inside a nodegroup (replacing the now obsoleted 'private vlan' feature in flukes) or to connect multiple nodes together. Currently nodes or nodegroups connected to a broadcast link cannot be bound to different domains (however you can connect two nodegroups with a point-to-point link and bind those nodegroups to different domains). 
     103 
     104Any link can be given an explicit label (VLAN tag). This tag must come from a specially defined pool of tags known to ORCA that lead to e.g. other substrates. For example, to put a node on a mesoscale VLAN 1750 at a particular site 
     105 
     106 1. create a node and a broadcast link 
     107 2. connect the two together 
     108 2. bind the node to a particular site (if submitting via ExoSM) 
     109 3. right-cick on the broadcast link and fill in the tag '1750' for it 
     110 4. submit this request. 
    97111 
    98112=== Node dependencies === 
     
    174188=== !OpenFlow === 
    175189 
    176 You can create simple slices that attach to your !OpenFlow controller. The easiest type of slice is a NodeGroup with an InternalVlan (you can assign IP addresses to nodes on this VLAN). At reservation level (click on 'Reservation' button) be sure to bind the request to one of the XO racks (other racks will not support !OpenFlow).  
     190You can create simple slices that attach to your !OpenFlow controller. The easiest type of slice is a NodeGroup with broadcast link (you can assign IP addresses to nodes on this VLAN). At reservation level (click on 'Reservation' button) be sure to bind the request to one of the XO racks (other racks will not support !OpenFlow).  
    177191 
    178192 * Start your openflow controller on some internet-reachable host