Add upgrade strategy 91/108391/1
authorkrishnaa96 <krishna.moorthy6@wipro.com>
Tue, 26 May 2020 16:01:09 +0000 (21:31 +0530)
committerVikas Varma <vikas.varma@att.com>
Thu, 28 May 2020 15:40:24 +0000 (15:40 +0000)
Issue-ID: OPTFRA-669
Signed-off-by: krishnaa96 <krishna.moorthy6@wipro.com>
Change-Id: I1de2e5e94c0f9e0d58476c2a984e1baae5085fd1
(cherry picked from commit 65c27642ccfd29b3eeb5cdad58483f4f8d81d72b)

docs/sections/upgradestrategy.rst [new file with mode: 0644]

diff --git a/docs/sections/upgradestrategy.rst b/docs/sections/upgradestrategy.rst
new file mode 100644 (file)
index 0000000..d461127
--- /dev/null
@@ -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.