From af4449cbc3ffac430ffe1b44dbc3f507e75f04bb Mon Sep 17 00:00:00 2001 From: garciadeblas Date: Tue, 8 Nov 2016 19:14:42 +0100 Subject: [PATCH] euag_distribution_of_OSM_SW_as_Docker_container_images.md Change-Id: I3e115615aaad2d845fda58bf1e41cc9732c08f85 --- ...on_of_OSM_SW_as_Docker_container_images.md | 30 +++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 Release2/euag_distribution_of_OSM_SW_as_Docker_container_images.md diff --git a/Release2/euag_distribution_of_OSM_SW_as_Docker_container_images.md b/Release2/euag_distribution_of_OSM_SW_as_Docker_container_images.md new file mode 100644 index 0000000..c2afbd8 --- /dev/null +++ b/Release2/euag_distribution_of_OSM_SW_as_Docker_container_images.md @@ -0,0 +1,30 @@ +# Distribution of OSM SW as Docker container images # + +## Proposer ## +**EUAG** + +## Type ## +**Feature** + +## Target MDG/TF ## +UI, SO, RO, VCA + +## Description ## +OSM SW distribution is currently done as source code, which is downloaded by an +installer, which also creates several LXD containers for each component, and +builds the SW on those containers. + +Docker containers provide an appropriate framework to separate the different +processes of a system in individual process containers so that the system +becomes much more flexible in field (for instance, HA or scale-out strategies +for an OSM system might be quickly aligned with the state of the art). With the +Docker approach, you get freedom to deploy each process in a different place, +scale them independently, design your own approach for High Availability, etc. + +This feature proposes the separation of the different OSM processes in Docker +container images. Here the use of the term ''process'' instead of ''component'' +is intentional. '''Processes running on each component must be identified and +Docker containers must be created per process and not per component'''. + +## Demo or definition of done ## +N/A -- 2.25.1