Some oslo libraries assume that stdlib is already patched when they are imported (e.g. oslo_concurrency.processutils tests the 'time' module for monkey_patching to detect which 'subprocess' module to import. This can cause issues when things like test frameworks import modules that monkey_patch, as the order imports are made can break this kind of check. It is always good to monkey patch as soon as possible, hence trying to do the patching in neutron/__init__.py. This is an alternative to https://review.openstack.org/#/c/153225/ which just patches neutron/tests/__init__.py. Unfortunately, just monkey_patching in tests/__init__.py didn't fix all of the issues I ran into. For example, tempest tests were failing with timeouts. Closes-bug: #1418541 Change-Id: I7f2115a99acae5b6d61aab2f7334f498b8d99858
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 git.openstack.org at <http://git.openstack.org/cgit/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/admin-guide-cloud/content/ch_networking.html
- Neutron API Reference:
-
http://docs.openstack.org/api/openstack-network/2.0/content/
- Current Neutron developer documentation is available at:
For help on usage and hacking of Neutron, please send mail to <mailto:openstack-dev@lists.openstack.org>.
For information on how to contribute to Neutron, please see the contents of the CONTRIBUTING.rst file.