Open Services Cloud, new OCL and controller API

[jbonofre]

In RC1, we directly create the end user resources (VM, network, etc) based on OCL description.

However, this is not the target objectives: the OSC objectives is to integrate into cloud infrastructure and let the end users still create their resources (via the cloud admin console for instance).

So, OSC should deploy "controller".

The OCL could look like:

{
  "name": "my-managed-service",
  "properties": {
    "category": "foo", 
    "billing.model": "monthly",
    "billing.rate": 10
  },  
  "controller": {
    "resource": {
       "type": "vm",
       "base": {
          "image": "ubuntu",
          "cpu": 2,
          ...
       },
      "provider": "my-controller.jar"
    },  
    "templates": {

    },  
  }  
}

The OCL properties are generic properties (open key/value pairs) containing OSC handled properties (like billing, admin console integration, etc).
The controller section provides:

• the resources needed to actual deploy the controller in the cloud infrastructure (the resources part)
• the end user resources created by the controller on user request (the templates part)

It means to register a managed service, software vendors have to provide:

• the OCL json file
• the controller implementation that use the OSC API
  (both could be package as a OSC archive like my-service.osc (zip file).

The software vendor would have to implement the Controller interface:

public interface Controller {

  public void createService(Template template) {
     // create end user service resources based on template. This is called by cloud backend when user request creation of service instancee
  }

  public void removeService(Template template) {

  }

With this approach, OSC doesn't create end user resources anymore, it creates and exposes controller used on user request to create end user service instances (multi tenant).

[jbonofre]

@swaroopar @Jiajia-Wen @iskey @niuzhenguo I started this discussion about OSC updated roadmap, introducing controller "approach".