Re: [devel] [PATCH 1/1] amfd: Set SA_AMF_READINESS_IN_SERVICE for qualified SU after cluster startup timeout [#2916]

2018-08-23 Thread nagendra
Hi Minh, Good patch. Ack from me. Thanks, Nagendra, 91-9866424860 High Availability Solutions Pvt. Ltd. (www.hasolutions.in) - OpenSAF Support and Services - Original Message - Subject: [PATCH 1/1] amfd: Set SA_AMF_READINESS_IN_SERVICE for qualified SU after cluster startup

Re: [devel] [PATCH 1/1] amfd: Set SA_AMF_READINESS_IN_SERVICE for qualified SU after cluster startup timeout [#2916]

2018-08-22 Thread Gary Lee
Hi Minh ack (review) Thanks Gary On 22/08/18 20:23, Minh Chau wrote: In the scenario of single step upgrade where the UNLOCK-IN/UNLOCK admin op are issued to a SU hosted on non-active node while cluster startup timer is active and not all ncs SU on that node are fully assigned. In such case,

Re: [devel] [PATCH 1/1] amfd: Set SA_AMF_READINESS_IN_SERVICE for qualified SU after cluster startup timeout [#2916]

2018-08-22 Thread Hans Nordeback
ack, review only/Thanks HansN On 08/22/2018 12:23 PM, Minh Chau wrote: In the scenario of single step upgrade where the UNLOCK-IN/UNLOCK admin op are issued to a SU hosted on non-active node while cluster startup timer is active and not all ncs SU on that node are fully assigned. In such case,

[devel] [PATCH 1/1] amfd: Set SA_AMF_READINESS_IN_SERVICE for qualified SU after cluster startup timeout [#2916]

2018-08-22 Thread Minh Chau
In the scenario of single step upgrade where the UNLOCK-IN/UNLOCK admin op are issued to a SU hosted on non-active node while cluster startup timer is active and not all ncs SU on that node are fully assigned. In such case, amfd currently accepts the UNLOCK admin op, change AdminState to UNLOCKED