Hi Minh,
Ticket #1354 is based on a user list complaint. This ticket is related to
states and runtime objects.
Other ticket #1306 is related to notification that AMFD seds but talks almost
similar problem from notification perspective.
I think we can do something like this:
1)For fresh assignment, runtime objects(SISU and CSICOMP) can be crated in IMM
but wihout updating the HA state. Here susi->fsm state can be updated as
AVD_SU_SI_STATE_ASGN (not required buy user). I think IMM will show HA sate as
empty in this case. When AMFND responds to AMFD for the completion of
assignment via susi_assign_event() then AMFD can update HA state, fsm state as
AVD_SU_SI_STATE_ASGND and send the notification also.
2)For modify operation, I think state should be updated after AMFD gets
assignment response from AMFND and also notification should be sent that time
only.
What do you think? Will it handle headless case also?
Thanks,
Praveen
---
** [tickets:#2134] AMF: Update RTA saAmfSISUHAState to IMM**
**Status:** unassigned
**Milestone:** 5.2.FC
**Created:** Thu Oct 20, 2016 07:58 PM UTC by Minh Hon Chau
**Last Updated:** Thu Oct 20, 2016 07:58 PM UTC
**Owner:** nobody
In scenario of 2N Si-swap, when AMFD sends QUIESCED su_si assignment msg (for
example) to AMFND that changes the HA State of SUSI assignment, AMFD updates
its local state AVD_SU_SI_REL::state, checkpoint this change to standby AMFD.
However, AMFD does not updates saAmfSISUHAState untill receiving su_si
assignment response. Question:
(1). Whether AMFD should update the runtime attribute saAmfSISUHAState to IMM
as long as local @state gets updated in implementer; to make IMM, active AMFD,
standby AMFD all are synced
(2). Or AMFD updates saAmfSISUHAState to IMM only if AMFD receives su_si
assignment from AMFND, as it has been implemented currently for some reason
(not expose the change of saAmfSISUHAState to user too early?)
grep "avd_susi_update" which updates saAmfSISUHAState to IMM, there is also an
inconsistency in usage. For avd_susi_mod_send() sends su_si msg and also
updates saAmfSISUHAState immediately, while avd_sg_su_si_mod_snd does
otherwise.
Since the headless recovery relies on IMM to restore the state. If
saAmfSISUHAState is not updated punctually and the node is reboot during
headless stage, so after headless saAmfSISUHAState read from IMM does not fit
with many other states (SG fsm, SUSI fsm, saAmfSISUHAState of the other SUSIs).
My question is if doing (1) will cause any problem for normal cluster? Pending
patches #1725 part 2 currently implement (1).
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed to 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.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
