Sorry, I have missed that.
No, actually. This would mean that the stop script for the new component type
must be able to stop any
previous version of that type which will limit what changes you can do for a
component type. The worst
part is that during a rollback of an campaign you could end up in a situation
where an old version must stop
any new version which it was not aware of when it was designed.
This is related to the problem we have with amfnd reading from IMM. If amfnd
gets all component info from
amfd when starting a component it’s easy to store this locally. If you then get
a restart order for this component
you should also get all (possibly new) component info. amfnd can then stop the
component using the stored info
it used when it started it and then use the new info to start it again (could
be the same info in case it’s a restart
without upgrading the component). I have discussed this with Hans and he thinks
this can be done.
/Bertil
From: Nagendra Kumar [mailto:[email protected]]
Sent: den 25 september 2013 11:28
To: [opensaf:tickets]
Subject: [tickets] [opensaf:tickets] #104 AVSV: wrong component command called
at upgrade using component restart
Hi Bertil,
Do we have agreement on my last comment.
________________________________
[tickets:#104]<http://sourceforge.net/p/opensaf/tickets/104/> AVSV: wrong
component command called at upgrade using component restart
Status: assigned
Created: Mon May 13, 2013 05:28 AM UTC by Nagendra Kumar
Last Updated: Fri Sep 06, 2013 12:40 PM 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]<mailto:[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.
---
** [tickets:#104] AVSV: wrong component command called at upgrade using
component restart**
**Status:** assigned
**Created:** Mon May 13, 2013 05:28 AM UTC by Nagendra Kumar
**Last Updated:** Wed Sep 25, 2013 09:27 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 http://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
http://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
