Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@brooklyn.apache.org
From: drigodwin <git@git.apache.org>
To: dev@brooklyn.apache.org
Reply-To: dev@brooklyn.apache.org
References: <git-pr-81-brooklyn-docs@git.apache.org>
In-Reply-To: <git-pr-81-brooklyn-docs@git.apache.org>
Subject: [GitHub] brooklyn-docs pull request #81: Expand OpenStack location docs
Content-Type: text/plain
Message-Id: <20160627101815.0E709DFDC3@git1-us-west.apache.org>
Date: Mon, 27 Jun 2016 10:18:15 +0000 (UTC)
archived-at: Mon, 27 Jun 2016 10:18:17 -0000

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

    https://github.com/apache/brooklyn-docs/pull/81#discussion_r68552982
  
    --- Diff: guide/ops/locations/_more-clouds.md ---
    @@ -300,7 +306,94 @@ Configuration of floating IPs is as networks; specify the pools to use as anothe
               - "pool name"
     
     
    +### Basic Location Structure
    +
    +This is a basic inline YAML template for an OpenStack location:
    +
    +```
    +location:
    +  jclouds:clouds:openstack-nova:
    +    endpoint: http://x.x.x.x:5000/v2.0/
    +    identity: "your-tenant:your-username"
    +    credential: your-password
    +
    +    imageId: your-region-name/your-image-id
    +    hardwareId: your-region-name/your-flavor-id
    +    loginUser: 'ubuntu'
    +    loginUser.privateKeyFile: /path/to/your/privatekey
    +    jclouds.openstack-nova.auto-generate-keypairs: false
    +    jclouds.openstack-nova.auto-create-floating-ips: true
    +
    +    templateOptions:
    +      networks: [ "your-network-id" ]
    +      floatingIpPoolNames: [ "your-floatingIp-pool" ]
    +      securityGroups: ['your-security-group']
    +      keyPairName: "your-keypair"
    +```
    +
    +This is the same OpenStack location in a format that can be added to your
    +`brooklyn.properties` file:
    +
    +```
    +brooklyn.location.named.My\ Openstack=jclouds:openstack-nova:http://x.x.x.x:5000/v2.0/
    +brooklyn.location.named.My\ OpenStack.identity=your-tenant:your-username
    +brooklyn.location.named.My\ OpenStack.credential=your-password
    +brooklyn.location.named.My\ OpenStack.endpoint=http://x.x.x.x:5000/v2.0/
    +
    +brooklyn.location.named.My\ OpenStack.imageId=your-region-name/your-image-id
    +brooklyn.location.named.My\ OpenStack.hardwareId=your-region-name/your-flavor-id
    +brooklyn.location.named.My\ OpenStack.loginUser=ubuntu
    +brooklyn.location.named.My\ OpenStack.loginUser.privateKeyFile=/path/to/your/privatekey
    +brooklyn.location.named.My\ OpenStack.openstack-nova.auto-generate-keypairs=false
    +brooklyn.location.named.My\ OpenStack.openstack-nova.auto-create-floating-ips=true
    +
    +brooklyn.location.named.My\ OpenStack.networks=your-network-id
    +brooklyn.location.named.My\ OpenStack.floatingIpPoolNames=your-floatingIp-pool
    +brooklyn.location.named.My\ OpenStack.securityGroups=your-security-group
    +brooklyn.location.named.My\ OpenStack.keyPair=your-keypair
    +```
    +
    +For an even more detailed example location configuration, consult the
    +[template properties file](https://brooklyn.apache.org/v/latest/start/brooklyn.properties).
    +
    +`my-flavor-id` can be chosen from the following options:
    +
    +```
    ++-----+-----------+-----------+------+
    +| ID  | Name      | Memory_MB | Disk |
    ++-----+-----------+-----------+------+
    +| 1   | m1.tiny   | 512       | 1    |
    +| 2   | m1.small  | 2048      | 20   |
    +| 3   | m1.medium | 4096      | 40   |
    +| 4   | m1.large  | 8192      | 80   |
    +| 5   | m1.xlarge | 16384     | 160  |
    ++-----+-----------+-----------+------+
    +```
    +
    --- End diff --
    
    Perhaps mention flavors are configured per openstack instance and link out to the [openstack docs](http://docs.openstack.org/admin-guide/cli_manage_flavors.html)?


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---