Skip to content
Snippets Groups Projects
README.md 907 B
Newer Older
Christos Tranoris's avatar
Christos Tranoris committed
# Generic Controller example
tranoris's avatar
tranoris committed

Christos Tranoris's avatar
Christos Tranoris committed
OSL's Service orchestrator (OSOM) has the capability of contacting external controllers, given a specific resource category that this controller can manage. 
tranoris's avatar
tranoris committed

Christos Tranoris's avatar
Christos Tranoris committed
This project is an example of creating a generic controller, that registers two Resource Specifications for managing resources ResourceA and ResourceB. 
tranoris's avatar
tranoris committed

Christos Tranoris's avatar
Christos Tranoris committed
Listens for messages on queues as registered by category name and version for CREATE/UPD/DELETE, with this scheme:
tranoris's avatar
tranoris committed

Christos Tranoris's avatar
Christos Tranoris committed
- CREATE / category_name / version
- UPDATE / category_name / version
- DELETE / category_name / version
tranoris's avatar
tranoris committed

Christos Tranoris's avatar
Christos Tranoris committed
here we have:
tranoris's avatar
tranoris committed

Christos Tranoris's avatar
Christos Tranoris committed
  - category: gcontroller.examples.osl.etsi.org
  - version: 0.1.0
tranoris's avatar
tranoris committed


Christos Tranoris's avatar
Christos Tranoris committed
The project registers automatically the two Resource Specifications (RSpecs) and we added handler functions for create, update and delete.
tranoris's avatar
tranoris committed

Christos Tranoris's avatar
Christos Tranoris committed
So when you create CFSs services using these (RSpecs) the Service Orchestrator will call these functions via the queue