OpenStack Networking (Neutron) Specifications
Find a file
jimin3-shin 996dc8e23e Add spec to add information to network ip availabilities
Related-Bug: #2107316
Change-Id: I2f3b4fc8275f5ffc940172de1125b3908cfec29e
Signed-off-by: Jimin Shin <jimin3.shin@samsung.com>
2025-12-04 13:17:14 +09:00
doc Spec folder for 2026.1 cycle 2025-08-29 07:14:42 +00:00
images Propose spec for OVN BGP integration 2025-08-20 07:38:21 -04:00
misc Fix issues pointed by the pre-commit checks 2024-05-06 12:58:11 +02:00
specs Add spec to add information to network ip availabilities 2025-12-04 13:17:14 +09:00
tests Fix py27 job in specs repo 2018-05-30 10:28:57 +02:00
.gitignore Switch to stestr 2018-06-22 12:50:11 +02:00
.gitreview OpenDev Migration Patch 2019-04-19 19:34:46 +00:00
.pre-commit-config.yaml Add pre-commit configuration 2024-05-06 12:59:17 +02:00
.stestr.conf Switch to stestr 2018-06-22 12:50:11 +02:00
.zuul.yaml Update to use openstack-python3-jobs template 2025-02-07 11:28:37 -05:00
LICENSE Add base neutron-specs framework 2014-04-14 03:08:02 +00:00
README.rst Remove url tags from README 2025-08-17 22:09:13 +00:00
requirements.txt Switch to stestr 2018-06-22 12:50:11 +02:00
setup.cfg setup.cfg: Replace dashes with underscores 2023-04-28 08:20:56 +00:00
setup.py Spec folder for Zed 2022-04-13 17:28:52 +02:00
tox.ini tox: Remove basepython and ineffective ignore_basepython_conflict 2025-08-17 21:44:14 +00:00

================================
OpenStack Neutron Specifications
================================

.. image:: https://governance.openstack.org/tc/badges/neutron-specs.svg

.. Change things from this point on

This git repository is used to hold approved design specifications for additions
to the Neutron project. Reviews of the specs are done in gerrit, using a
similar workflow to how we review and merge changes to the code itself.

The layout of this repository is::

  specs/<release>/

You can find an example spec in `specs/template.rst`.

Specifications are proposed for a given release by adding them to the
`specs/<release>` directory and posting it for review. The implementation
status of a blueprint for a given release can be found by looking at the
blueprint in launchpad. Not all approved blueprints will get fully implemented.

Specifications have to be re-proposed for every release. The review may be
quick, but even if something was previously approved, it should be re-reviewed
to make sure it still makes sense as written.

Prior to the Juno development cycle, this repository was not used for spec
reviews. Reviews prior to Juno were completed entirely through Launchpad
blueprints::

  https://blueprints.launchpad.net/neutron

Please note, Launchpad blueprints are still used for tracking the
current status of blueprints. For more information, see::

  https://wiki.openstack.org/wiki/Blueprints

For more information about working with gerrit, see::

  https://docs.openstack.org/infra/manual/developers.html#development-workflow

To validate that the specification is syntactically correct (i.e. get more
confidence in the Jenkins result), please execute the following command::

  $ tox

After running ``tox``, the documentation will be available for viewing in HTML
format in the ``doc/build/`` directory. Please do not check in the generated
HTML files as a part of your commit.