openstack
/
neutron
Code Issues Proposed changes
OpenStack Networking (Neutron)
9,154 Commits 9 Branches 75 Tags 995 MiB
Python 99.5%
Shell 0.4%
Jinja 0.1%
Go to file
Miguel Angel Ajo 90e833a3cb Enable Process Monitor by default. 
Process monitor is enabled by default by this patch,
with a default 60 second monitoring interval, this
interval was calculated early in the development
process to scale to 1000s of processes with light load.
We believe it's important to have it enabled to get
user feedback as we release kilo.

Process monitor is sucessfully enabled and backported
to Red Hat D/S distributions from icehouse to juno
without any issue.

Specific process monitor functional tests provide
coverage, also keepalived checks that it can be
properly respawned.

We should follow up with dhcp and l3 agent functional
testing for killing and checking their processes
correctly respawned. Normal process start/stop is
already validated by other functional tests and tempest.

DocImpact

Change-Id: I85fe31bee30714148168a293eea29fa0a37f9701
Implements: blueprint agent-child-processes-status
 		2015-03-27 09:52:42 +00:00
bin adopt namespace-less oslo imports 2015-02-20 17:36:47 -08:00
doc Add some useful notes in devref/db_layer.rst 2015-03-25 12:38:24 +03:00
etc Enable Process Monitor by default. 2015-03-27 09:52:42 +00:00
neutron Enable Process Monitor by default. 2015-03-27 09:52:42 +00:00
rally-jobs Run more Rally benchmark on every patch 2015-03-18 10:38:44 +00:00
tools Add rootwrap daemon mode support 2015-03-12 21:12:07 -05:00
.coveragerc fix some missing change from quantum to neutron 2013-07-08 12:11:04 +08:00
.gitignore Add support for retargetable functional api testing 2015-01-06 02:37:59 +00:00
.gitreview Rename quantum to neutron in .gitreview. 2013-07-06 12:25:09 -04:00
.mailmap Add mailmap entry 2014-05-16 13:40:04 -04:00
.pylintrc Remove 'free' exclusions from pylint 2015-03-06 09:37:00 -05:00
.testr.conf Add an explicit tox job for functional tests 2014-02-05 17:11:52 +00:00
CONTRIBUTING.rst Workflow documentation is now in infra-manual 2014-12-05 03:30:37 +00:00
HACKING.rst oslo: migrate to namespace-less import paths 2015-02-05 15:09:32 +01:00
LICENSE Adding Apache Version 2.0 license file. This is the official license agreement under which Quantum code is available to 2011-08-08 12:31:04 -07:00
MANIFEST.in Rename Quantum to Neutron 2013-07-06 15:02:43 -04:00
README.rst Updated the README.rst 2014-12-02 14:33:30 -06:00
TESTING.rst Add full-stack tests framework 2015-03-26 20:21:40 +02:00
babel.cfg Use babel to generate translation file 2013-01-24 00:20:32 +08:00
openstack-common.conf Migrate to oslo.log 2015-03-12 11:22:56 +01:00
requirements.txt Updated from global requirements 2015-03-21 00:10:47 +00:00
run_tests.sh Revert "monkey patch stdlib before importing other modules" 2015-02-11 17:26:33 -08:00
setup.cfg Merge "Add L3 router plugin shim for Brocade MLX" 2015-03-26 23:15:58 +00:00
setup.py Updated from global requirements 2014-04-30 02:41:29 +00:00
test-requirements.txt Updated from global requirements 2015-03-21 00:10:47 +00:00
tox.ini Add full-stack tests framework 2015-03-26 20:21:40 +02:00

README.rst

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:

http://wiki.openstack.org/NeutronDevelopment

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.