Github user drigodwin commented on a diff in the pull request:

    https://github.com/apache/brooklyn-docs/pull/85#discussion_r69470183
  
    --- Diff: guide/ops/locations/_openstack.md ---
    @@ -0,0 +1,169 @@
    +---
    +section: Openstack
    +title: Openstack
    +section_type: inline
    +section_position: 6
    +---
    +
    +## Openstack
    +
    +### Apache jclouds
    +
    +Support for OpenStack is provided by Apache jclouds. For more information, 
see their guide
    +[here](https://jclouds.apache.org/guides/openstack/).
    +
    +
    +### Networks
    +
    +When multiple networks are available you should indicate which ones 
machines should join.
    +Do this by setting the desired values id as an option in the
    +**[templateOptions](#custom-template-options)** configuration:
    +
    +    location:
    +      jclouds:openstack-nova:
    +        ...
    +        templateOptions:
    +          # Assign the node to all networks in the list.
    +          networks:
    +          - network-one-id
    +          - network-two-id
    +          - ...
    +
    +
    +### Floating IPs
    +
    +Configuration of floating IPs is as networks; specify the pools to use as 
another
    +[template option](#custom-template-options):
    +
    +    location:
    +      jclouds:openstack-nova:
    +        ...
    +        templateOptions:
    +          # Pool names to use when allocating a floating IP
    +          floatingIpPoolNames:
    +          - "pool name"
    +
    +
    +### Basic Location Structure
    +
    +This is a basic inline YAML template for an OpenStack location:
    +
    +```
    +location:
    --- End diff --
    
    The format of this code block is incorrect, please indent it like the 
others or use [liquid 
tags](https://jekyllrb.com/docs/templates/#code-snippet-highlighting).


---
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.
---

Reply via email to