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

    https://github.com/apache/brooklyn-docs/pull/98#discussion_r73162281
  
    --- Diff: guide/ops/locations/_openstack.md ---
    @@ -1,18 +1,66 @@
     ---
    -section: Openstack
    -title: Openstack
    +section: OpenStack
    +title: OpenStack
     section_type: inline
     section_position: 6
     ---
     
    -## Openstack
    +## OpenStack
     
     ### Apache jclouds
     
     Support for OpenStack is provided by Apache jclouds. For more information, 
see their guide
     [here](https://jclouds.apache.org/guides/openstack/).
     
     
    +### Connection Details
    +
    +The endpoint URI is that of keystone (normally on port 5000).
    +
    +The identity normally consists of the tenant and username, 
colons-separated. The credential is 
    +the password. For example:
    +
    +    location:
    +      jclouds:openstack-nova:
    +        endpoint: http://x.x.x.x:5000/v2.0/
    +        identity: "your-tenant:your-username"
    +        credential: your-password
    +
    +OpenStack Nova access information can be downloaded from the openstack web 
interface, for example 
    +as an openrc.sh file. This file will normally contain the identity and 
credential.
    +
    +
    +### Common Configuration Options
    +
    +Below are examples of configuration options that use values specific to 
OpenStack environments:
    +
    +* The `imageId` is the id of an image. For example,
    +  `imageId: RegionOne/08086159-8b0b-4970-b332-a7a929ee601f`.
    +  These ids can be found from the the CLI or the web-console, for example 
in IBM Blue Box, 
    --- End diff --
    
    not sure it is a good example as it is not a "public" cloud


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