- **status**: unassigned --> accepted
- **assigned_to**: Praveen
- **Comment**:
I think initially, the plan was not to allow the deletion of node group in
locked state if nodes are unlocked. But AMF PR doc does not mention anything
when NG is deleted in locked state with nodes unlocked. So a fix is surely
required. Only for the creation of nodegroup, AMF PR doc mentions:
"While creating the nodegroup through CCB operation if saAmfNGAdminState is not
configured
then AMF will keep default state as UNLOCKED but it will not lead to unlock of
any locked node
of nodegrou. Also if user creates a nodegroup with LOCKED admin state, it will
not lead to lock
of unlocked nodes of nodegroup."
---
** [tickets:#1435] AMF: Delete nodegroup leaves app su OUT_OF_SERVICE **
**Status:** accepted
**Milestone:** 4.6.1
**Labels:** nodegroup
**Created:** Thu Aug 06, 2015 06:24 AM UTC by Minh Hon Chau
**Last Updated:** Thu Aug 06, 2015 06:24 AM UTC
**Owner:** Praveen
**Attachments:**
-
[app3_twon2su2si.xml](https://sourceforge.net/p/opensaf/tickets/1435/attachment/app3_twon2su2si.xml)
(11.5 kB; text/xml)
Configuration: 2 SUs are hosted on PL-4 PL5 (as in app3_twon2su2si.xml)
Steps:
* Create nodegroup contains PL4 and PL5, with UNLOCK admin state
* Load app3_twon2su2si.xml, unlock-in, unlock 2 SUs
* Lock ng
-> Admin state of ng, PL4, PL5 are LOCKED.
* Unlock individual nodes PL4, PL5. This operation is allowed as documented
in AMF PR
(After completion of nodegroup SHUTDOWN or LOCK operation, a user can
unlock either the individual nodes by performing unlock on that node or by
performing unlock operation on that nodegorup. If unlock admin op is targeted
on nodegroup, all nodes of nodegroup will be marked unlocked by AMF.)
-> NG is LOCKED, both PL4 PL5 are UNLOCKED. Also there are no assignments
for amfdemo SU on PL4 PL5
* Now, delete NG. This operation is allowed per documentation
(Delete CCB operation is allowed on node group in LOCKED or UNLOCKED
admin state and when node group is not undergoing any admin operation)
At the end, all states of nodes and su(s) on PL4 PL5 are healthy but the
amfdemo su(s) are still out of service
safAmfNode=PL-4,safAmfCluster=myAmfCluster
saAmfNodeAdminState=UNLOCKED(1)
saAmfNodeOperState=ENABLED(1)
safAmfNode=PL-5,safAmfCluster=myAmfCluster
saAmfNodeAdminState=UNLOCKED(1)
saAmfNodeOperState=ENABLED(1)
safSu=SU4,safSg=AmfDemoTwon,safApp=AmfDemoTwon
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=OUT-OF-SERVICE(1)
safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemoTwon
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=OUT-OF-SERVICE(1)
At step 4, AMF could start app assignment once the nodes are UNLOCKED, or if NG
deletion ccb is accepted, AMF should ensure services up after operation
(provided that no interrupted error)
---
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.------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
