You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltacloud.apache.org by "Joseph J. VLcek (JIRA)" <ji...@apache.org> on 2013/03/11 20:45:14 UTC

[jira] [Commented] (DTACLOUD-487) Keypair support for ovirt backend

    [ https://issues.apache.org/jira/browse/DTACLOUD-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599187#comment-13599187 ] 

Joseph J. VLcek commented on DTACLOUD-487:
------------------------------------------

Currently RHEV does not support keypair injection, consequently it is not available for deltacloud to expose.
I am researching what plans, if any, there may be to add this feature to RHEV.

In the interim one possibility could be to explore having Deltacloud locally track keypairs and allowing for the
injection of the public key via cdrom of floppy device, as is done by deltacloud for userdata, but to have it land
in the instance in a different file so as not to conflict with the user data. This approach would require some
software to be built into the instance that would pick up the injected data and make it available as an ssh
public key.

Does the Author of this Jira have any thoughts/comments?
                
> Keypair support for ovirt backend
> ---------------------------------
>
>                 Key: DTACLOUD-487
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-487
>             Project: DeltaCloud
>          Issue Type: Improvement
>          Components: Server
>            Reporter: Ian Main
>            Assignee: Joseph J. VLcek
>              Labels: keypair, ovirt
>
> I had a chat with mfojtik in IRC about being able to add keypair support to ovirt.  He felt we could add a hook that would allow us to inject a keypair into the instance on startup.  I do not know enough about ovirt yet to know how this would work but I wanted to document this.  Lack of keypair support is a major obstacle for heat integration with deltacloud+ovirt.

--
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