Changes between Version 29 and Version 30 of flukes

Show
Ignore:
Timestamp:
12/05/11 12:48:00 (8 years ago)
Author:
ibaldin (IP: 152.54.9.21)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • flukes

    v29 v30  
    4545Flukes GUI opens with several tabs: 
    4646 
    47 here are several tabs:</p> 
     47here are several tabs: 
    4848 
    4949 * Resources pane - for inspecting available resources 
     
    5353The slice request can be created in the Request pane and either submitted to ORCA or saved for future use. Once the slice request is submitted, the user can switch to the Manifest pane and query ORCA for slice status. Once the valid manifest is received, the user can inspect the elements of the slice and login to the provisioned nodes.  
    5454 
    55 Left click places the nodes (in request mode). Right either displays a context menu for either 
     55Left click places the nodes or node groups (in request mode). Clicking on one node and dragging (while holding the mouse button) to another node creates a link. Right click displays a context menu for either 
    5656 * A node (when clicked on a node) 
    5757 * A link (when clicked on a link) 
     
    6363 * Pan - panning the graph image within the pane [All modes] 
    6464 
    65 == Post Boot Script templates  ==  
     65In pick mode the user can select multiple nodes (by clicking on a node or clicking and dragging to create a select area) and edit their common properties (e.g. image, domain binding etc) by right clicking anywhere except node or link and selecting 'Edit Selected Nodes'. 
     66 
     67=== Nodes === 
     68 
     69Nodes are a main element of the topology. A node group is a special kind of a node that represents some number of nodes sharing common properties. Node and node groups can 
     70 * Have IP addresses/IP address ranges within the dataplane assigned by the user 
     71 * Have functional dependencies on other nodes (node A depending on node B will not boot until node B boots) 
     72 * Nodes can have post boot scripts or post boot script templates. 
     73 
     74Nodes 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. 
     75 
     76Two 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. 
     77 
     78Similar 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 <it>first node</it> 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. 
     79 
     80=== Node dependencies === 
     81 
     82ORCA performs its own dependency analysis on resources to determine the specific order in which they need to be configured/booted. In some cases additional functional dependencies can be introduced by the user to reflect e.g. the semantics of the application (for example an application may have a head node, which must be booted prior to worker nodes). 
     83 
     84Node properties dialog allows for these additional dependencies to be specified. A dependency implies that the dependent node will not boot until its dependency target has booted. Dependencies may span multiple domains. 
     85 
     86=== Domain binding === 
     87 
     88One of the powerful features of ORCA is automatic domain binding of nodes or node groups to specific provider domains based on resource availability. There are scenarios in which a user may explicitly indicate a binding of nodes within a request to specific domains. This can be done at either reservation level (within reservation properties), which makes all nodes within this request bound to a single domain, or it can be done on the individual node or node group level, where a binding of a specific node to a domain can be selected through node properties. 
     89 
     90Nodes and node groups can be bound to resource provider domains by selecting one of the domains in the menu. Unbound nodes or domains in a  bound reservation will be automatically bound to the selected domain. 
     91 
     92An unbound node group may be split by the system among multiple domains depending on the availability of resources. A bound node group is never split and is allocated from the specific domain. A user can indicate the splittability of the group by checking the appropriate box in node group properties. 
     93 
     94=== Post Boot Scripts and templates  === 
    6695 
    6796Flukes allows a post boot script to be associated with each node or node group.  Post boot scripts are the preferred way to create customized instances from a shared image.   Specifically, a post boot script can contain an arbitrary script that is a executed immediately after the instance has booted.