Inject SSH keys into the docker container

[OpenStack Infra]

https://review.openstack.org/132291

Dear documentation bug triager. This bug was created here because we did not know how to map the project name "stackforge/nova-docker" to a launchpad project name. This indicates that the notify_impact config needs tweaks. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

commit 9f5930dfb2e8c35d069a8b3b1d2aa716d9be86e4
Author: Davanum Srinivas <email address hidden>
Date: Fri Oct 31 10:54:46 2014 -0400

    Inject SSH keys into the docker container

    Create a directory for .ssh, create a authorized_keys file with
    the correct permissions, then bind mount the .ssh directory when
    we start the container. This enables anyone to create a ssh
    key-pair in nova specify it in the nova boot command. This is
    an alternative mechanism modeled after libvirt's inject_key
    flag for environments that don't have metadata service (and
    since we don't have config drive support).

    DocImpact

    Change-Id: I71f87e9da62eee73a641d20be6bd6cafce4c0f3d

[Lana (loquacity)]

Related: https://bugs.launchpad.net/openstack-manuals/+bug/1398217

[Stephen Gordon (sgordon)]

The docker driver isn't part of the release.