I'm using OpenSAF 4.3.1
Using No-Redundancy Redundancy Model

I have an SU that contains a number of components. Once I start up, the 
components are assigned ACTIVE CSIs in dependency order, and then the SI is 
assigned ACTIVE to the SU.

Then when I kill one component (process) in the SU this forces a restart of the 
SU (recovery is "suRestart"). Which is all correct.

However.... when I query the SI while the SU is restarting it remains assigned 
as ACTIVE (the same applies to the CSI, it remains ACTIVE as well). Is this 
correct? What I thought would have happened is that the SI assignment is 
removed while restarting and then only assigned back once the components have 
come back up and re-accepted their CSI assignments.

Now other states do update as I would expect... for example, the 
suAmfPresenceState does update to RESTARTING. And on the Component the 
saCompOperState does update to DISABLED, the saAmfCompPresenceState does update 
to RESTARTING, and the saAmfCompReadinessState does update to OUT-OF-SERVICE 
(although I know Readiness state is not supported in 4.3.1).

Here is some output of the amf-state command, so notice:
- service unit is restarting, but still assigned ACTIVE.
- component is disabled, restarting and out of service, but still assigned 
ACTIVE.


SERVICE INSTANCE STATE
safSISU=safSu=node1.Test\,safSg=node1.Test\,safApp=TestApp,safSi=node1.Test,safApp=TestApp
 saAmfSISUHAState=ACTIVE(1) saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1)

SERVICE UNIT STATE
safSu=node1.Test,safSg=node1.Test,safApp=TestApp saAmfSUAdminState=UNLOCKED(1) 
saAmfSUOperState=ENABLED(1) saAmfSUPresenceState=RESTARTING(5) 
saAmfSUReadinessState=IN-SERVICE(2)

COMPONENT SERVICE INSTANCE STATE
safCSIComp=safComp=node1.Test.TestComp\,safSu=node1.Test\,safSg=node1.Test\,safApp=TestApp,safCsi=node1.Test.TestComp,safSi=node1.Test,safApp=TestApp
 saAmfCSICompHAState=ACTIVE(1) 
saAmfCSICompHAReadinessState=READY_FOR_ASSIGNMENT(1)

COMPONENT STATE
safComp=node1.Test.TestComp,safSu=node1.Test,safSg=node1.Test,safApp=TestApp 
saAmfCompOperState=DISABLED(2) saAmfCompPresenceState=RESTARTING(5) 
saAmfCompReadinessState=OUT-OF-SERVICE(1)


So am I wrong, and the above output is correct? Or is there a bug?


Chad Kirst 
Software Development Manager - NG911, MIS, Legacy CTI
Airbus DS Communications
42505 Rio Nedo 
Temecula, CA  92590 
951.719.2426 DIRECT
951.551.0508 MOBILE
www.Airbus-DSComm.com



------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Opensaf-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-users

Reply via email to