[openstack-dev] Unified Guest Agent proposal

Fox, Kevin M kevin.fox at pnnl.gov
Tue Dec 10 23:49:35 UTC 2013

Yeah. Its likely that the metadata server stuff will get more scalable/hardened over time. If it isn't enough now, lets fix it rather then coming up with a new system to work around it.

I like the idea of using the network since all the hypervisors have to support network drivers already. They also already have to support talking to the metadata server. This keeps OpenStack out of the hypervisor driver business.


From: Clint Byrum [clint at fewbar.com]
Sent: Tuesday, December 10, 2013 1:02 PM
To: openstack-dev
Subject: Re: [openstack-dev] Unified Guest Agent proposal

Excerpts from Dmitry Mescheryakov's message of 2013-12-10 12:37:37 -0800:
> >> What is the exact scenario you're trying to avoid?
> It is DDoS attack on either transport (AMQP / ZeroMQ provider) or server
> (Salt / Our own self-written server). Looking at the design, it doesn't
> look like the attack could be somehow contained within a tenant it is
> coming from.

We can push a tenant-specific route for the metadata server, and a tenant
specific endpoint for in-agent things. Still simpler than hypervisor-aware
guests. I haven't seen anybody ask for this yet, though I'm sure if they
run into these problems it will be the next logical step.

> In the current OpenStack design I see only one similarly vulnerable
> component - metadata server. Keeping that in mind, maybe I just
> overestimate the threat?

Anything you expose to the users is "vulnerable". By using the localized
hypervisor scheme you're now making the compute node itself vulnerable.
Only now you're asking that an already complicated thing (nova-compute)
add another job, rate limiting.

OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org

More information about the OpenStack-dev mailing list