Github user drigodwin commented on a diff in the pull request:
https://github.com/apache/brooklyn-docs/pull/98#discussion_r73153896
--- Diff: guide/ops/locations/index.md ---
@@ -6,21 +6,13 @@ children:
check_directory_for_children: true
---
-Locations are the environments to which Brooklyn deploys applications,
including:
+Locations are the environments to which Brooklyn deploys applications.
Most commonly these
+are cloud services such as AWS, GCE, and IBM Softlayer. Brooklyn also
supports deploying
+to a pre-provisioned network or to localhost (primarily useful for testing
blueprints).
-Brooklyn supports a wide range of locations:
-
-* <a href="#clouds">Clouds</a>, where it will provision machines
-* <a href="#localhost">Localhost</a> (e.g. your laptop),
- where it will deploy via `ssh` to `localhost` for rapid testing
-* <a href="#byon">BYON</a>, where you "bring your own nodes",
- specifying already-existing hosts to use
-* And many others, including object stores and online services
-
-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 matching selection and
provisioning behavior
-can also be set in `provisioning.properties`.
+Also see the [Locations yaml guide]({{ site.path.guide
}}/yaml/setting-locations.html),
+use within an entity of [provisioning.properties]({{ site.path.guide
}}/yaml/entity-configuration.html#entity-provisioningproperties-overriding-and-merging),
+how to add location definitions to the [Catalog]({{ site.path.guide
}}/ops/catalog/),
+and how to use [Externalized Configuration](({{ site.path.guide
}}/ops/externalized-configuration.html).
--- End diff --
This link has one too many opening parentheses
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
