-----Original Message-----
From: Anders Björnerstedt 
Sent: den 16 juli 2014 15:04
To: 'Neelakanta Reddy'
Cc: 'de...@list.opensaf.org'
Subject: RE: Regarding #895.

Hi Neel,

Good observation!


On the one hand I do think that performing a schema upgrade/change *during* any 
rolling upgrade would be a bad and pointless idea. And doing so during a 
rolling upgrade from OpenSAF 4.x to OpenSAF 4.5 would be bad, pointless and 
almost asking for problems. 

On the other hand, knowing reality, the fact that most users of upgrade 
procedures dont have a clue about what they are upgrading or why and that 
operator mistakes are the dominating factor in reducing systems availability. 

I will add an upgrade check for immModel_protocol45Allowed() to 
ImmModel::notCompatibleAtt() where it detects the case of adding a default.

Any upgrade to 4.5 should turn on the nostdFlags bit for 4.5 protocols allowed 
*after* the Upgrade to 4.5 is completed.

/AndersBj


-----Original Message-----
From: Neelakanta Reddy [mailto:reddy.neelaka...@oracle.com]
Sent: den 16 juli 2014 14:28
To: Anders Björnerstedt
Subject: Regarding #895.

Hi AndersBj,

Some Questions on #895 patch:

In the case of rolling upgrade, how does the foll wing case will have same 
results across the cluster:

a. two controllers(SC-1 and SC-2)

b. upgrade standby controller to SC-2 with #895 patch.

c. schema change for SC-2 by adding default value.

      Here SC-1 immnd is not having the default value (schema-change will fail).

d. when object is created in SC-2 will have default value and SC-1 will not 
have default value.


Adding default attribute by class schema change may be allowed when 
protocol45Allowed is enabled?

Thanks,
Neel.

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel

Reply via email to