-
Notifications
You must be signed in to change notification settings - Fork 15
CNF VNFD Example
Felipe Vicens edited this page Feb 27, 2019
·
13 revisions
This is an example of a VNFD which describes a CNF. It is a living document to define how such a descriptor should look like, so that we can create a schema for it. PNF and CNF schemas are currently developed in Issue 79.
---
descriptor_schema: "https://raw.githubusercontent.com/sonata-nfv/tng-schema/master/function-descriptor/vnfd-schema.yml"
vendor: "eu.5gtango"
name: "cloudnative-vnf"
version: "0.9"
author: "5GTANGO Developer"
description: "A clound native VNF example."
# Manuel: Have "cloudnative_deployment_units"
# instead of our normal "virtual_deployment_units"
# Felipe: This represents the containers inside the PODs
# cloud native deployment units inside the VNF
cloudnative_deployment_units:
- id: "cndu01"
image: some-docker-hub/nginx:latest
connection_points:
- id: "int-http"
port: 80
- id: "int-https"
port: 443
parameters: # (optional)
env: # In case of set environment variables to the containers
key1: valueA
key2: valueB
k8s_deployment:
key1: value2
k8s_service:
keyA: valueB
# VNF connection points to the outside world
connection_points:
- id: "http"
interface: "ipv4"
type: "serviceendpoint"
port: 80
- id: "https"
interface: "ipv4"
type: "serviceendpoint"
port: 443
# CNFs only use E-Tree links to map external ports to internal ports
virtual_links:
- id: "http-link"
connectivity_type: "E-Tree"
connection_points_reference:
- "http"
- "cdu01:int-http"
- id: "https-link"
connectivity_type: "E-Tree"
connection_points_reference:
- "https"
- "cdu01:int-https"