task: use CONF_FILE from constants 71/44871/2
authorRoss Brattain <ross.b.brattain@intel.com>
Thu, 12 Oct 2017 05:46:57 +0000 (22:46 -0700)
committerRoss Brattain <ross.b.brattain@intel.com>
Fri, 13 Oct 2017 03:46:54 +0000 (03:46 +0000)
I'm not sure why we hardcoded config_file when
the CONF_FILE constant will work.

Change-Id: I45a1dc17ac2b185c659725f55462214acb74838d
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
yardstick/benchmark/core/task.py

index 1512ca7..9b1b3f8 100644 (file)
@@ -28,6 +28,7 @@ from jinja2 import Environment
 
 from yardstick.benchmark.contexts.base import Context
 from yardstick.benchmark.runners import base as base_runner
+from yardstick.common.constants import CONF_FILE
 from yardstick.common.yaml_loader import yaml_load
 from yardstick.dispatcher.base import Base as DispatcherBase
 from yardstick.common.task_template import TaskTemplate
@@ -36,7 +37,6 @@ from yardstick.common import constants
 from yardstick.common.html_template import report_template
 
 output_file_default = "/tmp/yardstick.out"
-config_file = '/etc/yardstick/yardstick.conf'
 test_cases_dir_default = "tests/opnfv/test_cases/"
 LOG = logging.getLogger(__name__)
 
@@ -68,7 +68,7 @@ class Task(object):     # pragma: no cover
         self._set_log()
 
         try:
-            output_config = utils.parse_ini_file(config_file)
+            output_config = utils.parse_ini_file(CONF_FILE)
         except Exception:
             # all error will be ignore, the default value is {}
             output_config = {}