Bug 1042973

Summary:	[RFE][oslo]: Advanced validation of config options
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	Upstream M2	Keywords:	FutureFeature
Target Release:	5.0 (RHEL 7)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/oslo/+spec/oslo-config-options-validation
Whiteboard:	upstream_milestone_icehouse-2 upstream_status_implemented upstream_definition_approved
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-03-27 13:49:44 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-13 16:49:58 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/oslo/+spec/oslo-config-options-validation.

Description:

Currently  it is possible to specify the data types of config options. Each option class (IntOpt, FloatOpt, etc) defines a converter function, which transforms strings read from config files to values of target data types. Though, it's up to developers to check, that these values are actually eligible (e. g. an int value is within some predefined range). It would be very useful, to have such validators directly in oslo.config

Specification URL (additional information):

None

Comment 2 Stephen Gordon 2014-01-23 20:50:55 UTC

Moving to POST based on upstream status (Implemented).