[
https://issues.apache.org/jira/browse/JCLOUDS-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680294#comment-13680294
]
TangYong commented on JCLOUDS-120:
----------------------------------
This issue is fatal while using pallet to auto-provisioning openstack node.
While I talked with pallet team's Antoni, he said:
"
A better fix would be to have compute2.clj discover the template options
dynamically via reflection (as opposed to having these options hardcoded), as
it seems like compute2 is not always being kept up-to-date when a new option is
added on any of the providers. Not sure if it's possible at this point though...
"
Tang
> Having no way to set keyPairName while using pallet to start openstack node
> ---------------------------------------------------------------------------
>
> Key: JCLOUDS-120
> URL: https://issues.apache.org/jira/browse/JCLOUDS-120
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-compute
> Affects Versions: 1.5.10, 1.6.0
> Environment: 1 Openstack Essex
> 2 Pallet 0.7.3
> 3 Ubuntu
> Reporter: TangYong
> Priority: Critical
> Fix For: 1.7.0
>
> Attachments: computer2.clj.patch
>
>
> a bug from org.jclouds.compute2.clj (jclouds-compute-xxx.jar)
> Needing to add "key-pair-name" into org.jclouds.compute2.clj
> Otherwize, the following will failed
> (use '[pallet.crate.automated-admin-user :only [automated-admin-user]])
> (pallet.core/converge
> (pallet.core/group-spec "pallet-tang"
> :count 1
> :node-spec (pallet.core/node-spec
> :image {:os-family :ubuntu :image-id
> "RegionOne/7cf21d93-d04a-4fb4-a09b-f546a9461726" :key-pair-name "key2"})
> :phases {:bootstrap automated-admin-user})
> :compute (pallet.configure/compute-service :openstack))
> Because
> org.jclouds.openstack.nova.v2_0.compute.options.NovaTemplateOptions has
> a method called "keyPairName(String)" and this method is used for
> setting "--key_name" option.
> Currently, only having the following:
> (make-option-map
> kw-memfn-1arg
> [;; RunScriptOptions
> :override-login-credentials
> :override-login-user
> :override-login-password :override-login-private-key
> :override-authenticate-sudo
>
> :name-task :run-as-root :wrap-in-init-script :block-on-complete
> :block-on-port
> ;; TemplateOptions
> :run-script :install-private-key :authorize-public-key :tags
> ;; cloudstack
> :security-group-id :network-id :network-ids :setup-static-nat
> :ip-on-default-network :ips-to-networks
> ;; ec2
> :security-groups :user-data :block-device-mappings
> :unmap-device-named
> ;; cloudstack ec2
> :key-pair
> ;; aws-ec2
> :placement-group :subnet-id :spot-price :spot-options
> ;; cloudstack aws-ec2
> :security-group-ids
> ;; softlayer
> :domain-name
> ;; trmk-ecloud trmk-vcloudexpress
> :ssh-key-fingerprint
> ;; vcloud
> :description :customization-script :ip-address-allocation-mode])
> (make-option-map
> ...
> Among them, key-pair is not right method name while mapping into
> org.jclouds.openstack.nova.v2_0.compute.options.NovaTemplateOptions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
