From b3176821fd6e297b51d26e426347f40557b69fa7 Mon Sep 17 00:00:00 2001
From: marchettim <mmarchetti@sandvine.com>
Date: Tue, 7 Nov 2017 21:04:31 +0200
Subject: [PATCH] Deploy OSM on kubernetes infrastructure

Change-Id: I1105eada8b79fb382bf5b2d7ad304239feacb613
---
 Release4/OSM_on_K8 | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)
 create mode 100644 Release4/OSM_on_K8

diff --git a/Release4/OSM_on_K8 b/Release4/OSM_on_K8
new file mode 100644
index 0000000..37070b4
--- /dev/null
+++ b/Release4/OSM_on_K8
@@ -0,0 +1,18 @@
+# OSM on kubernetes
+
+## Proposer ##
+Michael Marchetti (Sandvine)
+
+## Type ##
+**Feature**
+
+## Target MDG/TF ##
+all MDG's
+
+## Description ##
+The OSM installer currently asssumes it will be installed on a host (or VM). The MDG
+components/services are deployed in separate lxc containers. A Release4 directive is to simplify
+the install process. Moving to docker containers will help with this strategy as the MDG images
+that are built and tested in the CI pipeline can be installed directly without having to go through
+a long term install process. Subsequently, the docker OSM components now need to be orchestrated
+with one another (UI<->SO<->RO, etc), and utilizing kubernetes will simplify this.
\ No newline at end of file
-- 
2.25.1