Vyatta configuration system (mirror of https://github.com/vyos/vyatta-cfg.git) https://git.amelek.net/vyos/vyatta-cfg.git/atom?h=debian%2F0.15.15 2009-09-05T04:17:23+00:00 2009-09-05T04:17:23+00:00 slioch slioch@eng-140.vyatta.com 2009-09-05T04:17:23+00:00 urn:sha1:f50e8a9c76156a003d07fbca48f35abd24a434d0 2009-07-06T20:38:22+00:00 slioch slioch@eng-140.vyatta.com 2009-06-30T20:52:01+00:00 urn:sha1:492372480adb0b24808c893b090d12f5703fa3fb 2009-07-06T20:37:44+00:00 slioch slioch@eng-140.vyatta.com 2009-06-27T06:18:33+00:00 urn:sha1:c3b23a060d2c949580873dc100469be9ad05734c 2009-06-26T22:08:02+00:00 slioch slioch@eng-140.vyatta.com 2009-06-26T22:05:48+00:00 urn:sha1:aa697721489c867de9b39121836c05a5bc3239b6 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. 2009-06-24T18:51:45+00:00 slioch slioch@eng-140.vyatta.com 2009-06-24T18:43:11+00:00 urn:sha1:bbf867acfcaa999dec75b3a76ca6d286db4b57f8 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. 2009-06-10T03:17:25+00:00 slioch slioch@eng-140.vyatta.com 2009-06-10T03:15:00+00:00 urn:sha1:7fee20a430a05b934b00d025bccb4281792ccb3d 2009-06-03T17:40:35+00:00 slioch slioch@eng-140.vyatta.com 2009-06-03T17:40:35+00:00 urn:sha1:9a729a8cb2929a5272da6e240c9bd63db198f6c4 "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 2009-06-01T18:55:47+00:00 slioch slioch@eng-140.vyatta.com 2009-06-01T18:55:47+00:00 urn:sha1:2c22465441bbb7bdd40bf7a12bbdeb8390e32471 2009-05-28T20:19:33+00:00 slioch slioch@eng-140.vyatta.com 2009-05-28T20:19:33+00:00 urn:sha1:81f970230c8a99acb5afb2e997b9f50e6e081e72 opaque directories are now handled corrected when a delete is followed by a set in a subsection of the deleted hierarchy. 2009-04-11T22:27:42+00:00 slioch slioch@eng-140.vyatta.com 2009-04-11T22:27:42+00:00 urn:sha1:664f649d0f455bd7f60b06659bf81d9bed952fe2 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.