OpenStack (nova boot exactly) allows only one SSH key.

[rozie]

ii nova-api 1:2015.1.1-0ubuntu1~cloud2 all OpenStack Compute - API frontend
ii nova-cert 1:2015.1.1-0ubuntu1~cloud2 all OpenStack Compute - certificate management
ii nova-common 1:2015.1.1-0ubuntu1~cloud2 all OpenStack Compute - common files
ii nova-conductor 1:2015.1.1-0ubuntu1~cloud2 all OpenStack Compute - conductor service
ii nova-consoleauth 1:2015.1.1-0ubuntu1~cloud2 all OpenStack Compute - Console Authenticator
ii nova-novncproxy 1:2015.1.1-0ubuntu1~cloud2 all OpenStack Compute - NoVNC proxy
ii nova-scheduler 1:2015.1.1-0ubuntu1~cloud2 all OpenStack Compute - virtual machine scheduler
ii python-nova 1:2015.1.1-0ubuntu1~cloud2 all OpenStack Compute Python libraries
ii python-novaclient 1:2.22.0-0ubuntu1~cloud0 all client library for OpenStack Compute API

Problem was described at https://ask.openstack.org/en/question/82224/is-it-possible-to-create-instance-with-multiple-ssh-keys/
Looks like OpenStack (nova) allows to specify only one SSH key when instance is created. I believe array of strings should be supported instead of single string only, as authorized_keys allows for more than one SSH key. Workarounds like using merged key are not always an option, as it scales poorly (see example in question linked above).

Wishlist/enhancement request of course.

[Matt Riedemann (mriedem)]

We don't track RFEs through launchpad bugs. If you'd like to submit a blueprint and spec to the nova-specs repo then we could review the idea there, if even a limited backlog spec where you don't necessarily need design/implementation details, just the high level problem statement and use cases.