In the given configuration, swapped SI2 was fully assigned in the beginning but
it had only one standby assignment. In N-Way model a SI will have multiple
standby assignments, so even if swap leads to removal of one standby there
would be other standby SUs to take over the active role.
So, I think, a general check for checking saAmfSGMaxStandbySIsperSU count for
highest ranked SU is not needed and operation should be allowed if there are
more than two standbys SU exists for the SI and it will lead to removal of
assignment after swap.
But in a case like where SI got reduced (by configuration or due to degraded
state of the system) to 2N type of redundancy such a check may be added.
---
** [tickets:#1516] AMF : si-swap operation in nway should honor
saAmfSGMaxStandbySIsperSU **
**Status:** unassigned
**Milestone:** 4.5.2
**Created:** Mon Oct 05, 2015 12:59 PM UTC by Srikanth R
**Last Updated:** Tue Oct 06, 2015 05:43 AM UTC
**Owner:** nobody
While processing si-swap operation in nway model, AMF should take care of
standby assignments also. If the saAmfSGMaxStandbySIsperSU is not met for the
new SU, si-swap operation should be rejected. In the current case, si-swap
operation is proceeded and si is degraded from fully assigned to partially
assigned state.
Initial state of SG :
****************************************************************************
| TestApp_SI1 | TestApp_SI2 | TestApp_SI3 | TestApp_SI4
| TestApp_SI5
*******************************************************************************
*
TestApp_SU1 | ACTIVE | ACTIVE | ACTIVE | STANDBY
|
TestApp_SU2 | STANDBY | | | ACTIVE
| ACTIVE
TestApp_SU3 | | STANDBY | |
|
****************************************************************************
After invoking si-swap operation on SI2, SI2 moved to partially assigned state.
****************************************************************************
|TestApp_SI1 | TestApp_SI2 | TestApp_SI3 | TestApp_SI4 |
TestApp_SI5
*********************************************************************************
TestApp_SU1 | ACTIVE | | ACTIVE | STANDBY |
TestApp_SU2 | STANDBY | | | ACTIVE |
ACTIVE
TestApp_SU3 | | ACTIVE | STANDBY | |
****************************************************************************
Configuration of SG is
saAmfSGNumPrefStandbySUs SA_UINT32_T 1 (0x1)
saAmfSGNumPrefInserviceSUs SA_UINT32_T 3 (0x3)
saAmfSGNumPrefAssignedSUs SA_UINT32_T 3 (0x3)
saAmfSGNumPrefActiveSUs SA_UINT32_T 3 (0x3)
saAmfSGNumCurrNonInstantiatedSpareSUs SA_UINT32_T 0 (0x0)
saAmfSGNumCurrInstantiatedSpareSUs SA_UINT32_T 0 (0x0)
saAmfSGNumCurrAssignedSUs SA_UINT32_T 3 (0x3)
saAmfSGMaxStandbySIsperSU SA_UINT32_T 1 (0x1)
saAmfSGMaxActiveSIsperSU SA_UINT32_T 3 (0x3)
---
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.------------------------------------------------------------------------------
Full-scale, agent-less Infrastructure Monitoring from a single dashboard
Integrate with 40+ ManageEngine ITSM Solutions for complete visibility
Physical-Virtual-Cloud Infrastructure monitoring from one console
Real user monitoring with APM Insights and performance trend reports
Learn More http://pubads.g.doubleclick.net/gampad/clk?id=247754911&iu=/4140
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
