Changes between Version 7 and Version 8 of orca-introduction

Show
Ignore:
Timestamp:
04/22/11 13:48:48 (8 years ago)
Author:
ibaldin (IP: 108.65.61.102)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • orca-introduction

    v7 v8  
    2121intermediaries respectively. There can be many instances of each actor type, e.g., representing di?erent substrate providers or resource consumers. 
    2222 
    23  * Authority or Aggregate Manager (AM). An authority actor controls access to some subset 
    24 of the substrate components. It corresponds directly to the aggregate manager (AM) in GENI. 
    25 Typically, an authority controls some set of infrastructure resources in a particular site, autonomous 
    26 system, transit domain, administrative domain, or component aggregate comprising a set of servers, 
    27 storage units, network elements, or other components under common ownership and control. 
    28 Terminology note. The term site or site authority (e.g., a cluster site or hosting center) is often 
    29 used to refer to a substrate authority/AM, as a result of our roots in virtual cloud computing. For 
    30 network substrates we are using the term domain authority more often when it is appropriate. 
     23 * Authority or Aggregate Manager (AM). An authority actor controls access to some subset of the substrate components. It corresponds directly to the aggregate manager (AM) in GENI. Typically, an authority controls some set of infrastructure resources in a particular site, autonomous system, transit domain, administrative domain, or component aggregate comprising a set of servers, storage units, network elements, or other components under common ownership and control. Terminology note. The term site or site authority (e.g., a cluster site or hosting center) is often used to refer to a substrate authority/AM, as a result of our roots in virtual cloud computing. For network substrates we are using the term domain authority more often when it is appropriate. 
    3124 
    32  * Slice/Service Manager (SM) or Slice Controller. This actor is responsible for creating, 
    33 con?guring, and adapting one or more slices. It runs on behalf of the slice owners to build each 
    34 slice to meet the needs of a guest that inhabits the slice. 
    35 Terminology note. This actor was originally called a service manager in SHARP (and in the Shirako 
    36 code) because the guest was presumed to be a service. As GENI has developed, we have adopted 
    37 the term slice controller because the actor’s role is to control the slice, rather than the guest itself, 
    38 and because in GENI the guest is an experiment rather than a service. Slice Manager (also SM) 
    39 is also OK since the “controller” is properly speaking a plugin module to the actor itself.  
     25 * Slice/Service Manager (SM) or Slice Controller. This actor is responsible for creating, configuring, and adapting one or more slices. It runs on behalf of the slice owners to build each slice to meet the needs of a guest that inhabits the slice. Terminology note. This actor was originally called a service manager in SHARP (and in the Shirako code) because the guest was presumed to be a service. As GENI has developed, we have adopted the term slice controller because the actor’s role is to control the slice, rather than the guest itself, and because in GENI the guest is an experiment rather than a service. Slice Manager (also SM) is also OK since the “controller” is properly speaking a plugin module to the actor itself.  
    4026 
    41  * Broker. A broker mediates resource discovery and arbitration by controlling the scheduling of 
    42 resources at one or more substrate providers over time. It may be viewed as a service that runs 
    43 within a GENI clearinghouse. A key principle in Orca is that the broker can have speci?c allocation 
    44 power delegated to it by one or more substrate authorities, i.e., the substrate providers “promise” 
    45 to abide by allocation decisions made by the broker with respect to their delegated substrate. 
    46 This power enables the broker to arbitrate resources and coordinate allocation across multiple 
    47 substrate providers, as a basis for federation and scheduling of complex slices across multiple 
    48 substrate aggregates. Brokers exercise this power by issuing tickets that are redeemable for leases. 
     27 * Broker. A broker mediates resource discovery and arbitration by controlling the scheduling of resources at one or more substrate providers over time. It may be viewed as a service that runswithin a GENI clearinghouse. A key principle in Orca is that the broker can have specific allocation power delegated to it by one or more substrate authorities, i.e., the substrate providers “promise” to abide by allocation decisions made by the broker with respect to their delegated substrate. This power enables the broker to arbitrate resources and coordinate allocation across multiple substrate providers, as a basis for federation and scheduling of complex slices across multiple substrate aggregates. Brokers exercise this power by issuing tickets that are redeemable for leases. 
    4928 
    5029