New feature: euag_improved_management_of_datacenter_capabilities.md

Improved management of datacenter capabilities

Proposer

EUAG

Type

Feature

Target MDG/TF

RO, SO, UI

Description

One of the features in the backlog for Release ONE was the ability to filter requests to the VIM based on the VIM and datacenter capabilities. For instance, it is desirable that some actions towards the VIM (e.g. deployment of a VM with data plane interfaces) could be rejected at RO level based on the declared capabilities of the VIM, without the need to run the long process of interacting to the VIM, running the associated task in VIM, and monitoring the status in VIM (e.g. VM in active state) to know if there was an error at deployment time.

It is suggested to upgrade this feature taking into account the following needs:

• It should not be restricted to the RO, but expanded to the UI and SO. Datacenters and the manual edition of the capabilities should be exposed in the UI. Default values for Openstack, OpenVIM and VMware should be loaded when adding a new datacenter in the UI, but these values could be changed at any moment through the UI.
• If a capability is not supported by a datacenter, two behaviors are allowed:
  • Either the request is rejected at RO level, without even asking to the VIM,
  • Or the request is adapted (i.e. translated) to the VIM capabilities, with no guarantees.

For instance, let’s imagine that we have a NS with two VNFs requiring EPA and we want to force their deployment in an Openstack environment with no EPA support just for functional testing purposes. The end users instantiating the NS would be able to specify if they want a strict instantiation or a best-effort instantiation. In a best-effort instantiation, the EPA requirements would be translated to non-EPA requirements.

Demo or definition of done

N/A