Amf doc section 2.2.2 Compliance Report has been updated with :
Amf can allow su to be added in unlocked state until and unless either its SG
is in locked-in state or hosting node is in locked-in state. Amf can also allow
su to be deleted if hosting node is absent, hosting node is in locked-in or sg
is in locked-in. SU can be added/deleted in locked-in state.
changeset: 122:30b45ab64302
tag: tip
user: Nagendra Kumar<[email protected]>
date: Fri Sep 05 14:17:42 2014 +0530
summary: Amf: update for su addition/deletion in unlock state [#911]
[staging:30b45a]
---
** [tickets:#911] AMF: allow creation/deletion of unlocked SUs**
**Status:** fixed
**Milestone:** 4.5.0
**Created:** Thu May 15, 2014 11:49 AM UTC by Hans Feldt
**Last Updated:** Wed Aug 27, 2014 10:34 AM UTC
**Owner:** Hans Feldt
Allow creation of unlocked SUs when:
1) the SG is locked-instantiation or
2) the configured hosting node is locked-instantiation
Use case for 1) is creating AMF models on the command line (TLC initiative)
Use case for 2) is extending a cluster with a new node and existing SUs are
"cloned" to the new node.
The reverse (delete SU) should also be possible.
---
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.
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
