[Xorp-hackers] RE: Xorp-hackers digest, Vol 1 #183 - 1 msg

[Weaver John-JWEAVER1]

The lib version of the xorpsh is prolly exactly what I need.  I would think
for the XORP project to be successful in an embedded market this would be
necessary.  Most of the switch/router projects I have done in the past have
always required many boot time decisions on how to configure all the
interfaces and protocols.  None of our systems have ever had direct
configuration by a user and almost always requires run-time changes via
applications that trigger off of upstream database changes.  I hope I can
come to a way to use XORP in this way because I hate to think of the other
vendor I will have to use if not.  Plus it puts me way behind schedule. ;)
I guess I can always resort to hacking out some scripts to try and configure
things but it sounds real risky and not very easy, especially since I don't
know shell scripting.

-----Original Message-----
From: xorp-hackers-admin@icir.org [mailto:xorp-hackers-admin@icir.org] On
Behalf Of xorp-hackers-request@icir.org
Sent: Thursday, August 25, 2005 2:03 PM
To: xorp-hackers@icir.org
Subject: Xorp-hackers digest, Vol 1 #183 - 1 msg

Send Xorp-hackers mailing list submissions to
	xorp-hackers@icir.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
or, via email, send a message with subject or body 'help' to
	xorp-hackers-request@icir.org

You can reach the person managing the list at
	xorp-hackers-admin@icir.org

When replying, please edit your Subject line so it is more specific than
"Re: Contents of Xorp-hackers digest..."


Today's Topics:

   1. Re: Interfacing for runtime config (Mark Handley)

--__--__--

Message: 1
Date: Thu, 25 Aug 2005 19:26:17 +0100
From: Mark Handley <mark.j.handley@gmail.com>
Reply-To: m.handley@cs.ucl.ac.uk
To: Weaver John-JWEAVER1 <John.Weaver@motorola.com>
Subject: Re: [Xorp-hackers] Interfacing for runtime config
Cc: Pavlin Radoslavov <pavlin@icir.org>, xorp-hackers@icir.org

On 8/25/05, Weaver John-JWEAVER1 <John.Weaver@motorola.com> wrote:
> So I guess there is no library that I can just make calls to pass just 
> address and interface info?  I was not looking forward to piecing 
> something together and scripting it.

We could build a library version of xorpsh that you would link against, and
which would present a programatic interface for changing the config.  So far
we haven't done this because you can do this from a scripting language with
the existing xorpsh, and because it's not clear what the user-based security
model would be.

Now, such an API would still know nothing about interfaces, vifs, etc.
 Bear in mind that in the XORP architecture, the rtrmgr and xorpsh have *no*
inbuilt knowledge about the components they are managing and configuring.
This knowledge comes from the template files that are read at runtime.

An alternative would be for the FEA to provide a programatic library for
configuring interfaces, but by itself this gives you nothing you can't
already access using XRLs.  The downside is that the rtrmgr would not learn
about the interfaces, so you couldn't use xorpsh to monitor them, etc.

Finally, and what I think you want, it would be possible to build a helper
library than can configure interfaces (via XRLs to the FEA) and then tell
the rtrmgr about them (using the same XRL interface that xorpsh uses).  This
might be worth doing.  Normally we've avoided building such helpers because
you can always code them yourself using XRLs.  However in this case the
requirement may be common enough, and actually coding it yourself may be
hard enough that it may well be worth doing.

 - Mark



--__--__--

_______________________________________________
Xorp-hackers mailing list
Xorp-hackers@icir.org
http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers


End of Xorp-hackers Digest