| Age | Commit message (Collapse) | Author |
|---|
|
with slash in
jenner.
|
|
corresponding changes made to node.defs
|
|
Use (void) rather than old K&R style.
Make some functions local.
|
|
|
|
|
|
available to the partial commit status api (bug fix 4919). this approach will
be revised in next
release.
|
|
accounting file.
|
|
from commit and via .changes
file used for commit active node set.
|
|
template tree and build the
priority file from "priority: val" tags found in node.def files. This
will now allow us to migrate the priority statements found to the specified nodes. Currently the
program does not order the priority nodes according to values (cosmetic
feature).
Finally once all the priority values have been migrated to the infected node.defs the priority
program can be added as a postinst hook on debian package install.
|
|
nodes are delimited by "/" rather than spaces.
|
|
deleted children. This change only affects
the commit check for nodes that are transactions and are not directly deleted, but have deleted children.
commit check is now being called.
|
|
missing the last 4 bytes on 64 bit copy.
|
|
|
|
functional without additional testing.
|
|
CREATE, DELETE, END, BEGIN) within a priority tree.
That means that all work (include the commit-check pass) will be
performed on a priority tree before proceeding to the next priority tree.
If a priority tree generates a failure in the commit-check pass
processing will halt on the priority tree and no further processing will
be performed on the priority tree. The failed priority tree will NOT be
copied to the active working directory.
All nodes in the priority tree will execute SYNTAX and COMMIT actions
except for nodes that have been deleted. Note this iteration is
performed on the working tree, so all commit-check nodes will either be
directly modified or have a node down the hierarchy that had been modified.
The working directory and active directory will not be modified until
after all priority trees have been processed.
|
|
Note that commit check only applies in the following cases:
1) On nodes or ancestors of nodes that have been set or modified
2) Does not applied to deleted nodes
Feature developers should:
1) locate commit checks at a common ancestor if checking across a hierarchy
2) expect that the commit check only enforces created behavior (therefore behaves more like a create check).
An additional flag is provided "-f" to allow for full syntax and commit checks. This allows a complete single pass on all syntax and
commit errors. The default behavior is to stop processing on the first error.
|
|
in the node.def. This change only affects display of nodes when -a option is used.
|
|
passes regression
|
|
Post unionfs directory magic until after all actions have been applied to node tree.
|
|
"ENV_SIBLING_POSITION". This value will either be "FIRST" or "LAST" or undefined.
"FIRST" means that the sibling is the first in the list of a common parent, provided that the sibling resides in the same priority group
"LAST" means that the sibling is the last in the list of a common parent, provided that the sibling resides in the same priority group
|
|
|
|
opaque directories are now handled corrected when a delete is followed by a set in a subsection of the deleted hierarchy.
|
|
end/begin transactions. now only end/begin are called on active nodes.
|
|
So,
100 load-balancing/wan/rule/node.tag/*
applies the priority of "100" to all children of the multinode "rule:value"
NEW TRANS
+ source (t: 0, p: 333)
+ address (t: 0, p: 1000)
+ 1.1.1.1/32 (t: 8, p: 1000) [VALUE]
NEW TRANS
+ protocol (t: 0, p: 333)
+ all (t: 8, p: 1000) [VALUE] [SYNTAX]
NEW TRANS
+ protocol (t: 0, p: 333)
+ all (t: 8, p: 1000) [VALUE] [SYNTAX]
NEW TRANS
+ load-balancing (t: 0, p: 1000)
+ wan (t: 0, p: 1000) [DELETE] [COMMIT]
+ rule (t: 0, p: 1000) [MULTI]
+ 1 (t: 1, p: 1000) [VALUE]
+ 2 (t: 1, p: 1000) [VALUE]
Where protocol is a child node of "rule:value"
This should allow us to compress some of the entries given the current state of the priority file.
|
|
|
|
now stops on failure within priority group (expected behavior).
|
|
|
|
action being applied.
|
|
|
|
not promote to enclosing transaction scope.
|
|
|
|
failures to be lost on repeated commits.
|
|
first non-space character on a line--if this character is a hash it is a comment otherwise it's an
active line.
|
|
The new command flag is "-a"
|
|
Remove unused variables
Remove extra arg from sprintf
Fix missing prototype for piecewise_copy.
|
|
Add headers with prototypes to remove compiler warnings
Make some obvious tables const to avoid any bugs.
|
|
TRUE and FALSE are already defined in glib causing warnings.
|
|
regression failure.
|
|
will need to be added later after some reworking of the old node
execution code.
|
|
general case, just happened to show up on qos-walkthrough (after def files were supported in the new
commit).
|
|
qos-walkthrough regression test. haven't tried it but system probably inherently prevents percents from
being used in embedded multinodes.
|
|
|
|
NOT executed if a multinode does not possess a value. Other source cleanup.
|
|
not reside
on node.tags, but on parent (node name of multinode)--this is to prevent priorities
splitting behaviors between different priorities on multinodes.
|
|
configured by system will now be suppressed via show command (same behavior as
with old commit).
|
|
indirection for actions in commit head.
Bug found when review policy_bgp regression failure.
|
|
to check whether commit is in a delete or set action. The environmental variable is
"COMMIT_ACTION" the value can either be "SET" or "DELETE". The variable is set for the duration of the call being made to the action in the node.def file.
This should allow some simplication of scripts (i.e. such as setting up static routes).
|
|
user to support the 'old' cli behavior if desired via the -o flag.
|
|
|
|
priority.
|
