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

Morales, Victor victor.morales at intel.com
Fri Nov 18 17:40:11 UTC 2016


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 AM, "Mathieu Gagné" <mgagne at calavera.ca> wrote:

>On Wed, Nov 16, 2016 at 11:52 AM, Clint Byrum <clint at fewbar.com> 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 and does not present any real surface area to the users.
>>
>
>Cannot agree more with you on that one.
>
>--
>Mathieu
>
>__________________________________________________________________________
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


More information about the OpenStack-dev mailing list