Gcube/Resource Management for the gCube Model/discussions

04.05.2018

Participants: Lino, Manuele

Discarded functionality: Merging two contexts is not a requirement
New functionality: Cloning a context. We clone users, services, resources, but not data.
New functionality: Create a template definition from an existing context to recreate (or clone) it at a later time
- Impact on the design: RM needs a new collection of resources Templates (in the REST sense) to operate on the templates of contexts.
- Cloning a context could be an operation on a Template resource.
The Resource Manager operates at Virtual Service level. A Virtual Service is a bag of Services that delivers a logical group of functionalities. A request to RM specifies which Virtual Service to add/remove/edit. The RM translates this request to the list of concrete services (by querying the Resource Registry) and then instructs the Resource Registry accordingly.
New functionality: When a Service is added or remove to a context, certain configuration steps could be necessary (e.g. create a new user o space in a DBMS). See Actions in the following.

Virtual Services: their definitions are created with a portlet
Often, the same Virtual Service differs from one VRE to another, only for 1 Service (typically a DBMS). In these cases, we would like to have a single Virtual Service definition, not many with just a slight difference
- Possible solution: Associate also a Type to a service and let the RM discovers the service of that Type in the parent context of the target context.
- TODO: investigate if it already exists in the gCube Resource Model
Actions to trigger associated to each Service
- TODO: Investigate if Configuration can be used
- Possible Action definition:

...

gxRest should be linked in the Core Facilities section
the TOC of the development guide should be a real Table of Contents. It's not possible that to find (for instance) the FWS, one has to click on several links sparse on the pages (Manuele).