Menu

#434 amf: Configuration parameter of a 2N SG are are not validated

never
duplicate
None
defect
amf
d
4.2.0
major
2015-07-03
2013-05-31
Praveen
No

Migrated from http://devel.opensaf.org/ticket/2205.

The parameters of the SG
saAmfSGNumPrefStandbySUs, saAmfSGNumPrefAssignedSUs, saAmfSGNumPrefActiveSUs, saAmfSGMaxStandbySIsperSU, saAmfSGMaxActiveSIsperSU
are currently not validated for the invalid configuration values.

Should these be validated as per the description of 2N redundancy model from the AMF specification ? i.e
saAmfSGNumPrefStandbySUs values 0 or 1
saAmfSGNumPrefAssignedSUs values 0 or 1 or 2
saAmfSGNumPrefActiveSUs values 0 or 1
saAmfSGMaxStandbySIsperSU = 1
saAmfSGMaxActiveSIsperSU = 1

Discussion

  • Nagendra Kumar

    Nagendra Kumar - 2015-07-03
    • status: unassigned --> assigned
    • assigned_to: Nagendra Kumar
     
  • Nagendra Kumar

    Nagendra Kumar - 2015-07-03
    • status: assigned --> duplicate
    • Part: - --> d
    • Milestone: future --> never
     
  • Nagendra Kumar

    Nagendra Kumar - 2015-07-03
    1. saAmfSGNumPrefActiveSUs and saAmfSGNumPrefStandbySUs are validated as part of ticket #296.
    2. saAmfSGNumPrefAssignedSUs is validated as part of ticket #2881 (CS #3876)
    3. saAmfSGMaxActiveSIsperSU and saAmfSGMaxStandbySIsperSU are validated as part of ticket #2418 (CS #3159).

    These variables are not used in all the redundancy models and hence couldn't be validated for those redundancy models, which don't use them.

    The mentioned attributes are not used for 2N as per Amf Specs, so user can configure any values, but they will not be used.

    Thanks
    -Nagu

     

Log in to post a comment.