cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9858) Retirement of midonet plugin (disabling ticket)
Date Wed, 12 Apr 2017 19:58:42 GMT


ASF GitHub Bot commented on CLOUDSTACK-9858:

Github user rafaelweingartner commented on the issue:
    I tried to access the Jenkins details to see the checking problems, but I am getting a
    Am I missing something?

> Retirement of midonet plugin (disabling ticket)
> -----------------------------------------------
>                 Key: CLOUDSTACK-9858
>                 URL:
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Rafael Weingärtner
>            Assignee: Rafael Weingärtner
> 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). Further, nobody else
has put the effort on fully testing and finishing its implementation. It seems that the plugin
was incorporated into our code base without being fully finished. Moreover, I have asked around
at the Midonet community, and the java client they use has changed quite a bit from the one
we use.
> It begs the question if it does not work, why do we advertise such integration? [3].

> Following the component retirement process defined in [4], a vote thread was started
in [5]. The community decided to retire this Midonet plugin. This task represents the first
step of the retirement, which is the disabling of the plugin in CloudStack`s build process.
> [1]
> [2]
> [3]
> [4]
> [5]

This message was sent by Atlassian JIRA

View raw message