[Demi-devel] Re: Developer for demi

[Leo Eraly]

Hi Guys,


I've read the proof of concept code and i saw that 
you use 'scp' to get the status of remote machines? Is this correct?

Before I saw this project I wanted to write my own tool.
And i had the following ideas about it, what do you think about them

First idea.

Work with a central deamon which has the information for all
the different hosts in the network.
With the following directory-structure on the server.
- Server

                CENTRAL SERVER
                WHICH HOLDS PKG DB

                                /var/cache/apt/demi/

                                                /var/cache/apt/demi/hostX

                                                                        /var/cache/apt/demi/hostX/hostinfo
                                                                        /var/cache/apt/demi/hostX/keys
                                                                        /var/cache/apt/demi/hostX/logs
                                                                        /var/cache/apt/demi/hostX/state

                                                /var/cache/apt/demi/host*
                                                                        /var/cache/apt/demi/host*/hostinfo
                                                                        /var/cache/apt/demi/host*/keys
                                                                        /var/cache/apt/demi/host*/logs
                                                                        /var/cache/apt/demi/host*/state (logged in xml perhaps?)
                                                ...


Then on the client side there should be a small program that runs from crontab and sends the necessary 
data over to central server at certain times.
And when the server sends certain reply's about updates to the client , the client should fetch this updates
from the server.

2nd idea.

All the hosts in the network should run a small daemon on which the central server could connect.
So the central server pulls all the necessary data from the different hosts/clients and collects it.
And pushes the updates to the client.
Offcourse an extra daemon on every hosts is an extra open port and therefore a possible security risk.
But It can't be that hard to allow only connections to the client-daemons from trusted hosts.


And just like Andrew I also suffer from 'Pythonitis' ; I'am also looking for a good reason to start with python ;-)

These were just some of my rough ideas that i got during a nightly-brainstorm-session(so don't shoot me). 
What do you guys think about it?

Groet

Leo

On Thu, Jun 03, 2004 at 08:28:57AM +1000, Andrew Pollock wrote:
> On Wed, Jun 02, 2004 at 07:03:13AM -0600, Leo Eraly wrote:
> > Hi,
> 
> Hi!
>  
> > I'am interested in helping you with the development
> > of demi.
> 
> That's great.
> 
> > I'am a system administrator myself,and we have a lot
> > of debian machines in our network.
> > Therefore i was looking for a central update solution
> > and that's how i noticed your project.
> > 
> > My programming skills are
> > perl
> > php
> > bash
> > java
> > some c.
> > 
> > What are your plans with the demi project?
> > Is there something i could help you with?
> 
> Well things have stalled a bit because I've been at Uni, but the midyear
> break is coming up, so I can hopefully put in a solid couple of weeks.
> 
> There's some proof of concept code up on the Demi page on Alioth. The game
> plan at this stage is to write it in Python. For now, subscribe yourself to
> the demi-devel list on Alioth, and have a look at the proof of concept
> stuff, and if you have any design suggestions, please send them to the list.
> Also take a look at the list archives to see what we've discussed (it isn't
> much) so far.
> 
> regards
> 
> Andrew
> 
> _______________________________________________
> Demi-devel mailing list
> Demi-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/demi-devel
> 

-- 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Leo ERALY					     
leo@RealROOT.be					www.RealROOT.be
+32 475 257 493				"Your Internet partner"
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++