On Tuesday 11 February 2003 04:28 pm, Eric Wolzak wrote:
> Kind of old kind of failure treatment, now and then a bang on the
> case brings the screen back . Not so now, so I have to tight-vnc in to
> edit this email ;(
Maybe you need a bigger hammer. ;-) Been there.
> Some remarks. lo leaf-c
On Tuesday 11 February 2003 12:19 am, Chad Carr wrote:
> On Mon, 2003-02-10 at 21:58, Lynn Avants wrote:
> Hmmm. I am still not quite getting this. I think that it assumes one
> callback for each variable? Am I wrong? Either that or we would have
> to have some way to walk the tree when we wer
On Mon, 2003-02-10 at 21:58, Lynn Avants wrote:
> On Sunday 09 February 2003 10:15 am, Chad Carr wrote:
>
> > Okay. We are speaking the same language, but mine is a bit more
> > abstract (could be considered good or bad). A group of changes (say ip
> > address, mask and gateway for an interface)
On Sunday 09 February 2003 10:15 am, Chad Carr wrote:
> Okay. We are speaking the same language, but mine is a bit more
> abstract (could be considered good or bad). A group of changes (say ip
> address, mask and gateway for an interface) may be aggregated into a
> single event using the trigger
On Sun, 2003-02-09 at 05:58, Eric Wolzak wrote:
> Hello Chad, I really think we were miscommunicating,( we have different background
> ;) ) but I'll try again > >
>
>Packages
> Packages own templates of their configuration files or scripts to generate those
> packages ( even better)
> Pac
Hello Chad, I really think we were miscommunicating,( we have different background
;) ) but I'll try again > >
Packages
Packages own templates of their configuration files or scripts to generate those
packages ( even better)
Packages own several variables ( necessary to configurate the packag
Chad Carr wrote:
On Fri, 2003-02-07 at 14:15, Matt Schalit wrote:
Does every package need a manifest of all possible variables
and commands? Is that possible?
Yes. For _complete_ configuration yes. Is it possible: not for
shorewall ;-). But not really required for a web interface. Our
compe
On Sat, 2003-02-08 at 14:35, Eric Wolzak wrote:
> Hello Chad
>
> > I am game for writing code that will accept any hierarchy
> > delimiter and allowing folks to use any of them. My preference is
> > actually '.' but it is not a proper character in a shell identifier. I
> > do think that the '
Hello Chad
> I am game for writing code that will accept any hierarchy
> delimiter and allowing folks to use any of them. My preference is
> actually '.' but it is not a proper character in a shell identifier. I
> do think that the '_' doesn't properly emphasize the "path" or "object"
> natur
On Sat, 2003-02-08 at 02:04, Eric Wolzak wrote:
> Hello Chad, Matt Lynn and list
>
> first of all my compliments for the programm ( much cleaner as what
> I did ;) )
> two small comments
> 1) to set a variable it should be set like this
> leaf-cdb set eth1/ipaddress 192.168.1.254
> but the s
Hello Chad, Matt Lynn and list
chad you wrote :
> On Fri, 2003-02-07 at 14:15, Matt Schalit wrote:
> >
> > Lynn Avants wrote:
> > > On Friday 07 February 2003 07:23 am, Chad Carr wrote:
> >
> > >>The api makes the hierarchy "feel" like name=value pairs. The output
> > >>from the api _is_ name v
On Fri, 2003-02-07 at 14:15, Matt Schalit wrote:
>
> Lynn Avants wrote:
> > On Friday 07 February 2003 07:23 am, Chad Carr wrote:
>
> >>The api makes the hierarchy "feel" like name=value pairs. The output
> >>from the api _is_ name value pairs; the input is sequential arguments
> >>that mimic na
On Fri, 2003-02-07 at 08:06, Lynn Avants wrote:
> On Friday 07 February 2003 07:23 am, Chad Carr wrote:
> > On Fri, 2003-02-07 at 00:30, Erich Titl wrote:
>
> > > For a single key=value file there is one already in Bering and I believe
> > > in Dachstein too, lrp.conf , why not use it? It only con
Lynn Avants wrote:
On Friday 07 February 2003 07:23 am, Chad Carr wrote:
The api makes the hierarchy "feel" like name=value pairs. The output
from the api _is_ name value pairs; the input is sequential arguments
that mimic name=value pairs. See the following transcript from my CVS
code:
On Friday 07 February 2003 07:23 am, Chad Carr wrote:
> On Fri, 2003-02-07 at 00:30, Erich Titl wrote:
> > For a single key=value file there is one already in Bering and I believe
> > in Dachstein too, lrp.conf , why not use it? It only contains parameters
> > we need to use anyway.
> > If a hiera
On Thu, 2003-02-06 at 22:01, Lynn Avants wrote:
> Eric and I are NOT proposing flattening the tree structure, but alloing for
> a inbetween layer that is actually interpretable by a human. Many humans
> have a need to fiddle w/o a API and want to find/fix possible bugs in a
> running configuratio
On Fri, 2003-02-07 at 00:30, Erich Titl wrote:
> Hi Guys
>
> At 10:01 06.02.2003 -0600, you wrote:
> >On Wednesday 05 February 2003 03:36 pm, Charles Steinkuehler wrote:
> >
> >
> >Duly noted. Where does the responsibility of the 'check' and 'restart' lie?
> >This would seem to be the respnsib
On Thursday 06 February 2003 10:42 am, Charles Steinkuehler wrote:
> Lynn Avants wrote:
> > Let's say something like this:
> >
> > /db-tree/interfaces/eth1/ip_address (contains 192.168.1.254)
> >
> > /etc/db.cfg contains:
> > PREFIX=/db-tree
> > LAN_IP='cat /$PREFIX/interfaces/eth1/ip_address'
> >
Hi Guys
At 10:01 06.02.2003 -0600, you wrote:
On Wednesday 05 February 2003 03:36 pm, Charles Steinkuehler wrote:
Duly noted. Where does the responsibility of the 'check' and 'restart' lie?
This would seem to be the respnsibility of the back-end (save-script), on
first glance. Would a "trig
On Thu, 2003-02-06 at 12:37, Lynn Avants wrote:
> On Thursday 06 February 2003 11:19 am, Mike Noyes wrote:
> > Lynn,
> > Maybe (probably) I'm confused, but I thought one of the main advantages
> > of Chad's suggestion was it avoided the use of a single file database.
>
> Mike, your not confused at
On Wed, Feb 05, 2003 at 05:21:05PM -0800, Matt Schalit wrote:
> Hi David, nice to hear from you on this list.
Hi! Good to be back...
> I'd like to ask off the top, because I don't know
> how you feel, but if a central-config-db is designed,
> and a new package format is developed that interaces
On Thu, 2003-02-06 at 12:37, Lynn Avants wrote:
> On Thursday 06 February 2003 11:19 am, Mike Noyes wrote:
> > Lynn,
> > Maybe (probably) I'm confused, but I thought one of the main advantages
> > of Chad's suggestion was it avoided the use of a single file database.
>
> Mike, your not confused at
Hello Leaf configurators
Sorry to answer my own post, but I wanted to keep it in the thread.
with a few small shell scripts ( ugly probably ;) ) it is possible to
extract the variables from the config files to the database ( for a first
setup not for persistant working that should be the wro
On Thursday 06 February 2003 11:19 am, Mike Noyes wrote:
> Lynn,
> Maybe (probably) I'm confused, but I thought one of the main advantages
> of Chad's suggestion was it avoided the use of a single file database.
Mike, your not confused at all.
I'm a bit confused to how nothing but a directory str
On Thu, 2003-02-06 at 08:01, Lynn Avants wrote:
> With some playing, I'm starting to agree with this to a point. A tree that
> contained '/path/variable/value' would be simple to set and change.
> However pairing the variable/value might not be too fun to use in
> the files that use this infomati
Hello Lynnand all other configurators
I did read the mails but kept back to not disturb the brainstorming ;)
sorry for the long post.
> > This works fine for things like ifconfig/route, and even
> > iptables/ipchains, where the built configuration resides in memory, but
> > it begins to fail wh
On Wednesday 05 February 2003 03:36 pm, Charles Steinkuehler wrote:
> This works fine for things like ifconfig/route, and even
> iptables/ipchains, where the built configuration resides in memory, but
> it begins to fail when configuration is via a file on the "disk". Using
> dhcpd as an example,
On Wed, 2003-02-05 at 10:11, Mike Noyes wrote:
> On Tue, 2003-02-04 at 20:18, Chad Carr wrote:
> > I am not trying to convince folks. I am not even sure that the
> > technical hurdles can be overcome without perl. I am no C guru, but I
> > can hold my own and would be willing to work on it if sh
David Douthitt wrote:
Hi David, nice to hear from you on this list.
I'd like to ask off the top, because I don't know
how you feel, but if a central-config-db is designed,
and a new package format is developed that interaces
with the db, would you use it in Oxygen?
If you considered making chan
Matt Schalit wrote:
Ray Olszewski wrote:
At 10:13 AM 2/4/03 -0600, Charles Steinkuehler wrote:
A few quick points about some of the recent discussion:
Regarding the config-db format: It really doesn't matter. The files
should be human-readable (plain text), with enough structure (probably
On Tue, 2003-02-04 at 20:18, Chad Carr wrote:
> I am not trying to convince folks. I am not even sure that the
> technical hurdles can be overcome without perl. I am no C guru, but I
> can hold my own and would be willing to work on it if shell does not
> suffice to create the interfaces we are
Chad Carr wrote:
Or maybe you are talking about a different Chad.
My apologies. That was Greg Morgan's very thorough
idea about using Anaconda/Python/XML/Weblet. I'm
sorry I did not put enough effort into properly learning
your names.
Matt
-
On Tuesday 04 February 2003 09:20 pm, Matt Schalit wrote:
> * Ok Ray. I agree with you on the need for a simple file
>of name=value pairs.
>
> * Ok Charles, I agree that the format shouldn't matter much,
>and that XML has many advantages.
XML and nested directories are
On Tue, 2003-02-04 at 19:20, Matt Schalit wrote:
> But it was pointed out to me that the XML database in Chad's idea
> was something to be kept seperate from LEAF and not stored on it.
> I think that the XML is used on seperate OS to configure the system.
> I think the idea of Chad's was to combin
Matt Schalit wrote:
Ray Olszewski wrote:
At 10:13 AM 2/4/03 -0600, Charles Steinkuehler wrote:
But it leaves one thing out ... an important way to simplify the
interface for configuration is to restrict the range of choices
available.
LEAF tends to be pulled in two directions all the time -
Ray Olszewski wrote:
At 10:13 AM 2/4/03 -0600, Charles Steinkuehler wrote:
A few quick points about some of the recent discussion:
Regarding the config-db format: It really doesn't matter. The files
should be human-readable (plain text), with enough structure (probably
via filesystem direc
At 10:13 AM 2/4/03 -0600, Charles Steinkuehler wrote:
A few quick points about some of the recent discussion:
Regarding the config-db format: It really doesn't matter. The files
should be human-readable (plain text), with enough structure (probably via
filesystem directories and filenames) to
A few quick points about some of the recent discussion:
Regarding the config-db format: It really doesn't matter. The files
should be human-readable (plain text), with enough structure (probably
via filesystem directories and filenames) to be easily navigated, but
all access to the database in
38 matches
Mail list logo
