1. RESOURCE MANAGEMENT AND TOPOLOGY EMBEDDING IN A DISTRIBUTED NETWORKED INFRASTRUCTURE ENVIRONMENT S. Papavassiliou, C. Papagianni NETMODE, NTUA I.Baldin, Y.Xin RENCI, UNC Chapel Hill

2. Outline Topology Embedding: Overview, Terminology and Supporting Functions Problem Overview and Application Domains Intra- and Inter-domain Embedding Coordination of Embedding Functions Architectural Approaches Implementation Approaches Broker-based Architecture Pros and Cons Resource Delegation Options Levels of Resource Abstraction Topology Embedding Enabling APIs

3. Problem Overview and Application Domains Network Virtualization Environment Virtual Network Embedding (VNE) or Topology Embedding Efficient utilization of resources, increase InP revenue.. Application Domains Multi-tenant virtualization environments Sliceable network testbeds Networked cloud environment

4. Intra-domain Topology Embedding Embedding Functions: Matching Placement Pathfinding across domain infrastructure AB CD EF GH I a 15 b 12 c 13 9045 67 89 78 53 1010 12 1010 22 1520 15 17 13 43 a bc VN Substrate 105 18

5. Inter-domain Topology Embedding Embedding Functions: Matching Partitioning Pathfinding across domains InP 1InP 2

6. Coordination of Embedding and other Functions Performing embedding requires coordination, either Tool InPs/aggregates.. Or across InPs Intermediary entity (broker) Requires InPs make promises/delegations of resource availability to brokers Described at the level of detail that supports embedding, but doesn’t compromise provider privacy Logically centralized or distributed Hierarchies of brokers

7. Broker-based Approach vs Tool-based Approach Improved Scalability – take on the distributed agreement from InPs Neutral PEP – implement federation-level authorization policies without the need to trust providers Dispute resolution Simplify User Tools development / Management SW for InPs Sophisticated and Fair Embedding – implement portions of embedding logic Exact partitioning of embedding functions between tools, brokers and InPs is an open problem

8. Broker-based Approach: Resource Delegation Resource Delegation Timeliness vs. Communication Overhead Strength of Promises Examples: ExoGENI – typically long-lived promises F4F Reservation Broker – typically short- lived Oversubscription Especially with multi-federation scenarios Must be possible, in order to help InPs with resource utilization Must remain a provider choice

9. Levels of Resource Abstraction & Topology Embedding Substrate or domain model abstraction Information disclosure vs. Embedding efficiency Example: domain ‘switch’ abstraction Requirements for a Broker-based Architecture Facilitate searching: use appropriate URIs for publishing and linking model elements across distributed models Embedding related: IM should support multiple levels of detail (InP to tenant) IM should support similarity relationships between resource descriptions for improved matching (semantics)

10. Enabling APIs Broker Delegation/update Accept resource delegations from InPs with different strength of promises Digitally Signed, Validity Term Support unsolicited updates InP (e.g., AM) or InP’s Monitoring System Possibly all the way to the tenant Query Matching: Querying for resources e.g., closest match, through time etc. Queries for historical information e.g., accounting, reputation etc. Reservation/embedding Support reservation process Support embedding and reservation (single or two-step procedure) Or support ticket issuing for the tenant

11. Thank you!