Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: OpenStack: Dev

Flagfiles vs. .ini files

 

 

OpenStack dev RSS feed   Index | Next | Previous | View Threaded


ghe.rivero at stackops

May 2, 2012, 12:32 AM

Post #1 of 3 (178 views)
Permalink
Flagfiles vs. .ini files

Essex was released with support for both types of configuration files,
flagfiles (using the --) and the .ini file style, being the
"nova.conf.sample" file included in nova upstream code using the .ini
format.

>From a deployer point of view, this can be really confusing since official
docs, use the .ini format, but Ubuntu 12.04 and docs based on ubuntu, use
the old deprecated flagfile format.

I think that we should start using only .ini files and stop supporting the
old flagfile behavior. The sooner we remove from the development cycle, the
more time the documenters and distributions have to catch up with the "new"
format. Anyway, nova-manage can still be used to convert from flagfiles to
.ini files: (I wouldn't remove this in folsom cycle)

$ ./bin/nova-manage config convert --help
Usage: nova-manage config convert <args> [options]

Options:
-h, --help show this help message and exit
--infile=<path> old-style flagfile to convert to config
--outfile=<path> path for output file. Writes configto stdout if not
specified.

Thanks,
--
Ghe Rivero
*OpenStack & Distribution Engineer
**www.stackops.com | * ghe.rivero [at] stackops <diego.parrilla [at] stackops>
** | +34 625 63 45 23 | skype:ghe.rivero*
* <http://www.stackops.com/>
*

*

******************** ADVERTENCIA LEGAL ********************
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

***************** PRIVILEGED AND CONFIDENTIAL ****************
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.


P at draigBrady

May 2, 2012, 1:43 AM

Post #2 of 3 (184 views)
Permalink
Re: Flagfiles vs. .ini files [In reply to]

On 05/02/2012 08:32 AM, Ghe Rivero wrote:
> Essex was released with support for both types of configuration files, flagfiles (using the --) and the .ini file style, being the "nova.conf.sample" file included in nova upstream code using the .ini format.
>
> From a deployer point of view, this can be really confusing since official docs, use the .ini format, but Ubuntu 12.04 and docs based on ubuntu, use the old deprecated flagfile format.
>
> I think that we should start using only .ini files and stop supporting the old flagfile behavior. The sooner we remove from the development cycle, the more time the documenters and distributions have to catch up with the "new" format. Anyway, nova-manage can still be used to convert from flagfiles to .ini files: (I wouldn't remove this in folsom cycle)

I agree, having multiple ways to do stuff is problematic.
Is it too late to change the ubuntu configs/docs now?
We should at least output warnings about the old format.

Standardising on the new ini style format make sense,
and that's what has been done in the Essex releases in Fedora and EPEL.
Note to simplify the docs and allow users to cut and paste instructions,
we also include a utility to edit these config files:

https://github.com/fedora-openstack/openstack-utils/blob/master/utils/openstack-config

cheers,
Pádraig.

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack [at] lists
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp


ghe.rivero at stackops

May 7, 2012, 2:27 AM

Post #3 of 3 (167 views)
Permalink
Re: Flagfiles vs. .ini files [In reply to]

On Wed, May 2, 2012 at 10:43 AM, Pádraig Brady <P [at] draigbrady> wrote:

> I agree, having multiple ways to do stuff is problematic.
> Is it too late to change the ubuntu configs/docs now?
> We should at least output warnings about the old format.
>

Having multiple ways of doing thins is confusing for final users, but i
wouldn't change ubuntu behavior once it has been released.
Anyway, i would upload a review today to remove it and start using only
.ini files. Just as a reminder, you can still use nova-manage to convert
files:

$ ./bin/nova-manage config convert --help
Usage: nova-manage config convert <args> [options]

Options:
-h, --help show this help message and exit
--infile=<path> old-style flagfile to convert to config
--outfile=<path> path for output file. Writes configto stdout if not
specified




> Standardising on the new ini style format make sense,
> and that's what has been done in the Essex releases in Fedora and EPEL.
> Note to simplify the docs and allow users to cut and paste instructions,
> we also include a utility to edit these config files:
>
>
> https://github.com/fedora-openstack/openstack-utils/blob/master/utils/openstack-config
>
> cheers,
> Pádraig.
>



--
Ghe Rivero
*OpenStack & Distribution Engineer
**www.stackops.com | * ghe.rivero [at] stackops <diego.parrilla [at] stackops>
** | +34 625 63 45 23 | skype:ghe.rivero*
* <http://www.stackops.com/>
*

*

******************** ADVERTENCIA LEGAL ********************
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

***************** PRIVILEGED AND CONFIDENTIAL ****************
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.

OpenStack dev RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.