Changes between Version 12 and Version 13 of NDL-OWL

02/15/11 18:14:29 (8 years ago)
yxin (IP:




    v12 v13  
    88This 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.  
    99   1 ''Domain Service Description''  
    10       [[Image(wiki:NDL-OWL:ndl-domain.png)]]  
    11       The class hierarchy is defined in the diagram. 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.  
     10      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.  
    1211The Class domain also has a property "NetworkService" which could have a number of "ServiceElement". This information would be passed to the advertisement RDF. 
    1312             * AccessMethod: e.g. ORCAActor, or GENI AM API. 
    1817   2 ''Compute Resource Description (compute.owl)'' 
    19        [[Image(wiki:NDL-OWL:ndl-compute.png)]]             
     18       The class hierarchy is defined in ndl-compute.png. Three subclass hierarchies are defined here: 
     19        * Features: 
     20                * VMM (XEN, KVM, VServer etc.) 
     21                * OS (Linux, Windows) 
     22                * ServerSize: Defined by the size of CPU, Memory, Storage.  
     23                      * MediumServerSize 
     24                      * LargeServerSize 
     25                      * SmallServerSize 
     26                 * Vendor 
     27        * ComputeElement 
     28                * ClassifiedServer : defined by the serverSize. 
     29                     * LargeServer  
     30                     * MediumServer 
     31                     * SmallServer  
     32                     * UnitServer 
     33                * ComputeComponentElement -> {VMImage, CPU, DiskImage, Memory} 
     35        *  NetworkElement -> Server -> {ServerCloud, VirtualMachine, PhysicalMachine); VirtualMachine->{EC2Node, PlanetLabNode, ProtoGeniVNode, ProtoGeniRaw)  
     36                * A specific server class is defined by property constraints on features and ComputeElement. 
     37                   E.g. The ''ProtoGeniVNode'' class is defined as a VirtualMachine that "hasVMM VServer". It can be further defined to "hasVMIImage x" and "is a MediumServer".               
    21    3 ''Network topology and resource description'' 
     39   3 ''Network topology and resource description'': extension of the original NDL 
     40         * topology.owl 
     41         * layer.owl 
     42         * ethernet.owl,ip4.owl,dtn.own 
    2344=== Substrate delegation model === 
    2445        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: 
    2950             * AggregateManager: e.g. the URL of its aggregate manager. 
    3051       * Domain topology abstraction: Currently, the whole doman is abstracted to a node, a network device with following information: 
    31                * switching matrix type: ethernet, IP, etc.. 
     52               * Switching matrix: capability (ethernet, IP, etc.), label swapping capability (means vlan translation for ethernet switching)  
    3253               * Border interfaces: connectivity to neighboring domains, bandwidth and available label set (e.g. vlan)  
    3655=== Slice request model === 
    3756        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'''.  
     57        * 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 (e.g. amount of smallSize servers).  
    3959=== Slice reservation model ===