2013-08-21 12:30:47 +10:00
|
|
|
#!/usr/bin/env python
|
2013-12-29 22:23:05 +01:00
|
|
|
#
|
|
|
|
# Licensed under the Apache License, Version 2.0 (the "License"); you may
|
|
|
|
# not use this file except in compliance with the License. You may obtain
|
|
|
|
# a copy of the License at
|
|
|
|
#
|
|
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
#
|
|
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
|
|
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
|
|
|
|
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
|
|
|
|
# License for the specific language governing permissions and limitations
|
|
|
|
# under the License.
|
|
|
|
|
2013-08-21 12:30:47 +10:00
|
|
|
import glob
|
2014-01-03 11:08:14 +01:00
|
|
|
import os
|
|
|
|
import sys
|
|
|
|
|
2013-08-21 12:30:47 +10:00
|
|
|
from xml.dom import minidom
|
|
|
|
from xml.sax.saxutils import escape
|
|
|
|
|
|
|
|
#Swift configuration example files live in
|
|
|
|
# swift/etc/*.conf-sample
|
|
|
|
# and contain sections enclosed in [], with
|
|
|
|
# options one per line containing =
|
|
|
|
# and generally only having a single entry
|
|
|
|
# after the equals (the default value)
|
|
|
|
|
Make swift config tables the source of truth
As discussed on the mailing list, this patch will make the swift
configuration tables found in common a source of truth for the
helptext. The script that generates them has been updated for this,
and will now only add/remove options, update default values, and
replace helptext where it does not exist in the tables. Another
run of the script was done and tables were updated.
Backstory: All projects other than Swift use OpenStack Common for
configuration, and define option, default value and help text in the
code in a way that it's possible to extract.
Since the code is able to act in this way, we can stop maintaining
separate instructive lines for configuration options, and instead
fix any text problems in the code itself. This both improves the
quality of the code and fixes our double maintenance problem.
For swift, we needed a different approach. Unfortunately, I think we
don't have the ability to treat the code as the definitive source and
move all maintenance there. The lack of instruction for every option,
and absence of structure precludes this.
So I wrote some nasty scraping things (from RST and sample conf file)
to seed an initial list of configuration options.
My plan from here was to make the 'update' portion of the script
treat the textual descriptions in common/tables/swift-*.xml as
definitive.
The script would still search the swift code to add or remove
options, so we could guarantee completeness, and after an initial
push to write out proper help text the maintenance becomes far
simpler.
Change-Id: I2464f5c63cb0da110e1871a09a59380dad9b6b27
2013-09-03 10:39:38 +10:00
|
|
|
|
2013-08-21 12:30:47 +10:00
|
|
|
def parse_line(line):
|
|
|
|
"""
|
|
|
|
takes a line from a swift sample configuration file and attempts
|
|
|
|
to separate the lines with actual configuration option and default
|
|
|
|
value from the rest. Returns None if the line doesn't appear to
|
|
|
|
contain a valid configuration option = default value pair, and
|
|
|
|
a pair of the config and its default if it does.
|
|
|
|
"""
|
|
|
|
if '=' not in line:
|
|
|
|
return None
|
|
|
|
temp_line = line.strip('#').strip()
|
|
|
|
config, default = temp_line.split('=', 1)
|
|
|
|
config = config.strip()
|
|
|
|
if ' ' in config and config[0:3] != 'set':
|
|
|
|
if len(default.split()) > 1 or config[0].isupper():
|
|
|
|
return None
|
|
|
|
if len(config) < 2 or '.' in config or '<' in config or '>' in config:
|
|
|
|
return None
|
|
|
|
return config, default.strip()
|
|
|
|
|
Make swift config tables the source of truth
As discussed on the mailing list, this patch will make the swift
configuration tables found in common a source of truth for the
helptext. The script that generates them has been updated for this,
and will now only add/remove options, update default values, and
replace helptext where it does not exist in the tables. Another
run of the script was done and tables were updated.
Backstory: All projects other than Swift use OpenStack Common for
configuration, and define option, default value and help text in the
code in a way that it's possible to extract.
Since the code is able to act in this way, we can stop maintaining
separate instructive lines for configuration options, and instead
fix any text problems in the code itself. This both improves the
quality of the code and fixes our double maintenance problem.
For swift, we needed a different approach. Unfortunately, I think we
don't have the ability to treat the code as the definitive source and
move all maintenance there. The lack of instruction for every option,
and absence of structure precludes this.
So I wrote some nasty scraping things (from RST and sample conf file)
to seed an initial list of configuration options.
My plan from here was to make the 'update' portion of the script
treat the textual descriptions in common/tables/swift-*.xml as
definitive.
The script would still search the swift code to add or remove
options, so we could guarantee completeness, and after an initial
push to write out proper help text the maintenance becomes far
simpler.
Change-Id: I2464f5c63cb0da110e1871a09a59380dad9b6b27
2013-09-03 10:39:38 +10:00
|
|
|
|
|
|
|
def get_existing_options(optfiles):
|
2013-08-21 12:30:47 +10:00
|
|
|
"""
|
|
|
|
parses an existing XML table to compile a list of existing options
|
|
|
|
"""
|
Make swift config tables the source of truth
As discussed on the mailing list, this patch will make the swift
configuration tables found in common a source of truth for the
helptext. The script that generates them has been updated for this,
and will now only add/remove options, update default values, and
replace helptext where it does not exist in the tables. Another
run of the script was done and tables were updated.
Backstory: All projects other than Swift use OpenStack Common for
configuration, and define option, default value and help text in the
code in a way that it's possible to extract.
Since the code is able to act in this way, we can stop maintaining
separate instructive lines for configuration options, and instead
fix any text problems in the code itself. This both improves the
quality of the code and fixes our double maintenance problem.
For swift, we needed a different approach. Unfortunately, I think we
don't have the ability to treat the code as the definitive source and
move all maintenance there. The lack of instruction for every option,
and absence of structure precludes this.
So I wrote some nasty scraping things (from RST and sample conf file)
to seed an initial list of configuration options.
My plan from here was to make the 'update' portion of the script
treat the textual descriptions in common/tables/swift-*.xml as
definitive.
The script would still search the swift code to add or remove
options, so we could guarantee completeness, and after an initial
push to write out proper help text the maintenance becomes far
simpler.
Change-Id: I2464f5c63cb0da110e1871a09a59380dad9b6b27
2013-09-03 10:39:38 +10:00
|
|
|
options = {}
|
|
|
|
for optfile in optfiles:
|
|
|
|
xmldoc = minidom.parse(optfile)
|
|
|
|
tbody = xmldoc.getElementsByTagName('tbody')[0]
|
|
|
|
trlist = tbody.getElementsByTagName('tr')
|
|
|
|
for tr in trlist:
|
|
|
|
try:
|
|
|
|
optentry = tr.childNodes[1].childNodes[0]
|
|
|
|
option, default = optentry.nodeValue.split('=', 1)
|
|
|
|
helptext = tr.childNodes[2].childNodes[0].nodeValue
|
|
|
|
except IndexError:
|
|
|
|
continue
|
|
|
|
if option not in options or 'No help text' in options[option]:
|
|
|
|
#options[option.split('=',1)[0]] = helptext
|
|
|
|
options[option] = helptext
|
2013-08-21 12:30:47 +10:00
|
|
|
return options
|
|
|
|
|
Make swift config tables the source of truth
As discussed on the mailing list, this patch will make the swift
configuration tables found in common a source of truth for the
helptext. The script that generates them has been updated for this,
and will now only add/remove options, update default values, and
replace helptext where it does not exist in the tables. Another
run of the script was done and tables were updated.
Backstory: All projects other than Swift use OpenStack Common for
configuration, and define option, default value and help text in the
code in a way that it's possible to extract.
Since the code is able to act in this way, we can stop maintaining
separate instructive lines for configuration options, and instead
fix any text problems in the code itself. This both improves the
quality of the code and fixes our double maintenance problem.
For swift, we needed a different approach. Unfortunately, I think we
don't have the ability to treat the code as the definitive source and
move all maintenance there. The lack of instruction for every option,
and absence of structure precludes this.
So I wrote some nasty scraping things (from RST and sample conf file)
to seed an initial list of configuration options.
My plan from here was to make the 'update' portion of the script
treat the textual descriptions in common/tables/swift-*.xml as
definitive.
The script would still search the swift code to add or remove
options, so we could guarantee completeness, and after an initial
push to write out proper help text the maintenance becomes far
simpler.
Change-Id: I2464f5c63cb0da110e1871a09a59380dad9b6b27
2013-09-03 10:39:38 +10:00
|
|
|
|
2013-08-21 12:30:47 +10:00
|
|
|
def extract_descriptions_from_devref(repo, options):
|
|
|
|
"""
|
|
|
|
loop through the devref RST files, looking for lines formatted
|
Make swift config tables the source of truth
As discussed on the mailing list, this patch will make the swift
configuration tables found in common a source of truth for the
helptext. The script that generates them has been updated for this,
and will now only add/remove options, update default values, and
replace helptext where it does not exist in the tables. Another
run of the script was done and tables were updated.
Backstory: All projects other than Swift use OpenStack Common for
configuration, and define option, default value and help text in the
code in a way that it's possible to extract.
Since the code is able to act in this way, we can stop maintaining
separate instructive lines for configuration options, and instead
fix any text problems in the code itself. This both improves the
quality of the code and fixes our double maintenance problem.
For swift, we needed a different approach. Unfortunately, I think we
don't have the ability to treat the code as the definitive source and
move all maintenance there. The lack of instruction for every option,
and absence of structure precludes this.
So I wrote some nasty scraping things (from RST and sample conf file)
to seed an initial list of configuration options.
My plan from here was to make the 'update' portion of the script
treat the textual descriptions in common/tables/swift-*.xml as
definitive.
The script would still search the swift code to add or remove
options, so we could guarantee completeness, and after an initial
push to write out proper help text the maintenance becomes far
simpler.
Change-Id: I2464f5c63cb0da110e1871a09a59380dad9b6b27
2013-09-03 10:39:38 +10:00
|
|
|
such that they might contain a description of a particular
|
2013-08-21 12:30:47 +10:00
|
|
|
option
|
|
|
|
"""
|
|
|
|
option_descs = {}
|
|
|
|
rsts = glob.glob(repo + '/doc/source/*.rst')
|
|
|
|
for rst in rsts:
|
|
|
|
rst_file = open(rst, 'r')
|
|
|
|
in_option_block = False
|
|
|
|
prev_option = None
|
|
|
|
for line in rst_file:
|
|
|
|
if 'Option ' in line:
|
|
|
|
in_option_block = True
|
|
|
|
if in_option_block:
|
|
|
|
if '========' in line:
|
|
|
|
in_option_block = False
|
|
|
|
continue
|
|
|
|
if line[0] == ' ' and prev_option is not None:
|
Make swift config tables the source of truth
As discussed on the mailing list, this patch will make the swift
configuration tables found in common a source of truth for the
helptext. The script that generates them has been updated for this,
and will now only add/remove options, update default values, and
replace helptext where it does not exist in the tables. Another
run of the script was done and tables were updated.
Backstory: All projects other than Swift use OpenStack Common for
configuration, and define option, default value and help text in the
code in a way that it's possible to extract.
Since the code is able to act in this way, we can stop maintaining
separate instructive lines for configuration options, and instead
fix any text problems in the code itself. This both improves the
quality of the code and fixes our double maintenance problem.
For swift, we needed a different approach. Unfortunately, I think we
don't have the ability to treat the code as the definitive source and
move all maintenance there. The lack of instruction for every option,
and absence of structure precludes this.
So I wrote some nasty scraping things (from RST and sample conf file)
to seed an initial list of configuration options.
My plan from here was to make the 'update' portion of the script
treat the textual descriptions in common/tables/swift-*.xml as
definitive.
The script would still search the swift code to add or remove
options, so we could guarantee completeness, and after an initial
push to write out proper help text the maintenance becomes far
simpler.
Change-Id: I2464f5c63cb0da110e1871a09a59380dad9b6b27
2013-09-03 10:39:38 +10:00
|
|
|
option_descs[prev_option] = (option_descs[prev_option]
|
|
|
|
+ ' ' + line.strip())
|
2013-08-21 12:30:47 +10:00
|
|
|
for option in options:
|
|
|
|
line_parts = line.strip().split(None, 2)
|
2013-12-18 21:23:12 +01:00
|
|
|
if (' ' in line and
|
|
|
|
len(line_parts) == 3 and
|
|
|
|
option == line_parts[0] and
|
|
|
|
line_parts[1] != '=' and
|
|
|
|
option != 'use' and
|
|
|
|
(option not in option_descs or
|
2013-08-21 12:30:47 +10:00
|
|
|
len(option_descs[option]) < len(line_parts[2]))):
|
2013-12-18 21:23:12 +01:00
|
|
|
option_descs[option] = line_parts[2]
|
|
|
|
prev_option = option
|
2013-08-21 12:30:47 +10:00
|
|
|
return option_descs
|
|
|
|
|
Make swift config tables the source of truth
As discussed on the mailing list, this patch will make the swift
configuration tables found in common a source of truth for the
helptext. The script that generates them has been updated for this,
and will now only add/remove options, update default values, and
replace helptext where it does not exist in the tables. Another
run of the script was done and tables were updated.
Backstory: All projects other than Swift use OpenStack Common for
configuration, and define option, default value and help text in the
code in a way that it's possible to extract.
Since the code is able to act in this way, we can stop maintaining
separate instructive lines for configuration options, and instead
fix any text problems in the code itself. This both improves the
quality of the code and fixes our double maintenance problem.
For swift, we needed a different approach. Unfortunately, I think we
don't have the ability to treat the code as the definitive source and
move all maintenance there. The lack of instruction for every option,
and absence of structure precludes this.
So I wrote some nasty scraping things (from RST and sample conf file)
to seed an initial list of configuration options.
My plan from here was to make the 'update' portion of the script
treat the textual descriptions in common/tables/swift-*.xml as
definitive.
The script would still search the swift code to add or remove
options, so we could guarantee completeness, and after an initial
push to write out proper help text the maintenance becomes far
simpler.
Change-Id: I2464f5c63cb0da110e1871a09a59380dad9b6b27
2013-09-03 10:39:38 +10:00
|
|
|
|
2013-08-21 12:30:47 +10:00
|
|
|
def new_section_file(sample, current_section):
|
2013-12-18 21:23:12 +01:00
|
|
|
section_filename = ('swift-' +
|
|
|
|
path.basename(sample).split('.conf')[0]
|
|
|
|
+ '-'
|
|
|
|
+ current_section.replace('[', '').
|
|
|
|
replace(']', '').replace(':', '-')
|
|
|
|
+ '.xml')
|
|
|
|
section_file = open(section_filename, 'w')
|
|
|
|
section_file.write('<?xml version="1.0" encoding="UTF-8"?>\n\
|
Make swift config tables the source of truth
As discussed on the mailing list, this patch will make the swift
configuration tables found in common a source of truth for the
helptext. The script that generates them has been updated for this,
and will now only add/remove options, update default values, and
replace helptext where it does not exist in the tables. Another
run of the script was done and tables were updated.
Backstory: All projects other than Swift use OpenStack Common for
configuration, and define option, default value and help text in the
code in a way that it's possible to extract.
Since the code is able to act in this way, we can stop maintaining
separate instructive lines for configuration options, and instead
fix any text problems in the code itself. This both improves the
quality of the code and fixes our double maintenance problem.
For swift, we needed a different approach. Unfortunately, I think we
don't have the ability to treat the code as the definitive source and
move all maintenance there. The lack of instruction for every option,
and absence of structure precludes this.
So I wrote some nasty scraping things (from RST and sample conf file)
to seed an initial list of configuration options.
My plan from here was to make the 'update' portion of the script
treat the textual descriptions in common/tables/swift-*.xml as
definitive.
The script would still search the swift code to add or remove
options, so we could guarantee completeness, and after an initial
push to write out proper help text the maintenance becomes far
simpler.
Change-Id: I2464f5c63cb0da110e1871a09a59380dad9b6b27
2013-09-03 10:39:38 +10:00
|
|
|
<!-- The tool that generated this table lives in the\n\
|
|
|
|
tools directory of this repository. As it was a one-time\n\
|
|
|
|
generation, you can edit this file. -->\n\
|
2013-08-21 12:30:47 +10:00
|
|
|
<para xmlns="http://docbook.org/ns/docbook" version="5.0">\n\
|
|
|
|
<table rules="all">\n\
|
|
|
|
<caption>Description of configuration options for <literal>'
|
2013-12-18 21:23:12 +01:00
|
|
|
+ current_section + '</literal> in <literal>'
|
|
|
|
+ path.basename(sample) +
|
|
|
|
'</literal></caption>\n\
|
|
|
|
<col width="50%"/>\n\
|
2013-08-21 12:30:47 +10:00
|
|
|
<col width="50%"/>\n\
|
|
|
|
<thead>\n\
|
|
|
|
<tr>\n\
|
|
|
|
<td>Configuration option=Default value</td>\n\
|
|
|
|
<td>Description</td>\n\
|
|
|
|
</tr>\n\
|
|
|
|
</thead>\n\
|
|
|
|
<tbody>')
|
2013-12-18 21:23:12 +01:00
|
|
|
return section_file
|
2013-08-21 12:30:47 +10:00
|
|
|
|
Make swift config tables the source of truth
As discussed on the mailing list, this patch will make the swift
configuration tables found in common a source of truth for the
helptext. The script that generates them has been updated for this,
and will now only add/remove options, update default values, and
replace helptext where it does not exist in the tables. Another
run of the script was done and tables were updated.
Backstory: All projects other than Swift use OpenStack Common for
configuration, and define option, default value and help text in the
code in a way that it's possible to extract.
Since the code is able to act in this way, we can stop maintaining
separate instructive lines for configuration options, and instead
fix any text problems in the code itself. This both improves the
quality of the code and fixes our double maintenance problem.
For swift, we needed a different approach. Unfortunately, I think we
don't have the ability to treat the code as the definitive source and
move all maintenance there. The lack of instruction for every option,
and absence of structure precludes this.
So I wrote some nasty scraping things (from RST and sample conf file)
to seed an initial list of configuration options.
My plan from here was to make the 'update' portion of the script
treat the textual descriptions in common/tables/swift-*.xml as
definitive.
The script would still search the swift code to add or remove
options, so we could guarantee completeness, and after an initial
push to write out proper help text the maintenance becomes far
simpler.
Change-Id: I2464f5c63cb0da110e1871a09a59380dad9b6b27
2013-09-03 10:39:38 +10:00
|
|
|
|
|
|
|
def create_new_tables(repo, verbose):
|
|
|
|
"""
|
|
|
|
writes a set of docbook-formatted tables, one per section in swift
|
|
|
|
configuration files. Uses existing tables and swift devref as a source
|
|
|
|
of truth in that order to determine helptext for options found in
|
|
|
|
sample config files
|
|
|
|
"""
|
2013-09-07 12:29:27 -07:00
|
|
|
existing_tables = glob.glob('../../doc/common/tables/swift*xml')
|
Make swift config tables the source of truth
As discussed on the mailing list, this patch will make the swift
configuration tables found in common a source of truth for the
helptext. The script that generates them has been updated for this,
and will now only add/remove options, update default values, and
replace helptext where it does not exist in the tables. Another
run of the script was done and tables were updated.
Backstory: All projects other than Swift use OpenStack Common for
configuration, and define option, default value and help text in the
code in a way that it's possible to extract.
Since the code is able to act in this way, we can stop maintaining
separate instructive lines for configuration options, and instead
fix any text problems in the code itself. This both improves the
quality of the code and fixes our double maintenance problem.
For swift, we needed a different approach. Unfortunately, I think we
don't have the ability to treat the code as the definitive source and
move all maintenance there. The lack of instruction for every option,
and absence of structure precludes this.
So I wrote some nasty scraping things (from RST and sample conf file)
to seed an initial list of configuration options.
My plan from here was to make the 'update' portion of the script
treat the textual descriptions in common/tables/swift-*.xml as
definitive.
The script would still search the swift code to add or remove
options, so we could guarantee completeness, and after an initial
push to write out proper help text the maintenance becomes far
simpler.
Change-Id: I2464f5c63cb0da110e1871a09a59380dad9b6b27
2013-09-03 10:39:38 +10:00
|
|
|
options = {}
|
|
|
|
#use the existing tables to get a list of option names
|
|
|
|
options = get_existing_options(existing_tables)
|
2013-08-21 12:30:47 +10:00
|
|
|
option_descs = extract_descriptions_from_devref(repo, options)
|
Make swift config tables the source of truth
As discussed on the mailing list, this patch will make the swift
configuration tables found in common a source of truth for the
helptext. The script that generates them has been updated for this,
and will now only add/remove options, update default values, and
replace helptext where it does not exist in the tables. Another
run of the script was done and tables were updated.
Backstory: All projects other than Swift use OpenStack Common for
configuration, and define option, default value and help text in the
code in a way that it's possible to extract.
Since the code is able to act in this way, we can stop maintaining
separate instructive lines for configuration options, and instead
fix any text problems in the code itself. This both improves the
quality of the code and fixes our double maintenance problem.
For swift, we needed a different approach. Unfortunately, I think we
don't have the ability to treat the code as the definitive source and
move all maintenance there. The lack of instruction for every option,
and absence of structure precludes this.
So I wrote some nasty scraping things (from RST and sample conf file)
to seed an initial list of configuration options.
My plan from here was to make the 'update' portion of the script
treat the textual descriptions in common/tables/swift-*.xml as
definitive.
The script would still search the swift code to add or remove
options, so we could guarantee completeness, and after an initial
push to write out proper help text the maintenance becomes far
simpler.
Change-Id: I2464f5c63cb0da110e1871a09a59380dad9b6b27
2013-09-03 10:39:38 +10:00
|
|
|
conf_samples = glob.glob(repo + '/etc/*conf-sample')
|
2013-08-21 12:30:47 +10:00
|
|
|
for sample in conf_samples:
|
|
|
|
current_section = None
|
|
|
|
section_file = None
|
Make swift config tables the source of truth
As discussed on the mailing list, this patch will make the swift
configuration tables found in common a source of truth for the
helptext. The script that generates them has been updated for this,
and will now only add/remove options, update default values, and
replace helptext where it does not exist in the tables. Another
run of the script was done and tables were updated.
Backstory: All projects other than Swift use OpenStack Common for
configuration, and define option, default value and help text in the
code in a way that it's possible to extract.
Since the code is able to act in this way, we can stop maintaining
separate instructive lines for configuration options, and instead
fix any text problems in the code itself. This both improves the
quality of the code and fixes our double maintenance problem.
For swift, we needed a different approach. Unfortunately, I think we
don't have the ability to treat the code as the definitive source and
move all maintenance there. The lack of instruction for every option,
and absence of structure precludes this.
So I wrote some nasty scraping things (from RST and sample conf file)
to seed an initial list of configuration options.
My plan from here was to make the 'update' portion of the script
treat the textual descriptions in common/tables/swift-*.xml as
definitive.
The script would still search the swift code to add or remove
options, so we could guarantee completeness, and after an initial
push to write out proper help text the maintenance becomes far
simpler.
Change-Id: I2464f5c63cb0da110e1871a09a59380dad9b6b27
2013-09-03 10:39:38 +10:00
|
|
|
sample_file = open(sample, 'r')
|
2013-08-21 12:30:47 +10:00
|
|
|
for line in sample_file:
|
|
|
|
if '[' in line and ']\n' in line and '=' not in line:
|
Make swift config tables the source of truth
As discussed on the mailing list, this patch will make the swift
configuration tables found in common a source of truth for the
helptext. The script that generates them has been updated for this,
and will now only add/remove options, update default values, and
replace helptext where it does not exist in the tables. Another
run of the script was done and tables were updated.
Backstory: All projects other than Swift use OpenStack Common for
configuration, and define option, default value and help text in the
code in a way that it's possible to extract.
Since the code is able to act in this way, we can stop maintaining
separate instructive lines for configuration options, and instead
fix any text problems in the code itself. This both improves the
quality of the code and fixes our double maintenance problem.
For swift, we needed a different approach. Unfortunately, I think we
don't have the ability to treat the code as the definitive source and
move all maintenance there. The lack of instruction for every option,
and absence of structure precludes this.
So I wrote some nasty scraping things (from RST and sample conf file)
to seed an initial list of configuration options.
My plan from here was to make the 'update' portion of the script
treat the textual descriptions in common/tables/swift-*.xml as
definitive.
The script would still search the swift code to add or remove
options, so we could guarantee completeness, and after an initial
push to write out proper help text the maintenance becomes far
simpler.
Change-Id: I2464f5c63cb0da110e1871a09a59380dad9b6b27
2013-09-03 10:39:38 +10:00
|
|
|
"""
|
|
|
|
it's a header line in the conf file, open a new table file
|
|
|
|
for this section and close any existing one
|
|
|
|
"""
|
2013-08-21 12:30:47 +10:00
|
|
|
if current_section != line.strip('#').strip():
|
|
|
|
if section_file is not None:
|
|
|
|
section_file.write('\n </tbody>\n\
|
|
|
|
</table>\n\
|
|
|
|
</para>')
|
|
|
|
section_file.close()
|
Make swift config tables the source of truth
As discussed on the mailing list, this patch will make the swift
configuration tables found in common a source of truth for the
helptext. The script that generates them has been updated for this,
and will now only add/remove options, update default values, and
replace helptext where it does not exist in the tables. Another
run of the script was done and tables were updated.
Backstory: All projects other than Swift use OpenStack Common for
configuration, and define option, default value and help text in the
code in a way that it's possible to extract.
Since the code is able to act in this way, we can stop maintaining
separate instructive lines for configuration options, and instead
fix any text problems in the code itself. This both improves the
quality of the code and fixes our double maintenance problem.
For swift, we needed a different approach. Unfortunately, I think we
don't have the ability to treat the code as the definitive source and
move all maintenance there. The lack of instruction for every option,
and absence of structure precludes this.
So I wrote some nasty scraping things (from RST and sample conf file)
to seed an initial list of configuration options.
My plan from here was to make the 'update' portion of the script
treat the textual descriptions in common/tables/swift-*.xml as
definitive.
The script would still search the swift code to add or remove
options, so we could guarantee completeness, and after an initial
push to write out proper help text the maintenance becomes far
simpler.
Change-Id: I2464f5c63cb0da110e1871a09a59380dad9b6b27
2013-09-03 10:39:38 +10:00
|
|
|
current_section = line.strip('#').strip()
|
2013-08-21 12:30:47 +10:00
|
|
|
section_file = new_section_file(sample, current_section)
|
|
|
|
elif section_file is not None:
|
Make swift config tables the source of truth
As discussed on the mailing list, this patch will make the swift
configuration tables found in common a source of truth for the
helptext. The script that generates them has been updated for this,
and will now only add/remove options, update default values, and
replace helptext where it does not exist in the tables. Another
run of the script was done and tables were updated.
Backstory: All projects other than Swift use OpenStack Common for
configuration, and define option, default value and help text in the
code in a way that it's possible to extract.
Since the code is able to act in this way, we can stop maintaining
separate instructive lines for configuration options, and instead
fix any text problems in the code itself. This both improves the
quality of the code and fixes our double maintenance problem.
For swift, we needed a different approach. Unfortunately, I think we
don't have the ability to treat the code as the definitive source and
move all maintenance there. The lack of instruction for every option,
and absence of structure precludes this.
So I wrote some nasty scraping things (from RST and sample conf file)
to seed an initial list of configuration options.
My plan from here was to make the 'update' portion of the script
treat the textual descriptions in common/tables/swift-*.xml as
definitive.
The script would still search the swift code to add or remove
options, so we could guarantee completeness, and after an initial
push to write out proper help text the maintenance becomes far
simpler.
Change-Id: I2464f5c63cb0da110e1871a09a59380dad9b6b27
2013-09-03 10:39:38 +10:00
|
|
|
"""
|
|
|
|
it's a config option line in the conf file, find out the
|
|
|
|
help text and write to the table file.
|
|
|
|
"""
|
2013-08-21 12:30:47 +10:00
|
|
|
parsed_line = parse_line(line)
|
|
|
|
if parsed_line is not None:
|
Make swift config tables the source of truth
As discussed on the mailing list, this patch will make the swift
configuration tables found in common a source of truth for the
helptext. The script that generates them has been updated for this,
and will now only add/remove options, update default values, and
replace helptext where it does not exist in the tables. Another
run of the script was done and tables were updated.
Backstory: All projects other than Swift use OpenStack Common for
configuration, and define option, default value and help text in the
code in a way that it's possible to extract.
Since the code is able to act in this way, we can stop maintaining
separate instructive lines for configuration options, and instead
fix any text problems in the code itself. This both improves the
quality of the code and fixes our double maintenance problem.
For swift, we needed a different approach. Unfortunately, I think we
don't have the ability to treat the code as the definitive source and
move all maintenance there. The lack of instruction for every option,
and absence of structure precludes this.
So I wrote some nasty scraping things (from RST and sample conf file)
to seed an initial list of configuration options.
My plan from here was to make the 'update' portion of the script
treat the textual descriptions in common/tables/swift-*.xml as
definitive.
The script would still search the swift code to add or remove
options, so we could guarantee completeness, and after an initial
push to write out proper help text the maintenance becomes far
simpler.
Change-Id: I2464f5c63cb0da110e1871a09a59380dad9b6b27
2013-09-03 10:39:38 +10:00
|
|
|
if (parsed_line[0] in options.keys()
|
|
|
|
and 'No help text' not in options[parsed_line[0]]):
|
|
|
|
# use the help text from existing tables
|
2013-12-18 21:23:12 +01:00
|
|
|
option_desc = options[parsed_line[0]].replace(u'\xa0',
|
|
|
|
u' ')
|
Make swift config tables the source of truth
As discussed on the mailing list, this patch will make the swift
configuration tables found in common a source of truth for the
helptext. The script that generates them has been updated for this,
and will now only add/remove options, update default values, and
replace helptext where it does not exist in the tables. Another
run of the script was done and tables were updated.
Backstory: All projects other than Swift use OpenStack Common for
configuration, and define option, default value and help text in the
code in a way that it's possible to extract.
Since the code is able to act in this way, we can stop maintaining
separate instructive lines for configuration options, and instead
fix any text problems in the code itself. This both improves the
quality of the code and fixes our double maintenance problem.
For swift, we needed a different approach. Unfortunately, I think we
don't have the ability to treat the code as the definitive source and
move all maintenance there. The lack of instruction for every option,
and absence of structure precludes this.
So I wrote some nasty scraping things (from RST and sample conf file)
to seed an initial list of configuration options.
My plan from here was to make the 'update' portion of the script
treat the textual descriptions in common/tables/swift-*.xml as
definitive.
The script would still search the swift code to add or remove
options, so we could guarantee completeness, and after an initial
push to write out proper help text the maintenance becomes far
simpler.
Change-Id: I2464f5c63cb0da110e1871a09a59380dad9b6b27
2013-09-03 10:39:38 +10:00
|
|
|
elif parsed_line[0] in option_descs:
|
|
|
|
# use the help text from the devref
|
2013-12-18 21:23:12 +01:00
|
|
|
option_desc = option_descs[parsed_line[0]].replace(
|
|
|
|
u'\xa0', u' ')
|
2013-08-21 12:30:47 +10:00
|
|
|
else:
|
|
|
|
option_desc = 'No help text available for this option'
|
Make swift config tables the source of truth
As discussed on the mailing list, this patch will make the swift
configuration tables found in common a source of truth for the
helptext. The script that generates them has been updated for this,
and will now only add/remove options, update default values, and
replace helptext where it does not exist in the tables. Another
run of the script was done and tables were updated.
Backstory: All projects other than Swift use OpenStack Common for
configuration, and define option, default value and help text in the
code in a way that it's possible to extract.
Since the code is able to act in this way, we can stop maintaining
separate instructive lines for configuration options, and instead
fix any text problems in the code itself. This both improves the
quality of the code and fixes our double maintenance problem.
For swift, we needed a different approach. Unfortunately, I think we
don't have the ability to treat the code as the definitive source and
move all maintenance there. The lack of instruction for every option,
and absence of structure precludes this.
So I wrote some nasty scraping things (from RST and sample conf file)
to seed an initial list of configuration options.
My plan from here was to make the 'update' portion of the script
treat the textual descriptions in common/tables/swift-*.xml as
definitive.
The script would still search the swift code to add or remove
options, so we could guarantee completeness, and after an initial
push to write out proper help text the maintenance becomes far
simpler.
Change-Id: I2464f5c63cb0da110e1871a09a59380dad9b6b27
2013-09-03 10:39:38 +10:00
|
|
|
if verbose > 0:
|
|
|
|
print parsed_line[0] + "has no help text"
|
2013-08-21 12:30:47 +10:00
|
|
|
section_file.write('\n <tr>\n\
|
Make swift config tables the source of truth
As discussed on the mailing list, this patch will make the swift
configuration tables found in common a source of truth for the
helptext. The script that generates them has been updated for this,
and will now only add/remove options, update default values, and
replace helptext where it does not exist in the tables. Another
run of the script was done and tables were updated.
Backstory: All projects other than Swift use OpenStack Common for
configuration, and define option, default value and help text in the
code in a way that it's possible to extract.
Since the code is able to act in this way, we can stop maintaining
separate instructive lines for configuration options, and instead
fix any text problems in the code itself. This both improves the
quality of the code and fixes our double maintenance problem.
For swift, we needed a different approach. Unfortunately, I think we
don't have the ability to treat the code as the definitive source and
move all maintenance there. The lack of instruction for every option,
and absence of structure precludes this.
So I wrote some nasty scraping things (from RST and sample conf file)
to seed an initial list of configuration options.
My plan from here was to make the 'update' portion of the script
treat the textual descriptions in common/tables/swift-*.xml as
definitive.
The script would still search the swift code to add or remove
options, so we could guarantee completeness, and after an initial
push to write out proper help text the maintenance becomes far
simpler.
Change-Id: I2464f5c63cb0da110e1871a09a59380dad9b6b27
2013-09-03 10:39:38 +10:00
|
|
|
<td>' + parsed_line[0] + '=' +
|
|
|
|
escape(str(parsed_line[1])) +
|
|
|
|
'</td><td>' + option_desc + '</td>\n' +
|
|
|
|
' </tr>')
|
2013-08-21 12:30:47 +10:00
|
|
|
if section_file is not None:
|
|
|
|
section_file.write('\n </tbody>\n\
|
|
|
|
</table>\n\
|
|
|
|
</para>')
|
|
|
|
section_file.close()
|
Make swift config tables the source of truth
As discussed on the mailing list, this patch will make the swift
configuration tables found in common a source of truth for the
helptext. The script that generates them has been updated for this,
and will now only add/remove options, update default values, and
replace helptext where it does not exist in the tables. Another
run of the script was done and tables were updated.
Backstory: All projects other than Swift use OpenStack Common for
configuration, and define option, default value and help text in the
code in a way that it's possible to extract.
Since the code is able to act in this way, we can stop maintaining
separate instructive lines for configuration options, and instead
fix any text problems in the code itself. This both improves the
quality of the code and fixes our double maintenance problem.
For swift, we needed a different approach. Unfortunately, I think we
don't have the ability to treat the code as the definitive source and
move all maintenance there. The lack of instruction for every option,
and absence of structure precludes this.
So I wrote some nasty scraping things (from RST and sample conf file)
to seed an initial list of configuration options.
My plan from here was to make the 'update' portion of the script
treat the textual descriptions in common/tables/swift-*.xml as
definitive.
The script would still search the swift code to add or remove
options, so we could guarantee completeness, and after an initial
push to write out proper help text the maintenance becomes far
simpler.
Change-Id: I2464f5c63cb0da110e1871a09a59380dad9b6b27
2013-09-03 10:39:38 +10:00
|
|
|
|
2013-08-21 12:30:47 +10:00
|
|
|
|
|
|
|
def main(repo, verbose=0):
|
|
|
|
"""
|
|
|
|
writes a set of docbook-formatted files, based on configuration sections
|
|
|
|
in swift sample configuration files
|
|
|
|
"""
|
|
|
|
|
Make swift config tables the source of truth
As discussed on the mailing list, this patch will make the swift
configuration tables found in common a source of truth for the
helptext. The script that generates them has been updated for this,
and will now only add/remove options, update default values, and
replace helptext where it does not exist in the tables. Another
run of the script was done and tables were updated.
Backstory: All projects other than Swift use OpenStack Common for
configuration, and define option, default value and help text in the
code in a way that it's possible to extract.
Since the code is able to act in this way, we can stop maintaining
separate instructive lines for configuration options, and instead
fix any text problems in the code itself. This both improves the
quality of the code and fixes our double maintenance problem.
For swift, we needed a different approach. Unfortunately, I think we
don't have the ability to treat the code as the definitive source and
move all maintenance there. The lack of instruction for every option,
and absence of structure precludes this.
So I wrote some nasty scraping things (from RST and sample conf file)
to seed an initial list of configuration options.
My plan from here was to make the 'update' portion of the script
treat the textual descriptions in common/tables/swift-*.xml as
definitive.
The script would still search the swift code to add or remove
options, so we could guarantee completeness, and after an initial
push to write out proper help text the maintenance becomes far
simpler.
Change-Id: I2464f5c63cb0da110e1871a09a59380dad9b6b27
2013-09-03 10:39:38 +10:00
|
|
|
create_new_tables(repo, verbose)
|
2013-08-21 12:30:47 +10:00
|
|
|
|
2013-12-18 21:23:12 +01:00
|
|
|
if __name__ == "__main__":
|
2013-08-21 12:30:47 +10:00
|
|
|
main(sys.argv[1])
|