Documentation

All written information, media, and other content regarding ebrainpool. This includes user guides, white papers, on-line help, quick-reference guides

eBrainPool across 3 multiple devices, & Meego too

Submitted by erle on

Found another video lying around, forgot about this one. Again, apologies for the video quality.
This shows ebrainpool running across a third device in the mix. As we have been mentioning, the real benefit comes into play when there is a multitude of devices connected. Is not sharing like that in real life too? The more in the mix, the better things are? No different here.
We had the client already running on moblin, so getting it running on meego was not too hard at all. Each machine can access the software on each others machines.
Heres a question, 3 machines are shown in the video.. so why does the client in the video show 3 machines? It should be two right? i.e. each machine connects to others, and 2 others are in the mix as shown in the video.
..... well as Sherlock Holmes said, eliminate all possibilities and the remaining one, no matter how implausible has got to be the truth.

... think...
 

heres why, we were testing out the n900 at this time too. The client inadvertantly picked up the stray 4th device. 

 

Category: 

Workfow Sketch, how it all fits

Submitted by erle on

We have been having a fun time of late. Talking about all this we are trying to to, with a variety of very helpful people. Love the community, Love the spirit. Its why we all do what we do. Been getting very interesting ideas from people more adept at the technologies we are using than us, and some great new directions. Looking forward to more help from all of you guys. Some of the nice folks over at Battlemesh have spent some time trying to understand the 'mess':) we have put together and sent across some great suggestions. There are others as well, so a big thanks to all of you and please keep the chatter going. Anyway, thought  a quick  sketch of the workflow is in order here, its time we started to go a little more in depth as to how this fits together. This was all proof-of-concept stuff, so it will change and the suggestions we are getting certainly seem to say so :)  Under the Hood gave a good look at the technologies used. This will give an idea  of the workflow, more to follow of course.
ebrain-workflowsketch.jpg

Category: 

X rendering, measured using gtkperf

Submitted by erle on

This is the application gtkperf (http://gtkperf.sourceforge.net/ ) running through ebrainpool. Its a good way to understand where the display (Xorg) fits into this mix. Here the app is actually running my machine (supernova) which has the Intel x3100 graphics card and is being also run simultaneously from my machine, through ebrainpool on a machine with an ATI radeon.  The pics below are shots taken out which show the results (yeah we know, bad video... sorry about that)

Notice in particular the times taken, rather the difference between the two. Keep in mind here this is the Same application, running of ONE machine, the same machine. It is installed on mine (intel x3100 graphics - 29 seconds) and the other machine running this very same installation of gtkperf of my machine, but via X, rendering it on another machine (ATI radeon graphics - 16 seconds). The Cpu being used in both cases is really mine, the graphics cards is the only difference.  

PB190125_0.JPG

PB190123.JPG

Category: 

Moving towards the N900

Submitted by jeetu on

We decided to throw the N900 into the mesh mix :) The above shows the N900 running the olsrd daemon and being able to see the other devices in the mesh :) While we still have not ported the client onto the N900 this was a good test to see where we stand on this platform....so far looking good :)

 

The picture below shows olsrd running on Moblin and able to see the N900 and other devices.

 

 

 

Category: 

Under the hood

Submitted by jeetu on

Under the hood

 

Now that we've seen a little of what eBrainPool can do, I thought I'd doodle a bit and do my best to explain how the current developer's release works under the hood :)

The above schematic shows how the different technologies used come together.

  • Olsr Routing - as mentioned earlier for mesh networking and discovery of neighbouring devices we're using the OLSR protocol implementation developed by the olsrd project (www.olsrd.org). This is a seperate daemon that needs to be started independently at the moment.
  • Olsr Plugin - we've created our own plugin and extended the core olsrd program. Whereas the core olsrd recognizes devices with olsrd running and sets up the routing table to form a mesh, the plugin explicitly publishes the current host as having the eBrainPool client working and thereby willing to share software. It also looks out for other such devices in the mesh. Finally it pushes out information such as IP of the found device and username to the client.
  • eBrainPool client - this client offers the interface by which a user can see the other users in the Beehive mesh networked pool around them and select applications to run from these users. It first checks to see that the IP the olsr plugin has told it has a valid client up and running. If so, the username of this client gets added into the list. When a user clicks on a partciular username all software currently hosted by that user is pulled out and shown. If a user wishes to run a particular remote software, an SSH connection is formed between the two devices. For this connection a custom ssh server gets started (currently via scripts) at the end hosting the software. The ssh client at the users end connects to this and requests the specific remote software to be X forwarded back through this tunnel. FUSE allows for data to be abstracted so that even if you are using software from someone else you can still use only your data. Neither end can access or view the other persons data.

Whew :)...hope this helps understanding the mayhem :). And yes I know I have terrible handwriting ;)

 

Category: 

Pages

Subscribe to RSS - Documentation