Even with this suggested change it's not completly backwards compatible. If 
someone has installed the correct SW, added components and then explicitly 
locked/unlocked the SU to activate the changes. Not suddenly the components are 
activated automatically when created. Another issue is if someone thinks they 
have installed the correct SW (but it was wrong) and then adds a component and 
the component is not started because it was the wrong SW that was installed. In 
this case there will be no indication about this (alarm etc.).


---

** [tickets:#597] AMF: support to add component in unlocked SU**

**Status:** unassigned
**Created:** Thu Oct 17, 2013 07:56 AM UTC by Hans Feldt
**Last Updated:** Mon Feb 03, 2014 10:51 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 [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.
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to