On 11/02/2016 09:53 PM, Turbo Fredriksson wrote: > On 1 Nov 2016, at 17:42, Debian Bug Tracking System <ow...@bugs.debian.org> > wrote: >> >> * Remove the neutron-fwaas-l3-agent init script, as this package is >> now just a plugin. Make the neutron-fwaas-l3-agent package a transition >> package. > > Ok, so this was done between the "1:9.0.0~b2-1” and "1:9.0.0~rc1-1” which is > (in) a RC > release. > > > !!! You CAN NOT do major changes like this in minor releases !!! > > > Not without making it VERY CLEAR for the user that this HAD to be done (and a > very good explanation of why! > Such notice would be a warning, using debconf etc. > > And you MUST provide an upgrade path! Just saying in a change log (which > isn’t for the user - _NO ONE_ reads them, it’s for you as an administrator) > isn’t > NEARLY enough!!
I very much agree with the above, the only issue is enough time to put these warning in place. Maybe some text in a NEWS or README.Debian file could do the trick. I'm not so fan of adding debconf text for such a warning. > How do I now get my FWaaS working again? Just configure Neutron. The doc from Red Hat seems to cover it well: https://access.redhat.com/documentation/en/red-hat-enterprise-linux-openstack-platform/7/paged/networking-guide/chapter-16-configure-firewall-as-a-service-fwaas Basically, you just use the "normal" neutron-l3-agent, and configure neutron.conf with: service_plugins = neutron.services.firewall.fwaas_plugin.FirewallPlugin I hope this helps, Cheers, Thomas Goirand (zigo)