Hi, Ack with comments: - The statement of 5) seems to be included in 2), maybe can combine 2) and 5) - Since ERR_UNAVAILABLE could be returned in A.02.01, PR doc should recommend what's client's behavior when receiving this error code, eg. try API again since node has not joined cluster, or ...
Thanks, Minh On 07/04/16 16:01, praveen malviya wrote: > Hi, > > Please find attached NTFS PR doc updated for #1639. > Details of changes (done on top of changes of #1180): > > a) Modified highst supported version in section "2.2.3: Compliance > Report" as: > > "Notification service includes generic saNtf.h for versions up to > A.03.01 but current implementation supports A.01.02." > > b)Added section : > > "3.2.6 Intergration of NTFSv with CLMSv for return code > SA_AIS_ERR_UNAVAILABLE > > From OpenSAF 5.0 release, NTFSv gets integrated with CLMSv service. > NTFSv, currently, conforms to A.01.01 SAF spec version. Integration of > NTFSv service with CLMSv is not mentioned in A.01.01. In the later spec > version viz A.02.01, section "3.13 Unavailability of the Notification > Service API on a Non-Member Node" page no. 42 talks about integration of > NTFSv with CLMSv. OpenSAF release 5.0, now supports this functionality > for A.01.01 APIs via enhancement ticket > https://sourceforge.net/p/opensaf/tickets/1639/ > This enhancement does not implement any new API of A.02.01. > > Important facts for existing users and new users : > 1) Highest supported version for NTFSv is now A.01.02 (Minor version got > updated). > 2) A user initializing with A.01.01 (exact match) will not get > SA_AIS_ERR_UNAVAILABLE as return code anytime for any API even on CLMSv > Non-Member node. Such a user will get A.01.01 as returned version and > not the highest supported version. This ensures backward compatibility > for existing users. > 3) An application trying to initialize other than A.01.01 will get > returned version A.01.02 provided release Code and Major Version are > respectively ‘A’ and ‘01’. > 4) There is no impact on NTFSv integrated OpenSAF Middleware services > (like AMF, PLMSv, CLMSv and SMFSv) as they initialize with NTFSv with > A.01.01 version. > 5) This enhancement introduces a minor deviation from spec that an > application trying to initialize with A.01.01 will get A.01.01 as > returned version not the highest supported version A.01.02. > > Thanks, > Praveen > > > ------------------------------------------------------------------------------ _______________________________________________ Opensaf-devel mailing list Opensaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-devel
