Dear Debian maintainer, On Wednesday, May 22, 2013, I notified you of the beginning of a review process concerning debconf templates for heat.
The debian-l10n-english contributors have now reviewed these templates, and the final proposed changes are attached to this update to the original bug report. Please review the suggested changes, and if you have any objections, let me know in the next 3 days. However, please try to avoid uploading heat with these changes right now. The second phase of this process will begin on Wednesday, June 19, 2013, when I will coordinate updates to translations of debconf templates. The existing translators will be notified of the changes: they will receive an updated PO file for their language. Simultaneously, a general call for new translations will be sent to the debian-i18n mailing list. Both these calls for translations will request updates to be sent as individual bug reports. That will probably trigger a lot of bug reports against your package, but these should be easier to deal with. The call for translation updates and new translations will run until about Wednesday, July 10, 2013. Please avoid uploading a package with fixed or changed debconf templates and/or translation updates in the meantime. Of course, other changes are safe. Please note that this is an approximative delay, which depends on my own availability to process this work and is influenced by the fact that I simultaneously work on many packages. Around Thursday, July 11, 2013, I will contact you again and will send a final patch summarizing all the updates (changes to debconf templates, updates to debconf translations and new debconf translations). Again, thanks for your attention and cooperation. --
# These templates have been reviewed by the debian-l10n-english
# team
#
# If modifications/additions/rewording are needed, please ask
# debian-l10n-engl...@lists.debian.org for advice.
#
# Even minor modifications require translation updates and such
# changes should be coordinated with translators and reviewers.
Template: heat/configure_db
Type: boolean
Default: true
_Description: Set up a database for heat-engine?
No database has been set up for heat-engine to use. Before
continuing, you should make sure you have the following information:
.
* the type of database that you want to use;
* the database server host name (that server must allow TCP connections from
this
machine);
* a username and password to access the database.
.
If some of these requirements are missing, do not choose this option and run
with
regular SQLite support.
.
You can change this setting later on by running "dpkg-reconfigure -plow
heat-engine".
# These templates have been reviewed by the debian-l10n-english # team # # If modifications/additions/rewording are needed, please ask # debian-l10n-engl...@lists.debian.org for advice. # # Even minor modifications require translation updates and such # changes should be coordinated with translators and reviewers. Template: heat/auth-host Type: string Default: 127.0.0.1 _Description: Auth server hostname: Please specify the hostname of your authentication server. Typically this is also the hostname of your OpenStack Identity Service (Keystone). Template: heat/admin-tenant-name Type: string Default: admin _Description: Authentication server tenant name: Please specify the authentication server tenant name. Template: heat/admin-user Type: string Default: admin _Description: Authentication server username: Please specify the username to use with the authentication server. Template: heat/admin-password Type: password _Description: Authentication server password: Please specify the password to use with the authentication server.
# These templates have been reviewed by the debian-l10n-english
# team
#
# If modifications/additions/rewording are needed, please ask
# debian-l10n-engl...@lists.debian.org for advice.
#
# Even minor modifications require translation updates and such
# changes should be coordinated with translators and reviewers.
Template: heat/auth-host
Type: string
Default: 127.0.0.1
_Description: Authentication server hostname:
Please specify the hostname of the authentication server. Typically
this is also the hostname of the OpenStack Identity Service (Keystone).
Template: heat/admin-tenant-name
Type: string
Default: admin
# Translators: a "tenant" in OpenStack world is
# an entity that contains one or more username/password couples.
# It's typically the tenant that will be used for billing. Having more than one
# username/password is very helpful in larger organization.
# You're advised to either keep "tenant" without translating it
# or keep it parenthezised. Example for French:
# locataire ("tenant")
_Description: Authentication server tenant name:
Please specify the authentication server tenant name.
Template: heat/admin-user
Type: string
Default: admin
_Description: Authentication server username:
Please specify the username to use with the authentication server.
Template: heat/admin-password
Type: password
_Description: Authentication server password:
Please specify the password to use with the authentication server.
Template: heat/admin-tenant-name
Type: string
Default: admin
# Translators: a "tenant" in OpenStack world is
# an entity that contains one or more username/password couples.
# It's typically the tenant that will be used for billing. Having more than one
# username/password is very helpful in larger organization.
# You're advised to either keep "tenant" without translating it
# or keep it parenthezised. Example for French:
# locataire ("tenant")
_Description: Authentication server tenant name:
Please specify the authentication server tenant name.
Template: heat/admin-user
Type: string
Default: admin
_Description: Authentication server username:
Please specify the username to use with the authentication server.
Template: heat/admin-password
Type: password
_Description: Authentication server password:
Please specify the password to use with the authentication server.
# These templates have been reviewed by the debian-l10n-english
# team
#
# If modifications/additions/rewording are needed, please ask
# debian-l10n-engl...@lists.debian.org for advice.
#
# Even minor modifications require translation updates and such
# changes should be coordinated with translators and reviewers.
Template: heat/auth-host
Type: string
Default: 127.0.0.1
_Description: Authentication server hostname:
Please specify the hostname of the authentication server. Typically
this is also the hostname of the OpenStack Identity Service (Keystone).
Template: heat/admin-tenant-name
Type: string
Default: admin
# Translators: a "tenant" in OpenStack world is
# an entity that contains one or more username/password couples.
# It's typically the tenant that will be used for billing. Having more than one
# username/password is very helpful in larger organization.
# You're advised to either keep "tenant" without translating it
# or keep it parenthezised. Example for French:
# locataire ("tenant")
_Description: Authentication server tenant name:
Please specify the authentication server tenant name.
Template: heat/admin-user
Type: string
Default: admin
_Description: Authentication server username:
Please specify the username to use with the authentication server.
Template: heat/admin-password
Type: password
_Description: Authentication server password:
Please specify the password to use with the authentication server.
Template: heat/register-endpoint
Type: boolean
Default: false
_Description: Register Heat 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: heat/keystone-ip
Type: string
_Description: Keystone server IP address:
Please enter the IP address of the Keystone server, so that heat-api can
contact Keystone to do the Heat service and endpoint creation.
Template: heat/keystone-auth-token
Type: password
_Description: Keystone authentication token:
To configure its endpoint in Keystone, heat-api needs the Keystone
authentication token.
Template: heat/endpoint-ip
Type: string
_Description: Heat endpoint IP address:
Please enter the IP address that will be used to contact Heat.
.
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: heat/region-name
Type: string
Default: regionOne
_Description: Name of the region to register:
OpenStack supports using availability zones, with each region representing
a location. Please enter the zone that you wish to use when registering the
endpoint.
Source: heat
Section: web
Priority: optional
Maintainer: PKG OpenStack <openstack-de...@lists.alioth.debian.org>
Uploaders: Loic Dachary (OuoU) <l...@debian.org>,
Julien Danjou <a...@debian.org>,
Thomas Goirand <z...@debian.org>,
Ghe Rivero <ghe.riv...@stackops.com>,
Mehdi Abaakouk <sil...@sileht.net>
Build-Depends: debhelper (>= 9),
po-debconf,
python-all (>= 2.6.6-3~),
openstack-pkg-tools (>= 4)
Build-Depends-Indep: pep8 (>= 1.3.3),
python-argparse,
python-babel,
python-boto,
python-cinderclient,
python-coverage,
python-crypto,
python-eventlet (>= 0.9.16),
python-extras,
python-glanceclient,
python-greenlet (>= 0.3.1),
python-httplib2,
python-iso8601,
python-keystoneclient,
python-kombu,
python-lxml (>= 2.3),
python-memcache,
python-migrate,
python-mox,
python-nose,
python-nosexcover,
python-novaclient,
python-oslo.config,
python-paste,
python-pastedeploy,
python-paramiko,
python-pycryptopp,
python-qpid,
python-quantumclient,
python-routes,
python-sendfile,
python-setuptools,
python-sphinx,
python-sqlalchemy (>= 0.7.8),
python-swiftclient,
python-webob,
python-yaml
Standards-Version: 3.9.3
Vcs-Browser: http://anonscm.debian.org/gitweb/?p=openstack/heat.git;a=summary
Vcs-Git: git://anonscm.debian.org/openstack/heat.git
Homepage: http://wiki.openstack.org/Heat
Package: python-heat
Section: python
Architecture: all
Pre-Depends: dpkg (>= 1.15.6~)
Depends: ${python:Depends}, ${misc:Depends},
python-argparse,
python-boto,
python-cinderclient,
python-crypto,
python-eventlet (>= 0.9.16),
python-extras,
python-glanceclient,
python-greenlet (>= 0.3.1),
python-httplib2,
python-iso8601,
python-keystoneclient,
python-kombu,
python-lxml (>= 2.3),
python-memcache,
python-migrate,
python-novaclient,
python-oslo.config,
python-paste,
python-pastedeploy,
python-pycryptopp,
python-qpid,
python-quantumclient,
python-routes,
python-sendfile,
python-setuptools,
python-sqlalchemy (>= 0.7.8),
python-swiftclient,
python-webob,
python-yaml
Description: OpenStack orchestration service - Python files
Heat is a service to orchestrate multiple composite cloud applications using
templates, through both an OpenStack-native ReST API and a
CloudFormation-compatible Query API.
.
This package contains the Python libraries.
Package: heat-common
Architecture: all
Pre-Depends: dpkg (>= 1.15.6~)
Depends: ${python:Depends}, ${misc:Depends}, python-heat (=${binary:Version}),
adduser
Description: OpenStack orchestration service - common files
Heat is a service to orchestrate multiple composite cloud applications using
templates, through both an OpenStack-native ReST API and a
CloudFormation-compatible Query API.
.
This package contains the common files.
Package: heat-engine
Architecture: all
Pre-Depends: dpkg (>= 1.15.6~)
Depends: ${ostack-lsb-base}, ${python:Depends}, ${misc:Depends}, heat-common
(=${binary:Version}),
adduser
Description: OpenStack orchestration service - engine
Heat is a service to orchestrate multiple composite cloud applications using
templates, through both an OpenStack-native ReST API and a
CloudFormation-compatible Query API.
.
This package contains the heat engine, which is the core service of heat, and
which the API servers will use.
Package: heat-api
Architecture: all
Pre-Depends: dpkg (>= 1.15.6~)
Depends: ${ostack-lsb-base}, ${python:Depends}, ${misc:Depends}, heat-common
(=${binary:Version}),
adduser
Description: OpenStack orchestration service - ReST API
Heat is a service to orchestrate multiple composite cloud applications using
templates, through both an OpenStack-native ReST API and a
CloudFormation-compatible Query API.
.
This package contains the ReST API.
Package: heat-api-cfn
Architecture: all
Pre-Depends: dpkg (>= 1.15.6~)
Depends: ${ostack-lsb-base}, ${python:Depends}, ${misc:Depends}, heat-common
(=${binary:Version}),
adduser
Description: OpenStack orchestration service - CFN API
Heat is a service to orchestrate multiple composite cloud applications using
templates, through both an OpenStack-native ReST API and a
CloudFormation-compatible Query API.
.
This package contains the CloudFormation (CFN) API.
Package: heat-api-cloudwatch
Architecture: all
Pre-Depends: dpkg (>= 1.15.6~)
Depends: ${ostack-lsb-base}, ${python:Depends}, ${misc:Depends}, heat-common
(=${binary:Version}),
adduser
Description: OpenStack orchestration service - CloudWatch API
Heat is a service to orchestrate multiple composite cloud applications using
templates, through both an OpenStack-native ReST API and a
CloudFormation-compatible Query API.
.
This package contains the CloudWatch API.
--- heat.old/debian/heat-engine.templates 2013-05-18 12:40:45.925186402
+0200
+++ heat/debian/heat-engine.templates 2013-06-16 18:53:48.633344954 +0200
@@ -1,17 +1,26 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# debian-l10n-engl...@lists.debian.org for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
Template: heat/configure_db
Type: boolean
Default: true
_Description: Set up a database for heat-engine?
- No database has been set up for heat-engine to use. Before continuing, you
- should make sure you have:
+ No database has been set up for heat-engine to use. Before
+ continuing, you should make sure you have the following information:
.
- - the server host name (that server must allow TCP connections from this
+ * the type of database that you want to use;
+ * the database server host name (that server must allow TCP connections from
this
machine);
- - a username and password to access the database.
- - A database type that you want to use.
+ * a username and password to access the database.
.
- If some of these requirements are missing, reject this option and run with
- regular sqlite support.
+ If some of these requirements are missing, do not choose this option and run
with
+ regular SQLite support.
.
- You can change this setting later on by running 'dpkg-reconfigure -plow
- heat-engine'.
+ You can change this setting later on by running "dpkg-reconfigure -plow
+ heat-engine".
--- heat.old/debian/heat-api-cfn.templates 2013-05-18 12:40:45.921186296
+0200
+++ heat/debian/heat-api-cfn.templates 2013-06-16 18:53:48.653345569 +0200
@@ -1,20 +1,33 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# debian-l10n-engl...@lists.debian.org for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
Template: heat/auth-host
Type: string
Default: 127.0.0.1
_Description: Auth server hostname:
- Please specify the URL of your authentication server. Typically this is also
- the URL of your OpenStack Identity Service (Keystone).
+ Please specify the hostname of your authentication server. Typically this is
also
+ the hostname of your OpenStack Identity Service (Keystone).
Template: heat/admin-tenant-name
Type: string
Default: admin
-_Description: Auth server tenant name:
+_Description: Authentication server tenant name:
+ Please specify the authentication server tenant name.
Template: heat/admin-user
Type: string
Default: admin
-_Description: Auth server username:
+_Description: Authentication server username:
+ Please specify the username to use with the authentication server.
Template: heat/admin-password
Type: password
-_Description: Auth server password:
+_Description: Authentication server password:
+ Please specify the password to use with the authentication server.
+
--- heat.old/debian/heat-api-cloudwatch.templates 2013-05-18
12:40:45.925186402 +0200
+++ heat/debian/heat-api-cloudwatch.templates 2013-06-16 18:53:49.465369737
+0200
@@ -1,20 +1,63 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# debian-l10n-engl...@lists.debian.org for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
Template: heat/auth-host
Type: string
Default: 127.0.0.1
-_Description: Auth server hostname:
- Please specify the URL of your authentication server. Typically
- this is also the URL of your OpenStack Identity Service (Keystone).
+_Description: Authentication server hostname:
+ Please specify the hostname of the authentication server. Typically
+ this is also the hostname of the OpenStack Identity Service (Keystone).
+
+Template: heat/admin-tenant-name
+Type: string
+Default: admin
+# Translators: a "tenant" in OpenStack world is
+# an entity that contains one or more username/password couples.
+# It's typically the tenant that will be used for billing. Having more than one
+# username/password is very helpful in larger organization.
+# You're advised to either keep "tenant" without translating it
+# or keep it parenthezised. Example for French:
+# locataire ("tenant")
+_Description: Authentication server tenant name:
+ Please specify the authentication server tenant name.
+
+Template: heat/admin-user
+Type: string
+Default: admin
+_Description: Authentication server username:
+ Please specify the username to use with the authentication server.
+
+Template: heat/admin-password
+Type: password
+_Description: Authentication server password:
+ Please specify the password to use with the authentication server.
Template: heat/admin-tenant-name
Type: string
Default: admin
-_Description: Auth server tenant name:
+# Translators: a "tenant" in OpenStack world is
+# an entity that contains one or more username/password couples.
+# It's typically the tenant that will be used for billing. Having more than one
+# username/password is very helpful in larger organization.
+# You're advised to either keep "tenant" without translating it
+# or keep it parenthezised. Example for French:
+# locataire ("tenant")
+_Description: Authentication server tenant name:
+ Please specify the authentication server tenant name.
Template: heat/admin-user
Type: string
Default: admin
-_Description: Auth server username:
+_Description: Authentication server username:
+ Please specify the username to use with the authentication server.
Template: heat/admin-password
Type: password
-_Description: Auth server password:
+_Description: Authentication server password:
+ Please specify the password to use with the authentication server.
--- heat.old/debian/heat-api.templates 2013-05-18 12:40:45.921186296 +0200
+++ heat/debian/heat-api.templates 2013-06-16 18:53:50.473399803 +0200
@@ -1,52 +1,70 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# debian-l10n-engl...@lists.debian.org for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
Template: heat/auth-host
Type: string
Default: 127.0.0.1
-_Description: Auth server hostname:
- Please specify the URL of your authentication server. Typically this is also
- the URL of your OpenStack Identity Service (Keystone).
+_Description: Authentication server hostname:
+ Please specify the hostname of the authentication server. Typically
+ this is also the hostname of the OpenStack Identity Service (Keystone).
Template: heat/admin-tenant-name
Type: string
Default: admin
-_Description: Auth server tenant name:
+# Translators: a "tenant" in OpenStack world is
+# an entity that contains one or more username/password couples.
+# It's typically the tenant that will be used for billing. Having more than one
+# username/password is very helpful in larger organization.
+# You're advised to either keep "tenant" without translating it
+# or keep it parenthezised. Example for French:
+# locataire ("tenant")
+_Description: Authentication server tenant name:
+ Please specify the authentication server tenant name.
Template: heat/admin-user
Type: string
Default: admin
-_Description: Auth server username:
+_Description: Authentication server username:
+ Please specify the username to use with the authentication server.
Template: heat/admin-password
Type: password
-_Description: Auth server password:
+_Description: Authentication server password:
+ Please specify the password to use with the authentication server.
Template: heat/register-endpoint
Type: boolean
Default: false
-_Description: Register Heat in the keystone endpoint catalog?
- Each Openstack services (each API) should be registered in order to be
+_Description: Register Heat 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: heat/keystone-ip
Type: string
-_Description: Keystone IP address:
- Enter the IP address of your keystone server, so that heat-api can
+_Description: Keystone server IP address:
+ Please enter the IP address of the Keystone server, so that heat-api can
contact Keystone to do the Heat service and endpoint creation.
Template: heat/keystone-auth-token
Type: password
-_Description: Keystone Auth Token:
- To configure its endpoint in Keystone, heat-api needs the Keystone auth
- token.
+_Description: Keystone authentication token:
+ To configure its endpoint in Keystone, heat-api needs the Keystone
+ authentication token.
Template: heat/endpoint-ip
Type: string
_Description: Heat endpoint IP address:
- Enter the IP address that will be used to contact Heat (eg: the Heat
- endpoint IP address).
+ Please enter the IP address that will be used to contact Heat.
.
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
@@ -56,6 +74,6 @@
Type: string
Default: regionOne
_Description: Name of the region to register:
- Openstack can be used using availability zones, with each region representing
+ OpenStack supports using availability zones, with each region representing
a location. Please enter the zone that you wish to use when registering the
endpoint.
signature.asc
Description: Digital signature
