You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltacloud.apache.org by "Ronelle Landy (JIRA)" <ji...@apache.org> on 2012/05/03 22:06:49 UTC
[jira] [Updated] (DTACLOUD-205) "Permission denied" when ssh'ing to
an Openstack instance - launched through Deltacloud (no way to pass a
keypair in the current API)
[ https://issues.apache.org/jira/browse/DTACLOUD-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ronelle Landy updated DTACLOUD-205:
-----------------------------------
Summary: "Permission denied" when ssh'ing to an Openstack instance - launched through Deltacloud (no way to pass a keypair in the current API) (was: "Permission denied" when ssh'ing to an Openstack instance - launched through Deltacloud)
The HP Openstack interface allows users to allocate ip addresses and work with keys. Are these collections going to be added to the Deltacloud driver?
Answer from Marios:
These aren't part of the 'standard' Openstack API (see http://docs.openstack.org/api/openstack-compute/2/content/API_Operations-d1e2068.html - no mention of IP address or key pair management). We need to figure out how to deal with these. Ultimately involves extending the Openstack gem.
> "Permission denied" when ssh'ing to an Openstack instance - launched through Deltacloud (no way to pass a keypair in the current API)
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-205
> URL: https://issues.apache.org/jira/browse/DTACLOUD-205
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: Deltacloud git commit version: c13da7b50bbbbdc529b42207f58dbe5099006ad1
> RHEL 6.2
> Openstack V2.0
> Reporter: Ronelle Landy
> Assignee: Marios Andreou
>
> I receive a "permission denied" error when ssh'ing into an instance launched through Deltacloud to my Openstack account : "Permission denied (publickey,gssapi-keyex,gssapi-with-mic)." I used the public ip address to ssh to the instance.
> When the instance was in a pending state, there was a password visible. Once the instance went to a RUNNING state, the password disappeared. Is it possible to pass a key pair?
> Answer from Marios:
> In the HP implementation, by default, password authentication seems to be disabled and you have to use a keypair. HOWEVER, the openstack API doesn't provide a way for passing 'key_pair' parameter into an instance during creation. Referencing API doc: (no mention of key_pair parameter under server creation at http://api-docs.hpcloud.com/hpcloud-compute/1.0/content/ch03s01s02.html ). Digging a little deeper I noticed this http://api-docs.hpcloud.com/hpcloud-compute/1.0/content/key-pairs.html and one of the examples shows a 'key_pair' parameter passed in.
> This is another jira issue - not because of something we can fix directly in the deltacloud code - but rather try and get this functionality into the oOpenstack gem (i.e. accept key_pair parameter and pass onto provider, and also key_pair management)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira