[tickets] [opensaf:tickets] #589 mds: configurable TIPC importance
- **status**: assigned --> review --- ** [tickets:#589] mds: configurable TIPC importance** **Status:** review **Created:** Tue Oct 08, 2013 10:57 AM UTC by Ingvar Bergström **Last Updated:** Wed Oct 09, 2013 05:21 AM UTC **Owner:** Ingvar Bergström In some cases OpenSAF systems are hosting applications also using TIPC transport. This can cause the TIPC level buffers to be filled and messages to be lost, causing trouble for OpenSAF. If the TIPC importance level can be configured such situations can be avoid by raising the level for MDS. The special importance level for AVND is also removed since it is no longer needed when the heartbeat mechanism is removed. To configure the TIPC importance: -DTIPCIMPORTANCE=level where level could be any of -TIPC_LOW_IMPORTANCE -TIPC_MEDIUM_IMPORTANCE -TIPC_HIGH_IMPORTANCE -TIPC_CRITICAL_IMPORTANCE e.g. -DTIPCIMPORTANCE=TIPC_HIGH_IMPORTANCE In a configure statement e.g.: configure CFLAGS="-DRUNASROOT -DTIPCIMPORTANCE=TIPC_HIGH_IMPORTANCE" --disable-ais-plm --- 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.-- 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=60134071&iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #538 AMF: fail-over assignments despite comps in TERM-FAILED state
- **Type**: enhancement --> defect --- ** [tickets:#538] AMF: fail-over assignments despite comps in TERM-FAILED state** **Status:** unassigned **Created:** Fri Aug 09, 2013 06:43 AM UTC by Hans Feldt **Last Updated:** Wed Oct 09, 2013 12:54 PM UTC **Owner:** nobody AMF currently performs fail-over recovery action although a component is in termination-failed presence state. This can lead to severe inconsistencies for the application. The specification also clearly states how this should work in 4.8: "If the component and any of its contained components (for a container component) were assigned the active HA state for some component service instances when the CLEANUP command was executed, and semantics of the redundancy model of its enclosing service group guarantee that at a point in time only one component can be in the active HA state for a given component service instance, the failure to terminate that component prevents the Availability Management Framework from assigning to another component the active HA state for these component service instances (and by the same token prevents the assignment of the active HA state to other service units for the service instances that contain the involved CSIs). In this case, the ser- vice instances will stay unassigned until an administrative action is performed to ter- minate the failed component." Can be tested by running the AMF 2N sa-aware sample app and modifying the cleanup script to do "exit 1" which gives this effect when the active component is killed: Aug 9 08:40:01 Vostro osafamfnd[11307]: NO 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' faulted due to 'avaDown' : Recovery is 'componentRestart' Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Cleanup of 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' failed Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Reason:'Exec of script success, but script exits with non-zero status' Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Exit code: 1 Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Component Failover trigerred for 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1': Failed component: 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Aug 9 08:40:01 Vostro osafamfnd[11307]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State INSTANTIATED => TERMINATION_FAILED Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Assigning 'safSi=AmfDemo,safApp=AmfDemo1' QUIESCED to 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Assigned 'safSi=AmfDemo,safApp=AmfDemo1' QUIESCED to 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Assigning 'safSi=AmfDemo,safApp=AmfDemo1' ACTIVE to 'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1' Aug 9 08:40:01 Vostro amf_demo[11620]: CSI Set - HAState Active for all assigned CSIs Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Assigned 'safSi=AmfDemo,safApp=AmfDemo1' ACTIVE to 'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1' Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Removing 'safSi=AmfDemo,safApp=AmfDemo1' from 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Removed 'safSi=AmfDemo,safApp=AmfDemo1' from 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' --- 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.-- 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=60134071&iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #538 AMF: fail-over assignments despite comps in TERM-FAILED state
The "behaviour" that will change anyway oes not work. That is what #573 was about. Instead of fixing this broken bad incorrect behaviour we should do what the specification says. --- ** [tickets:#538] AMF: fail-over assignments despite comps in TERM-FAILED state** **Status:** unassigned **Created:** Fri Aug 09, 2013 06:43 AM UTC by Hans Feldt **Last Updated:** Wed Oct 09, 2013 12:54 PM UTC **Owner:** nobody AMF currently performs fail-over recovery action although a component is in termination-failed presence state. This can lead to severe inconsistencies for the application. The specification also clearly states how this should work in 4.8: "If the component and any of its contained components (for a container component) were assigned the active HA state for some component service instances when the CLEANUP command was executed, and semantics of the redundancy model of its enclosing service group guarantee that at a point in time only one component can be in the active HA state for a given component service instance, the failure to terminate that component prevents the Availability Management Framework from assigning to another component the active HA state for these component service instances (and by the same token prevents the assignment of the active HA state to other service units for the service instances that contain the involved CSIs). In this case, the ser- vice instances will stay unassigned until an administrative action is performed to ter- minate the failed component." Can be tested by running the AMF 2N sa-aware sample app and modifying the cleanup script to do "exit 1" which gives this effect when the active component is killed: Aug 9 08:40:01 Vostro osafamfnd[11307]: NO 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' faulted due to 'avaDown' : Recovery is 'componentRestart' Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Cleanup of 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' failed Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Reason:'Exec of script success, but script exits with non-zero status' Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Exit code: 1 Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Component Failover trigerred for 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1': Failed component: 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Aug 9 08:40:01 Vostro osafamfnd[11307]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State INSTANTIATED => TERMINATION_FAILED Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Assigning 'safSi=AmfDemo,safApp=AmfDemo1' QUIESCED to 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Assigned 'safSi=AmfDemo,safApp=AmfDemo1' QUIESCED to 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Assigning 'safSi=AmfDemo,safApp=AmfDemo1' ACTIVE to 'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1' Aug 9 08:40:01 Vostro amf_demo[11620]: CSI Set - HAState Active for all assigned CSIs Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Assigned 'safSi=AmfDemo,safApp=AmfDemo1' ACTIVE to 'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1' Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Removing 'safSi=AmfDemo,safApp=AmfDemo1' from 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Removed 'safSi=AmfDemo,safApp=AmfDemo1' from 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' --- 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.-- 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=60134071&iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #573 SG in unstable state when SU moves to TERM_FAILED.
Duplicate of #538 --- ** [tickets:#573] SG in unstable state when SU moves to TERM_FAILED.** **Status:** duplicate **Labels:** TERM_FAILED **Created:** Fri Sep 20, 2013 11:19 AM UTC by Praveen **Last Updated:** Wed Sep 25, 2013 05:41 AM UTC **Owner:** Praveen Branch: Default. Configuration: 2N model, 2 SUS with 2 comps each, 2 SIs with 2 CSIs each. Recovery policy: componentRestart. steps: 1) Bring application up. 2)Component binary should have provision to timeout for terminate callback. Also cleanup script of comp1 should exit with non-zero status. 3)Kill comp1. Cleanup failure of comp1 will lead to both comp1 and SU to move to TERM_FAILED state. 4)AMFND issues term callback to comp2. In between AMFD sends quiesced assignment to AMFND. 5) Comp2 times out. AMFND performs its cleanup successfully but it never responds to AMFD for "quiesced assignment done" SG remains in unstable state. Since currently AMF performs failover and brings SG to stable state, above mentioned case should be handled in the same way (despite #538). Attached log.tgz containslogs and configuration. --- 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.-- 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=60134071&iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #538 AMF: fail-over assignments despite comps in TERM-FAILED state
- **Type**: defect --> enhancement --- ** [tickets:#538] AMF: fail-over assignments despite comps in TERM-FAILED state** **Status:** unassigned **Created:** Fri Aug 09, 2013 06:43 AM UTC by Hans Feldt **Last Updated:** Wed Aug 21, 2013 07:30 AM UTC **Owner:** nobody AMF currently performs fail-over recovery action although a component is in termination-failed presence state. This can lead to severe inconsistencies for the application. The specification also clearly states how this should work in 4.8: "If the component and any of its contained components (for a container component) were assigned the active HA state for some component service instances when the CLEANUP command was executed, and semantics of the redundancy model of its enclosing service group guarantee that at a point in time only one component can be in the active HA state for a given component service instance, the failure to terminate that component prevents the Availability Management Framework from assigning to another component the active HA state for these component service instances (and by the same token prevents the assignment of the active HA state to other service units for the service instances that contain the involved CSIs). In this case, the ser- vice instances will stay unassigned until an administrative action is performed to ter- minate the failed component." Can be tested by running the AMF 2N sa-aware sample app and modifying the cleanup script to do "exit 1" which gives this effect when the active component is killed: Aug 9 08:40:01 Vostro osafamfnd[11307]: NO 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' faulted due to 'avaDown' : Recovery is 'componentRestart' Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Cleanup of 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' failed Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Reason:'Exec of script success, but script exits with non-zero status' Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Exit code: 1 Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Component Failover trigerred for 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1': Failed component: 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Aug 9 08:40:01 Vostro osafamfnd[11307]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State INSTANTIATED => TERMINATION_FAILED Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Assigning 'safSi=AmfDemo,safApp=AmfDemo1' QUIESCED to 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Assigned 'safSi=AmfDemo,safApp=AmfDemo1' QUIESCED to 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Assigning 'safSi=AmfDemo,safApp=AmfDemo1' ACTIVE to 'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1' Aug 9 08:40:01 Vostro amf_demo[11620]: CSI Set - HAState Active for all assigned CSIs Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Assigned 'safSi=AmfDemo,safApp=AmfDemo1' ACTIVE to 'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1' Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Removing 'safSi=AmfDemo,safApp=AmfDemo1' from 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Aug 9 08:40:01 Vostro osafamfnd[11307]: NO Removed 'safSi=AmfDemo,safApp=AmfDemo1' from 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' --- 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.-- 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=60134071&iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #573 SG in unstable state when SU moves to TERM_FAILED.
- **status**: review --> duplicate - **Type**: defect --> enhancement --- ** [tickets:#573] SG in unstable state when SU moves to TERM_FAILED.** **Status:** duplicate **Labels:** TERM_FAILED **Created:** Fri Sep 20, 2013 11:19 AM UTC by Praveen **Last Updated:** Wed Sep 25, 2013 05:41 AM UTC **Owner:** Praveen Branch: Default. Configuration: 2N model, 2 SUS with 2 comps each, 2 SIs with 2 CSIs each. Recovery policy: componentRestart. steps: 1) Bring application up. 2)Component binary should have provision to timeout for terminate callback. Also cleanup script of comp1 should exit with non-zero status. 3)Kill comp1. Cleanup failure of comp1 will lead to both comp1 and SU to move to TERM_FAILED state. 4)AMFND issues term callback to comp2. In between AMFD sends quiesced assignment to AMFND. 5) Comp2 times out. AMFND performs its cleanup successfully but it never responds to AMFD for "quiesced assignment done" SG remains in unstable state. Since currently AMF performs failover and brings SG to stable state, above mentioned case should be handled in the same way (despite #538). Attached log.tgz containslogs and configuration. --- 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.-- 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=60134071&iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #586 DOC: Clarify handling of token @Cd, @CD, @Nd and @Nd
- **status**: assigned --> review --- ** [tickets:#586] DOC: Clarify handling of token @Cd, @CD, @Nd and @Nd ** **Status:** review **Created:** Fri Oct 04, 2013 10:07 AM UTC by elunlen **Last Updated:** Fri Oct 04, 2013 10:07 AM UTC **Owner:** elunlen Specification of token @Cd, @CD, @Nd and @ND in AIS is unclear and contains errors. Therefore a description of how handling of them is implemented should be described in the log service PR document. See also [#565] --- 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.-- 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=60134071&iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #477 AMF should honour admin commands on middleware SU only when originated from SMF
- **status**: fixed --> assigned - **assigned_to**: Nagendra Kumar --> Mathi Naickan --- ** [tickets:#477] AMF should honour admin commands on middleware SU only when originated from SMF** **Status:** assigned **Created:** Wed Jun 26, 2013 09:36 AM UTC by Mathi Naickan **Last Updated:** Fri Oct 04, 2013 06:35 AM UTC **Owner:** Mathi Naickan AMF should allow admin commands on middleware SU only if these commands are originated from SMF. Commands like lock, lock-in and unlock, unlock-in of middleware 2N su should succeed only when SMF trigerrs them through the campaign. If we dont bring in this restriction then there are problem areas (that are still not concretely defined but can be potential problems) as described in the migrated ticket #443. Once this is fixed, the patch distributed by anders is acknowledged. --- 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.-- 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=60134071&iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #477 AMF should honour admin commands on middleware SU only when originated from SMF
changeset: 4541:4e5fabb7417a tag: tip user:Nagendra Kumar date:Wed Oct 09 16:13:22 2013 +0530 summary: amfd: Revert of changeset 4530:c567a8243dcc for ticket #477 --- ** [tickets:#477] AMF should honour admin commands on middleware SU only when originated from SMF** **Status:** assigned **Created:** Wed Jun 26, 2013 09:36 AM UTC by Mathi Naickan **Last Updated:** Fri Oct 04, 2013 06:35 AM UTC **Owner:** Mathi Naickan AMF should allow admin commands on middleware SU only if these commands are originated from SMF. Commands like lock, lock-in and unlock, unlock-in of middleware 2N su should succeed only when SMF trigerrs them through the campaign. If we dont bring in this restriction then there are problem areas (that are still not concretely defined but can be potential problems) as described in the migrated ticket #443. Once this is fixed, the patch distributed by anders is acknowledged. --- 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.-- 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=60134071&iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
