Changes between Version 22 and Version 23 of orca-introduction

04/22/11 16:37:09 (8 years ago)
ibaldin (IP:



  • orca-introduction

    v22 v23  
    3030 * 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. 
    32 Actors in ORCA are referred to by names and GUIDs. Each actor must be identifier by a unique name and GUID.  
    3432[[Image(orca-arch.png, 600px)]] 
    3836Slices are used to group resources together. A slice in a Service Manager represents resources owned by a particular user (e.g. for the purpose of an experiment). A slice in a Broker represents a portion of slivers given to a particular service manager slice from this Broker. If a Service Manager acquires resources from multiple brokers, they are not aware of each other. A slice in an authority represents the resources given by this authority to a particular service manager slice. Notice that architecturally in ORCA ''only the Service Manager knows the exact composition of the slice''. All other actors may have only a partial view of the slice.  
     38== Naming == 
     40Actors in ORCA are referred to by names and GUIDs. Each actor must be identifier by a unique name and GUID.  
    4042Slices are referred to by names and GUIDs. Those are normally automatically generated by various actors: