Add mention of location wizard into the documentation

tbouron · tbouron · commit 26c6bca65b40 · 2016-03-17T09:30:15.000Z
diff --git a/guide/ops/locations/byon.md b/guide/ops/locations/byon.md
@@ -47,6 +47,9 @@ brooklyn.location.named.On-Prem\ Iron\ Example.privateKeyFile=~/.ssh/produser_id
 brooklyn.location.named.On-Prem\ Iron\ Example.privateKeyPassphrase=s3cr3tpassphrase
 {% endhighlight %}
 
+Alternatively, you can create a specific BYON location through the location wizard tool available within the web console.
+This location will be saved as a [catalog entry]({{ site.path.guide }}/ops/catalog/index.html#locations-in-catalog) for easy reusability.
+
 For more complex host configuration, one can define custom config values per machine. In the example 
 below, there will be two machines. The first will be a machine reachable on
 `ssh -i ~/.ssh/brooklyn.pem -p 8022 myuser@50.51.52.53`. The second is a windows machine, reachable 
diff --git a/guide/ops/locations/clouds.md b/guide/ops/locations/clouds.md
@@ -37,6 +37,10 @@ brooklyn.location.jclouds.aws-ec2.credential=s3cr3tsq1rr3ls3cr3tsq1rr3ls3cr3tsq1
 
 And in this case you can reference the location in YAML with `location: jclouds:aws-ec2`.
 
+Alternatively, you can use the location wizard tool available within the web console
+to create any cloud location supported by <a href="http://jclouds.org">Apache jclouds</a>.
+This location will be saved as a [catalog entry]({{ site.path.guide }}/ops/catalog/index.html#locations-in-catalog) for easy reusability.
+
 Brooklyn irons out many of the differences between clouds so that blueprints run similarly
 in a wide range of locations, including setting up access and configuring images and machine specs.
 The configuration options are described in more detail below.
diff --git a/guide/ops/locations/index.md b/guide/ops/locations/index.md
@@ -17,7 +17,8 @@ Brooklyn supports a wide range of locations:
   specifying already-existing hosts to use
 * And many others, including object stores and online services
 
-Configuration can be set in `~/.brooklyn/brooklyn.properties`
+Configuration can be set in `~/.brooklyn/brooklyn.properties`, through the
+location wizard tool available within the web console
 or directly in YAML when specifying a location.
 On some entities, config keys determining maching selection and provisioning behavior
 can also be set `in `provisioning.properties`.  
diff --git a/guide/ops/locations/localhost.md b/guide/ops/locations/localhost.md
@@ -17,6 +17,9 @@ brooklyn.location.localhost.privateKeyFile=~/.ssh/brooklyn_key
 brooklyn.location.localhost.privateKeyPassphrase=s3cr3tPASSPHRASE
 {% endhighlight %}
 
+Alternatively, you can create a specific localhost location through the location wizard tool available within the web console.
+This location will be saved as a [catalog entry]({{ site.path.guide }}/ops/catalog/index.html#locations-in-catalog) for easy reusability.
+
 If you encounter issues or for more information, see [SSH Keys Localhost Setup](ssh-keys.html#localhost-setup). 
 
 If you are normally prompted for a password when executing `sudo` commands, passwordless `sudo` must also be enabled.  To enable passwordless `sudo` for your account, a line must be added to the system `/etc/sudoers` file.  To edit the file, use the `visudo` command:
