18 Nov
2021
18 Nov
'21
9:51 a.m.
So, I started a bit of a thing here, eh? :D
So my thought is as follows. I'm going to re-write the tunnel config
tool soon(ish) and will focus on the existing Cisco bits for the GRE
mesh but when I was configuring your router I saw the options for GRE
and I thought to myself wouldn't it be neat if I could auto-configure
pydecnet as well.
The only thing I'd really do is create/update/delete circuits (doesn't
even need to be GRE specific circuits, I'd be able to configure any
kind!). Being able to do so from external to the machine pydecnet is
running on would be a bit more flexible. Worst case my new architecture
plan has an agent that can run anywhere so it's reasonable for me to be
able to just manage config files and process restart from the agent.
As far as re-config goes if the API would allow me to alter circuit
configs (how it stores them is up to it) and just do a full router
reload that's basically what I'll be forced to do anyway if I can't use
an API to do it.
I'll put together an arch diagram for what I have in mind and we'll look
into it.
-brian
On 17/11/21 16:50, Paul Koning wrote:
Not at the moment, and it's a large change to the
design to allow
configuration to change at runtime.
I have done a bit of work to allow "change" type NICE requests,
starting with the "zero counters" request. ?That isn't done yet.
A specific change that should be small and straightforward is updating
the list of node name/address pairs. ?I'm thinking of doing that in
the network mapper, since it already fetches the current list from
MIM. ?Right now that updates the mapper data but not the main DECnet
node list. ?Once it does that, you'd be able to do the NCP "copy from
28NH" request for NCPs that implement that, or an equivalent script,
to get the current database.
paul
On Nov 17, 2021, at 11:42 AM, Brian Hechinger
<wonko at 4amlunch.net> wrote:
Speaking of the API, would it be possible to configure pydecnet via
the API?
-brian
On 17/11/21 14:54, Paul Koning wrote:
> BTW, I'm still trying to figure out how best to construct the API.
> ?What's there now seems clumsy. ?The existing network application
> API (see decnet/application/mirror.py) feels more like what I want,
> but I need to go back and see how best to work that for requests
> initiated from the outside, as opposed to subprocesses started from
> PyDECnet.
>
> paul
>
>> On Nov 17, 2021, at 9:44 AM, Brian Hechinger <wonko at 4amlunch.net>
>> wrote:
>>
>> Read documentation? Heathen. :-P
>>
>> Got a systemd unit file written for it and it's up and running for
>> good now. Woo!
>>
>> Now to figure out what I can do with the API.
>>
>> -brian
>>