Thanks Anders for your comments.
I can explain in detail about cb apply for csi addition.
1. ccb_1 apply comes and amfd adds csi in its data base. After that Amfd sends
csi assignment message to Amfnd. Amfnd sends CSI assignment to application.
2. Amfd responds comes back from apply and is ready for processing any other
ccbs.
3. Imm sends completed callback to Amfd for ccb_2. Amfd validates whether the
Service Group is stable and can ccb_2 be applied. Amfd finds that CSI
assignment is undergoing as application is yet to respond(application has time
to respond till configured csi timeout, it may be 1 seconds or 1 hour or more).
Amfd can't allow ccb_2 because the SG is not stable and can't commit this ccb
as when Amfd adds csi in its data base, it need to send csi assignment to Amfnd
and Amfnd will send Csi assignment to application(same stuff done in ccb_1
apply).
As Amfd follows principle of serializing the admin operations, it serialize the
ccb operations also as doing multiple operations on SG at the same time will
result in unrecoverable conditions and unhandled error cases.
We can't store apply because Act controller will store it and standby
controller will add it in its data as applier. We don't want asymetric
configurations, which leads to unrecoverable conditions during
failovers/switchovers.
Anyway, if we return NO_RESOURCE, then imm will return TRY_AGAIN to SMF and SMF
can TRY again, is that correct ? If yes, then we can return NO_RESOURCE in the
above cases mentioned.
Thanks
-Nagu
---
** [tickets:#750] AMF: creating multiple CSIs are rejected**
**Status:** accepted
**Milestone:** future
**Created:** Mon Jan 27, 2014 10:24 AM UTC by Hans Feldt
**Last Updated:** Tue Mar 18, 2014 10:03 AM UTC
**Owner:** Nagendra Kumar
AMF supports adding one CSI per CCB to an unlocked SI. This means if several
CSIs are to be added, many CCBs will be performed by SMF (from a campaign).
However since the first CSI create is still "pending" when the second CSI one
comes to AMF, the second one is can be rejected (by AMF). All depending in
timing.
One problem is that the OI completed callback does not give the OI any chance
to say TRYAGAIN. It is either accept or reject.
Adding a delay to the campaign between each CSI create is not a plausible
solution thus AMF needs to support this case.
---
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.
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
