Merge pull request #256 from Metaswitch/update_filename

[No reviewer] Update filename

docs/Clearwater_Configuration_Options_Reference.md

@@ -80,8 +80,8 @@ This section describes options for the basic configuration of a Clearwater deplo
 * `sprout_registation_store` - this is the locations of Sprout's registration stores. It has the format `<site_name>=<domain>[:<port>][,<site_name>=<domain>[:<port>]]`. In a non-GR deployment, only one domain is provided (and the site name is optional). For a GR deployment, each domain is identified by the site name, and one of the domains must relate to the local site.
 * `ralf_session_store` - this is the locations of ralf's session stores. It has the format `<site_name>=<domain>[:<port>][,<site_name>=<domain>[:<port>]]`. In a non-GR deployment, only one domain is provided (and the site name is optional). For a GR deployment, each domain is identified by the site name, and one of the domains must relate to the local site.
 * `memento_auth_store` - this is the location of Memento's authorization vector store. It just has the format `<domain>[:port]`. If not present, defaults to the loopback IP.
-* `sprout_chronos_callback_uri` - the callback hostname used on Sprout's Chronos timers. If not present, defaults to the host specified in `sprout-hostname`. In a GR deployment, should be set to a deployment-wide Sprout hostname (that will be resolved by using static DNS records in `/etc/clearwater/dns_config`).
-* `ralf_chronos_callback_uri` - the callback hostname used on ralf's Chronos timers. If not present, defaults to the host specified in `ralf-hostname`. In a GR deployment, should be set to a deployment-wide Dime hostname (that will be resolved by using static DNS records in `/etc/clearwater/dns_config`).
+* `sprout_chronos_callback_uri` - the callback hostname used on Sprout's Chronos timers. If not present, defaults to the host specified in `sprout-hostname`. In a GR deployment, should be set to a deployment-wide Sprout hostname (that will be resolved by using static DNS records in `/etc/clearwater/dns.json`).
+* `ralf_chronos_callback_uri` - the callback hostname used on ralf's Chronos timers. If not present, defaults to the host specified in `ralf-hostname`. In a GR deployment, should be set to a deployment-wide Dime hostname (that will be resolved by using static DNS records in `/etc/clearwater/dns.json`).
 * `cassandra_hostname` - a hostname that resolves by DNS round-robin to the signaling interface of all Vellum nodes in the local site.
 * `chronos_hostname` - a hostname that resolves by DNS round-robin to the signaling interface of all Vellum nodes in the local site.
 
@@ -232,7 +232,7 @@ This section describes settings that may vary between systems in the same deploy
 
 ## DNS Config
 
-This section describes the static DNS config which can be used to override DNS results. This is set in `/etc/clearwater/dns_config`. Currently, the only supported record type is CNAME and the only component which uses this is Chronos and the I-CSCF. The file has the format:
+This section describes the static DNS config which can be used to override DNS results. This is set in `/etc/clearwater/dns.json`. Currently, the only supported record type is CNAME and the only component which uses this is Chronos and the I-CSCF. The file has the format:
 
     {
       "hostnames": [

docs/Modifying_Clearwater_settings.md

@@ -34,12 +34,12 @@ To change one of these files:
 
 *This configuration can be freely modified without impacting service*
 
-It's possible to add static overrides to DNS to a clearwater node. This is done by adding entries to `/etc/clearwater/dns_config`. Currently, only CNAME records are supported and this is only used by Chronos and the I-CSCF.
+It's possible to add static overrides to DNS to a clearwater node. This is done by adding entries to `/etc/clearwater/dns.json`. Currently, only CNAME records are supported and this is only used by Chronos and the I-CSCF.
 
 To change this file:
 
 * Edit the file on one of your nodes in each site.
-* Run `sudo /usr/share/clearwater/clearwater-config-manager/scripts/upload_dns_config`.
+* Run `sudo cw-upload_dns_json`.
 * The change will be automatically propagated around the site (using Clearwater's [automatic configuration sharing](Automatic_Clustering_Config_Sharing.md) functionality) and will start being used.
 
 ## Starting from scratch