cfg-schema dump: snapshot 2013-09-05 05:40:55 +0200
cfg-schema dump: snapshot 2013-09-05 05:41:29 +0200
cfg-schema dump: snapshot 2013-09-06 05:38:48 +0200
cfg-schema dump: snapshot 2013-09-07 06:22:59 +0200
cfg-schema dump: snapshot 2013-09-08 06:24:16 +0200
cfg-schema dump: snapshot 2013-09-09 05:59:16 +0200
cfg-schema dump: snapshot 2013-09-09 18:42:37 +0200
Provide support for /etc/ngcp-config/$FILENAME.yml handling via config.d directory

Revision scripts inside /usr/share/ngcp-cfg-schema/cfg_scripts/config.d/
are assumed to be available as:

  /usr/share/ngcp-cfg-schema/cfg_scripts/config.d/$FILENAME/$revscript

resulting in file /etc/ngcp-config/config.d/$FILENAME.yml when being processed.

Testing: https://bugtracker.sipwise.com/view.php?id=3745
Provide script get_new_revision_number.sh to retrieve a globally unique and new revision number
cfg-schema dump: snapshot 2013-09-10 06:30:09 +0200
cfg-schema dump: snapshot 2013-09-10 16:25:25 +0200
cfg-schema dump: snapshot 2013-09-10 16:25:34 +0200
cfg-schema dump: snapshot 2013-09-10 16:25:47 +0200
cfg-schema dump: snapshot 2013-09-11 06:42:47 +0200
cfg-schema dump: snapshot 2013-09-11 06:42:57 +0200
cfg-schema dump: snapshot 2013-09-11 06:43:10 +0200
cfg-schema dump: snapshot 2013-09-12 06:31:39 +0200
Use batch execution as supported by recent ngcp-db-schema

This reduces required time for execution if all or most
scripts have been applied already.

Old behaviour (all scripts have been applied already):

| # time { ngcp-update-cfg-schema >/dev/null ; }
|
| real    0m13.225s
| user    0m11.329s
| sys     0m1.248s

vs new behaviour:

| # time ./ngcp-update-cfg-schema
|
| real    0m3.075s
| user    0m2.312s
| sys     0m0.280s
cfg-schema dump: snapshot 2013-09-12 14:26:45 +0200
cfg-schema dump: snapshot 2013-09-12 14:56:37 +0200