Skip to content

Feature for MAAS as a VIM

MAAS as a VIM

Proposer

Adam Israel (Canonical) Arno van Huyssteen (Canonical) David Garcia (Canonical) Eduardo Sousa (Canonical)

Type

Feature

Target MDG/TF

UI, RO, IM

Description

The rising of edge use cases combined with the limitation of resources at those sites indicate that there needs to be a lower footprint VIM in terms of control when compared with Openstack.

One option would be MAAS (http://www.maas.io). MAAS is capable of provisioning baremetal clouds, which would allow to run VNFs on top of nodes instead of VMs. MAAS also allows to slice nodes into a number of static VMs, so there could be sites where nodes are already partitioned, which would allow to have a set of slots for VNF per site.

The proposal goes into the adaptation of the VIM plugins to support baremetal clouds (eg. MAAS, Openstack Ironic) and the creation of a VIM plugin for RO that allows the usage of MAAS.

UI requires changes in order to accommodate for the different configuration options required for the plugins. RO requires a plugin so it can communicate with the MAAS API.

Since MAAS doesn't perform scheduling of workloads as Openstack does, it is necessary to pass the tags of the machines to be used for placement of VNFs. This doesn't mean that the user will manually place the workloads into nodes, it just requires the user to specify which group of nodes where those VNFs should be deployed. This will require an optional configuration of the NSR/VNFR in order to contain the required tags of the machines where those workloads should be deployed.

Demo or definition of done

  • Being able to add MAAS as a VIM.
  • Being able to deploy VNFs in MAAS clouds.
  • Being able to create VLDs in MAAS clouds.