From c6b675bf45077fb00428684fee1d16f0355bdc3e Mon Sep 17 00:00:00 2001 From: garciadeblas Date: Tue, 8 Nov 2016 19:14:50 +0100 Subject: [PATCH] euag_interoperability_with_public_clouds.md Change-Id: I7eb106ce4f26cb8c20c98d4636ffc584d67cf57f --- ...uag_interoperability_with_public_clouds.md | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 Release2/euag_interoperability_with_public_clouds.md diff --git a/Release2/euag_interoperability_with_public_clouds.md b/Release2/euag_interoperability_with_public_clouds.md new file mode 100644 index 0000000..f048c41 --- /dev/null +++ b/Release2/euag_interoperability_with_public_clouds.md @@ -0,0 +1,26 @@ +# Interoperability with public clouds # + +## Proposer ## +**EUAG** + +## Type ## +**Feature** + +## Target MDG/TF ## +RO + +## Description ## +Currently OSM can deploy VNFs in sites controlled by VIMs of the following +types: Openstack, Openvim and VMware vCloud Director. In practice, this is +forcing the user to have access to a VIM of one of those types, which might not +be simple for a general user that just wants to test OSM. + +Being able to interact with public clouds such as AWS and Google Cloud would +allow a general user to test OSM without the need to deploy a VIM. Moreover, +those public clouds could be part of multi-site deployments in production. + +In practice, this feature would require interacting with AWS APIs and Google +Cloud APIs as a minimum, in a similar way as it is done with other VIMs. + +## Demo or definition of done ## +N/A -- 2.25.1