You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@brooklyn.apache.org by he...@apache.org on 2017/11/17 11:29:57 UTC

[1/3] brooklyn-docs git commit: instructions for using a keypair in AWS

Repository: brooklyn-docs
Updated Branches:
  refs/heads/master 6c4d98ed1 -> d00c98a79


instructions for using a keypair in AWS


Project: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/commit/3306aae0
Tree: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/tree/3306aae0
Diff: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/diff/3306aae0

Branch: refs/heads/master
Commit: 3306aae0ba18d815a604e883e0faa952912ae2bb
Parents: 62cf36a
Author: Alex Heneveld <al...@cloudsoftcorp.com>
Authored: Wed Nov 15 17:10:36 2017 +0000
Committer: Alex Heneveld <al...@cloudsoftcorp.com>
Committed: Wed Nov 15 17:10:36 2017 +0000

----------------------------------------------------------------------
 guide/locations/_AWS.md | 45 ++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 45 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/3306aae0/guide/locations/_AWS.md
----------------------------------------------------------------------
diff --git a/guide/locations/_AWS.md b/guide/locations/_AWS.md
index 16cb88d..074adf0 100644
--- a/guide/locations/_AWS.md
+++ b/guide/locations/_AWS.md
@@ -43,6 +43,51 @@ Below are examples of configuration options that use values specific to AWS EC2:
   For example, `securityGroups: mygroup1` or `securityGroups: [ mygroup1, mygroup2 ]`.
 
 
+### Using a Registered Key Pair
+
+You can specify a `keyPair` to use for initial provisioning as a configuration option.
+If this is omitted, Brooklyn will use jclouds to create a new ad hoc key pair at AWS
+for that machine, and it will delete it afterwards.  This is usually seamless and
+occurs behind the scenes, with the post-provision user set up and configured as normal
+for all locations.  However if you are optimizing for creation of many machines,
+or you are using an image where keypair installation is not reliable (such as [some
+RightImages](https://issues.apache.org/jira/browse/JCLOUDS-1356)), then you may wish
+to use a registered key pair.
+
+First, in the AWS Console, open the EC2 service in the region you are interested in,
+then click "Key Pairs" at the left.  For `us-east-1`, the link is 
+[here](https://console.aws.amazon.com/ec2/v2/home?region=us-east-1#KeyPairs:sort=keyName).
+Click "Create Key Pair" (or "Import Key Pair" if you want to provide a public key) and
+follow the instructions.
+
+Then define your location as follows for `aws-us-east-1`.  Make sure to replace the
+`XXXX` sections with the key-pair name defined above and the corresponding private key data. 
+
+```yaml
+brooklyn.catalog:
+  version: "1.0"
+  itemType: location
+  items:
+  - id: aws-base
+    item:
+      type: jclouds:aws-ec2
+      brooklyn.config:
+        identity: XXXXXXXXXXXXXXXX
+        credential: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXx
+  - id: aws-us-east-1
+    item:
+      type: aws-base
+      region: us-east-1
+      keyPair: XXXXXXXXX
+      login.privateKeyData: |
+        -----BEGIN RSA PRIVATE KEY-----
+        XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+        XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+        XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+        -----END RSA PRIVATE KEY-----
+```
+
+
 ### Using Subnets and Security Groups
 
 Apache Brooklyn can run with AWS VPC and both public and private subnets.


[2/3] brooklyn-docs git commit: address PR comments, fix yaml

Posted by he...@apache.org.
address PR comments, fix yaml


Project: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/commit/3f3e41d6
Tree: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/tree/3f3e41d6
Diff: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/diff/3f3e41d6

Branch: refs/heads/master
Commit: 3f3e41d6d5253d2280617390ee5c75dabb72f3c4
Parents: 3306aae
Author: Alex Heneveld <al...@cloudsoftcorp.com>
Authored: Thu Nov 16 18:08:15 2017 +0000
Committer: Alex Heneveld <al...@cloudsoftcorp.com>
Committed: Thu Nov 16 18:08:15 2017 +0000

----------------------------------------------------------------------
 guide/locations/_AWS.md | 25 +++++++++++++------------
 1 file changed, 13 insertions(+), 12 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/3f3e41d6/guide/locations/_AWS.md
----------------------------------------------------------------------
diff --git a/guide/locations/_AWS.md b/guide/locations/_AWS.md
index 074adf0..070f2df 100644
--- a/guide/locations/_AWS.md
+++ b/guide/locations/_AWS.md
@@ -49,10 +49,10 @@ You can specify a `keyPair` to use for initial provisioning as a configuration o
 If this is omitted, Brooklyn will use jclouds to create a new ad hoc key pair at AWS
 for that machine, and it will delete it afterwards.  This is usually seamless and
 occurs behind the scenes, with the post-provision user set up and configured as normal
-for all locations.  However if you are optimizing for creation of many machines,
-or you are using an image where keypair installation is not reliable (such as [some
-RightImages](https://issues.apache.org/jira/browse/JCLOUDS-1356)), then you may wish
-to use a registered key pair.
+for all locations.  However using AWS heavily or optimizing creation, using a known
+key pairs can  
+[make some images](https://issues.apache.org/jira/browse/JCLOUDS-1356) more reliable
+and speed things up.
 
 First, in the AWS Console, open the EC2 service in the region you are interested in,
 then click "Key Pairs" at the left.  For `us-east-1`, the link is 
@@ -77,14 +77,15 @@ brooklyn.catalog:
   - id: aws-us-east-1
     item:
       type: aws-base
-      region: us-east-1
-      keyPair: XXXXXXXXX
-      login.privateKeyData: |
-        -----BEGIN RSA PRIVATE KEY-----
-        XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-        XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-        XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-        -----END RSA PRIVATE KEY-----
+      brooklyn.config:
+        region: us-east-1
+        keyPair: XXXXXXXXX
+        loginUser.privateKeyData: |
+          -----BEGIN RSA PRIVATE KEY-----
+          XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+          XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+          XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+          -----END RSA PRIVATE KEY-----
 ```
 
 


[3/3] brooklyn-docs git commit: This closes #237

Posted by he...@apache.org.
This closes #237


Project: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/commit/d00c98a7
Tree: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/tree/d00c98a7
Diff: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/diff/d00c98a7

Branch: refs/heads/master
Commit: d00c98a791851c5cea44df64d855e522d1b0784b
Parents: 6c4d98e 3f3e41d
Author: Alex Heneveld <al...@cloudsoftcorp.com>
Authored: Fri Nov 17 11:29:44 2017 +0000
Committer: Alex Heneveld <al...@cloudsoftcorp.com>
Committed: Fri Nov 17 11:29:44 2017 +0000

----------------------------------------------------------------------
 guide/locations/_AWS.md | 46 ++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 46 insertions(+)
----------------------------------------------------------------------