Changes between Version 62 and Version 63 of NDL-OWL

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

--

Legend:

Unmodified
Added
Removed
Modified
  • NDL-OWL

    v62 v63  
    11= NDL-OWL Models in ORCA = 
    22 
    3 We describe the models in the life cycle of resource reservations and the resource allocation policy and stitching workflow implementation. The implementation details refer to the Camano generation of ORCA code. 
     3We describe the models in the life cycle of resource reservations (leases) and the resource allocation policy and stitching workflow implementation. The implementation details refer to the Camano release of ORCA code. 
    44 
    5 We 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. 
     5We need a set of unified semantic schemas for representing the data models to describe resources in a reservation across the stages of its life cycle. 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. NDL-OWL gives us a flexible semantic query-based programming approach to implement the policies for resource allocation, path computation, and topology embedding applications.  It enables these functions to be coded generically to operate on declarative specifications, rather than baking in assumptions about the resources. 
    66 
    7 There are at least 5 types of models to be defined, that are circulated among the ORCA actors (authority/AM, broker and slice manager).  
     7There are at least 5 types of models to be defined.  ORCA actors (authority/AM, broker and slice manager/SM) pass these representations as they interact to stand up reservations at multiple substrate aggregates and stitch them into an end-to-end slice. 
    88 
    99== 1. Substrate description model == 
    10 This is the substrate-specific detailed resource and topology model that is used by the owner of the substrate to describe its physical resources including edge (compute and storage) resource and network topology. It also describes the domain services exposed to the broker(s).  
     10This is the detailed resource and topology model that is used by the owner of the substrate to describe its physical resources including edge (compute and storage) resource and network topology.  ORCA AMs use this representation to delegate advertised resources to ORCA broker(s).  AMs may also use this representation to describe resources in response to queries (e.g., ListResources) or to advertise resources to a GENI clearinghouse.  
    1111 '''a. Domain Service Description ([source:orca/trunk/network/src/main/resources/orca/network/schema/domain.owl domain.owl])'''  
    12       The class hierarchy is defined in the diagram below. A substrate (domain) is defined as a collection of !PoPs. Each PoP, with a geographical location, is a collection of network devices and/or data center. The Class ''Domain'' also has a property ''!NetworkService'' which could have a number of ''!ServiceElement''. This information would be passed to the advertisement RDF. 
     12      The class hierarchy is defined in the diagram below. A substrate (domain) is defined as a collection of !PoPs. Each PoP has a geographical location and a collection of network devices and/or edge resources (e.g., a cloud provider site). The Class ''Domain'' also has a property ''!NetworkService'' which could have a number of ''!ServiceElement''. This information would be passed to the advertisement RDF. 
    1313             * !AccessMethod: e.g. ORCAActor, or GENI AM API. 
    1414             * Topology: Topology abstraction level exposed to outside. Right now, only node abstraction is defined. 
    15              * !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.    
     15             * !ResourceType: This is inferred via a list of defined available resource label set, e.g. 32 VMs, 100 VLANS.    
    1616             * !AggregateManager: e.g. the URL of its aggregate manager. 
    1717