15a912b1ca
Neutron client expects token to be passed as token= argument, while neutron-metadata-agent passes auth_token= instead. This effectively makes the client to authenticate against keystone each time it's instantiated. In neutron-metadata-agent case, it means 'each time a client sends a metadata request.' The issue results in high cpu utilization on keystone side when simultaneously invoking multiple nova instances with cloud-init. Change-Id: I2a31f9c0c3cfa915975ecc53d71168a3895528d8 Closes-Bug: 1274487 (cherry picked from commit 3799efe792700e7736666c40cc42c265eee09230)
# -- Welcome!
You have come across a cloud computing network fabric controller. It has identified itself as "Neutron." It aims to tame your (cloud) networking!
# -- External Resources:
The homepage for Neutron is: http://launchpad.net/neutron . Use this site for asking for help, and filing bugs. Code is available on github at <http://github.com/openstack/neutron>.
The latest and most in-depth documentation on how to use Neutron is available at: <http://docs.openstack.org>. This includes:
Neutron Administrator Guide http://docs.openstack.org/trunk/openstack-network/admin/content/
Neutron API Reference: http://docs.openstack.org/api/openstack-network/2.0/content/
The start of some developer documentation is available at: http://wiki.openstack.org/NeutronDevelopment
For help using or hacking on Neutron, you can send mail to <mailto:openstack-dev@lists.openstack.org>.