magnum service-list needs backend support
Bug #1492501 reported by
Surojit Pathak
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Magnum |
Fix Released
|
Undecided
|
Surojit Pathak | ||
Bug Description
As part of BP[1],
we want to implement 'magnum service-list' after 'nova service-list'.
To do so we need backend support for the same, i.e.
- periodic write onto a table maintaining the healthcheck status.
[1] - https:/
| Changed in magnum: | |
| assignee: | nobody → Surojit Pathak (suro-patz) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to magnum (master) | #1 |
| Changed in magnum: | |
| status: | New → Fix Committed |
| Changed in magnum: | |
| milestone: | none → mitaka-1 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 3674ce278d4f17a
Author: Surojit Pathak <email address hidden>
Date: Thu Sep 3 00:19:47 2015 +0000
Backend support for magnum service
To support 'magnum service-list' after 'nova service-list', we need to
introduce periodic status update functionality for internal services.
Change-Id: Ia0c09222405c87
Partially-
Closes-bug: #1492501