Open Stack

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 07/02/2015 06:35 PM, Matt Riedemann wrote:
> This change in neutron [1] renames the linuxbridge and openvswitch 
> plugin config files.  I'm familiar with the %config(noreplace)
> directive in rpm but I'm not sure if there is a special trick with
> rpm to rename a config file while not losing the changes in the
> config file during the upgrade.
> 
> Is this just something that has to be handled with trickery in the
> %post macro where we merge the contents together if the old config
> file exists?  Would symbolic links help?
> 
> Changes like this seem like a potential giant pain in the ass for 
> packagers.
> 
> [1] https://review.openstack.org/#/c/195277/
> 

Tha change was long overdue. Hopefully, now that the file name is not
that misleading, debian packages will avoid loading
plugin.ini/ml2_conf.ini for the agents. :)

My plan for RDO is to make agents read a config-dir instead of
config-files for those files, and populate a config-dir with symlinks
pointing to those files that exist on the system. For upgrade
scenario, the config-dir will contain links to both files, while for
new installations, it will be a single symlink case.

And here is the RDO review for your reference:
https://review.gerrithub.io/238887

I don't believe those kind of upgrade hacks belong to deployment tools
like puppet. Ideally, you would just switch the name of the
configuration file and be done with it.

Ihar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJVm8+dAAoJEC5aWaUY1u57+o8IAKOR9Sij61EkdU3jZXivRZSt
oRjvACi4uqHdzfYbzY57/mVG999NHJm2Nzkva7b6vvWzltTkHzNIla32tKYUIJjA
mjLv5j8ADW10DsHle2EFlJJkEs/uq+Hs+auRLuZmwaWLJt9EeAaPx67w6i4j8/I8
iYsaAWnuM73LoRJQpeODVbeyIi+u4OntybXoFGYxsFfxPlPXKp7+nTgsXd7qRPuj
ETEjLiJxc/hsPoD1ItWjuPEjpMg5RV9gTlkH3VDC/xLRINSMqOB/ylE7mcVrh+gb
IfR2iEz2iUhJgKyGzjU1zPZLGb3LjafgZzYlUdDSgvnrwqibV4XFj+EtisO11ZI=
=dcby
-----END PGP SIGNATURE-----