Re: [openstack-dev] [Neutron] how to deprecate a plugin
On Thu, Jul 31, 2014 at 1:43 AM, YAMAMOTO Takashi yamam...@valinux.co.jp wrote: On Wed, Jul 30, 2014 at 12:17 PM, YAMAMOTO Takashi yamam...@valinux.co.jp wrote: hi, what's the right procedure to deprecate a plugin? we (ryu team) are considering deprecating ryu plugin, in favor of ofagent. probably in K-timeframe, if it's acceptable. The typical way is to announce the deprecation at least one cycle before removing the deprecated plugin from the tree. So, you could announce the ryu plugin is deprecated in Juno, and then remove it from the tree in Kilo. where is an appropriate place to announce? this ML? Yes, and also, put an item on the weekly Neutron meeting agenda [1] in the announcements section. [1] https://wiki.openstack.org/wiki/Network/Meetings i added an item. i'll try to attend the next meeting but i'm not sure if i can. i have an overlapping schedule this month. sorry. YAMAMOTO Takashi YAMAMOTO Takashi Thanks, Kyle YAMAMOTO Takashi ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] how to deprecate a plugin
On Wed, Jul 30, 2014 at 12:17 PM, YAMAMOTO Takashi yamam...@valinux.co.jp wrote: hi, what's the right procedure to deprecate a plugin? we (ryu team) are considering deprecating ryu plugin, in favor of ofagent. probably in K-timeframe, if it's acceptable. The typical way is to announce the deprecation at least one cycle before removing the deprecated plugin from the tree. So, you could announce the ryu plugin is deprecated in Juno, and then remove it from the tree in Kilo. where is an appropriate place to announce? this ML? YAMAMOTO Takashi Thanks, Kyle YAMAMOTO Takashi ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] how to deprecate a plugin
hi, In Nova we have done the following: - add a warning in the current version that this will be deprecated in K - start of K drop the code It is also important to have an upgrade path. What happens if I have my RYU plugin in production and I upgrade to the next version. That should be clearly documented. it depends on what functionalities of the plugin you are using. i think simple setups (eg. vlan isolation) can be covered by other plugins like ofagent. but we haven't investigated further. I think that maybe we should consider on working on a migration scheme - from plugin A to plugin B. i afraid it's impossible in general. YAMAMOTO Takashi Thanks Gary On 7/30/14, 8:17 PM, YAMAMOTO Takashi yamam...@valinux.co.jp wrote: hi, what's the right procedure to deprecate a plugin? we (ryu team) are considering deprecating ryu plugin, in favor of ofagent. probably in K-timeframe, if it's acceptable. YAMAMOTO Takashi ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] how to deprecate a plugin
On Thu, Jul 31, 2014 at 1:43 AM, YAMAMOTO Takashi yamam...@valinux.co.jp wrote: On Wed, Jul 30, 2014 at 12:17 PM, YAMAMOTO Takashi yamam...@valinux.co.jp wrote: hi, what's the right procedure to deprecate a plugin? we (ryu team) are considering deprecating ryu plugin, in favor of ofagent. probably in K-timeframe, if it's acceptable. The typical way is to announce the deprecation at least one cycle before removing the deprecated plugin from the tree. So, you could announce the ryu plugin is deprecated in Juno, and then remove it from the tree in Kilo. where is an appropriate place to announce? this ML? Yes, and also, put an item on the weekly Neutron meeting agenda [1] in the announcements section. [1] https://wiki.openstack.org/wiki/Network/Meetings YAMAMOTO Takashi Thanks, Kyle YAMAMOTO Takashi ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron] how to deprecate a plugin
hi, what's the right procedure to deprecate a plugin? we (ryu team) are considering deprecating ryu plugin, in favor of ofagent. probably in K-timeframe, if it's acceptable. YAMAMOTO Takashi ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] how to deprecate a plugin
On Wed, Jul 30, 2014 at 12:17 PM, YAMAMOTO Takashi yamam...@valinux.co.jp wrote: hi, what's the right procedure to deprecate a plugin? we (ryu team) are considering deprecating ryu plugin, in favor of ofagent. probably in K-timeframe, if it's acceptable. The typical way is to announce the deprecation at least one cycle before removing the deprecated plugin from the tree. So, you could announce the ryu plugin is deprecated in Juno, and then remove it from the tree in Kilo. Thanks, Kyle YAMAMOTO Takashi ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] how to deprecate a plugin
In Nova we have done the following: - add a warning in the current version that this will be deprecated in K - start of K drop the code It is also important to have an upgrade path. What happens if I have my RYU plugin in production and I upgrade to the next version. That should be clearly documented. I think that maybe we should consider on working on a migration scheme - from plugin A to plugin B. Thanks Gary On 7/30/14, 8:17 PM, YAMAMOTO Takashi yamam...@valinux.co.jp wrote: hi, what's the right procedure to deprecate a plugin? we (ryu team) are considering deprecating ryu plugin, in favor of ofagent. probably in K-timeframe, if it's acceptable. YAMAMOTO Takashi ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
