openstack
/
zaqar
Code Issues Proposed changes

Add release notes 

Change-Id: Iecb4c53add040e564f9cf7e1ccb7b44755b3355d
This commit is contained in:
Fei Long Wang 2016-06-08 07:11:15 +12:00
parent 5d1964d96b
commit e9dbb19a3a
3 changed files with 22 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
releasenotes/notes/fix_auth_issue_for_root_path-b15e1c4e92e4e8b1.yaml Normal file
View File

@ -0,0 +1,7 @@
---
fixes:
- |
When access the root path of Zaqar service, for example:
curl GET http://127.0.0.1:8888/, user will see 401 error. Which
will cause some front end proxy (like HAProxy) to complain. Now this issue
has been fixed.

8
releasenotes/notes/show_default_attributes_for_queue-3d87333752484c87.yaml Normal file
View File

@ -0,0 +1,8 @@
---
features:
- Currently Zaqar can support more built-in/reserved attributes in queue.
For now there are two important attributes 'max_messages_post_size' and
'max_message_ttl'. With this feature, when user query queues Zaqar will show
those two attributes (read from config file if there is no customized value
from user) in queue metadata so that user can know what value it is.

7
releasenotes/notes/user_ipv6_sockets-1e1b436de6b81ae3.yaml Normal file
View File

@ -0,0 +1,7 @@
---
fixes:
- In IPv6 management network environment, starting Zaqar server will
run into 'Address family for hostname not support' error when use WSGI
simple server. The root cause is that Python's TCPServer implementation
is hard-coded to use IPv4, even in IPv6 environments. Now this issue has
been fixed.