[Openstack-devel] Bug#708747: [RFR] templates://ceilometer/{ceilometer-api.templates}

Christian PERRIER bubulle at debian.org
Sat Jun 1 05:20:19 UTC 2013


Please find, for review, the debconf templates for the ceilometer source package.

This review will last from Saturday, June 01, 2013 to Tuesday, June 11, 2013.

Please send reviews as unified diffs (diff -u) against the original
files. Comments about your proposed changes will be appreciated.

Your review should be sent as an answer to this mail.

When appropriate, I will send intermediate requests for review, with
"[RFRn]" (n>=2) as a subject tag.

When we will reach a consensus, I send a "Last Chance For
Comments" mail with "[LCFC]" as a subject tag.

Finally, a summary will be sent to the review bug report,
and a mail will be sent to this list with "[BTS]" as a subject tag.

Rationale:
--- ceilometer.old/debian/ceilometer-api.templates	2013-05-18 13:40:43.837128341 +0300
+++ ceilometer/debian/ceilometer-api.templates	2013-05-24 11:19:12.743085643 +0300
@@ -1,31 +1,31 @@
 Template: ceilometer/register-endpoint
 Type: boolean
 Default: false
-_Description: Register Ceilometer in the keystone endpoint catalog?
- Each Openstack services (each API) should be registered in order to be
+_Description: Register Ceilometer in the Keystone endpoint catalog?
+ Each Openstack service (each API) should be registered in order to be
  accessible. This is done using "keystone service-create" and "keystone
- endpoint-create". Select if you want to run these commands now.
+ endpoint-create". This can be done automatically now.
  .
- Note that you will need to have an up and running keystone server on which to
- connect using the Keystone auth token.
+ Note that you will need to have an up and running Keystone server on which to
+ connect using the Keystone authentication token.

These proposed changes will be common to several other
Openstack-related packages.

normalize on "Keystone" with a capital "K"

"each" --> singular

"Select": select what? The point is indeed that the action will be
done if one answers positively to the question. So, just say this.

 
 Template: ceilometer/keystone-ip
 Type: string
-_Description: Keystone IP address:
- Enter the IP address of your keystone server, so that ceilometer-api can
+_Description: Keystone server IP address:
+ Please enter the IP address of the Keystone server, so that ceilometer-api can
  contact Keystone to do the Ceilometer service and endpoint creation.

This is the address of the Keystone *server*, I guess.

Use our standard "Please enter" formulation.

 
 Template: ceilometer/keystone-auth-token
 Type: password
 _Description: Keystone Auth Token:
- To configure its endpoint in Keystone, ceilometer-api needs the Keystone auth
- token.
+_Description: Keystone authentication token:
+ To configure its endpoint in Keystone, ceilometer-api needs the Keystone
+ authentication token.

Do not use abbreviations. And ungermanize the synopsis..:-)
 
 Template: ceilometer/endpoint-ip
 Type: string
 _Description: Ceilometer endpoint IP address:
- Enter the IP address that will be used to contact Ceilometer (eg: the
- Ceilometer endpoint IP address).
+ Please enter the IP address that will be used to contact Ceilometer.
  .
  This IP address should be accessible from the clients that will use this
  service, so if you are installing a public cloud, this should be a public

Use "please enter".

Drop the "eg" part : "eg" is a latinism and would anyway mean "for
example" while the address *is* the contact address, period. One could
eventually say something like "also named the Ceilometer endpoint IP
address" but I don't really see the need tom make things look more
complicated than they are.

-- 


-------------- next part --------------
Template: ceilometer/register-endpoint
Type: boolean
Default: false
_Description: Register Ceilometer in the Keystone endpoint catalog?
 Each Openstack service (each API) should be registered in order to be
 accessible. This is done using "keystone service-create" and "keystone
 endpoint-create". This can be done automatically now.
 .
 Note that you will need to have an up and running Keystone server on which to
 connect using the Keystone authentication token.

Template: ceilometer/keystone-ip
Type: string
_Description: Keystone server IP address:
 Please enter the IP address of the Keystone server, so that ceilometer-api can
 contact Keystone to do the Ceilometer service and endpoint creation.

Template: ceilometer/keystone-auth-token
Type: password
_Description: Keystone Auth Token:
_Description: Keystone authentication token:
 To configure its endpoint in Keystone, ceilometer-api needs the Keystone
 authentication token.

Template: ceilometer/endpoint-ip
Type: string
_Description: Ceilometer endpoint IP address:
 Please enter the IP address that will be used to contact Ceilometer.
 .
 This IP address should be accessible from the clients that will use this
 service, so if you are installing a public cloud, this should be a public
 IP address.

