brooklyn-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sjcorb...@apache.org
Subject [1/7] incubator-brooklyn git commit: Update to /guide/ops/locations/index.md to simplify text by moving some detail to sub-page.
Date Mon, 26 Oct 2015 11:16:41 GMT
Repository: incubator-brooklyn
Updated Branches:
  refs/heads/master 9a441be8f -> 39653056d


Update to /guide/ops/locations/index.md to simplify text by moving some detail to sub-page.

Move section "AWS VPC issues which may affect users with older AWS accounts" to its own
page.  This was one of the observations from the First Encounter of the Belfast team.


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

Branch: refs/heads/master
Commit: c9bc03ca7a86f2b3019c8d1d3ccbf5f340674adc
Parents: 5fda6ed
Author: Geoff Macartney <geoff.macartney@cloudsoftcorp.com>
Authored: Mon Oct 19 17:59:57 2015 +0100
Committer: Geoff Macartney <geoff.macartney@cloudsoftcorp.com>
Committed: Mon Oct 19 17:59:57 2015 +0100

----------------------------------------------------------------------
 docs/guide/ops/locations/index.md      | 31 +---------------------------
 docs/guide/ops/locations/vpc-issues.md | 32 +++++++++++++++++++++++++++++
 2 files changed, 33 insertions(+), 30 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/blob/c9bc03ca/docs/guide/ops/locations/index.md
----------------------------------------------------------------------
diff --git a/docs/guide/ops/locations/index.md b/docs/guide/ops/locations/index.md
index 6cb5ec3..db3cbd1 100644
--- a/docs/guide/ops/locations/index.md
+++ b/docs/guide/ops/locations/index.md
@@ -254,40 +254,11 @@ If the method call cannot be matched to the template options available
- for exa
 specific option but your location is an OpenStack cloud - then a warning is logged and the
option is ignored.
 
 
-### AWS VPC issues which may affect users with older AWS accounts
 
-AWS now has different default behaviour depending on the age of your AWS account and whether
you used the target region before, or during, 2013.
-In this case VM provisioning may fail with an error like:
-
-{% highlight text %}
-
-Detected that your EC2 account is a legacy 'classic' account, but the recommended instance
type requires VPC. 
-You can specify the 'eu-central-1' region to avoid this problem, or you can specify a classic-compatible
instance type, 
-or you can specify a subnet to use with 'networkName' 
-taking care that the subnet auto-assigns public IP's and allows ingress on all ports, 
-as Brooklyn does not currently configure security groups for non-default VPC's; 
-or setting up Brooklyn to be in the subnet or have a jump host or other subnet access configuration).

-For more information on VPC vs classic see http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-vpc.html.
-
-{% endhighlight %}
-
-Specifically, there are issues with the certain AMIs and instance types.  If these are specified
or a recommended 
-by brooklyn then you may see the above error. There are a few options for fixing this:
-
-- specify a different region which does not support EC2-classic.  
-  You can check this on the AWS console under "Supported Platforms.
-  Frankfurt (eu-central-1) is guaranteed to be VPC only.
-  
-- specify an instance type that is compatible with ec2-classic.  
-  Instance types C4, M4, T2 are only supported in VPC so should not be used.
-  This is described [here](index.html#vm-creation)
-    
-- create a subnet to use with the instance. Ensure that the subnet is set to auto-assign
public IPs
-  and allows ingress on all ports.  Brooklyn cannot currently do this for you.
-  Use the networkName parameter to specify this value in your blueprint.
   
 See the following resources for more information:
 
+- [AWS VPC issues which may affect users with older AWS accounts](vpc-issues.html)
 - [Amazon EC2 and Amazon Virtual Private Cloud](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-vpc.html#vpc-only-instance-types)
 - [Your Default VPC and Subnets](http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/default-vpc.html)
 - [Amazon VPC FAQs](http://aws.amazon.com/vpc/faqs/#Default_VPCs)

http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/blob/c9bc03ca/docs/guide/ops/locations/vpc-issues.md
----------------------------------------------------------------------
diff --git a/docs/guide/ops/locations/vpc-issues.md b/docs/guide/ops/locations/vpc-issues.md
new file mode 100644
index 0000000..b2b362b
--- /dev/null
+++ b/docs/guide/ops/locations/vpc-issues.md
@@ -0,0 +1,32 @@
+
+### AWS VPC issues which may affect users with older AWS accounts
+
+AWS now has different default behaviour depending on the age of your AWS account and whether
you used the target region before, or during, 2013.
+In this case VM provisioning may fail with an error like:
+
+{% highlight text %}
+
+Detected that your EC2 account is a legacy 'classic' account, but the recommended instance
type requires VPC. 
+You can specify the 'eu-central-1' region to avoid this problem, or you can specify a classic-compatible
instance type, 
+or you can specify a subnet to use with 'networkName' 
+taking care that the subnet auto-assigns public IP's and allows ingress on all ports, 
+as Brooklyn does not currently configure security groups for non-default VPC's; 
+or setting up Brooklyn to be in the subnet or have a jump host or other subnet access configuration).

+For more information on VPC vs classic see http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-vpc.html.
+
+{% endhighlight %}
+
+Specifically, there are issues with the certain AMIs and instance types.  If these are specified
or a recommended 
+by brooklyn then you may see the above error. There are a few options for fixing this:
+
+- specify a different region which does not support EC2-classic.  
+  You can check this on the AWS console under "Supported Platforms.
+  Frankfurt (eu-central-1) is guaranteed to be VPC only.
+  
+- specify an instance type that is compatible with ec2-classic.  
+  Instance types C4, M4, T2 are only supported in VPC so should not be used.
+  This is described [here](index.html#vm-creation)
+    
+- create a subnet to use with the instance. Ensure that the subnet is set to auto-assign
public IPs
+  and allows ingress on all ports.  Brooklyn cannot currently do this for you.
+  Use the networkName parameter to specify this value in your blueprint.
\ No newline at end of file


Mime
View raw message