summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorShankaranarayanan Puzhavakath Narayanan <snarayanan@research.att.com>2020-05-28 19:14:54 +0000
committerGerrit Code Review <gerrit@onap.org>2020-05-28 19:14:54 +0000
commitd19432040dd1d6cf8c7b13cd67d581314dc52e63 (patch)
treecd4164e3090bf1d5c3e5fc7f663abeb3382a3a0d
parent8102c6f6d133dbead0b9844160d58c84028fe831 (diff)
parentb3bb1f758cbfba5e604e1c7fb3dc0947f4be2e03 (diff)
Merge "Add upgrade strategy to docs" into frankfurt6.0.0-ONAPfrankfurt
-rw-r--r--docs/sections/upgradestrategy.rst22
1 files changed, 22 insertions, 0 deletions
diff --git a/docs/sections/upgradestrategy.rst b/docs/sections/upgradestrategy.rst
new file mode 100644
index 0000000..6357fac
--- /dev/null
+++ b/docs/sections/upgradestrategy.rst
@@ -0,0 +1,22 @@
+..
+ This work is licensed under a Creative Commons Attribution 4.0
+ International License.
+
+================
+Upgrade Strategy
+================
+
+OSDF can be upgraded in place(remove and replace) or in a blue-green
+strategy.
+
+There is no need for database migration. Since, there is no database
+being used by OSDF.
+
+Supporting Facts
+================
+
+OSDF is a stateless component. It doesn't store any information in the
+database. It holds on to the optimization request in memory only until
+the optimization process is complete. The optimization is done either by
+OSDF itself or other external components(such as HAS) are leveraged for
+optimization.