Hmm. In the absence of HARS support, I think this 'automatic instantiation'
behavior could be controlled based on a configuration attribute, say
"autostart" or "autoinstantiate"
This could give flexibility (to do a readiness check!?).
One way of looking at this proposal is to treat it as equivalent to introducing
a new admin operation called "REPROVISION" that internally orchestrates a set
of CCB commands to be executed.
Having said that, I'm not sure(need to figure out) how the statemachines will
be impacted if this proposal is to be supported!
Cheers,
Mathi.
From: Hans Feldt [mailto:[email protected]]
Sent: Thursday, October 17, 2013 1:27 PM
To: Ticket 597
Subject: [tickets] [opensaf:tickets] #597 AMF: support to add component in
unlocked SU
_____
HYPERLINK "http://sourceforge.net/p/opensaf/tickets/597/"[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: Thu Oct 17, 2013 07:56 AM UTC
Owner: nobody
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 HYPERLINK
"mailto:[email protected]"[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:#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:** Thu Oct 17, 2013 07:56 AM UTC
**Owner:** nobody
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 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=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
