From 65c27642ccfd29b3eeb5cdad58483f4f8d81d72b Mon Sep 17 00:00:00 2001 From: krishnaa96 Date: Tue, 26 May 2020 21:31:09 +0530 Subject: Add upgrade strategy Issue-ID: OPTFRA-669 Signed-off-by: krishnaa96 Change-Id: I1de2e5e94c0f9e0d58476c2a984e1baae5085fd1 --- docs/sections/upgradestrategy.rst | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 docs/sections/upgradestrategy.rst (limited to 'docs/sections/upgradestrategy.rst') 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.   -- cgit 1.2.3-korg