Merge pull request #268 from Metaswitch/change_sudo

change commands to show if they need sudo or not

docs/Backups.md

@@ -259,11 +259,11 @@ To backup the shared configuration:
 
 To restore a previous backup, copy the six files listed above to `/etc/clearwater` on one of your sprout nodes. Then run the following commands on that node:
 
-    cw-upload_shared_config
-    cw-upload_bgcf_json
-    cw-upload_enum_json
-    cw-upload_scscf_json
-    cw-upload_shared_ifcs_xml
-    cw-upload_fallback_ifcs_xml
+    sudo cw-upload_shared_config
+    sudo cw-upload_bgcf_json
+    sudo cw-upload_enum_json
+    sudo cw-upload_scscf_json
+    sudo cw-upload_shared_ifcs_xml
+    sudo cw-upload_fallback_ifcs_xml
 
 See [Modifying Clearwater settings](Modifying_Clearwater_settings.md) for more details on this.

docs/Manual_Install.md

@@ -197,7 +197,7 @@ If you are creating a [geographically redundant deployment](Geographic_redundanc
 
 Now run the following to upload the configuration to a shared database and propagate it around the cluster (see [Modifying Clearwater settings](Modifying_Clearwater_settings.md) for more details on this).
 
-    cw-upload_shared_config
+    sudo cw-upload_shared_config
 
 ## Provision Telephone Numbers in Ellis
 
@@ -345,11 +345,11 @@ Each `SharedIFCsSet` element can contain multiple `InitialFilterCriteria` elemen
 
 To change the Shared iFC configuration, edit this file on any Sprout node, then upload it to the shared configuration database by running `sudo cw-upload_shared_ifcs_xml`.
 
-To validate the Shared iFC configuration file before uploading it, run the command `sudo cw-validate_shared_ifcs_xml <file_location>` on the Sprout node the file is present on.
+To validate the Shared iFC configuration file before uploading it, run the command `cw-validate_shared_ifcs_xml <file_location>` on the Sprout node the file is present on.
 
 To remove the Shared iFC configuration, run the command `sudo cw-remove_shared_ifcs_xml` on any Sprout node.
 
-To view the Shared iFCs being used on any Sprout node, run the command `sudo cw-display_shared_ifcs` on that Sprout node.
+To view the Shared iFCs being used on any Sprout node, run the command `cw-display_shared_ifcs` on that Sprout node.
 
 ### Fallback iFC configuration
 
@@ -372,8 +372,8 @@ There must be exactly one `FallbackIFCsSet` element, which can can contain multi
 
 To change the fallback iFC configuration, edit this file on any Sprout node, then upload it to the shared configuration database by running `sudo cw-upload_fallback_ifcs_xml`.
 
-To validate the fallback iFC configuration file before uploading it, run the command `sudo cw-validate_fallback_ifcs_xml <file_location>` on the Sprout node the file is present on.
+To validate the fallback iFC configuration file before uploading it, run the command `cw-validate_fallback_ifcs_xml <file_location>` on the Sprout node the file is present on.
 
 To remove the fallback iFC configuration, run the command `sudo cw-remove_fallback_ifcs_xml` on any Sprout node.
 
-To view the Fallback iFCs being used on any Sprout node, run the command `sudo cw-display_fallback_ifcs` on that Sprout node.
+To view the Fallback iFCs being used on any Sprout node, run the command `cw-display_fallback_ifcs` on that Sprout node.

docs/Modifying_Clearwater_settings.md

@@ -11,8 +11,8 @@ Settings in `/etc/clearwater/shared_config` can be safely changed without entire
 To change one of these settings:
 
 *   Edit `/etc/clearwater/shared_config` on *one* node in each site and change to the new value.
-*   Run `cw-upload_shared_config` to upload the new config to etcd. The changes to the shared configuration are logged to `/var/log/syslog` and to the console. Each node in the site picks up the changed shared configuration (using Clearwater's [automatic configuration sharing](Automatic_Clustering_Config_Sharing.md) functionality) and safely restarts itself to use it.
-*   You can check which nodes are using the new shared config by running `cw-check_restart_queue_state`. If this command shows that there's been an error (i.e. a node wasn't able to restart after picking up the new config), simply fix the `/etc/clearwater/shared_config` and run the `cw-upload_shared_config` script again.
+*   Run `sudo cw-upload_shared_config` to upload the new config to etcd. The changes to the shared configuration are logged to `/var/log/syslog` and to the console. Each node in the site picks up the changed shared configuration (using Clearwater's [automatic configuration sharing](Automatic_Clustering_Config_Sharing.md) functionality) and safely restarts itself to use it.
+*   You can check which nodes are using the new shared config by running `cw-check_restart_queue_state`. If this command shows that there's been an error (i.e. a node wasn't able to restart after picking up the new config), simply fix the `/etc/clearwater/shared_config` and run the `sudo cw-upload_shared_config` script again.
 
 ## Modifying Sprout JSON Configuration