Changes between Version 22 and Version 23 of NDL-OWL

Show
Ignore:
Timestamp:
02/16/11 18:50:06 (8 years ago)
Author:
yxin (IP: 152.54.9.71)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NDL-OWL

    v22 v23  
    1 = A. Domain data models =  
     1= A. Models =  
    22 
    3 We need a set of unified semantic schemas for 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 are trying to stay away from the procedural programming model to a semantic query based programming approach to implement the policies for resource allocation, path computation, and topology embedding applications. 
     3We 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 are trying to stay away from the procedural programming model to a semantic query based programming approach to implement the policies for resource allocation, path computation, and topology embedding applications. 
    44 
    55There are at least 5 types of models to be defined, that are circulated among the site authorities, broker and service manager. 
     
    5454 
    5555== 3. Slice request model == 
    56         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. This description is sent to the clearing house via '''Request Ticket'''.  
     56        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.  
    5757        * 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).  
     58        * In redeeming the ticket to a specific site, the controller would dynamically create a sub-request to ask for a sliver. 
    5859 
    5960== 4. Slice reservation model (Not implemented yet) ==  
     
    6364        This is used to describe the access method, state, and other post-configuration information of the reserved slivers. 
    6465 
    65 = B. Semantic description of the data models =  
    66 We envision NDL-OWL would provide an unified semantic schema for above 5 types of data models, which will be represented in RDF format. We use NDL-OWL - a further development of the [http://www.science.uva.nl/research/sne/ndl Network Description Language], for the [http://ben.renci.org BEN] network resource description, slice requests and slice descriptors. We have extended the original NDL using OWL. We are also in the process of including more technologies into the NDL-OWL [https://geni-orca.renci.org/owl schema]. 
     66= B. Resource allocation and stitching policies = 
     67Current 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. 
    6768 
    68 = C. Service provisioning implementation =  
    69 We are trying to stay away from the procedural programming model to a semantic query based programming approach. 
    70 We use a number of [wiki:OrcaNDL tools] to create and manipulate NDL-OWL ontologies.  
    71  
    72 = D. Resource allocation policies = 
     69* Stitching Resource Components Information (=Common Topology Schema Information) 
     70* Common Topology Schema definition 
     71* AM API Extensions for Stitching  
     72* Stitching WorkFlow API Definition 
     73* Stitching Path Computation API Definition  
     74* Stitching Topology Service API Definition