Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Wed, 12 Apr 2017 13:37:42 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.13061137.1491229698000.265518.1492004262027@Atlassian.JIRA>
In-Reply-To: <JIRA.13061137.1491229698000@Atlassian.JIRA>
References: <JIRA.13061137.1491229698000@Atlassian.JIRA> <JIRA.13061137.1491229698216@jira-lw-us.apache.org>
Subject: [jira] [Commented] (CLOUDSTACK-9858) Retirement of midonet plugin
 (disabling ticket)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Wed, 12 Apr 2017 13:37:48 -0000


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9858?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=
=3D15965858#comment-15965858 ]=20

ASF GitHub Bot commented on CLOUDSTACK-9858:
--------------------------------------------

Github user wido commented on the issue:

    https://github.com/apache/cloudstack/pull/2036
 =20
    LGTM


> Retirement of midonet plugin (disabling ticket)
> -----------------------------------------------
>
>                 Key: CLOUDSTACK-9858
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-985=
8
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>            Reporter: Rafael Weing=C3=A4rtner
>            Assignee: Rafael Weing=C3=A4rtner
>
> Recently there have been two threads asking and discussing the =E2=80=9Cm=
idonet=E2=80=9D 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). Further, nobody else has put the effort on fully testing and fi=
nishing its implementation. It seems that the plugin was incorporated into =
our code base without being fully finished. Moreover, I have asked around a=
t the Midonet community, and the java client they use has changed quite a b=
it from the one we use.
> It begs the question if it does not work, why do we advertise such integr=
ation? [3].=20
> Following the component retirement process defined in [4], a vote thread =
was started in [5]. The community decided to retire this Midonet plugin. Th=
is task represents the first step of the retirement, which is the disabling=
 of the plugin in CloudStack`s build process.
> =20
> [1] http://cloudstack.markmail.org/thread/qyedle5jb2c34gsc#query:+page:1+=
mid:xn2zq2v3eim5vl2q+state:results
> [2] http://cloudstack.markmail.org/message/rewzk4v7dgzpsxkm?q=3Dmidonet+o=
rder:date-backward&page=3D1#query:midonet%20order%3Adate-backward+page:1+mi=
d:i563khxlginf6smg+state:results
> [3] http://docs.cloudstack.apache.org/en/latest/networking/midonet.html
> [4] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=3D68=
720798
> [5] http://markmail.org/message/qigrtfirwnmct4hr


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)