Version 4 (modified by yxin, 8 years ago)


Overall, we need to develop following components for resource provisioning services in the GENI control framework.

== Domain data models. There are at least 5 types of models to be defined==

Substrate description model

This is substrate specific detailed resource and topology model that is used by the substrate manager to maintain the current state of its resource.

  • Compute Resource Description (compute.owl)

The class hierarchy diagram is shown here

  1. Substrate delegation model: This is the abstract model that is used by the substrate manager to delegate its available services and resources to outsiders, the clearing house in the GENI context. This mode should allow multiple abstraction levels as different substrate manager may want to expose different levels of resource and topology description of its substrate.
  2. Slice request model: This is used by the user, or the slice controller after interpreting the user's requests in ad hoc format, to describe the specifics of the user's request, often this is represented in the form of a virtual topology. This description is sent to the clearing house via Request Ticket.
  3. Slice reservation model: This is used by the clearing house (brokers) to return resource reservation description to the slice controller so that the controller can use to talk to related substrate manager to redeem tickets. This model should be able to describe the interdependency relationship among the slivers so that the controller can stitch to a slice.
  4. Slice manifest model: This is used to describe the access method, state, and other post-configuration information of the reserved slivers.

2. Semantic description of the data models. We envision NDL-OWL wold provide an unified semantic schema for above 5 types of data models, which will be represented in RDF format. We use NDL-OWL - a further development of the Network Description Language, for the BEN network resource description, slice requests and slice descriptors. We have extended the original NDL using OWL. We are also in the process of including more technologies into the NDL-OWL schema.

3. Service provisioning implementation. We are trying to stay away from the procedural programming model to a semantic query based programming approach.

We use a number of tools to create and manipulate NDL-OWL ontologies.

4. Resource allocation policies.