Move usage_timeout out of guest options
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-manuals |
Fix Released
|
Medium
|
Andreas Jaeger |
Bug Description
https:/
Dear documentation bug triager. This bug was created here because we did not know how to map the project name "openstack/trove" to a launchpad project name. This indicates that the notify_impact config needs tweaks. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.
commit 8e699bf8193f28e
Author: Amrith Kumar <email address hidden>
Date: Mon Jul 14 06:51:58 2014 -0400
Move usage_timeout out of guest options
In an effort to further separate the guest and task manager,
the usage_timeout has been moved into the common cfg. The
datastores have no need for this. the default is now set as
the largest timeout, cassandra.
DocImpact: This change modifies a configuration parameter.
partially implements: blueprint refactoring-
Co-Author: Michael Basnight <email address hidden>
Change-Id: I3b4b2a9bffb40d
Changed in openstack-manuals: | |
importance: | Undecided → Medium |
Fix proposed to branch: master /review. openstack. org/117945
Review: https:/