From: garciadeblas Date: Tue, 8 Nov 2016 18:14:41 +0000 (+0100) Subject: New feature: euag_deployment_of_OSM_in_reduced_environments.md X-Git-Url: https://osm.etsi.org/gitweb/?a=commitdiff_plain;h=refs%2Fchanges%2F30%2F630%2F2;p=osm%2FFeatures.git New feature: euag_deployment_of_OSM_in_reduced_environments.md Change-Id: I8ce205ce9ec45cd38621bf30e5b15c00ab8effa8 --- diff --git a/Release2/euag_deployment_of_OSM_in_reduced_environments.md b/Release2/euag_deployment_of_OSM_in_reduced_environments.md new file mode 100644 index 0000000..1b7947f --- /dev/null +++ b/Release2/euag_deployment_of_OSM_in_reduced_environments.md @@ -0,0 +1,31 @@ +# Deployment of OSM in reduced environments # + +## Proposer ## +**EUAG** + +## Type ## +**Feature** + +## Target MDG/TF ## +UI, SO, RO, VCA + +## Description ## +Currently OSM requires 8 CPUs and 16GB RAM to run. This makes really complicated +for observers and initial testers to use OSM for the first time. Being able to +run OSM in a reduced environment with less required resources would ease the +first time use. + +As a reference, the target should be 2CPUs and 4GB RAM for running the whole OSM +(RO, VCA, SO, UI). In that way, OSM could run in a laptop or in a Virtualbox VM +without problems. + +In addition, in order to test the deployment of the NS, it would be required to +run a VIM and compute nodes in a reduced setup. The use of LXD containers as +compute nodes fits well with this idea. A single host with LXD containers and +Linux bridges could be used as datacenter for this testing purpose, being able +to deploy simple NS on that single host. The reference target of CPU and memory +resources for this single host running LXD containers could be 2CPUs and 4 GB +RAM. + +## Demo or definition of done ## +N/A