Github user ahgittin commented on the pull request:
https://github.com/apache/incubator-brooklyn/pull/705#issuecomment-114372985
Got to the bottom of it:
* `networkName` sets `TemplateOptions.networks(...)` which it looks like is
only supported for CloudStack and OpenStack. @andreaturli can you confirm?
i've mapped this to `subnetId` for AWS, and log warning in SoftLayer. we might
want other warnings in future.
* the `not available after creating` message appears to be a very
occasional race behaviour; on a retry it was fine. I've upped the timeout in
hopes of reducing it.
* however for *non-default* VPC's (i.e. if you set `networkId: subnet-ID`)
jclouds does not set up security groups, so that suggestion now says to
configure the default security group for that VPC to allow all the access you
want. not ideal, but advanced-networking is wanted when working with this so
we can live ith it.
the message for "classic" users who get the VPC error now says:
LOG.error("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.";);
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
