Open aledsage opened 8 years ago
Odd, because ::/0
is a valid CIDR, but for IPV6. The equivalent of 0.0.0.0/0
for IPV4. OpenStack supports the syntax (at least in the Horizon UI, I'm sure) but it's what you get in the default set of rules for a security group.
@grkvlt I'm still seeing this with a build of brooklyn/advanced-networking from master and the #272 pr of clocker. I've specified the security group in my location and would have expected that to be used instead of having to specify the docker.host.securityGroup
property but still see the JcloudsLocationSecurityGroupCustomizer
being invoked and a new default security group being created.
We always add the customizer, it should be optional, yes
Partially addressed this in https://github.com/brooklyncentral/clocker/pull/272/commits/d88341abb0ab1334666289a85b3c64e484d996cf in #272 which will use the securityGroup in the location if present and a String
.
Still need to sort out handling for the IPv6 wildcards.
Not sure whether to report this again jclouds, Brooklyn or Clocker (so reporting it here for now)! I'll likely cross-post on jclouds jira.
When launching
docker-cloud-weave
to OpenStack (BlueBox), without specifying a security group anywhere, it gave the error below. This prevented it from creating any VMs.