From 7de12b550f8839f2ee6a8f5ab7be243be66d1758 Mon Sep 17 00:00:00 2001 From: garciadeblas Date: Tue, 8 Nov 2016 19:14:57 +0100 Subject: [PATCH] euag_support_of_floating_ip_addresses.md Change-Id: I1c2bb080ca4185595625cdc26e9782ec91657454 --- .../euag_support_of_floating_ip_addresses.md | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 Release5/euag_support_of_floating_ip_addresses.md diff --git a/Release5/euag_support_of_floating_ip_addresses.md b/Release5/euag_support_of_floating_ip_addresses.md new file mode 100644 index 0000000..c5617d6 --- /dev/null +++ b/Release5/euag_support_of_floating_ip_addresses.md @@ -0,0 +1,26 @@ +# Floating IP addresses in VNF interfaces for public access from outside a DC # + +## Proposer ## +**EUAG** + +## Type ## +**Feature** + +## Target MDG/TF ## +RO + +## Description ## +Currently OSM allows creating and using VIM networks, but it does not allow +assigning a floating IP address to a VNF interface in order to make that VNF +publicly available from outside the datacenter. + +The end user should be able to use the UI to assign, during instantiation time +or when updating a running NS instance, a floating IP address to a VNF +interface. The VNF interface will map implicitly to a VM interface, which will +be the interface where the floating IP address will be actually enforced. +The floating IP address should come from the pool of floating IP addresses in +the datacenter where the VNF is deployed. + +## Demo or definition of done ## +N/A + -- 2.25.1