Re: [Openstack] Newton: not able to login via public key

Hi all, I have reconfigured everything, working fine but not sure where what went wrong last time, Can anyone explain, how this works, like metadata agent is *neutron *service, is it responsible for adding key inside new instance? It should be a job of *nova *service. Thanks and Regards Amit Un

Re: [Openstack] Newton: not able to login via public key

The metadata agent in Neutron is just a proxy that relays metadata requests to Nova after adding in HTTP headers that identify the instance. On Sun, Mar 5, 2017 at 5:44 AM, Amit Uniyal wrote: > Hi all, > > I have reconfigured everything, working fine but not sure where what went > wrong last time

Re: [Openstack] Newton: not able to login via public key

Hi Kevin, Thanks for response. Can you tell which service or which configuration(file) is responsible for adding metadata to instance. like adding adding keys in new instance ? Thanks and Regards Amit Uniyal On Sun, Mar 5, 2017 at 8:18 PM, Kevin Benton wrote: > The metadata agent in Neutron

[Openstack] [kolla][keyston] better way to rotate and distribution keystone fernet keys in container env

Kolla have support keystone fernet keys. But there are still some topics worth to talk. The key issue is key distribution. Kolla's solution is like * there is a task run frequently by cronjob to check whether the key should be rotate. This is controlled by `fernet_token_expiry` variable * Whe

Re: [Openstack] [kolla][keystone] better way to rotate and distribution keystone fernet keys in container env

fix subject typo On Mon, Mar 6, 2017 at 12:28 PM, Jeffrey Zhang wrote: > Kolla have support keystone fernet keys. But there are still some > topics worth to talk. > > The key issue is key distribution. Kolla's solution is like > > * there is a task run frequently by cronjob to check whether >