Template: ceilometer/region-name
Type: string
Default: regionOne
_Description: Name of the region to register:
 Openstack can be used using availability zones, with each region representing
 a location. Please enter the zone that you wish to use when registering the
 endpoint.
-------------- next part --------------
--- ceilometer.old/debian/ceilometer-api.templates	2013-05-18 13:40:43.837128341 +0300
+++ ceilometer/debian/ceilometer-api.templates	2013-05-24 11:19:12.743085643 +0300
@@ -1,31 +1,31 @@
 Template: ceilometer/register-endpoint
 Type: boolean
 Default: false
-_Description: Register Ceilometer in the keystone endpoint catalog?
- Each Openstack services (each API) should be registered in order to be
+_Description: Register Ceilometer in the Keystone endpoint catalog?
+ Each Openstack service (each API) should be registered in order to be
  accessible. This is done using "keystone service-create" and "keystone
- endpoint-create". Select if you want to run these commands now.
+ endpoint-create". This can be done automatically now.
  .
- Note that you will need to have an up and running keystone server on which to
- connect using the Keystone auth token.
+ Note that you will need to have an up and running Keystone server on which to
+ connect using the Keystone authentication token.
 
 Template: ceilometer/keystone-ip
 Type: string
-_Description: Keystone IP address:
- Enter the IP address of your keystone server, so that ceilometer-api can
+_Description: Keystone server IP address:
+ Please enter the IP address of the Keystone server, so that ceilometer-api can
  contact Keystone to do the Ceilometer service and endpoint creation.
 
 Template: ceilometer/keystone-auth-token
 Type: password
 _Description: Keystone Auth Token:
- To configure its endpoint in Keystone, ceilometer-api needs the Keystone auth
- token.
+_Description: Keystone authentication token:
+ To configure its endpoint in Keystone, ceilometer-api needs the Keystone
+ authentication token.
 
 Template: ceilometer/endpoint-ip
 Type: string
 _Description: Ceilometer endpoint IP address:
- Enter the IP address that will be used to contact Ceilometer (eg: the
- Ceilometer endpoint IP address).
+ Please enter the IP address that will be used to contact Ceilometer.
  .
  This IP address should be accessible from the clients that will use this
  service, so if you are installing a public cloud, this should be a public
-------------- next part --------------
Source: ceilometer
Section: web
Priority: optional
Maintainer: PKG OpenStack <openstack-devel at lists.alioth.debian.org>
Uploaders: Loic Dachary (OuoU) <loic at debian.org>,
           Julien Danjou <acid at debian.org>,
           Thomas Goirand <zigo at debian.org>,
           Ghe Rivero <ghe.rivero at stackops.com>,
           Mehdi Abaakouk <sileht at sileht.net>
Build-Depends: debhelper (>= 9),
 po-debconf,
 python-all (>= 2.6.6-3~),
 openstack-pkg-tools
Build-Depends-Indep: pep8,
 python-argparse,
 python-anyjson (>= 0.2.4),
 python-babel,
 python-coverage,
 python-docutils,
 python-eventlet,
 python-extras,
 python-flask (>= 0.9),
 python-glance (>= 2013.1~),
 python-glanceclient (>= 1:0.6),
 python-iso8601,
 python-keystoneclient (>= 1:0.2.3),
 python-kombu,  
 python-lockfile,
 python-lxml,
 python-ming,
 python-mock,
 python-mox,   
 python-netaddr,
 python-netifaces,
 python-nose,
 python-nova (>= 2013.1~),
 python-novaclient (>= 2:2.6.10),
 python-oslo.config,
 python-pecan (>= 0.2.1),
 python-pymongo,
 python-requests,
 python-setuptools-git,
 python-sphinx,
 python-sqlalchemy (>= 0.7.3),
 python-sqlalchemy (<< 0.8.0~),
 python-stevedore (>= 0.6),
 python-swiftclient,
 python-unittest2,
 python-webob (>= 1.2),
 python-wsme,
 python-yaml
Standards-Version: 3.9.3
Vcs-Browser: http://anonscm.debian.org/gitweb/?p=openstack/ceilometer.git;a=summary
Vcs-Git: git://anonscm.debian.org/openstack/ceilometer.git
Homepage: http://wiki.openstack.org/Ceilometer

