CORD : E2E Slicing

E2E design discussion page .

UI Mockups

Please note that these are mockups, they are intended to express functionalities not appearance, the final implementation will look different and more graphic oriented.

Slicing UI

For a more detailed mockup please refer to: https://invis.io/B88ABR035

XOS Service Structure (to be confirmed)

Slicing UI Helper

This is not strictly a service from an XOS point of view (as it will not require a synchronizer). It's only task is to create a representation of the Topology displayed in the UI reading the information from other services.

This is the proposed data structure to store UI related informations, model related information are stored in the related service, referenced here by `model_id` and models will be synced by their related service.

Nodes

id	name	type	model_id	plane
1	ue-1	ue	1	null
2	profile-1	profile	1	null
3	ran-cu-1	ran-ru	1	data
4	ran-cu-1	ran-ru	1	control
5	ran-cu-1	ran-cu	1	data
6	ran-cu-1	ran-cu	1	control

Links

id	source	target	plane
1	1	2	data
2	2	3	data
3	3	5	data
4	3	4	control
5	5	6	control

REST API response

Retrieve the topology structure:

[GET] /api/services/mcord/slicing

{
    nodes: [
        {id: 1, name: 'ue-1', type: 'ue', model_id: 1, plane: null},
        ...
    ],
    links: [
        {id: 1, source: 1, target: 2, plane: 'data'}
    ]
}

NOTE: All the update action will be performed agains the related service APIs

TODO:

Define which attributes should be contained in the services models:
- Progran (Murat Parlakisik)
  - UE
  - Profile
  - Enode
  - Tenant
- MME (Pingping Lin)
- PGW (Pingping Lin)
- SGW (Pingping Lin)
Document required REST endpoints for services (eg: update a UE, update a PROFILE, select PGW image) (Matteo Scandolo)
Create the services (to follow XOS guidelines [Tenants])
Define the service chain