summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorkrishnaa96 <krishna.moorthy6@wipro.com>2020-05-26 21:31:09 +0530
committerkrishnaa96 <krishna.moorthy6@wipro.com>2020-05-26 21:31:55 +0530
commit65c27642ccfd29b3eeb5cdad58483f4f8d81d72b (patch)
treee606d8a692e7c6eb526c2c75b1817fd451498aee
parent1a1cf011bf02423c277533765f46e591f8190c2c (diff)
Add upgrade strategy
Issue-ID: OPTFRA-669 Signed-off-by: krishnaa96 <krishna.moorthy6@wipro.com> Change-Id: I1de2e5e94c0f9e0d58476c2a984e1baae5085fd1
-rw-r--r--docs/sections/upgradestrategy.rst20
1 files changed, 20 insertions, 0 deletions
diff --git a/docs/sections/upgradestrategy.rst b/docs/sections/upgradestrategy.rst
new file mode 100644
index 0000000..d461127
--- /dev/null
+++ b/docs/sections/upgradestrategy.rst
@@ -0,0 +1,20 @@
+..
+ This work is licensed under a Creative Commons Attribution 4.0
+ International License.
+
+================
+Upgrade Strategy
+================
+
+HAS can be upgraded in place(remove and replace) or using a blue-green
+strategy.
+
+There is no database migration required.
+
+Supporting Facts
+================
+
+HAS only stores the info and status of the incoming homing requests. It
+leverages MUSIC APIs for storing this information. It also leverages
+MUSIC for communication among the HAS components. So, redeploying HAS
+will not impact the data stored in MUSIC.