[
https://issues.apache.org/jira/browse/DTACLOUD-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599504#comment-13599504
]
David Lutterkort commented on DTACLOUD-487:
-------------------------------------------
Just to be clear: what we can do shortterm from the DC side is adding another
parameter to the create_instance request (say ssh_key) that we would then put
on the virtual floppy in a separate file. From DC's point of view this would be
purely passthrough - the API user would be expected to make sure that the
ssh_key param is set to something sensible, and that the instance is
instrumented to pick the key up from the virtual floppy and put it into the
right place (presumably, /root/.ssh/authorized_keys)
More comprehensive solutions would require that ovirt adds ssh key mgmt
> 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
