Re: [openstack-dev] [neutron][metadata] Is there HTTP attack issue in metadata proxy functionality offered by reference implementation?

Thant’s remind me when we tried to improve cloud-init. Basically, the discovery process checks sequentially where the instance is being landed(EC2, GoogleCompute, OpenStack). This process could be done in parallel and reduce the time to boot. Regards, Victor Morales On 11/16/16, 11:31

Re: [openstack-dev] [neutron][metadata] Is there HTTP attack issue in metadata proxy functionality offered by reference implementation?

On Wed, Nov 16, 2016 at 11:52 AM, Clint Byrum wrote: > > IMO the HTTP metadata service and the way it works is one of the worst > ideas we borrowed from EC2. Config drive (which I didn't like when I > first saw it, but now that I've operated clouds, I love) is a simpler > system

Re: [openstack-dev] [neutron][metadata] Is there HTTP attack issue in metadata proxy functionality offered by reference implementation?

Excerpts from huangdenghui's message of 2016-11-17 00:05:39 +0800: > hi > Currently, nova metadata service is proxy by metadata agent in dhcp agent > or l3 router agent, it is depended on whether network attach to router or > not. In essential, metadata agent implements a http proxy

[openstack-dev] [neutron][metadata] Is there HTTP attack issue in metadata proxy functionality offered by reference implementation?

hi Currently, nova metadata service is proxy by metadata agent in dhcp agent or l3 router agent, it is depended on whether network attach to router or not. In essential, metadata agent implements a http proxy functionality by computer node host protocal stack. In other words, it exposes