I need to check and tweak the code and it may take some time.
Is other stakeholders agreeing to Math's suggestion and it solves their problem
?
---
** [tickets:#597] AMF: support to add component in unlocked SU**
**Status:** fixed
**Created:** Thu Oct 17, 2013 07:56 AM UTC by Hans Feldt
**Last Updated:** Wed Feb 05, 2014 09:29 AM UTC
**Owner:** Nagendra Kumar
Today it is possible to add a component in an unlocked SU but it will not be
instantiated until the SU has gone through the admin operation cycle
lock->lockin->unlockin->unlock.
This enhancement proposes that when a component is added to an unlocked SU it
should be automatically instantiated (if sa-aware).
When the corresponding CSI is added to component should either be 1) assigned
(SA-aware) or 2) instantiated (non-sa-aware)
The reverse should also work. When a CSI is removed, the corresponding
component should either be 1) unassigned (sa-aware) or 2) terminated
(non-sa-aware). When the component is removed the sa-aware component shold be
terminated.
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
