Azure connector

Proposers

Gerardo Garcia (Telefonica)
Francisco Javier Ramon (Telefonica)

Type

Feature

Target MDG/TF

Description

With this feature the support of Azure as part of the public cloud portfolio of supported VIM will be significantly enhanced.

The initial implementation of Azure connector in RO currently is not passing any of the E2E integration tests. It is only able to deploy a very simple NS under some pre-configured circumstances. Besides, it lacks of most of the features, which makes it of limited practical use today.

The connector needs to be re-implemented to:

Perform a proper authentication via an Azure Service Principal
Leverage mechanism to inject SSH keys and day-0 configuration (cloudinit)
Manage resources in several resource groups (one per NS or project). Currently all resources land in a single resource group, passed as VIM config parameter
Create networks and subnets on demand if needed. Currently a network needs to be pre-provisioned and all VLDs are translated to subnets in that network. Instead, each VLD should lead to its own network and subnet.

Demo or definition of done

Once implemented, all OSM E2E tests over Azure Cloud infrastructure excepting those related to EPA and Azure Monitoring services should pass.