Ack from me with the following three minor comments: (1) To be consistent and complete section 2.1 should mention API version A.2.14 (om API only) related to OpenSAF 4.5. The new API is for saImmOmCcbValidate and saImmOmCcbAbort (can be found under osaf/libs/saf/include/saImmOm_A_2_14.h) but included by saImmOm.h.
(2) Section 3.4 point 3 explicitly talks about there not being any ccb-abort om call. But an abort call was added to the OM API in 4.5. So this should be reformulated slightly. The offical A.2.1 API has no OM ccb abort call. But OpenSAF OM API 4.2.14 adds it. (3) Section 3.4 point 4 talks a about a CCB-handle has to be closed if a ccb failed to apply with ERR_FAILED_OPERATION. But this is also remedied in OpenSAF4.5 where the user can confirm the abort by invoking saImmOmCcbAbort on the handle. The ccb-handle will then be in the same state as if it had just been initialized, i.e. empty but ready for new operations. /AndersBj Neelakanta Reddy wrote: > Hi AndersBj, > > The following sections has been modified/added for Opensaf Release 4.5 : > 1. 2.2 (#205) > 2. 2.2.6.6 > 3. 2.2.7 > 4. 2.2.8 > 5. 3.4 (#936) > 6. 3.5.6 > > IMMSV PR document is attached. > > /Neel. ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Opensaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-devel
