You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by mikezaccardo <gi...@git.apache.org> on 2016/06/27 09:44:55 UTC
[GitHub] brooklyn-docs pull request #81: Expand OpenStack location docs
GitHub user mikezaccardo opened a pull request:
https://github.com/apache/brooklyn-docs/pull/81
Expand OpenStack location docs
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mikezaccardo/brooklyn-docs openstack-location-doc
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-docs/pull/81.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #81
----
commit 8ed3108f065514fdeaed35a9126a567d17770cbe
Author: Mike Zaccardo <mi...@cloudsoftcorp.com>
Date: 2016-06-27T09:44:14Z
Expand OpenStack location docs
----
---
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.
---
[GitHub] brooklyn-docs pull request #81: Expand OpenStack location docs
Posted by drigodwin <gi...@git.apache.org>.
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.
---
[GitHub] brooklyn-docs pull request #81: Expand OpenStack location docs
Posted by mikezaccardo <gi...@git.apache.org>.
Github user mikezaccardo commented on a diff in the pull request:
https://github.com/apache/brooklyn-docs/pull/81#discussion_r68629195
--- 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 --
Done
---
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.
---
[GitHub] brooklyn-docs pull request #81: Expand OpenStack location docs
Posted by andreaturli <gi...@git.apache.org>.
Github user andreaturli commented on a diff in the pull request:
https://github.com/apache/brooklyn-docs/pull/81#discussion_r68553079
--- 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"
--- End diff --
with `jclouds.openstack-nova.auto-generate-keypairs: false` then you may want to specify a `keyPairName` otherwise keyPairName is optional. We should find a better way to make it explicit
---
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.
---
[GitHub] brooklyn-docs issue #81: Expand OpenStack location docs
Posted by ahgittin <gi...@git.apache.org>.
Github user ahgittin commented on the issue:
https://github.com/apache/brooklyn-docs/pull/81
looks good - we don't host a JAR afaik so instructions are okay; new jclouds should fix
---
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.
---
[GitHub] brooklyn-docs pull request #81: Expand OpenStack location docs
Posted by andreaturli <gi...@git.apache.org>.
Github user andreaturli commented on a diff in the pull request:
https://github.com/apache/brooklyn-docs/pull/81#discussion_r68552950
--- 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
--- End diff --
imageId, hardwareId, loginUser* are optional
---
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.
---
[GitHub] brooklyn-docs pull request #81: Expand OpenStack location docs
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/brooklyn-docs/pull/81
---
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.
---
[GitHub] brooklyn-docs pull request #81: Expand OpenStack location docs
Posted by mikezaccardo <gi...@git.apache.org>.
Github user mikezaccardo commented on a diff in the pull request:
https://github.com/apache/brooklyn-docs/pull/81#discussion_r68629206
--- 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 |
++-----+-----------+-----------+------+
+```
+
+
### Other features
Consult jclouds' [Nova template options](https://jclouds.apache.org/reference/javadoc/1.9.x/org/jclouds/openstack/nova/v2_0/compute/options/NovaTemplateOptions.html)
for futher options when configuring Openstack locations.
+
+### Troubleshooting
+
+#### jclouds Namespace Issue
+
+A change to Nova's API resulted in all extensions having the same "fake" namespace which
+the current version of jclouds does not yet support.
+
+If you are having problems deploying to OpenStack, consult your Brooklyn debug log and
+look for the following:
+
+```
+"namespace": "http://docs.openstack.org/compute/ext/fake_xml"
+```
+
+If this appears, perform the following steps as a workaround:
+
+* Generate a patch JAR `openstack-devtest-compute-1.9.2.jar`
+by building: https://github.com/cloudsoft/jclouds-openstack-devtest
+* Copy the patch JAR into $BROOKLYN_HOME/lib/patch
+* Change `jclouds:openstack-nova` to `jclouds:openstack-devtest-compute` in your location
+configuration
--- End diff --
Done
---
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.
---
[GitHub] brooklyn-docs pull request #81: Expand OpenStack location docs
Posted by mikezaccardo <gi...@git.apache.org>.
Github user mikezaccardo commented on a diff in the pull request:
https://github.com/apache/brooklyn-docs/pull/81#discussion_r68629570
--- Diff: guide/ops/locations/_more-clouds.md ---
@@ -300,7 +306,124 @@ 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, hardwareId, and loginUser* are optional
+ 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']
+
+ # Optional if 'jclouds.openstack-nova.auto-generate-keypairs' is assigned to 'true'
+ 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
+```
+
+Chose a value of `your-flavor-id` from one of the defaults, or create your own flavor if
+you have administrator privileges.
+For for more information, see the
+[OpenStack flavors guide](http://docs.openstack.org/admin-guide/cli_manage_flavors.html).
+
+The default flavors are:
+
+```
++-----+-----------+-----------+------+
+| 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 |
++-----+-----------+-----------+------+
+```
+
+For an even more detailed example location configuration, consult the
+[template properties file](https://brooklyn.apache.org/v/latest/start/brooklyn.properties).
+
+
### Other features
Consult jclouds' [Nova template options](https://jclouds.apache.org/reference/javadoc/1.9.x/org/jclouds/openstack/nova/v2_0/compute/options/NovaTemplateOptions.html)
for futher options when configuring Openstack locations.
+
+### Troubleshooting
+
+#### jclouds Namespace Issue
+
+A change to Nova's API resulted in all extensions having the same "fake" namespace which
+the current version of jclouds does not yet support.
+
+If you are having problems deploying to OpenStack, consult your Brooklyn debug log and
+look for the following:
+
+```
+"namespace": "http://docs.openstack.org/compute/ext/fake_xml"
+```
+
+If this appears, perform the following steps as a workaround:
+
+* Generate a patch JAR `openstack-devtest-compute-1.9.2.jar`
--- End diff --
Is this JAR hosted somewhere? Probably better to offer a download link vs. asking users to build it themselves.
---
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.
---
[GitHub] brooklyn-docs pull request #81: Expand OpenStack location docs
Posted by andreaturli <gi...@git.apache.org>.
Github user andreaturli commented on a diff in the pull request:
https://github.com/apache/brooklyn-docs/pull/81#discussion_r68553089
--- 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 |
++-----+-----------+-----------+------+
+```
+
+
### Other features
Consult jclouds' [Nova template options](https://jclouds.apache.org/reference/javadoc/1.9.x/org/jclouds/openstack/nova/v2_0/compute/options/NovaTemplateOptions.html)
for futher options when configuring Openstack locations.
+
+### Troubleshooting
+
+#### jclouds Namespace Issue
+
+A change to Nova's API resulted in all extensions having the same "fake" namespace which
+the current version of jclouds does not yet support.
+
+If you are having problems deploying to OpenStack, consult your Brooklyn debug log and
+look for the following:
+
+```
+"namespace": "http://docs.openstack.org/compute/ext/fake_xml"
+```
+
+If this appears, perform the following steps as a workaround:
+
+* Generate a patch JAR `openstack-devtest-compute-1.9.2.jar`
+by building: https://github.com/cloudsoft/jclouds-openstack-devtest
+* Copy the patch JAR into $BROOKLYN_HOME/lib/patch
+* Change `jclouds:openstack-nova` to `jclouds:openstack-devtest-compute` in your location
+configuration
--- End diff --
I'd probably suggest a complete yaml like
```
location:
jclouds:openstack-devtest-compute:
endpoint: http://x.x.x.x:5000/v2.0/
identity: "my-tenant:my-username"
credential: my-password
templateOptions:
networks: [ "network-id" ]
floatingIpPoolNames: [ "name-of-my-floatingIp-pool" ]
```
Notice this will set by default
```
jclouds.keystone.credential-type=passwordCredentials
jclouds.openstack-nova.auto-generate-keypairs: true
jclouds.openstack-nova.auto-create-floating-ips: true
```
---
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.
---
[GitHub] brooklyn-docs pull request #81: Expand OpenStack location docs
Posted by alrick87 <gi...@git.apache.org>.
Github user alrick87 commented on a diff in the pull request:
https://github.com/apache/brooklyn-docs/pull/81#discussion_r68573798
--- 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 --
Admin user can create custom flavors, the ones listed above are the default ones.
---
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.
---