On 31-Dec-14 4:04 PM, Nagendra Kumar wrote:
> For checking mw si swap preconditions, the following are needed:
> 1. Standby controller should have joined. This means Amf director's cold
> sync is completed.
> But this doesn't mean that other directors are in sync and are fail safe.
> 2. SI Assignments on mw SUs should be completed. It is individual mw
> services responsibility to make sure that when director components/No
> red components(on standby controller) have responded to SI assignments
> to Amf, it is assumed to be safe for failover. For example, if immnd on
> standby controller has responded OK for SI assignment, that means immnd
> has been in sync with co-ordinator immnd and is in fail safe mode.
>
> Any comments?
>
For 2) ticket already exists:
#1234 middleware services to respond to CSI setcallback only after they
are ready to provide service.
Thanks
Praveen
> ------------------------------------------------------------------------
>
> *[tickets:#1169] <http://sourceforge.net/p/opensaf/tickets/1169> amfd:
> SI_SWAP operation accepted but will always fail when cold sync not finished*
>
> *Status:* accepted
> *Milestone:* 4.5.1
> *Created:* Tue Oct 14, 2014 12:43 PM UTC by Ingvar Bergström
> *Last Updated:* Wed Dec 31, 2014 07:10 AM UTC
> *Owner:* Nagendra Kumar
>
> If a SI Swap operation is issued to SI "safSi=SC-2N,safApp=OpenSAF"
> before cold sync of standby node is finished, the swap will alwayas fail.
> -The swap is started and applications are taken into operation on the
> new active node.
> -After a while AMF detect that coldsync is not completed and will try to
> swap back again.
> -The return code from the admin operation is SA_AIS_OK.
>
> To my opinion the SI Swap operation shall not start until coldsync is
> finished and return TRY_AGAIN while waiting.
>
> Some observations:
> -No check is made for coldsync finished in method SG_2N::si_swap
> (sg_2n_fsm.cc)
> -the control block AVD_CL_CB variable "stby_sync_state" is initially set
> to AVD_STBY_IN_SYNC already at start, so this can not be used to test
> for coldsync in this case.
> -all return codes except SA_AIS_OK are converted to
> SA_AIS_ERR_BAD_OPERATION in function si_admin_op_cb for SWAP operation
> (si.cc).
>
> ------------------------------------------------------------------------
>
> Sent from sourceforge.net because [email protected]
> is subscribed to https://sourceforge.net/p/opensaf/tickets/
> <https://sourceforge.net/p/opensaf/tickets>
>
> To unsubscribe from further messages, a project admin can change
> settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or,
> if this is a mailing list, you can unsubscribe from the mailing list.
>
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net
>
>
>
> _______________________________________________
> Opensaf-tickets mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
>
---
** [tickets:#1169] amfd: SI_SWAP operation accepted but will always fail when
cold sync not finished**
**Status:** accepted
**Milestone:** 4.5.1
**Created:** Tue Oct 14, 2014 12:43 PM UTC by Ingvar Bergström
**Last Updated:** Wed Dec 31, 2014 10:34 AM UTC
**Owner:** Nagendra Kumar
If a SI Swap operation is issued to SI "safSi=SC-2N,safApp=OpenSAF" before cold
sync of standby node is finished, the swap will alwayas fail.
-The swap is started and applications are taken into operation on the new
active node.
-After a while AMF detect that coldsync is not completed and will try to swap
back again.
-The return code from the admin operation is SA_AIS_OK.
To my opinion the SI Swap operation shall not start until coldsync is finished
and return TRY_AGAIN while waiting.
Some observations:
-No check is made for coldsync finished in method SG_2N::si_swap (sg_2n_fsm.cc)
-the control block AVD_CL_CB variable "stby_sync_state" is initially set to
AVD_STBY_IN_SYNC already at start, so this can not be used to test for coldsync
in this case.
-all return codes except SA_AIS_OK are converted to SA_AIS_ERR_BAD_OPERATION in
function si_admin_op_cb for SWAP operation (si.cc).
---
Sent from sourceforge.net because [email protected] is
subscribed to http://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
http://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
