Hello, I agree this feature of injecting a new keypair is something of great use. We are always dealing with users that cant access their VMs anymore.
But AFAIU here we are talking about injecting a new key at REBUILD. So it does not fit the scenario of a staff member that leaves ! We hardly never use the rebuild feature in our workflow. Our users just use create and delete. I think it would be more useful a feature where you can reinject a new keypair in the VM at any time. Ahhh it makes the users happy but of course it is a security nightmare :D Cheers Saverio 2017-09-27 11:15 GMT+02:00 Marcus Furlong <furlo...@gmail.com>: > On 27 September 2017 at 09:23, Michael Still <mi...@stillhq.com> wrote: >> >> Operationally, why would I want to inject a new keypair? The scenario I can >> think of is that there's data in that instance that I want, and I've lost >> the keypair somehow. Unless that data is on an ephemeral, its gone if we do >> a rebuild. > > This is quite a common scenario - staff member who started the > instance leaves, and you want to access data on the instance, or > maintain/debug the service running on the instance. > > Hitherto, I have used direct db calls to update the key, so it would > be nice if there was an API call to do so. > > Cheers, > Marcus. > -- > Marcus Furlong > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators _______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
