Changes between Version 61 and Version 62 of NDL-OWL

Show
Ignore:
Timestamp:
02/24/11 17:30:09 (8 years ago)
Author:
chase (IP: 152.54.6.232)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NDL-OWL

    v61 v62  
    55We need a set of unified semantic schemas for representing the data models needed in the life circle of resource reservation. We develop NDL-OWL - an extension of the [http://www.science.uva.nl/research/sne/ndl Network Description Language] using OWL.  We use a number of [wiki:OrcaNDL tools] to create and manipulate NDL-OWL ontologies. We deliberately stay away from the procedural programming model in favor of a more flexible semantic query-based programming approach to implement the policies for resource allocation, path computation, and topology embedding applications. 
    66 
    7 There are at least 5 types of models to be defined, that are circulated among the ORCA actors (authorities, broker and service manager).  
     7There are at least 5 types of models to be defined, that are circulated among the ORCA actors (authority/AM, broker and slice manager).  
    88 
    99== 1. Substrate description model == 
     
    7272 
    7373== 2. Substrate delegation model == 
    74         This is the abstract model that is used by the substrate manager to delegate its available services and resources to outsiders, the clearing house in the GENI context. This mode should allow multiple abstraction levels as different substrate manager may want to expose different levels of resource and topology description of its substrate. The model is obtained online when a substrate is stand up. It contains two types of information: 
     74        This is the abstract model that is used by the substrate manager (AM) to delegate its available services and resources to external brokers, e.g., a GENI clearinghouse. This mode should allow multiple abstraction levels, as different AM may want to expose different levels of resource and topology description of its substrate. The model is obtained online when a substrate stands up; ideally this can be automated.  The model contains two types of information: 
    7575       * Domain network service. 
    7676             * !AccessMethod: e.g. ORCAActor, or GENI AM API. 
    7777             * Topology: Topology abstraction level exposed to outside. Right now, only node abstraction is defined. 
    7878             * !ResourceType: This is inferred via a list of defined available resource label set, e.g. 32 VMs, 100 VLANS, that will be delegated to the broker.    
    79              * !AggregateManager: e.g. the URL of its aggregate manager. 
    80        * Domain topology abstraction: Currently, the whole doman is abstracted to a node, a network device with following information: 
    81                * Switching matrix: capability (ethernet, IP, etc.), label swapping capability (means vlan translation for ethernet switching)  
    82                * Border interfaces: connectivity to neighboring domains, bandwidth and available label set (e.g. vlan)  
     79             * !AggregateManager: e.g. the URL of the AM. 
     80       * Domain topology abstraction: Currently, the whole domain is abstracted to a node, a network device with following information: 
     81               * Switching matrix: capability (ethernet, IP, etc.), label swapping capability (i.e., VLAN translation for ethernet switching)  
     82               * Border interfaces: connectivity to neighboring domains, bandwidth and available label set (e.g. VLAN)  
    8383 
    8484== 3. Slice request model == 
    8585 * [source:orca/trunk/network/src/main/resources/orca/network/schema/request.owl request.owl] 
    8686         
    87         It would define a top-level ''Reservation'' object to describe a particular reservation (term, etc.).  
    88         This is used by the user, or the slice controller after interpreting the user's requests in ad hoc format, to describe the specifics of the user's request, often this is represented in the form of a virtual topology and amount of particular resource types.   
    89          In the multi-domain setting, the controller (in the service manager) would automatically break the user request into domain-specific sub-requests that are sent to the substrate AM when redeeming. This happens after the controller finishes inter-domain path or topology computation.         
     87        This defines a top-level ''Reservation'' object to describe a particular lease reservation (term, etc.).  
     88        It describes the specifics of the user's request.  Often this is represented in the form of a virtual topology with specific resources at the edges.  It might be generated by unspecified experiment control tools.  In our implementation, it is generated by a controller module in the slice manager (SM) after interpreting the user's request in an ad hoc format. 
     89         In our current implementation for the multi-domain setting, this SM controller performs inter-domain path or topology computation and automatically breaks the user request into domain-specific sub-requests.         
    9090 
    91         * The topology request is defined a collection of bounded or unbounded connections. The end node of the connection can specify the amount of requested edge resource type (e.g. amount of VMs).  
    92         * In redeeming the ticket to a specific site, the controller would dynamically create a sub-request to ask for a sliver. 
     91        * The topology request is defined as a collection of bounded or unbounded connections. The end node of the connection can specify the amount of requested edge resource type (e.g. number of VMs or other slivers).  
     92        * In redeeming the ticket to a specific site, the SM controller dynamically creates a sub-request to ask for a sliver. 
    9393 
    9494== 4. Slice reservation model (Not implemented yet) ==  
    95         This is used by the clearing house (brokers) to return resource reservation description to the slice controller so that the controller can use to talk to related substrate manager to '''redeem tickets'''. This model should be able to describe the interdependency relationship among the slivers so that the controller can stitch to a slice. 
     95        This is used by the clearing house (brokers) to return resource reservation description to the SM controller so that the controller can use it to talk to related substrate manager to '''redeem tickets'''. This model should be able to describe the interdependency relationship among the slivers so that the controller can stitch to a slice. 
    9696   
    9797== 5. Slice manifest model (Not implemented yet) ==