>> should
> > > > >> > be
> > > > >> > >> removed, in my opinion. Disabling it in the
> build is a
> > good
> > > > first
> > > > >> > step.
> > > > >> > >>
> > > > >> >
com
> > > >> > >>
> > > >> > >> On Wed, Mar 15, 2017 at 8:18 AM, Rohit Yadav <
> > > >> > rohit.ya...@shapeblue.com>
> > > >> > >> wrote:
> > > >&g
Looks good to me.
t;>
> > > >> > >> *Jeff Hair*
> > > >> > >> Technical Lead and Software Developer
> > > >> > >>
> > > >> > >> Tel: (+354) 415 0200
> > > >> > >> j...@greenqloud.com
> >
> > >> > >>
> > >> > >> > +1 as others have noted
> > >> > >> >
> > >> > >> >
> > >> > >> > Disable the plugin from the default build for next few
>
> > >> On Wed, Mar 15, 2017 at 8:18 AM, Rohit Yadav <
> > >> > rohit.ya...@shapeblue.com>
> > >> > >> wrote:
> > >> > >>
> > >> > >> > +1 as others have noted
> > >> > >
t; >> > >> wrote:
> >> > >>
> >> > >> > +1 as others have noted
> >> > >> >
> >> > >> >
> >> > >> > Disable the plugin from the default build for next few
> releases
> >> > and
> >> >
>> > >> > look something like:
>> > >> >
>> > >> > - Announce on the MLs that we're planning to do this, send a PR
>> > and get
>> > >> it
>> > >> > accepted
>> > &
is, send a PR
> > and get
> > >> it
> > >> > accepted
> > >> >
> > >> > - During the release process RM should make this information
> > available to
> > >> > everyone (including voting thread, would be nice to have a
> > shortlog of
> > >>
is, send a PR
> > and get
> > >> it
> > >> > accepted
> > >> >
> > >> > - During the release process RM should make this information
> > available to
> > >> > everyone (including voting thread, would be nice to have a
> > sh
gt; > - In the release notes and release announcement, note that
> midonet is no
> >> > longer included in the default build and is planned to be
> deprecated
> >> >
> >> > - By end of the year, if we've no communication received
>
n the default build and is planned to be deprecated
>> >
>> > - By end of the year, if we've no communication received deprecate and
>> > remove the plugin with an announcement
>> >
>> >
>> > I think this should be done with M
> remove the plugin with an announcement
>> >
>> >
>> > I think this should be done with Midonet and any other plugins that are
>> > causing issues and are no longer maintained by anyway.
>> >
>> >
>> > Regards.
>> >
>&g
using is good.
>
> Regards,
> Marty Godsey
> Principal Engineer
> nSource Solutions, LLC
>
> -Original Message-
> From: Will Stevens [mailto:williamstev...@gmail.com]
> Sent: Sunday, March 19, 2017 7:39 AM
> To: dev@cloudstac
ource Solutions, LLC
-Original Message-
From: Will Stevens [mailto:williamstev...@gmail.com]
Sent: Sunday, March 19, 2017 7:39 AM
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] Retirement of midonet plugin
I think there needs to be at least 6 months betw
ll Stevens [mailto:williamstev...@gmail.com]
Sent: Sunday, March 19, 2017 7:39 AM
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] Retirement of midonet plugin
I think there needs to be at least 6 months between the disable code being
released and the delete PR being merged. I feel like the cl
e that midonet
> is no
> > > longer included in the default build and is planned to be
> deprecated
> > >
> > > - By end of the year, if we've no communication received deprecate
> and
> > > remove the plugin with an announcement
> > >
> > &g
t; > > major changes in the voting email?)
>> > >
>> > > - In the release notes and release announcement, note that
>> midonet is no
>> > > longer included in the default build and is planned to be
>> deprecated
>> &
issues and are no longer maintained by anyway.
> >
> >
> > Regards.
> >
> >
> > From: Sergey Levitskiy
> > Sent: 15 March 2017 07:00:51
> > To: dev@cloudstack.apache.o
emove the plugin with an announcement
> >
> >
> > I think this should be done with Midonet and any other plugins that are
> > causing issues and are no longer maintained by anyway.
> >
> >
> > Regards.
> >
> >
> &
ent
>
>
> I think this should be done with Midonet and any other plugins that are
> causing issues and are no longer maintained by anyway.
>
>
> Regards.
>
>
> From: Sergey Levitskiy
> Sent: 15 March 2017 07:00:51
> To: dev@cloud
_
From: Sergey Levitskiy
Sent: 15 March 2017 07:00:51
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] Retirement of midonet plugin
I am for:
(i) disable the build for the plugin for the next 2 major release followed by
(ii) remove everything in ACS 4.12 if no one express regre
7, 9:10PM
To: dev@cloudstack.apache.org [dev@cloudstack.apache.org]
Subject: [DISCUSS] Retirement of midonet plugin
Dear ACS fellows,
Recently there have been two threads asking and discussing the “midonet”
integration with Apache CloudStack (ACS) [1-2].
ceived: Tuesday, 14 Mar 2017, 9:10PM
To: dev@cloudstack.apache.org [dev@cloudstack.apache.org]
Subject: [DISCUSS] Retirement of midonet plugin
Dear ACS fellows,
Recently there have been two threads asking and discussing the “midonet”
integration with Apache CloudS
I agree with Sergey and Will. Let's disable it first.
Simon Weller/615-312-6068
-Original Message-
From: Rafael Weingärtner [rafaelweingart...@gmail.com]
Received: Tuesday, 14 Mar 2017, 9:10PM
To: dev@cloudstack.apache.org [dev@cloudstack.apache.org]
Subject: [DISCUSS] Retireme
I think we approach these with a disable, then delete approach. Disable for
one or two releases and if no one steps in to revive it in that period, we
delete it.
On Mar 14, 2017 9:10 PM, "Rafael Weingärtner"
wrote:
Dear ACS fellows,
Recently there have been two threads asking and discussing the
I am for:
(i) disable the build for the plugin for the next 2 major release followed by
(ii) remove everything in ACS 4.12 if no one express regrets by then
Dear ACS fellows,
Recently there have been two threads asking and discussing the “midonet”
integration with Apache CloudStack (ACS) [1-2].
After quite some discussions, we noticed that despite having some people
willing to use it, the plugin has never been fully developed by its vendor
(Midokura).
28 matches
Mail list logo
