Re: [PKG-Openstack-devel] OpenStack switching to a unified template system

2018-03-06 Thread Thomas Goirand
On 03/06/2018 11:12 PM, Justin B Rye wrote: > Thomas Goirand wrote: >> As much as OpenStack is concerned, MySQL or MariaDB is the same, what we >> are configuring here is the SQLAlchemy driver (SQLAlchemy is a python >> library to abstract db access). Anyway, I've wrote now: >> >> * the type of d

Re: [PKG-Openstack-devel] OpenStack switching to a unified template system

2018-03-06 Thread Justin B Rye
Thomas Goirand wrote: > As much as OpenStack is concerned, MySQL or MariaDB is the same, what we > are configuring here is the SQLAlchemy driver (SQLAlchemy is a python > library to abstract db access). Anyway, I've wrote now: > > * the type of database that you want to use - generally the MySQL

Re: [PKG-Openstack-devel] OpenStack switching to a unified template system

2018-03-06 Thread Thomas Goirand
On 03/06/2018 01:11 PM, Justin B Rye wrote: > (In openstack-pkg-tools.configure-endpoint.templates:) > -_Description: Keystone admin name: > - To create the service endpoint, this package needs to know the Admin login, > - username, project name, and password, so it can issue commands through th

Re: [PKG-Openstack-devel] OpenStack switching to a unified template system

2018-03-06 Thread Justin B Rye
Comments, revised versions, and diff to the originals. Thomas Goirand wrote: >> (I'm hoping that also makes it obvious that we don't mean "dots and >> dashes" in the sense of "· · · — — — · · ·".) > > I'm using a regular expression to make sure what's entered isn't too > bad. Probably the SOS wha

Re: [PKG-Openstack-devel] OpenStack switching to a unified template system

2018-03-06 Thread Thomas Goirand
Hi Justin, As always, you're doing awesome reviews, and every sentence becomes crystal clear with your changes. Thanks! On 03/06/2018 03:02 AM, Justin B Rye wrote: >> Template: ospt/api-keystone-admin-username >> Type: string >> Default: admin >> _Description: Keystone admin name: >> To create t

Re: OpenStack switching to a unified template system

2018-03-05 Thread victory
On Tue, 6 Mar 2018 02:02:03 + Justin B Rye wrote: > > # ### database configuration ### > > Template: ospt/configure_db > > _Description: Set up a database for this package? > > No database has been set up for this package. Before continuing, you should > > make sure you have the following in

Re: OpenStack switching to a unified template system

2018-03-05 Thread Justin B Rye
Thomas Goirand wrote: [...] > Therefore, I've moved the shared debconf templates from each individual > services to openstack-pkg-tools. When building, packages are copying the > templates from /usr/share/openstack-pkg-tools/debconf, and merge the > translations into debian/po from > /usr/share/ope

OpenStack switching to a unified template system

2018-03-05 Thread Thomas Goirand
Hi there! In OpenStack, we use debconf to configure the same thing on a number of services (ie: different package). It used to be that OpenStack services were in a small number, and the debconf templates were maintainable in each service, with translators sending translations to each and every ind