changeset:   4677:e12e751254a8
branch:      opensaf-4.2.x
parent:      4674:3a4fb8292452
user:        Nagendra Kumar<[email protected]>
date:        Fri Dec 06 16:11:17 2013 +0530
summary:     amfd: Use correct CLC command to term/clean component [#104]

changeset:   4678:ef5cef176061
branch:      opensaf-4.3.x
parent:      4675:931feeee43c4
user:        Nagendra Kumar<[email protected]>
date:        Fri Dec 06 16:11:37 2013 +0530
summary:     amfd: Use correct CLC command to term/clean component [#104]

changeset:   4679:3c0c8c6288af
tag:         tip
parent:      4676:3293fb333eaa
user:        Nagendra Kumar<[email protected]>
date:        Fri Dec 06 16:12:00 2013 +0530
summary:     amfd: Use correct CLC command to term/clean component [#104]

[staging:e12e75]
[staging:ef5cef]
[staging:3c0c8c]



---

** [tickets:#104] AMF: wrong CLC command used at component restart**

**Status:** fixed
**Created:** Mon May 13, 2013 05:28 AM UTC by Nagendra Kumar
**Last Updated:** Mon Dec 02, 2013 10:34 AM UTC
**Owner:** Nagendra Kumar

Migrated from http://devel.opensaf.org/ticket/3139

When SMF is using upgrade with component restart the saAmfCompType attribute is 
first set and then the restart operation is called. This causes AMF to call the 
terminate/cleanup command from the new component type when terminating the old 
component. So for this to work today the component commands has to be able to 
terminate any old version of a component. So you can't use any version specific 
name etc. in the terminate commands. To avoid this limitation AMF would need to 
remember the old terminate/cleanup commands when the saAmfCompType attribute is 
set and the component is instantiated. 
--------------------------------------------------------------------

Changed 13 days ago by nagendra ¶
  The script should be backward compatible, if old scripts works, new scripts 
should also work.


Changed 13 days ago by bertil ¶
  Is this documented somewhere ? I.e. that the terminate/cleanup commands has 
to be made so it will terminate any old version of the component.


Changed 11 days ago by nagendra ¶
  No, it is not. But once the comp type is changed, further any action will 
proceed as per new comp type.





---

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.
------------------------------------------------------------------------------
Sponsored by Intel(R) XDK 
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to