VNF Appliance Integration

Project Introduction

There are following user cases

• Users want to be able to deploy Virtual Network Function (VNF) VM appliances in a seamless manner

• Users also want to be able to access the management portal of their VNFs directly “from” ACS

• Service providers want integration of VNFs with ACS, this FR provides for basic integration in a vendor neutral manner

Currently in order to deploy a VNF appliances end-users need to create at least 3 networks (north, south and management) and then attach the relevant networks to the VM.

This feature provides for a new Appliance deployment wizard where end-users can select 3 networks when deploying the VNF VM appliance.

Functional Description

1. Register a VNF template

Adding an appliance template or ISO will be almost identical to adding a compute template or ISO. They will be denoted as being for appliances in the database, and additional metadata stored for them; including:

· Informational text relating to NICs that will be expected and their order

· Default username and password

· Default web url path and port of the http mgmt interface (if there is one).

· Any other helpful 'getting started' information

· Custom (Vendor) Icon for representation in the UI

· Appliance image versio

2. Create a VNF appliance from VNF template

VNF appliance integration by the cloud operator, for a new VNF the operator must:

- Assign interfaces for North, South and management. On registration of a template they select:

o Interface1 = (North, South, mgmt.)

o Interface2 = (North, South, mgmt.)

o Interface3 = (North, South, mgmt.)

o Management URL for the VNF

- When deploying a VNF appliance the end-user must select

o Network for North interface

o Network for South interface

o Network for management

- After deployment of the VNF, ACS must present to end-user:

o Management URL in the format https(s)://IPMGMTInterface/managementURLspecifiedbyoperator:portSpecifiedByOperato

Non-Functional Requirements

ISOs, templates and VM instances which are Appliances, are essentially no different from existing VM templates, ISOs and instances. They need not have separate tables in the DB. Largely existing attributes such as 'type' can be extended to denote that the element is an appliance in nature.

Instantiating an appliance is actually simply provisioning a VM. However, these 'Appliances' should not be presented alongside "normal" VMs - they are a distinct object type from the users' perspective and will be displayed within the networking tab.

User Interface

Milestones

Glossary