Open Stack

We are glad to announce the release of:

networking-baremetal 0.1.0: Neutron plugin that provides deep
Ironic/Neutron integration.

This is the first release of networking-baremetal. This release is
part of the pike release series.

The source is available from:

    http://git.openstack.org/cgit/openstack/networking-baremetal

Download the package from:

    https://pypi.python.org/pypi/networking-baremetal

Please report issues through launchpad:

    http://bugs.launchpad.net/networking-baremetal

For more details, please see below.

0.1.0
^^^^^

Prelude

This is the initial release of the networking-baremetal. The project
includes the "baremetal" ml2 mechanism driver performing binding of
the Networking service ports with "binding_vnic_type=baremetal" in
flat networks. It also includes the devstack plugin to simplify the
development setup and testing.

Changes in networking-baremetal 207b1df0c6b078e5a83fd65ef19f58ee8b0681da..0.1.0
-------------------------------------------------------------------------------

9208c7c Add initial release note
83b2792 Add installation documentation
14891cc Add devstack plugin to install networking_baremetal
5c4f279 Add baremetal ML2 driver
c9e5a5a Add .gitignore
69c8889 Initial commit from cookiecutter




Requirements updates
--------------------

diff --git a/requirements.txt b/requirements.txt
new file mode 100644
index 0000000..dd9bf85
--- /dev/null
+++ b/requirements.txt
@@ -0,0 +1,9 @@
+# The order of packages is significant, because pip processes them in the order
+# of appearance. Changing the order has an impact on the overall integration
+# process, which may cause wedges in the gate later.
+
+neutron-lib>=1.7.0  # Apache-2.0
+oslo.i18n>=2.1.0,!=3.15.2  # Apache-2.0
+oslo.log>=3.22.0  # Apache-2.0
+oslo.utils>=3.20.0                       # Apache-2.0
+pbr>=2.0.0,!=2.1.0  # Apache-2.0
diff --git a/test-requirements.txt b/test-requirements.txt
new file mode 100644
index 0000000..06634e5
--- /dev/null
+++ b/test-requirements.txt
@@ -0,0 +1,19 @@
+# The order of packages is significant, because pip processes them in the order
+# of appearance. Changing the order has an impact on the overall integration
+# process, which may cause wedges in the gate later.
+
+bashate>=0.2 # Apache-2.0
+hacking>=0.12.0,!=0.13.0,<0.14  # Apache-2.0
+coverage>=4.0 # Apache-2.0
+oslotest>=1.10.0 # Apache-2.0
+python-subunit>=0.0.18 # Apache-2.0/BSD
+testtools>=1.4.0 # MIT
+os-testr>=0.8.0 # Apache-2.0
+testscenarios>=0.4  # Apache-2.0/BSD
+
+# Doc requirements
+sphinx>=1.5.1 # BSD
+openstackdocstheme>=1.16.0 # Apache-2.0
+
+# releasenotes
+reno>=1.8.0 # Apache-2.0