Hi Anders, Reviewed the patch. Ack. README is not updated with the immadm changes, related to #642.
/Neel. On Tuesday 17 December 2013 11:16 PM, Anders Bjornerstedt wrote: > osaf/services/saf/immsv/README | 17 +++++++++- > osaf/services/saf/immsv/README.NO_DANGLING | 47 > +++++++++++++++++++++++++++++- > 2 files changed, 61 insertions(+), 3 deletions(-) > > > diff --git a/osaf/services/saf/immsv/README b/osaf/services/saf/immsv/README > --- a/osaf/services/saf/immsv/README > +++ b/osaf/services/saf/immsv/README > @@ -1624,8 +1624,8 @@ Bit 4 controls 2PBE oneSAfe2PBE (see 2PB > 2PBE Allow IMM PBE to be configured without shared file system (4.4) > =================================================================== > http://sourceforge.net/p/opensaf/tickets/21/ > - > -The 2PBE enhancement allows the IMM to have PBE configred so that it > +OpenSAF 4.4 adds the enhancement of supporting 2PBE. > +The 2PBE enhancement allows the IMM to have PBE configured so that it > does not rely on a shared filesystem, such as DRBD. > > See: osaf/services/saf/immsv/README.2PBE for details. > @@ -1634,12 +1634,25 @@ See: osaf/services/saf/immsv/README.2PBE > Support for reference integrity checking - SA_IMM_ATTR_NO_DANGLING (4.4) > ======================================================================== > http://sourceforge.net/p/opensaf/tickets/49/ > +OpenSAF 4.4 adds the immsv enhancement of supporting referential integrity > +checking. The feature is available for clients that register with imm API > +version A.2.13. > > A new attribute definition flag has been defined: > #define SA_IMM_ATTR_NO_DANGLING 0x0000000004000000 > > See: osaf/services/saf/immsv/README.NO_DANGLING for details. > > +Support search for objects having NO_DANGLING refrence to a target (4.4) > +======================================================================== > +http://sourceforge.net/p/opensaf/tickets/50/ > +OpenSAF 4.4 adds the immsv enhancement of supporting search/iteration > +for finding all objects that have a NO_DANGLING reference to a provided > +target. This feature is available for clients that register with imm API > +version A.2.13. > + > +See: osaf/services/saf/immsv/README.NO_DANGLING for details. > + > ---------------------------------------- > DEPENDENCIES > ============ > diff --git a/osaf/services/saf/immsv/README.NO_DANGLING > b/osaf/services/saf/immsv/README.NO_DANGLING > --- a/osaf/services/saf/immsv/README.NO_DANGLING > +++ b/osaf/services/saf/immsv/README.NO_DANGLING > @@ -58,7 +58,7 @@ by the IMM. > The IMM will also perform interference checking in the operational phase of > a CCB. A failed interference check will typically only reject that latest > operation, without aborting the CCB. Interference checks are mainly for > -regulationg concurrency conflicts between CCBs, but also catch blatant errors > +regulating concurrency conflicts between CCBs, but also catch blatant errors > that are local to the operation. The rejection of such a bad operation is > done > before any OIs receive the operation callback. If an interference check > fails > then no OI will get that operation callback. This is important because > there is > @@ -112,5 +112,50 @@ o Check if there is a NO_DANGLING refe > > > > +Support search for objects having NO_DANGLING refrence to a target (4.4) > +======================================================================== > +http://sourceforge.net/p/opensaf/tickets/50/ > +OpenSAF 4.4 adds the immsv enhancement of supporting search/iteration > +for finding all objects that have a NO_DANGLING reference to a provided > +target. This feature is available for clients that register with imm API > +version A.2.13. > > +The search API saImmOmSearchInitialize_2 is defined in section > +4.5.1 of the IMM A.02.01 specification. > > +Such a search will be created by filling in the arguments of > +saImmOmSearchInitialize_2 in the following way: > + > +1) The searchOptions parameter must set a new search-criteria flag: > + > + #define SA_IMM_SEARCH_NO_DANGLING_DEPENDENTS 0x0000000100000000 > + > +This flag indicates that the intention of the search is to find all > +objects that have any NO_DANGLING reference pointing to a particular > +target object. The target object must of course be a currently existing > +imm object. Attribute-options (such as SA_IMM_SEARCH_GET_NO_ATTR) may > +also be or-ed to the searchOptions argument in the normal way, to avoid > +fetching not needed data. > + > +2) The target object is identified in the searchParam parameter as follows: > + > + a) attrName must be set to NULL. > + b) attrValue must be the DN of an object. > + c) attrValueType may be either SA_IMM_ATTR_SANAMET or > + SA_IMM_ATTR_SASTRINGT. > + > +The value must of course be the DN of a currently existing object. The use > +of SaStringT is allowed here to accommodate future enhancements that > +replace the use of SaNameT with SaStringT. > + > +This makes it possible to find all objects that are no-dangling dependent > +on the target. Only NO_DANGLING references will be returned because only > +such references can efficiently be located for any given object DN as > +target. > + > +The return result is an iteration, as usual, where each searchNext returns > +an object that contains one or more NO_DANGLING flagged references pointing > +to the target. The reference attributes may be included (along with other > +attributes!) or not depending on the search options setting, e.g. > +SA_IMM_SEARCH_GET_ALL_ATTR. > + ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Opensaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-devel
