Please see inline. Thanks, Praveen On 05-Jul-13 1:31 AM, opensaf dev wrote: > Hi, > > I am trying solve the init order of dependent components preferably through > IMM.xml attributes or if not through code. I have listed some of my > thoughts. Appreciate if anybody can advise on these?? > > > I have two java based SA-Aware critical components A and B. B depends on A > so that it can be initialized if and only if A is UP, else B can not be UP. > And until component A is fully UP and Running (couple of additional > application specific activities is done after component A is assigned CSI > though SetCSICallBack with HA state as ACTIVE and before A send the > response is to AMF), > > a. I need a mechanism by which, component B will wait and then INSTANTIATE > and become UP. Similarly if I have more then 2 components, wait and start > and so on... OR For this configure saAmfCompInstantiationLevel for individual components A , B and so on. So AMF will instantiate comp A first. If it gets instantiated successfully then only AMF will try to instantiate B (different instantiation level).
> b. AMF to delay assignment of HA active state to component B till it > receives success response to setCSICallBack() from component A. > > Options I am considering.. > > 1. I heard of instantiationlevel and CSI dependency attributes, but does > these attributes guarantee the above order of initialization? A component may require to make itself ready before actually start servicing to an application. For this a component may require to take some system resources . At the same time a component B may want to make itself ready only after other component A has already become ready. Such dependency among components from the perspective of execution environment can be achieved by configuring saAmfCompInstantiationLevel with different value for each component (Refer SAI-AIS-AMF-B.04.01 Section 3.8.2 for more clarity). Attribute is for order of initialization. All the components will be instantiated following instantiationlevel. So if they are up now they need to be assigned some work load (assigning csis). If this also needs to be assigned in some order then one can configure CSI dependency between the CSIs that go to comp A and comp B. For this association between csi and comp should be controlled through configuration. > 2. Also in the above scenario, to order initialization sequence is there > any delay that can be introduced BTW two INSTANTIATE command? A single component A which is at instantiationlevel=1 can take as much time for initialization as configured in saAmfCompInstantiateTimeout. As soon as component A responds successfully, AMF will go and try to instantiate comp B which is say at instantiationlevel=2. > 3. Is it possible to access the presence state of the component like HA > state, inside java components using any API (Ex: getHAState()) or any other > means? No, It is not exposed to the component. > 4. Can the HA state of component A be accessed inside component B and vice > versa? > Yes this can be done using the concept of Protection group (SAI-AIS-AMF-B.04.01 Section 3.1.8 and SAI-AIS-AMF-B.04.01 Section 7.11). > > Thanks, > > Dev > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > Opensaf-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/opensaf-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Opensaf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-users
