Version 2 (modified by ibaldin, 8 years ago)


Request model


This is the abstract model to represent user resource requests. A typical request might be a virtual topology with specific resources at the edges, generated by unspecified experiment control tools. In our implementation, the representation is produced by a controller module in the slice manager (SM) after interpreting the user's request in an ad hoc format.

In the current implementation for the multi-domain setting, this SM controller performs inter-domain path or topology computation based on a description of the global topology, and automatically breaks the user request into sub-requests for each domain.

  • The topology request is defined as a collection of bounded or unbounded connections. The end node of the connection can specify the amount of requested edge resource type (e.g. number of VMs or other slivers).
  • In redeeming the ticket to a specific site, the SM controller dynamically creates a sub-request to ask for a sliver.