Ihar Hrachyshka 3e6393de51 Don't instantiate RPC clients on import
In oslo.messaging port, we'll need to make sure no RPC clients or
servers or notifiers are created before RPC layer is initialized using
n_rpc.init(). This means that there should be no global objects that
create those objects on __init__.

There should also be no such class attributes because in that case
import will itself instantiate the object, probably before RPC layer is
ready.

blueprint oslo-messaging

Change-Id: Ia8a9fd39777c75e4253f5518c2de6be551cc365b
2014-06-17 21:56:24 +02:00
2013-11-28 23:18:03 +08:00
2014-05-16 13:40:04 -04:00
2014-05-19 12:16:56 +02:00
2013-07-06 15:02:43 -04:00
2013-07-06 15:02:43 -04:00
2014-04-30 02:41:29 +00:00
2014-02-26 11:03:46 -05:00

# -- 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>.

Description
A set of Neutron drivers for the VMware NSX.
Readme 97 MiB
Languages
Python 98.5%
Shell 1.5%