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
