Update README to state a requirement for memcache

Bug #1638713 reported by Duk Loi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
trove-dashboard
Fix Released
Medium
Duk Loi

Bug Description

The trove dashboard has a requirement for memcache to be configured as the cache.

For example, the configuration group parameter handling assembles the new parameters in memory before applying them via the trove api.

The readme file should reflect this requirement.

Duk Loi (duktesora)
Changed in trove-dashboard:
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to trove-dashboard (master)

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

Changed in trove-dashboard:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to trove-dashboard (master)

Reviewed: https://review.openstack.org/407527
Committed: https://git.openstack.org/cgit/openstack/trove-dashboard/commit/?id=230a112ee6f5d11f31d4cf89cc7ffa9e3fd0594a
Submitter: Jenkins
Branch: master

commit 230a112ee6f5d11f31d4cf89cc7ffa9e3fd0594a
Author: Duk Loi <email address hidden>
Date: Tue Dec 6 09:07:23 2016 -0500

    Add requirement for cross-process cache

    Some of the trove-dashboard panels require a cross-process cache
    to be used to temporarily store data until it is committed to the
    server. For example, building up the list of configuration
    parameters is store in the cache until it is applied to the the
    database instance.

    This requirement is now added to the readme to inform users to
    enable the cache.

    Change-Id: I1928da600c7364d8681a8c0b45fe1c66c97032df
    Closes-Bug: #1638713

Changed in trove-dashboard:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/trove-dashboard 8.0.0.0b2

This issue was fixed in the openstack/trove-dashboard 8.0.0.0b2 development milestone.

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.