Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Here be dragons, for now.
|
|
|
|
|
|
|
|
|
|
|
|
This restores the original behaviour/design. No real rationale
was given for splitting into a status node other than that the
server did not support returning the same node name for running
and operational. It does now, so let's do this.
|
|
|
|
|
|
|
|
|
|
Since we process the <NAME/> tag already, just remove it from the
interface node entirely. This means we don't have to 'filter' on it
later in the for loop, saving cycles during iteration.
|
|
|
|
|
|
|
|
|
|
This is very early code, but seems to work.
|
|
|
|
|
|
|
|
|
|
|
|
ifupdown-ng's `ifparse` will always give a CIDR format address.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This allows us to have a true picture of the system for the
operational datastore, separate from the config datastore.
|
|
|
|
This makes reuse and reflection easier.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|