brooklyn-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From henev...@apache.org
Subject [26/51] [abbrv] brooklyn-docs git commit: tidy for GCE, in response to issues encountered
Date Mon, 01 Feb 2016 17:44:52 GMT
tidy for GCE, in response to issues encountered


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

Branch: refs/heads/0.8.0-incubating
Commit: 637928b1ddf15edaadac6b712e68bfd2cd08f30e
Parents: 7da046c
Author: Alex Heneveld <alex.heneveld@cloudsoftcorp.com>
Authored: Sat Aug 29 02:50:23 2015 +0100
Committer: Alex Heneveld <alex.heneveld@cloudsoftcorp.com>
Committed: Sat Aug 29 03:52:21 2015 +0100

----------------------------------------------------------------------
 docs/guide/start/brooklyn.properties | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/637928b1/docs/guide/start/brooklyn.properties
----------------------------------------------------------------------
diff --git a/docs/guide/start/brooklyn.properties b/docs/guide/start/brooklyn.properties
index 2d6682f..0858f94 100644
--- a/docs/guide/start/brooklyn.properties
+++ b/docs/guide/start/brooklyn.properties
@@ -152,10 +152,10 @@ brooklyn.location.named.aws-ireland = jclouds:aws-ec2:eu-west-1
 brooklyn.location.named.aws-tokyo = jclouds:aws-ec2:ap-northeast-1
 
 ## Google Compute
-## Note at present you have to create and download the P12 key from the Google "APIs &
auth -> Registered Apps" interface,
-## then convert to PEM private key format using  `openssl pkcs12 -in Certificates.p12 -out
Certificates.pem -nodes`
-## then embed that on one line as the 'credential, replacing new lines with \n as below
-## (hopefully this will be improved in jclouds in the future)
+## The credentials for GCE come from the "APIs & auth -> Credentials" page,
+## creating a "Service Account" of type JSON, then extracting 
+## the client_email as the identity and private_key as the identity,
+## keeping new lines as \n (exactly as in the JSON supplied)
 # brooklyn.location.jclouds.google-compute-engine.identity=1234567890-somet1mesArand0mU1Dhere@developer.gserviceaccount.com
 # brooklyn.location.jclouds.google-compute-engine.credential=-----BEGIN PRIVATE KEY-----
\nMIIblahablahblah \nblahblahblah \n-----END PRIVATE KEY-----
 # brooklyn.location.named.Google\ US = jclouds:google-compute-engine
@@ -169,7 +169,7 @@ brooklyn.location.named.aws-tokyo = jclouds:aws-ec2:ap-northeast-1
 # brooklyn.location.jclouds.google-compute-engine.networkName=brooklyn-default-network
 ## gce images have bad entropy, this ensures they have noisy /dev/random (even if the "randomness"
is not quite as random)
 # brooklyn.location.jclouds.google-compute-engine.installDevUrandom=true
-## gce images often start with iptables turned on; turn it off 
+## gce images often start with iptables turned on; turn it off unless your blueprints are
iptables-aware 
 # brooklyn.location.jclouds.google-compute-engine.stopIptables=true
 
 ## HP Cloud - also Ubuntu 12.04 LTS


Mime
View raw message