[release-announce] masakari-dashboard 0.1.0 (rocky)

no-reply at openstack.org no-reply at openstack.org
Mon Jul 30 16:20:52 UTC 2018


We high-spiritedly announce the release of:

masakari-dashboard 0.1.0: Horizon plugin for masakari

This is the first release of masakari-dashboard. This release is part
of the rocky release series.

The source is available from:

    http://git.openstack.org/cgit/openstack/masakari-dashboard

Download the package from:

    https://tarballs.openstack.org/masakari-dashboard/

Please report issues through launchpad:

    http://bugs.launchpad.net/masakari

For more details, please see below.

Changes in masakari-dashboard 3ba35deadc31e4c6ac0834f9042690db4c6cd886..0.1.0
-----------------------------------------------------------------------------

b18ad52 Implement update segment
4996c37 Implement segment detail tab
30d3188 Implement delete segment
c429554 Add segment panel
b09b094 Initial UI-Cookiecutter commit




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

diff --git a/requirements.txt b/requirements.txt
new file mode 100644
index 0000000..b1d58f4
--- /dev/null
+++ b/requirements.txt
@@ -0,0 +1,15 @@
+# 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.
+# Order matters to the pip dependency resolver, so sorting this file
+# changes how packages are installed.  New dependencies should be
+# added in alphabetical order, however, some dependencies may need to
+# be installed in a specific order.
+#
+# PBR should always appear first
+pbr!=2.1.0,>=2.0.0 # Apache-2.0
+
+# Horizon Core Requirements
+horizon>=13.0.0  # Apache-2.0
+openstacksdk>=0.13.0
+PyYAML>=3.12 # MIT
diff --git a/test-requirements.txt b/test-requirements.txt
new file mode 100644
index 0000000..a6e9896
--- /dev/null
+++ b/test-requirements.txt
@@ -0,0 +1,24 @@
+# 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.
+# Order matters to the pip dependency resolver, so sorting this file
+# changes how packages are installed.  New dependencies should be
+# added in alphabetical order, however, some dependencies may need to
+# be installed in a specific order.
+#
+# Hacking should appear first in case something else depends on pep8
+hacking!=0.13.0,<0.14,>=0.12.0 # Apache-2.0
+
+# Testing Requirements
+coverage!=4.4,>=4.0 # Apache-2.0
+django-nose>=1.4.4 # BSD
+mock>=2.0.0 # BSD
+mox3>=0.20.0  # Apache-2.0
+nodeenv>=0.9.4 # BSD
+nose>=1.3.7 # LGPL
+nose-exclude>=0.3.0 # LGPL
+nosexcover>=1.0.10 # BSD
+openstack.nose-plugin>=0.7 # Apache-2.0
+nosehtmloutput>=0.0.3 # Apache-2.0
+selenium>=2.50.1 # Apache-2.0
+xvfbwrapper>=0.1.3 #license: MIT






More information about the Release-announce mailing list