Changes between Version 59 and Version 60 of NDL-OWL

Show
Ignore:
Timestamp:
02/24/11 16:42:54 (8 years ago)
Author:
yxin (IP: 152.54.6.102)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NDL-OWL

    v59 v60  
    4343                     * !ProtoGeniNode 
    4444                 
    45                 For example, the ''EC2M1Small'' is defined that has the ''EC2CPUCore'' (an EC2 core equivalent of AMD 1.7Ghz) , 1 cpu core  count, 128M memory, 2G storage, and support both ''Xen'' and ''KVM'' VMM virtualization. See [source:orca/trunk/network/src/main/resources/orca/network/schema/geni.owl geni.owl] for details. 
     45                For example, the ''EC2M1Small'' is defined that has the ''EC2CPUCore'' (an EC2 core equivalent of AMD 1.7Ghz) , 1 cpu core  count, 128M memory, 2G storage, and support both ''Xen'' and ''KVM'' VMM virtualization. See [source:orca/trunk/network/src/main/resources/orca/network/schema/geni.owl geni.owl] for details. This allows describing a server/server cloud instance to host an instance of the  VM instance via the property ''VM-in-Server'' which is a sub-property of ''AdaptationProperty''. 
    4646                                
    4747   [[Image(ndl-geni-ComputeElement.png)]] 
    4848 
    49                 * !ClassifiedServerInstance: has above ''!ClassifiedServer'' classes as its instance members.  
     49                * !ClassifiedServerInstance: has above ''!ClassifiedServer'' classes as its instance members. This enables a specific server cloud to claim the type of VM node it can support. 
    5050  
    5151                * !ComputeComponentElement:  
     
    8787        It would define a top-level ''Reservation'' object to describe a particular reservation (term, etc.).  
    8888        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 and amount of particular resource types.   
     89         In the multi-domain setting, the controller (in the service manager) would automatically break the user request into domain-specific sub-requests that are sent to the substrate AM when redeeming. This happens after the controller finishes inter-domain path or topology computation.         
     90 
    8991        * 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).  
    9092        * In redeeming the ticket to a specific site, the controller would dynamically create a sub-request to ask for a sliver.