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.
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
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
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.
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
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
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
