Resource allocation policies and stitching API

Current implementation is based on a two-level resource allocation and stitching model: the controller and the broker policies do the cross-site path/topology computation/embedding and resource allocation based on the abstract delegation models. Upon reservation redemption, each site implements its own control policy to do intra-site sub-path/topology computation/embedding and resource allocation based on the its substrate RDF model. The core of the process is a reservation dependency workflow model.

1. Stitching Resource Components Information (Common Topology Schema Information)

The information should be obtained online when a substrate is stand up and contains two types of information:

  • Domain network service.
    • AccessMethod: e.g. ORCAActor, or GENI AM API.
    • Topology: Topology abstraction level exposed to outside. Right now, only node abstraction is defined.
    • ResourceType: This is inferred via a list of defined available resource label set, e.g. 32 VMs, 100 VLANS, that will be delegated to the broker.
    • AggregateManager: e.g. the URL of its aggregate manager.
  • Domain topology abstraction: Currently, the whole doman is abstracted to a node, a network device with following information:
    • Switching matrix: capability (ethernet, IP, etc.), label swapping capability (means vlan translation for ethernet switching)
    • Border interfaces: connectivity to neighboring domains, bandwidth and available label set (e.g. vlan)

2. Common Topology Schema definition

3. AM API Extensions for Stitching

  • AM abstraction delegation: abstract rSpec.
  • AM query: available resource
  • AM sub-request redeeming: local provisioning

4. Stitching Workflow API Definition

  • Input: outputs of 5 and 6.
  • Output: parent-children relationship in a dependency workflow DIG.

5. Stitching Path Computation API Definition

  • Input: (source <resource type,units,IP address>, destination<resource type,units,IP address>, performance <layer,bandwidth,delay>, <source site>,<destination site>)
  • Output: List of sites.

6. Stitching Topology Service API Definition

  • Input: (A collection of requested paths, A collection of available sites)
  • Output: a collection of list of sites per path.

External stitching Ports and References