-
Story
-
Resolution: Done
-
Medium
-
None
-
None
-
RICP_T4 Sprint B.D2
General Requirements
The same KA Mechanism as today - wake up each X time and sending KA in Broadcast, and the same KA Response algorithm.
If E2T has to be deleted - this is what we have to do -
| current State / trigger | State = Active | State =To be Deleted |
| KA decide to kill E2T instance | · Move to “To be deleted” State; · Update Routing Manager, if fail – error but continue · Store in DB the Disassociation RAN to E2T, Delete the E2T Address at all. |
(Transient State, should not occurs unless E2M restarted) · Do all the steps Just like in Active (Previous Cell), except updating the state which is already “To be Deleted”. |
Note that state RM Failure - it isn't actual anymore.
Fix the Design - also KA & E2T Initialize - note that it should be open in the new Confluent
Fix Automation
DoD:
There are 2 E2T instances. See KA Broadcast is sent, see they are responding properly.
Kill one of them which is connected to Y RANs. See, after KA Timestamp, there is HTTP to deactivate the E2T Address with the list of Y RANs. See the RAN state is Disconnected, it doesn't point to any E2T and the dead E2T object doesn't exist at all.
Repeat it with no RM. See the same behavior (Plus Log Error)
1.
|
Implement changes |
|
Done | Unassigned |
2.
|
Fix unit tests |
|
Done | Unassigned |
3.
|
Fix Automation tests |
|
Done | Unassigned |
4.
|
Update design |
|
Done | Unassigned |
5.
|
Code review |
|
Done | Hunter Pero |