datasource add/delete not effected until next sync

Bug #1638729 reported by Eric K
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
congress
Fix Released
High
Masahito Muroi

Bug Description

If the API is deployed on a separate node from the datasources:
When the API node processes datasource add/delete, it modifies the database and returns success, even though the datasource service has not been created or removed. We give a strange user experience that after adding a datasource returns success, the newly added datasource does not exist or have status until the next periodic sync (default 30 seconds?).

Proposed fix:
add a new datasource_manager service that is automatically started on the dse_node that hosts the datasource services.
On the datasource_model api, instead of calling self.bus.add_datasource/delete_datasource, rpc call the datasource_manager (which may be on the same or different node).

Consider backporting fix to Newton.

Changed in congress:
status: New → Confirmed
assignee: nobody → Masahito Muroi (muroi-masahito)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to congress (master)

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

Changed in congress:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to congress (stable/newton)

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/400322

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

Reviewed: https://review.openstack.org/397096
Committed: https://git.openstack.org/cgit/openstack/congress/commit/?id=22ce339f23f7311e31796b9a530794c85c095930
Submitter: Jenkins
Branch: master

commit 22ce339f23f7311e31796b9a530794c85c095930
Author: Masahito Muroi <email address hidden>
Date: Mon Nov 14 19:01:10 2016 +0900

    Route datasource add/delete request to datasource node

    API request adding/deleting datasource should be routed to datasource
    node, and then the datasource node creates/removes the requested
    datasource during the request. It enables user to use the datasource
    just after recieving the response of request.

    Change-Id: If365c6d1db9ecc5c578421ad5c362326fc262a78
    Closes-bug: #1638729
    Closes-bug: #1639116

Changed in congress:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to congress (stable/newton)

Reviewed: https://review.openstack.org/400322
Committed: https://git.openstack.org/cgit/openstack/congress/commit/?id=1149270e1fc47f1d3b397f24701e40d213c7efd2
Submitter: Jenkins
Branch: stable/newton

commit 1149270e1fc47f1d3b397f24701e40d213c7efd2
Author: Masahito Muroi <email address hidden>
Date: Mon Nov 14 19:01:10 2016 +0900

    Route datasource add/delete request to datasource node

    API request adding/deleting datasource should be routed to datasource
    node, and then the datasource node creates/removes the requested
    datasource during the request. It enables user to use the datasource
    just after recieving the response of request.

    Change-Id: If365c6d1db9ecc5c578421ad5c362326fc262a78
    Closes-bug: #1638729
    Closes-bug: #1639116

tags: added: in-stable-newton
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/congress 5.0.0.0b2

This issue was fixed in the openstack/congress 5.0.0.0b2 development milestone.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/congress 4.0.1

This issue was fixed in the openstack/congress 4.0.1 release.

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.