This was news to me that 2.2 will no longer have GEO migration.
In that case, maybe it is not that bad so OK with me based on
Hui's analysis below, to address in 2.2.
Thanks !!
Natasha
From: <Dail>, Christopher <Christopher.Dail@emc.com>
Date: Monday, September 22, 2014 12:08 PM
To: "Liu, Hui (Eng Beijing)" <hui.liu@emc.com>, Corporate User
<natasha.mace@emc.com>, "Zhang, Yue (ASD)"
<yue.zhang2@emc.com>, "Pan, Peter (ASD)" <Peter.Pan3@emc.com>,
"Qin, Yun" <yun.qin@emc.com>, Liping Bao <liping.bao@emc.com>
Cc: "Nelluri, Venu" <Venu.Nelluri@emc.com>, ViPR SysMgmt Infra QE
<ViPRSysMgmtInfraQE@emc.com>, "Saxena, Nitin"
<Nitin.Saxena2@emc.com>, "Sarkar, Devanjan"
<Devanjan.Sarkar@emc.com>, "soltysik, sean"
<sean.soltysik@emc.com>, "Chen, Grace" <Grace.Chen1@emc.com>,
"Li, Echo" <echo.li@emc.com>
Subject: Re: Force option for geo-upgrade
Any objections leaving this for 2.2 then?
Chris
From: <Liu>, "Hui (Eng Beijing)" <hui.liu@emc.com>
Date: Monday, 22 September, 2014 12:26 PM
To: "mace, natasha" <natasha.mace@emc.com>, "Zhang, Yue (ASD)"
<yue.zhang2@emc.com>, "Pan, Peter (ASD)" <Peter.Pan3@emc.com>,
"Qin, Yun" <yun.qin@emc.com>, Christopher Dail
<Christopher.Dail@emc.com>, "Bao, Liping" <liping.bao@emc.com>
Cc: "Nelluri, Venu" <Venu.Nelluri@emc.com>, ViPR SysMgmt Infra QE
<ViPRSysMgmtInfraQE@emc.com>, "Saxena, Nitin"
<Nitin.Saxena2@emc.com>, "Sarkar, Devanjan"
<Devanjan.Sarkar@emc.com>, "soltysik, sean"
<sean.soltysik@emc.com>, "Chen, Grace" <Grace.Chen1@emc.com>,
"Li, Echo" <echo.li@emc.com>
Subject: RE: Force option for geo-upgrade
Major reason for geo upgrade check – We don’t want to see >2
different geodb schema versions in a vipr federation. It introduces
unneeded code complexities to handle more than 2 schema versions
in both db layer and upper layers. So we designed a UpgradeVoter in
geosvc to say no for vipr upgrade if geosvc detects >2 geodb schema
versions caused by this upgrade.
That design is based on the assumption that we’ll have geodb schema
version changes soon in 2.2 introduced by some Tenant management
feature. But as far as I know, that feature is dropped and we won’t
have geodb schema changes from 2.1->2.2 upgrade. So if we don’t do
that check in 2.1, we still have chance to do it in 2.2. That’s my point.
Especially for your questions
#1 – I don’t see risky issue. If no geodb schema change from 2.1->2.2,
nice to have the checks but not a must.
#2 – Depends on discussion between Chris and Shane.. I don’t see we
need do that.
#3 - The use case for force parameter: customer may want to apply a
critical hot fix to vipr - no matter UpgradeVoter say yes or no. In very
corner cases we may have bugs in UpgradeVoters and it returns
incorrect values. We need provide a way for customer to do a force
upgrade – if he/she clearly knows the situation.
We also have some other geo checks like – we don’t allow upgrade
during add-vdc/remove-vdc etc because upgrade triggers reboot and
may bring interruptions to add/remove vdc. Considering upgrade and
add/remove vdc are less frequent operations and we can document
that..
Thanks,
Hui
From: mace, natasha Sent: Monday, September 22, 2014 10:55 PM
To:
Zhang, Yue (ASD); Pan, Peter (ASD); Liu, Hui (Eng Beijing); Qin, Yun; Dail,
Christopher; Bao, Liping
Cc: Nelluri, Venu; ViPR SysMgmt Infra QE;
Saxena, Nitin; Sarkar, Devanjan; soltysik, sean; Chen, Grace
Subject: Re:
Force option for geo-upgrade
Yun/Venu/Shane/Yue,
Seems that having the force parameter have caused issues in the GUI (since
GUI have always used this in some cases with original design since 1.0).
SO:
1. Will the current issue (CTRL-5631) be risky for users who
upgrade 2.1 -> 2.2 (if force in GUI used all the time , can they inadvertently
make system in bad state if prechecks are skipped?
2.If #1 is critical to address, should we back out force parameter
altogether from 2.1, and re-implement if needed in 2.2?
3. Can someone elaborate on exact cases (with latest design)
when user or CS will want to use force parameter? At least one case
from Yue below: "Allow upgrade one VDC to a hotfix when there is
another VDC in disconnected state".I think removing the force
parameter would block users if such case arises in production site.
If we leave current code as is foe now, we should make sure we are
not causing serious issues for 2.1-> 2.2 upgrade by skipping important
prechecks for GEO upgrade,
+Others from bug review today..
Thanks!
Natasha
From: <Zhang>, "Yue (ASD)" <yue.zhang2@emc.com>
Date: Monday,
September 8, 2014 11:43 PM
To: Corporate User
<natasha.mace@emc.com>, "Pan, Peter (ASD)"
<Peter.Pan3@emc.com>, "Liu, Hui (Eng Beijing)" <hui.liu@emc.com>,
"Qin, Yun" <yun.qin@emc.com>
Cc: "Nelluri, Venu"
<Venu.Nelluri@emc.com>, ViPR SysMgmt Infra QE
<ViPRSysMgmtInfraQE@emc.com>
Subject: RE: Force option for geoupgrade
We had a conversation with Hui and Yun last week. This is to bypass
the upgrade precheck for certain scenarios (for example, upgrade one
VDC to a hotfix when there is another VDC in disconnected state).
This is not required in 2.1, as in 2.1 there will be another mechanism
(check upgrade image version) to allow above scenario. But the plan is
to replace the checking version way with this force parameter. +Hui
and Yun to confirm.
Regards,
Yue
From: mace, natasha Sent: Friday, September 05, 2014 11:05 PM
To:
Zhang, Yue (ASD); Pan, Peter (ASD)
Cc: Nelluri, Venu; ViPR SysMgmt Infra
QE
Subject: Re: Force option for geo-upgrade
Yue/Peter,
Do you think we need this force option for geo upgrade for some rare
cases? Any concerns ?
Original idea I believe was that it would be nice to have it if users needed
to get unstuck if they need to have more than 2 upgrade images in GEO,
etc.
But, I think the design for GEO upgrade has changed a bit, do we still need
to have this force option and is there and risk in it? I believe we have a
force option in regular upgrade..
From: <Nelluri>, Venu <Venu.Nelluri@emc.com>
Date: Friday,
September 5, 2014 11:01 AM
To: Corporate User
<natasha.mace@emc.com>
Subject: Force option for geo-upgrade
Do you need this to be in release-2.1 or there is a work around
already?
https://asdjira.isus.emc.com:8443/browse/CTRL-5631?filter=-1
Thanks
-Venu