Hi, I will incorporate the comment before pushing. Thanks Praveen On 02-Aug-13 12:46 PM, Nagendra Kumar wrote: > I mean : > >>> saAmfSGAutoRepair and saAmfSgtDefAutoRepair :Though dynamic >>> modification is supported, these attributes will be considered > when SU will be failed-over as a single entity i.e. in the the context of SU > fail-over only. > > Thanks > -Nagu > > -----Original Message----- > From: Nagendra Kumar > Sent: 02 August 2013 12:45 > To: Praveen Malviya; Hans Feldt; Mathivanan Naickan Palanivelu > Cc: [email protected] > Subject: Re: [devel] AMF PR doc updates related to saAMFSUFailover > implementation (#98) > > We can add only after the below statement to make it explicit: > >>> saAmfSGAutoRepair and saAmfSgtDefAutoRepair :Though dynamic >>> modification is supported, these attributes will be considered > when SU will be failed-over as a single entity i.e. in the the context of SU > fail-over. > > Thanks > -Nagu > > -----Original Message----- > From: praveen malviya > Sent: 30 July 2013 16:20 > To: Hans Feldt; Nagendra Kumar; Mathivanan Naickan Palanivelu > Cc: [email protected] > Subject: AMF PR doc updates related to saAMFSUFailover implementation (#98) > > Hi, > Following are the documentation related changes for AMF PR doc in the context > of saAMFSUFailover implementation (#98): > > 1) Section 2.2.2 of PR doc (Compliance Report): Change in subsection > 3.11.1.3: > Component Failover: In Nway, N-Way Active and N+M redundancy > models, all assignments of the faulted SU will be removed gracefully. > Su Failover: AMF abruptly terminates all components of faulted SU > without honoring component instantiation order. > 2) Section 2.2.2 if PR doc (Compliance Report): Change in subsection > 3.11.1.4: > In case of fail-over of SU as a single entity, saAmfSGAutoRepair > will be considered by AMF to repair the faulted SU. > 3) Section 2.2.2 of PR doc (Compliance Report) :Change in subsection 8: > a)Section 8.9: > saAmfSGAutoRepair and saAmfSgtDefAutoRepair :Though dynamic > modification is supported, these attributes will be considered > when SU will be failed-over as a single entity i.e. in the > the context of SU fail-over. > b)Section 8.10: > saAmfSUFailover : No support when proxy/proxied configured in SU. > During 'SU Fail-over' termination of components will be abrupt and unordered > without honoring any component Instantiation Level. > 4) Section 6.1 of PR doc (Unsupported attributes): > Removal of saAmfSUFailover and saAmfSutDefSUFailover from table. > > 5) Section 6.2 of PR doc (Unmodifiable Attributes at runtime): > Removal of saAmfSutDefSUFailover and saAmfSgtDefAutoRepair. > > Please review the changes. > > Thanks > Praveen > > ------------------------------------------------------------------------------ > Get your SQL database under version control now! > Version control is standard for application code, but databases havent caught > up. So what steps can you take to put your SQL databases under version > control? Why should you start doing it? Read more to find out. > http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > _______________________________________________ > Opensaf-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/opensaf-devel
------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ Opensaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-devel
