RE: [dsdp-tm-dev] Sub-hosts with the Remote System Explorer

["Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>]

Hello Serge,

This is a good question. I think it really boils down to
where you want the Subsystem level to be.

Let's assume an OS Awareness Subsystem that gives you 
information about the Threads running on your hardware.

You can have one master subsystem showing all threads
regardless of DCU they run on. Then the Target is your
IHost. Or, you can have separate subsystems on each of
the DCUs. Then each DCU is a host of itself, and what
you need is Target Grouping in order to group the
separate DCUs (Ihost objets) under a single parent.

We've had some discussions about connection grouping
a long time ago,
   http://wiki.eclipse.org/DSDP/TM/Connection_Groups
 
http://wiki.eclipse.org/DSDP-TM_Proposal_for_RSE_Hierarchy_by_Dave_Dykst
al_2005x11x09

I'd love to see these discussions get active again.

I think what's really missing right now is a much
clearer picture of the use-cases related to multi-target
and connection grouping. Could you start filling in your
envisioned system on the "Connecton Groups" Wiki page?

I think that one guideline here can be that a 
"Conenction Groups" concept which merely groups several
independent IHost connections will always be a light
coupling between the IHosts only. 

For systems that have a tight coupling between the 
various (co)devices on a board, a single subsystem
giving access to those (co)devices might be the 
better approach.

The "connection group" approach will likely require
API changes in RSE, in order to support multiple levels
if nesting in the SystemView before the IHost objects
are shown. But it might also work without API changes.

The "subsystem" approach is totally up to each extender
of RSE to implement by himself.

Hope that helps for now, let's get the discussion going!

Cheers,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
 
 

> -----Original Message-----
> From: dsdp-tm-dev-bounces@xxxxxxxxxxx 
> [mailto:dsdp-tm-dev-bounces@xxxxxxxxxxx] On Behalf Of Serge Beauchamp
> Sent: Mittwoch, 23. April 2008 13:40
> To: dsdp-tm-dev@xxxxxxxxxxx
> Subject: [dsdp-tm-dev] Sub-hosts with the Remote System Explorer
> 
> Hi,
> 
> I've been looking in the Remote System Explorer feature, and 
> we'd like 
> to use it to be able to model the hardware setup that our 
> customers are 
> using.
> 
> Basically, the typical setup consist of a hardware board (the target) 
> and a numbers of Data Collection Units (DCU) setup for the target.  
> 
> In the RSE, I understand that the target would need to be 
> represented as 
> a host, but since the DCU are different boards with their own 
> IP and can 
> be reconfigured for a different host, it seems that they 
> don't fit the 
> RSE model as being sub-systems of the host but rather hosts 
> themselves, no?
> 
> Ideally, I would like to be able to specify the DCU as 
> children of each 
> target, while the user can re-parent them or move them at top 
> level if 
> necessary, is that possible with the current RSE design?
> 
> Thanks.
> 
> Serge Beauchamp
> Software Engineer
> Freescale Semiconductor
> _______________________________________________
> dsdp-tm-dev mailing list
> dsdp-tm-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev
>