[queues] Return shard listing as object, not array
Bug #1243898 reported by
Allele Dev
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
zaqar |
Fix Released
|
Medium
|
Allele Dev |
Bug Description
Return the array encapsulated in an object (e.g., {}). This will allow for extensions and adding fields that won't break backwards-
Currently, it is returned as an array.
Changed in marconi: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in marconi: | |
assignee: | nobody → Alejandro Cabrera (cpp-cabrera) |
Changed in marconi: | |
status: | Triaged → In Progress |
Changed in marconi: | |
milestone: | none → icehouse-1 |
status: | Fix Committed → Fix Released |
Changed in marconi: | |
milestone: | icehouse-1 → 2014.1 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/50998 github. com/openstack/ marconi/ commit/ f6c321dd8b3f4f9 21c3cbf82fc385b b6e71cf9c0
Committed: http://
Submitter: Jenkins
Branch: master
commit f6c321dd8b3f4f9 21c3cbf82fc385b b6e71cf9c0
Author: Alejandro Cabrera <email address hidden>
Date: Thu Oct 10 09:12:53 2013 -0400
feat: integrate shard storage with transport
This patch refines the interface and storage implementation defined in
the last patch and integrates it with the transport layer.
A few updates have been made:
- 'name' -> 'href' for listing shards
- limiting, markers, and detailed are all used
- use of common_utils.fields to clean up shards transport PATCH
- add missing init for schemas
- fix schema issues found: 'location' -> 'uri', __init__.py
- shard resource correctly implements PUT semantics (replaces)
Transport: the admin API concept has been expanded to include
functionality from the public interface *in addition* to admin
functionality. Part of the rationale behind this is to simplify unit
testing. The other part of this is that an admin should be able to do
everything a normal user can do in addition to their special
functions.
Storage: now divided into control and data plane. The bootstrap passes
a control driver down to the transport which *can* be used for
endpoints as needed.
A test suite has been added that exercises the functionality from the
transport side of the shard registry resource.
Finally, the way the FaultyStorage driver tests were handled was
changed. Something about the setattr magic in that suite's setup made
it such that *all* tests would use the Faulty storage driver. This is
possibly related to the use of lazy_property decorators. To address
this issue, this patch promotes the faulty storage driver to setup.cfg
visibility and removes the setattrs.
Change-Id: I5b8cdb3a11d294 22762b52f1e15e3 3167eecb867 implements: blueprint storage-sharding Closes: 1241686
Partitally-
Partially-
Closes-Bug: 1243898