Issue opened as requested:
https://issues.apache.org/jira/browse/JCLOUDS-1096
I'll post a workaround here if I find a good one.
Ignasi Barrera je 21. 03. 2016 ob 12:17 napisal:
Well, jclouds will create key pairs based on the login credentials. If
you provide the "login private key" option, jc
Well, jclouds will create key pairs based on the login credentials. If
you provide the "login private key" option, jclouds will create a key
pair for it, if it still doesn't exist, and generate a unique name for
the key pair based on the group name (using the mentioned group naming
convention that
Since createNodesInGroup() accepts group name as a parameter am I
correct to assume that the current logic with key pairs and security
groups should be ignored in this case and the name provided should be
used as the group name?
Also, if I created security group and/or key together with the node,
w
Regarding the group names thing, jclouds tries to infer the group name
from the security groups and key pairs [1]. When key pairs or security
groups are (indirectly) created as part of the "createNodesInGroup"
call, jclouds applies the naming convention taking into account the
group name. The code
