OpenStack DBaaS (Trove)

Service ID for Notifications should bind to Service Type

Bug #1215649 reported by Justin Hopper
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Fix Released
Undecided
Justin Hopper
OpenStack DBaaS (Trove) 2014.1 "icehouse"

Bug Description

Currently there is only one configuration for Service ID as part of the Notifications. This ID needs to vary per Service Type (e.g. a service id for MySQL, and a different service id for reddis).

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to trove (master)

Fix proposed to branch: master
Review: https://review.openstack.org/45309

Changed in trove:
assignee: nobody → Justin Hopper (justin-hopper)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to trove (master)

Reviewed: https://review.openstack.org/45309
Committed: http://github.com/openstack/trove/commit/64774095a3861cee956725fbb13f95510ff4fcd9
Submitter: Jenkins
Branch: master

commit 64774095a3861cee956725fbb13f95510ff4fcd9
Author: justin-hopper <email address hidden>
Date: Thu Sep 5 12:09:09 2013 -0700

    Allow service_id per service_type for Usage Events

        notification_service_id is not of type DictOpt,
        this allows for a comma-sep list of
        service_type:service_id pairs

    Fixes: Bug 1215649
    Change-Id: Ic747bf50bf6f4c2b705ecae96a7ead52ebcdae38

Changed in trove:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in trove:
milestone: none → icehouse-1
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in trove:
milestone: icehouse-1 → 2014.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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