From 276dd95b3e4ad6f7a1784b4bb2e82be732550a83 Mon Sep 17 00:00:00 2001
From: Zane Bitter <zbitter@redhat.com>
Date: Wed, 10 Apr 2019 09:25:01 -0400
Subject: [PATCH] Added release note for QosBandwithLimitRule direction
 property

Change-Id: I5f0f2f79427f868381a6127e1d50f4943e93e7c4
Task: 30445
---
 .../qos-bandwidth-limit-ingress-182a6300cd6e7aa3.yaml      | 7 +++++++
 1 file changed, 7 insertions(+)
 create mode 100644 releasenotes/notes/qos-bandwidth-limit-ingress-182a6300cd6e7aa3.yaml

diff --git a/releasenotes/notes/qos-bandwidth-limit-ingress-182a6300cd6e7aa3.yaml b/releasenotes/notes/qos-bandwidth-limit-ingress-182a6300cd6e7aa3.yaml
new file mode 100644
index 0000000000..b8bf6f5f12
--- /dev/null
+++ b/releasenotes/notes/qos-bandwidth-limit-ingress-182a6300cd6e7aa3.yaml
@@ -0,0 +1,7 @@
+---
+features:
+  - |
+    The ``OS::Neutron::QosBandwidthLimitRule`` resource type now supports an
+    optional ``direction`` property, allowing users to set the ingress
+    bandwidth limit in a QoS rule. Previously only the egress bandwidth limit
+    could be set.