Oh!
Ubuntu's guy.
Can you say why you didn't ship 2013.2.4? It was available in announced
support lifecycle for cloudarchive, and you just stops to do anything
with 2013.2.3 (havana) somewhere in the middle of the summer. It was
really bad, because few important fixes for neutron were landed in
2013.2.4 and was not available in 2013.2.3 (f.e.
https://bugs.launchpad.net/neutron/+bug/1240849)
(about configs)
Actual config file does not matter - we have own chef'ed configs,
created from scratch & databags. All I wanted were to have no unexpected
questions during installation. And I completely forgot about
non-interactive mode for dpkg.
On 12/15/2014 07:46 PM, James Page wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Thomas
On 15/12/14 08:49, Thomas Goirand wrote:
and ubuntu just put files
in proper places without changing configs.
Ahem... Ubuntu simply doesn't care much about config files. See
what they ship for Nova and Cinder. I wouldn't say "without
changing configs" in this case.
Just for the record, we (Ubuntu) ship either a minimal functional
configuration files or the upstream sample configuration files with
sufficient patching to be functional.
We made the choice to specifically not include debconf for
configuration file generation; in terms of where we wanted to focus
the resources we have working on packaging, debconf was not high on
the list of priorities as the majority of users are deploying across
multiple servers and are using some sort of configuration management
tool; maintaining debconf for OpenStack packages added overhead we did
not want to take on.
So we do care about configuration files... just not in the same way
you do for Debian!
- --
James Page
Ubuntu and Debian Developer
james.p...@ubuntu.com
jamesp...@debian.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJUjx55AAoJEL/srsug59jDcQQP/1wFJdmf038q7Fwjgfev0iTJ
3j8IXgsz6OLi1jSxsIYzCGvME6U6SMpfV6edX/X637nHxr1gYg00npz51xJjbVap
c33T5MxWkq6L/e0MdwEX4OqEejOiBuayw61h1+9Kg+BlkYJI+o/GZ+soMGbWAu/T
xKIwzGLYRjr8s7ToeKxv8HYwiyrdeMjwaHb2Ontpyh8psPMprOwyXeV91shGxdY6
RN6Fw3NGLAUyl2JsyCDAeeg6UZ1Cb5tnHfoZg1Tu0MGl+VrSLUy7KvPGf5vNXT8l
XmE9IiYSFlW70b4jliuE44LhR4p/PCfQXBV5a60PUJWIWxtjcVSEb+MtwzZpSIQm
tg9+q2dIJlbWUGCLaE39wJfNuZoUPNoFCOxruAYkwZ3DGnozt36XYDL5jyCmMfX3
jnbZ11YfmBa0ZILUmlwQ6ZRVL3BWxKsFVLPauq0u79fhF0H5i6lpVmx7S4LEt5GE
EwJH2yhAnx4qzzl9x6y/wyCcHh+0JgdYWIYGlYylGkw27mfMsEtowQfHypf7cB3l
5dwA+d/NWZb2fKX/vPvrTCIPJuN7czWTZDVATOSjCwoZMfafMa/66E+LvCD5GZ+S
8etVt4uXY6yWOxrvyw411/gNtXvKbuoUpLky+skdjjNGcnB24ZQQ4W8mOq1yNMQc
1WO0buP8OUF2FItrg0JP
=GxCK
-----END PGP SIGNATURE-----
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
