magnum service-list needs backend support

Bug #1492501 reported by Surojit Pathak
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
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] -

Tags: magnum
Changed in magnum:
assignee: nobody → Surojit Pathak (suro-patz)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnum (master)

Submitter: Jenkins
Branch: master

commit 3674ce278d4f17aeb4f29377b8f9ba47e1016a37
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: Ia0c09222405c87cb61e5de4a43ba345ae3405b50
    Partially-Implements: blueprint magnum-service-list
    Closes-bug: #1492501

Changed in magnum:
status: New → Fix Committed
Adrian Otto (aotto)
Changed in magnum:
milestone: none → mitaka-1
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.