cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rafaelweingartner <>
Subject [GitHub] cloudstack pull request #2036: [CLOUDSTACK-9858] Retirement of midonet plugi...
Date Tue, 11 Apr 2017 20:07:51 GMT
GitHub user rafaelweingartner opened a pull request:

    [CLOUDSTACK-9858] Retirement of midonet plugin (build disabling)

    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.

You can merge this pull request into a Git repository by running:

    $ git pull midoneDisablingForRetirement

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2036
commit a3f351c07e73e4a207d10e3d23003c81cb3ab58b
Author: Rafael Weingartner <>
Date:   2017-04-11T20:04:10Z

    [CLOUDSTACK-9858] Retirement of midonet plugin (build disabling)


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message