Changes between Version 41 and Version 42 of NDL-OWL

Show
Ignore:
Timestamp:
02/17/11 10:15:13 (8 years ago)
Author:
yxin (IP: 152.54.9.71)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NDL-OWL

    v41 v42  
    4949 
    5050== 2. Substrate delegation model == 
    51         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 and contains two types of information: 
     51        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: 
    5252       * Domain network service. 
    5353             * !AccessMethod: e.g. ORCAActor, or GENI AM API. 
     
    7171 
    7272= B. Resource allocation and stitching policies = 
    73 Current implementation is based on a two-level resource allocation and stitching model: the controller and the broker policies do the cross-site path/topology computation/embedding and resource allocation based on the abstract delegation models. Upon reservation redemption, each site implements its own control policy to do intra-site sub-path/topology computation/embedding and resource allocation based on the its substrate RDF model. The whole process is based on a reservation dependency workflow. 
     73Current implementation is based on a two-level resource allocation and stitching model: the controller and the broker policies do the cross-site path/topology computation/embedding and resource allocation based on the abstract delegation models. Upon reservation redemption, each site implements its own control policy to do intra-site sub-path/topology computation/embedding and resource allocation based on the its substrate RDF model. The core of the process is a reservation dependency workflow model. 
    7474 
    7575 == 1. Stitching Resource Components Information (Common Topology Schema Information) ==