Changes between Version 18 and Version 19 of NDL-OWL

02/16/11 14:06:17 (8 years ago)
yxin (IP:




    v18 v19  
    33There are at least 5 types of models to be defined. 
    5 == Substrate description model == 
     5== 1. Substrate description model == 
    66This is the substrate specific detailed resource and topology model that is used by the substrate manager to describe its physical resource including edge (compute and storage) resource and network topology. It also describes the domain service exposed to the broker.  
    7  '''1. Domain Service Description(domain.owl)'''  
     7 '''1.a. Domain Service Description(domain.owl)'''  
    88      The class hierarchy is defined in the diagram ndl-domain.png. 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.  
    99The Class domain also has a property ''NetworkService'' which could have a number of ''ServiceElement''. This information would be passed to the advertisement RDF. 
    1313             * AggregateManager: e.g. the URL of its aggregate manager. 
    15    '''2. Compute Resource Description (compute.owl)''' 
     15   '''1.b. Compute Resource Description (compute.owl)''' 
    1616       The class hierarchy is shown in ''ndl-compute.png''. Three subclass hierarchies are defined here: 
    1717        * Features: 
    3535                   E.g. The ''ProtoGeniVNode'' class is defined as a VirtualMachine that ''hasVMM VServer''. It can be further constrained to ''hasVMIImage x'' and ''is a MediumServer''.               
    37    '''3. Network topology and resource description''': extension of the original NDL 
     37   '''1.c. Network topology and resource description''': extension of the original NDL 
    3838         * topology.owl 
    3939         * layer.owl 
    4040         * ethernet.owl,ip4.owl,dtn.own 
    42 == Substrate delegation model == 
     42== 2. Substrate delegation model == 
    4343        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: 
    4444       * Domain network service. 
    5151               * Border interfaces: connectivity to neighboring domains, bandwidth and available label set (e.g. vlan)  
    53 == Slice request model == 
     53== 3. Slice request model == 
    5454        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'''.  
    5555        * 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).  
    57 == Slice reservation model ==  
     57== 4. Slice reservation model ==  
    5858        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. 
    60 == Slice manifest model == 
     60== 5. Slice manifest model == 
    6161        This is used to describe the access method, state, and other post-configuration information of the reserved slivers.