summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorkrishnaa96 <krishna.moorthy6@wipro.com>2020-05-26 21:29:13 +0530
committerVikas Varma <vikas.varma@att.com>2020-05-28 15:43:25 +0000
commitb3bb1f758cbfba5e604e1c7fb3dc0947f4be2e03 (patch)
tree90c1393aa78b63dae8675e918492d593ddcdb7b5
parent7ef2bbb80f0cedebbd9b8eae97c16d9327ee724c (diff)
Add upgrade strategy to docs
Issue-ID: OPTFRA-672 Signed-off-by: krishnaa96 <krishna.moorthy6@wipro.com> Change-Id: I8a503a3aff1b4a92c4ba04cea258c171d00213f4 (cherry picked from commit 272dbc27931acb0a15264d6dd4039a57d413f542)
-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.