On Mon, Aug 22, 2016 at 8:01 AM, Vladyslav Drok <vd...@mirantis.com> wrote: > On Fri, Aug 19, 2016 at 5:15 PM, Jim Rollenhagen <j...@jimrollenhagen.com> > wrote: >> >> Hi Ironickers, >> >> There was a big thread here[0] about Cinder, driver removal, and standard >> deprecation policy. If you haven't read through it yet, please do before >> continuing here. :) >> >> The outcome of that thread is summarized well here.[1] >> >> I know that I previously had a different opinion on this, but I think we >> should go roughly the same route, for the sake of the users. >> >> 1) A ``supported`` flag for each driver that is True if and only if the >> driver >> is tested in infra or third-party CI (and meets our third party CI >> requirements). >> 2) If the supported flag is False for a driver, deprecation is implied >> (and >> a warning is emitted at load time). A driver may be removed per >> standard >> deprecation policies, with turning the supported flag False to start >> the >> clock. >> 3) Add a ``enable_unsupported_drivers`` config option that allows enabling >> drivers marked supported=False. If a driver is in enabled_drivers, has >> supported=False, and enable_unsupported_drivers=False, ironic-conductor >> will fail to start. Setting enable_unsupported_drivers=True will allow >> ironic-conductor to start with warnings emitted. > > > Just for clarity, its default value is False?
Sorry, I meant to add that. Yes, default for enable_unsupported_drivers is False. // jim __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
