[openstack-dev] [packaging] how to deal with the rename of config files in neutron on upgrade?
ihrachys at redhat.com
Mon Jul 13 06:22:22 UTC 2015
-----BEGIN PGP SIGNED MESSAGE-----
UPD: in the end, we went the easy way, emulating .rpmnew process in
%post scriptlets (see the patch linked in my previous email, if you
want to see details).
AFAIK there is no distinguished directive or macro that would allow to
maintain .rpmnew process on renames.
On 07/07/2015 03:09 PM, Ihar Hrachyshka wrote:
> On 07/02/2015 06:35 PM, Matt Riedemann wrote:
>> This change in neutron  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
>>  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:
> 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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----
More information about the OpenStack-dev