Package: python-ceilometer
Section: python
Architecture: all
Pre-Depends: dpkg (>= 1.15.6~)
Depends: ${python:Depends}, ${misc:Depends},
 libjs-jquery,
 python-argparse,
 python-anyjson (>= 0.2.4),
 python-eventlet,
 python-extras,
 python-flask (>= 0.9),
 python-glanceclient (>= 1:0.6),
 python-greenlet (>= 0.4),
 python-keystoneclient (>= 1:0.2.3),
 python-iso8601,
 python-kombu,
 python-lockfile,
 python-lxml,
 python-netaddr,
 python-novaclient (>= 2:2.6.10),
 python-oslo.config,
 python-pecan (>= 0.2.1),
 python-pymongo (>= 2.2),
 python-requests,
 python-sqlalchemy (>= 0.7.3),
 python-sqlalchemy (<< 0.8.0~),
 python-stevedore (>= 0.6),
 python-swiftclient,
 python-webob (>= 1.2),
 python-yaml
Description: OpenStack efficient metering counters system - Python libraries
 Ceilometer aims to deliver a Single Point Of Contact for billing systems,
 providing all the counters they need to establish customer billing, accross
 all current and future OpenStack components. The delivery of counters must be
 traceable and auditable, the counters must be easily extensible to support new
 projects, and agents doing data collections should be independent of the
 overall system.
 .
 This package contains the Python libraries that are needed for all parts of
 Ceilometer.

Package: ceilometer-common
Architecture: all
Pre-Depends: dpkg (>= 1.15.6~)
Depends: python-ceilometer (= ${binary:Version}), ${python:Depends}, ${misc:Depends}, adduser
Provides: ${python:Provides}
Description: OpenStack efficient metering counters system - common files
 Ceilometer aims to deliver a Single Point Of Contact for billing systems,
 providing all the counters they need to establish customer billing, accross
 all current and future OpenStack components. The delivery of counters must be
 traceable and auditable, the counters must be easily extensible to support new
 projects, and agents doing data collections should be independent of the
 overall system.
 .
 This package contains files that are needed for all parts of Ceilometer.

Package: ceilometer-collector
Architecture: all
Pre-Depends: dpkg (>= 1.15.6~)
Depends: ${ostack-lsb-base}, ceilometer-common (= ${binary:Version}), ${python:Depends}, ${misc:Depends}
Description: OpenStack efficient metering counters system - collector service
 Ceilometer aims to deliver a Single Point Of Contact for billing systems,
 providing all the counters they need to establish customer billing, accross
 all current and future OpenStack components. The delivery of counters must be
 traceable and auditable, the counters must be easily extensible to support new
 projects, and agents doing data collections should be independent of the
 overall system.
 .
 This package contains the collector service.

Package: ceilometer-api
Architecture: all
Pre-Depends: dpkg (>= 1.15.6~)
Depends: adduser, debconf, ${ostack-lsb-base}, ceilometer-common (= ${binary:Version}), ${python:Depends}, ${misc:Depends}
Description: OpenStack efficient metering counters system (API service)
 Ceilometer aims to deliver a Single Point Of Contact for billing systems,
 providing all the counters they need to establish customer billing, accross
 all current and future OpenStack components. The delivery of counters must be
 traceable and auditable, the counters must be easily extensible to support new
 projects, and agents doing data collections should be independent of the
 overall system.
 .
 This package contains the API service.

Package: ceilometer-agent-compute
Architecture: all
Pre-Depends: dpkg (>= 1.15.6~)
Depends: ${ostack-lsb-base}, ceilometer-common (= ${binary:Version}), ${python:Depends}, ${misc:Depends}
Description: OpenStack efficient metering counters system - compute agent
 Ceilometer aims to deliver a Single Point Of Contact for billing systems,
 providing all the counters they need to establish customer billing, accross
 all current and future OpenStack components. The delivery of counters must be
 traceable and auditable, the counters must be easily extensible to support new
 projects, and agents doing data collections should be independent of the
 overall system.
 .
 This package contains the compute agent.

Package: ceilometer-agent-central
Architecture: all
Pre-Depends: dpkg (>= 1.15.6~)
Depends: ${ostack-lsb-base}, ceilometer-common (= ${binary:Version}), ${python:Depends},
 ${misc:Depends}
Description: OpenStack efficient metering counters system - central agent
 Ceilometer aims to deliver a Single Point Of Contact for billing systems,
 providing all the counters they need to establish customer billing, accross
 all current and future OpenStack components. The delivery of counters must be
 traceable and auditable, the counters must be easily extensible to support new
 projects, and agents doing data collections should be independent of the
 overall system.
 .
 This package contains the central agent.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/openstack-devel/attachments/20130601/7f022936/attachment-0001.pgp>


More information about the Openstack-devel mailing list