Merge pull request #81 from Metaswitch/config-sync-json-files

Reviewer Ellie - Add instructions to upload JSON files

docs/ENUM.md

@@ -405,7 +405,7 @@ To enable ENUM lookups on Sprout, edit `/etc/clearwater/shared_config` and add t
     enum_server=<IP addresses of enum servers>
     enum_file=<location of enum file>
 
-If you use the ENUM file, enter the ENUM rules in the JSON format (shown above).
+If you use the ENUM file, enter the ENUM rules in the JSON format (shown above).  If you are using the enhanced node management framework provided by `clearwater-etcd`, and you use `/etc/clearwater/enum.json` as your ENUM filename, you can automatically synchronize changes across your deployment by running `sudo /usr/share/clearwater/clearwater-config-manager/scripts/upload_enum_json` after creating or updating the file.  In this case, other Sprout nodes will automatically download and use the uploaded ENUM rules.
 
 It's possible to configure Sprout with secondary and tertiary ENUM servers, by providing a comma-separated list (e.g. `enum_server=1.2.3.4,10.0.0.1,192.168.1.1`). If this is done:
 

docs/IBCF.md

@@ -74,3 +74,5 @@ There can be only one route set for any given SIP trunk IP address or host name.
 A default route set can be configured by having an entry where the domain is set to `"*"`. This will be used by the BGCF if it is trying to route based on the the domain and there's no explicit match for the domain in the configuration. 
 
 There is no default route set if the BGCF is routing based on the routing number provided. 
+
+After making a change to this file you should run `sudo /usr/share/clearwater/clearwater-config-manager/scripts/upload_bgcf_json` to ensure the change is synchronized to other Sprout nodes on your system (including nodes added in the future).