Since Spec is not very clear about saAmfSGNumPrefInserviceSUs, here is the 
implementation specifics:

1. Amf should instantiate SUs(locked or unlocked) as per 
saAmfSGNumPrefInserviceSUs.
2. Amf should give preference to instantiate to unlocked SU than locked SU. For 
example:
   Consider the below configuration:
   2N, 3 SUs, saAmfSGNumPrefInserviceSUs as 2. SU1 Act, SU2 Std and SU3 is also 
unlocked, but it is uninstantiated.
   2.1 When SU1 is locked, 
        a.) SU1 assignments are removed and SU2 becomes Act.
        b.) Since SU1 is now Out of service, Amf should start SU3 as it is 
unlocked. But 
                it can't exceeds more than 2 SUs. So, it prefers to terminate 
SU1 and instantiate SU3.
        c.) After SU3 becomes instantiated, Amf assigns Standby role.
    So, as of now, SU2 and SU3 are instantiated and assigned. SU1 is locked and 
uninstantiated.
    Now, even if SU1 is unlocked, Amf will not instantiate SU1 as there are 
already 2 Sus instantiated.
    If possible, Amf should try to pick higher rank SU to instantiate and lower 
rank SU to terminate.

More example of such cases has been provided in the patch review email.



---

** [tickets:#445] saAmfSGNumPrefInserviceSUs is not honoured as per Specs.**

**Status:** review
**Milestone:** 4.3.3
**Created:** Fri Jun 07, 2013 11:27 AM UTC by surender khetavath
**Last Updated:** Wed Jul 16, 2014 11:33 AM UTC
**Owner:** Nagendra Kumar

Reference to Devel Ticket #2794, is in Fixed state but still reproducible.

Change Set:4241 with patches 2794, 3117, 367, 43,161, 222, 273, 236

Configuration: 2N redundency model.
               4SU, 1 COMP each,2SI
               saAmfSGNumPrefInserviceSUs=2

Steps to Reproduce:-
1.Unlock-in and Unlock all the SUs.
SU1  UNLOCKED| ENABLE| IN-SERVICE| INSTANTIATED
SU2  UNLOCKED| ENABLE| IN-SERVICE| INSTANTIATED
SU3  UNLOCKED| ENABLE| OUT-OF-SERVICE| UNINSTANTIATED
SU4  UNLOCKED| ENABLE| OUT-OF-SERVICE| UNINSTANTIATED

2.SU1 got Active assignment and SU2 got STANDBY .

3.LOCK SU1 with ADMIN operation .

4.SU2 became ACTIVE But SU3 didnot INSTANTIATE,And No STANDBY assignment to any 
SU.

safSISU=safSu=SC-1\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed2,safApp=OpenSAF
        saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SC-1\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF
        saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=suOrder_2n_2\,safSg=SG_suOrder_2n\,safApp=2nApp,safSi=suOrder_2n,safApp=2nApp
        saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=suOrder_2n_2\,safSg=SG_suOrder_2n\,safApp=2nApp,safSi=suOrder_2n_1,safApp=2nApp
        saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=PL-3\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed1,safApp=OpenSAF
        saAmfSISUHAState=ACTIVE(1)
 


---

Sent from sourceforge.net because [email protected] is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to