generate and update climate config sample with oslo config tools

Bug #1271875 reported by Swann Croiset
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Blazar
Fix Released
Medium
Swann Croiset

Bug Description

We need to have a consistent config file sample with all available options
and to have validation to not miss new option added

Swann Croiset (swann-w)
Changed in climate:
assignee: nobody → Swann Croiset (swann-w)
milestone: none → 0.1.1
importance: Undecided → Medium
status: New → Confirmed
Changed in climate:
status: Confirmed → In Progress
Revision history for this message
Dina Belova (dbelova) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to climate (master)

Reviewed: https://review.openstack.org/71243
Committed: https://git.openstack.org/cgit/stackforge/climate/commit/?id=e9d03ee1ea57b3bdf7e50b7b2f55fd36ca6f19d9
Submitter: Jenkins
Branch: master

commit e9d03ee1ea57b3bdf7e50b7b2f55fd36ca6f19d9
Author: Swann Croiset <email address hidden>
Date: Thu Jan 23 11:28:02 2014 +0100

    Reworking configuration options

    Use config tools from Oslo-incubator :

    * generate a consistant config file sample:
      etc/climate/climate.conf.sample

    * Add a new check in tox env 'pep8' to check out-dated config file sample.

    Move specifics options for admin credential in group config 'physical:host'

    Factorize by declaring config options in each plugins with available values and
    centralizing RESOURCE_TYPE value in plugin's module (one dir per plugin)

    Use socket.gethostname() in place of socket.getfqdn() to have
    predictable default value for 'host' config in climate.config,
    since it's ugly forced in openstack.common.config.generator#L232

    Fixes: bug #1271875

    Change-Id: Ie54fc98b58b49400360c4fd2ce7d8bb3b75915e2

Changed in climate:
status: In Progress → Fix Committed
Changed in blazar:
status: Fix Committed → Fix Released
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.