Changes between Version 29 and Version 30 of orca-and-rspec

Show
Ignore:
Timestamp:
07/23/12 11:18:56 (7 years ago)
Author:
ibaldin (IP: 152.54.9.21)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • orca-and-rspec

    v29 v30  
    6161 * Dataplane IP address - ORCA allows the user to specify the IP address of an interface in a slice dataplane (not to be confused with the management address through which the user logs in). This can be done by adding an 'ip' element within an interface definition (see example above) 
    6262 * Management IP address - the address from which the user can have ssh access the sliver. This cannot be specified and is reported as 'service' element within the manifest RSpec. Note that the port may not be 22, as some sites lack direct access to the Internet and use NAT. For these sites Gush may not work well as it requires a listening port open on the sliver which in this case will not be NATted.  
    63  * Domain binding - you can use standard ORCA site names (uncvmsite, rencivmsite, acisvmsite, dukevmsite). Note that nodes in a request can be bound to different domains to create an inter-domain topology. The domain can be specified as either part of component_id or component_manager_id (see both below): 
     63 * Domain binding - you can use standard ORCA site names (uncvmsite, rencivmsite, acisvmsite, dukevmsite). Note that nodes in a request can be bound to different domains to create an inter-domain topology. The domain can be specified as either part of  component_manager_id: 
    6464{{{ 
    65 <node component_id="urn:publicid:IDN+uncvmsite+node+vm" 
    66         component_manager_id="urn:publicid:IDN+uncvmsite+authority+cm" 
     65<node component_manager_id="urn:publicid:IDN+uncvmsite+authority+cm" 
    6766        client_id="pc175" 
    6867        exclusive="true">