Prompted by JCLOUDS-120 [1], I was wondering about the different approaches taken by the EC2 and Nova providers for the same (?) option:

EC2: "keyPair" (or null to have a key pair generated) [2]
Nova: "keyPairName" and "generateKeyPair" [3]

Any idea where the divergence came from? Just accidental, or intentional?

Regarding JCLOUDS-120, would it be a good idea to auto-map the ":key-pair" argument to keyPairName for Nova, or does it make more sense to introduce ":key-pair-name" for consistency?

Thanks!

ap

[1] https://issues.apache.org/jira/browse/JCLOUDS-120
[2] http://javadocs.jclouds.cloudbees.net/org/jclouds/ec2/compute/options/EC2TemplateOptions.html#getKeyPair() [3] http://javadocs.jclouds.cloudbees.net/org/jclouds/openstack/nova/v2_0/compute/options/NovaTemplateOptions.html

Reply via email to