Github user rafaelweingartner commented on the issue:
https://github.com/apache/cloudstack/pull/2036
I tried to access the Jenkins details to see the checking problems, but I
am getting a 404.
Am I missing something?
---
If your project is set up for it, you can reply to this em
Github user wido commented on the issue:
https://github.com/apache/cloudstack/pull/2036
LGTM
---
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 feat
GitHub user rafaelweingartner opened a pull request:
https://github.com/apache/cloudstack/pull/2036
[CLOUDSTACK-9858] Retirement of midonet plugin (build disabling)
Recently there have been two threads asking and discussing the
âmidonetâ integration with Apache CloudStack (ACS
Folks,
I am now closing the voting for the retirement of the Midonet plugin.
The final tally is:
[+1] 12
[0] null
[-1] null
Based on this result I will move forward the retirement process.
Thank you all for your valuable contributions to the discussion thread and
then showing your opinion
+1
Regards,
Sateesh
From: Rafael Weingärtner
Sent: 29 March 2017 02:16:09
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: [VOTE] Retirement of midonet plugin
Dear ACS fellows,
We have discussed the
+1
From: Rafael Weingärtner
Sent: 29 March 2017 02:16:09
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: [VOTE] Retirement of midonet plugin
Dear ACS fellows,
We have discussed the retirement of Midonet plugin [*]. After quite some
talk, we
...@cloudstack.apache.org]
Subject: Re: [VOTE] Retirement of midonet plugin
+1
> Op 28 maart 2017 om 22:46 schreef Rafael Weingärtner
> :
>
>
> Dear ACS fellows,
> We have discussed the retirement of Midonet plugin [*]. After quite some
> talk, we converged in a retirement process and it se
+1
> Op 28 maart 2017 om 22:46 schreef Rafael Weingärtner
> :
>
>
> Dear ACS fellows,
> We have discussed the retirement of Midonet plugin [*]. After quite some
> talk, we converged in a retirement process and it seems that we all agree
> that the Midonet plugin s
+1
Erik
On Tue, Mar 28, 2017 at 10:46 PM, Rafael Weingärtner
wrote:
> Dear ACS fellows,
> We have discussed the retirement of Midonet plugin [*]. After quite some
> talk, we converged in a retirement process and it seems that we all agree
> that the Midonet plugin should be ret
+1
On Mar 29, 2017 2:36 AM, "Daan Hoogland"
wrote:
> +1
>
> On 28/03/17 22:46, "Rafael Weingärtner"
> wrote:
>
> Dear ACS fellows,
> We have discussed the retirement of Midonet plugin [*]. After quite
> some
> talk, we converged i
From: Daan Hoogland
Sent: Wednesday, March 29, 2017 12:06 PM
To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
Subject: Re: [VOTE] Retirement of midonet plugin
+1
On 28/03/17 22:46, "Rafael Weingärtner" wrote:
Dear ACS fellows,
W
Please remove me from the mailing list.
From: Daan Hoogland
Sent: Wednesday, March 29, 2017 12:06 PM
To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
Subject: Re: [VOTE] Retirement of midonet plugin
+1
On 28/03/17 22:46, "Rafael Weingärtner&qu
+1
On 28/03/17 22:46, "Rafael Weingärtner" wrote:
Dear ACS fellows,
We have discussed the retirement of Midonet plugin [*]. After quite some
talk, we converged in a retirement process and it seems that we all agree
that the Midonet plugin should be retired. So, to
...@cloudstack.apache.org
Subject: RE: [VOTE] Retirement of midonet plugin
+1 to retire.
Regards,
Marty Godsey
Principal Engineer
nSource Solutions, LLC
-Original Message-
From: Rafael Weingärtner [mailto:rafaelweingart...@gmail.com]
Sent: Tuesday, March 28, 2017 4:46 PM
To: dev
midonet plugin
Dear ACS fellows,
We have discussed the retirement of Midonet plugin [*]. After quite some talk,
we converged in a retirement process and it seems that we all agree that the
Midonet plugin should be retired. So, to formalize things, we should vote
Midonet retirement.
All users and
Dear ACS fellows,
We have discussed the retirement of Midonet plugin [*]. After quite some
talk, we converged in a retirement process and it seems that we all agree
that the Midonet plugin should be retired. So, to formalize things, we
should vote Midonet retirement.
All users and devs are
You right, it is a tricky ;)
Well, it seems that we have discussed and formalized the retirement
process. We also discussed the retirement of Midonet plugin, and it seems
that we have a consensus here. To proceed with Midonet retirement I will
create a voting thread; so, we follow our brand new
>
> On 28/03/17 16:00, "Rafael Weingärtner"
> wrote:
>
> I created a page describing the retirement process (it is general, not
> Midonet specific). Could I get some feedback from you guys?
>
> https:
Looks good to me.
gt; Arguably a q&a section only makes sense after a while when questions came
> forward but I am fine with the other questions as is.
>
> On 28/03/17 16:00, "Rafael Weingärtner"
> wrote:
>
> I created a page describing the retirement process (it is general, not
&
after a while when questions came
forward but I am fine with the other questions as is.
On 28/03/17 16:00, "Rafael Weingärtner" wrote:
I created a page describing the retirement process (it is general, not
Midonet specific). Could I get some feedback from you guy
I created a page describing the retirement process (it is general, not
Midonet specific). Could I get some feedback from you guys?
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Plugin+retirement+process
Then, I will create a proper voting thread and proceed with the steps
described in
+1 on retiring midonet.
2017-03-28 10:50 GMT-03:00 Syed Ahmed :
> +1 That plugin needs to go :)
>
> On Mon, Mar 27, 2017 at 4:36 PM, Erik Weber wrote:
> > Sounds good :-)
> >
> >
> > Erik
> >
> > man. 27. mar. 2017 kl. 18.03 skrev Will Stevens :
>
d is a good first
>> > step.
>> > >>
>> > >> *Jeff Hair*
>> > >> Technical Lead and Software Developer
>> > >>
>> > >> Tel: (+354) 415 0200
>> > >> j...@greenqloud.com
>&g
t; > >> wrote:
> > >>
> > >> > +1 as others have noted
> > >> >
> > >> >
> > >> > Disable the plugin from the default build for next few releases
> > and
> > >> > e
> rohit.ya...@shapeblue.com>
> > >> wrote:
> > >>
> > >> > +1 as others have noted
> > >> >
> > >> >
> > >> > Disable the plugin from the default build for next few releases
>
ecate/remove the plugin from the codebase. The
> roadmap can
> >> > look something like:
> >> >
> >> > - Announce on the MLs that we're planning to do this, send a PR
> and get
> >> it
> >> > accepted
> >> &
>> > look something like:
>> >
>> > - Announce on the MLs that we're planning to do this, send a PR and get
>> it
>> > accepted
>> >
>> > - During the release process RM should make this information ava
do this, 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
>> > major changes in the voting emai
Sorry for the delay guys. I have been a little busy lately.
I will write down a wiki page detailing the code retirement steps. Then, I
will proceed and kick off the Midonet plugin retirement process.
On Mon, Mar 20, 2017 at 3:39 AM, Daan Hoogland
wrote:
> Don’t worry Marty, non-committ
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
dmap can
> > > look something like:
> > >
> > > - Announce on the MLs that we're planning to do this, send a PR
> and get
> > it
> > > accepted
> > >
> > > - During the release process RM should make this i
t build for next few releases
>> and
>> > > eventually deprecate/remove the plugin from the codebase. The
>> roadmap can
>> > > look something like:
>> > >
>> > > - Announce on the MLs that we're planning to do this, send a PR
>>
ding voting thread, would be nice to have a shortlog of
> > 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
> &g
on the MLs that we're planning to do this, 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
> > major changes in the votin
s 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
>
> - By end of the year, if we've no communication received deprecate and
> remove the plugin with an announcem
lease process RM should make this information available to
everyone (including voting thread, would be nice to have a shortlog of 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
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
nt of midonet plugin
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 v
ussing 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
fin
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
Midokura told us that it was a bad idea, probably wouldn't work and
> we
> > should just switch to openstack.
> >
> >
> > - Si
> >
> > ____
> > From: Erik Weber
> > Sent: T
__
> From: Erik Weber
> Sent: Tuesday, March 14, 2017 3:28 AM
> To: dev
> Subject: Re: midonet-client and Guava dependency conflict
>
> On Mon, Mar 13, 2017 at 7:45 PM, Rafael Weingärtner
> wrote:
> > I got a reply
: Erik Weber
> Sent: Tuesday, March 14, 2017 3:28 AM
> To: dev
> Subject: Re: midonet-client and Guava dependency conflict
>
> On Mon, Mar 13, 2017 at 7:45 PM, Rafael Weingärtner
> wrote:
> > I got a reply from Midonet community; they said
just
switch to openstack.
- Si
From: Erik Weber
Sent: Tuesday, March 14, 2017 3:28 AM
To: dev
Subject: Re: midonet-client and Guava dependency conflict
On Mon, Mar 13, 2017 at 7:45 PM, Rafael Weingärtner
wrote
You use it, you maintain it. I am happy
> to charge money to whoever wants to not maintain what they use.
>
Having said this, what do you guys think about removing this plugin from
ACS? Then, we remove from our documentation the “MidoNet support”.
Nowadays, I think we may bring expectat
We took a look at testing it in the lab back in early 2016 and Midokura told
us that it was a bad idea, probably wouldn't work and we should just switch to
openstack.
- Si
From: Erik Weber
Sent: Tuesday, March 14, 2017 3:28 AM
To: dev
Subject: Re: mi
On Mon, Mar 13, 2017 at 7:45 PM, Rafael Weingärtner
wrote:
> I got a reply from Midonet community; they said that midonet-client was
> incorporated by midonet-cluster (
> https://github.com/midonet/midonet/tree/staging/v5.4/midonet-cluster).
>
>
> So, if anyone wants to invest
k we should check if
> there
> > > are
> > > > > > people
> > > > > > > using it, right?
> > > > > > >
> > > > > > > On Thu, Mar 9, 2017
I got a reply from Midonet community; they said that midonet-client was
incorporated by midonet-cluster (
https://github.com/midonet/midonet/tree/staging/v5.4/midonet-cluster).
So, if anyone wants to invest energy on this, it might be a good idea to
upgrade the dependency. Moreover, I start to
paul.an...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
-Original Message-
From: Jeff Hair [mailto:j...@greenqloud.com]
Sent: 10 March 2017 13:45
To: dev@cloudstack.apache.org
Subject: Re: midonet-client and Guava dependency
ing the guava classes from the Midonet jar
> works. Did that yesterday. I can't find any updated version of the jar on
> their cs-maven repository. The only one is 1.1.0.
>
> *Jeff Hair*
> Technical Lead and Software Developer
>
> Tel: (+354) 415 0200
> j...@greenqloud.com
Yes, I already confirmed removing the guava classes from the Midonet jar
works. Did that yesterday. I can't find any updated version of the jar on
their cs-maven repository. The only one is 1.1.0.
*Jeff Hair*
Technical Lead and Software Developer
Tel: (+354) 415 0200
j...@greenqlou
Have you thought/tried to be a bit more brute with this situation? Like
hammering the Midonet jar and removing the guava classes from it.
This idea of packaging libraries into a jar may cause these problems
because Maven will not be able to solve dependencies conflicts. Have we
checked if
After forcing the midonet jar to the end of the classpath, the error still
comes up. This means that the ordered classloader is being overridden, or
this problem is not solvable simply by changing classpath order. On an
important note, when running the simulator through embedded Jetty, this
does
The Midonet jar has Guava 18 packaged into it with the Shade plugin.
Guava-19.0 is also on the classpath. But for whatever
reason, com.google.common.base.Equivalence is being loaded from the Midonet
jar instead of guava-19.0.jar, even with an alphabetically sorted
classpath. This causes the error
Are these Guava classes in the Midonet jar? Or do you have two jars for the
same library with two different version in the lib folder?
On Fri, Mar 10, 2017 at 8:32 AM, Jeff Hair wrote:
> I have managed to confirm with advanced debugging techniques (i.e. sticking
> log statements ever
t;
> Several plugins in 'plugins/network-elements/' may be removed from the
> default build/packaging. However, 'midonet' was never fully implemented or
> completed and most definitely removed.
>
>
> Regards.
>
>
> F
+1 Retire unsupported plugins, with at least comment them from the default
build/packaging in plugins/pom.xml?
Several plugins in 'plugins/network-elements/' may be removed from the default
build/packaging. However, 'midonet' was never fully implemented or completed
The midonet plugin is not fully implemented or maintained for several years
now. Like several of the networking plugins, it started as a PoC but never got
finished to be used in production.
For such network plugins, unless you get support from your networking vendor
avoid using them
Marty, midonet has been in there for a long time but is not maintained
very well and as far as we know is not intensively tested in
production environments. So if you are willing to put in the effort
and maintain it you are very welcome (if you don't you are welcome to)
but your millage may
hypervisor so Midonet
has not been an option.
Regards,
Marty Godsey
Principal Engineer
nSource Solutions, LLC
-Original Message-
From: williamstev...@gmail.com [mailto:williamstev...@gmail.com] On Behalf Of
Will Stevens
Sent: Thursday, March 9, 2017 5:50 PM
To: dev@cloudstack.apache.org
You use it, you maintain it. I am
> > > happy
> > > > > > > to charge money to whoever wants to not maintain what they use.
> > > > > > >
> > > > > > > On Thu, Mar 9, 2017 at 7:11 PM, Rafael Weingärtner
> > > > &g
> > > > > > On Thu, Mar 9, 2017 at 7:11 PM, Rafael Weingärtner
> > > > > > > wrote:
> > > > > > > > Daan, before removing anything, I think we should check if
> > there
> > > > ar
Mar 9, 2017 at 7:11 PM, Rafael Weingärtner
> > > > > > wrote:
> > > > > > > Daan, before removing anything, I think we should check if
> there
> > > are
> > > > > > people
> > > > > > > using it, rig
> > people
> > > > > > using it, right?
> > > > > >
> > > > > > On Thu, Mar 9, 2017 at 11:08 AM, Daan Hoogland <
> > > > daan.hoogl...@gmail.com>
> > > > > > wrote:
> > > > > >
> > &g
2017 at 11:08 AM, Daan Hoogland <
> > > daan.hoogl...@gmail.com>
> > > > > wrote:
> > > > >
> > > > >> I was about to reply along those lines. As you brought it up, we
> are
> > > > >> now considering it. If the fix is
t; > > wrote:
> > > >
> > > >> I was about to reply along those lines. As you brought it up, we are
> > > >> now considering it. If the fix is easy I'd say let it stay till the
> > > >> next problem but it is ot the first time mido
Haha, your timing is amazing. There is another thread going on about
MidoNet right now. Are you using it already?
*Will STEVENS*
Lead Developer
<https://goo.gl/NYZ8KK>
On Thu, Mar 9, 2017 at 4:07 PM, Marty Godsey wrote:
> Has MidoNet support for XenServer been added to
e fix is easy I'd say let it stay till the
> > >> next problem but it is ot the first time mido bugs us.
> > >>
> > >> On Thu, Mar 9, 2017 at 5:07 PM, Simon Weller wrote:
> > >> > So this brings
; next problem but it is ot the first time mido bugs us.
> >>
> >> On Thu, Mar 9, 2017 at 5:07 PM, Simon Weller wrote:
> >> > So this brings up a good discussion point. As Jeff points out, the
> >> Midonet plugin hasn'
Has MidoNet support for XenServer been added to ACS 4.9.2?
Regards,
Marty Godsey
Principal Engineer
nSource Solutions, LLC
ill the
>> next problem but it is ot the first time mido bugs us.
>>
>> On Thu, Mar 9, 2017 at 5:07 PM, Simon Weller wrote:
>> > So this brings up a good discussion point. As Jeff points out, the
>> Midonet plugin hasn't been actively supported fo
the
> next problem but it is ot the first time mido bugs us.
>
> On Thu, Mar 9, 2017 at 5:07 PM, Simon Weller wrote:
> > So this brings up a good discussion point. As Jeff points out, the
> Midonet plugin hasn't been actively supported for almost 5 years. At what
> poin
As Jeff points out, the Midonet
> plugin hasn't been actively supported for almost 5 years. At what point do we
> consider retiring unsupported plugins?
>
>
> - Si
>
>
>
> From: Jeff Hair
> Sent: Thursday, March 9, 2017 9:43 A
So this brings up a good discussion point. As Jeff points out, the Midonet
plugin hasn't been actively supported for almost 5 years. At what point do we
consider retiring unsupported plugins?
- Si
From: Jeff Hair
Sent: Thursday, March 9, 2017 9:43 AM
To
After doing some more digging, I have confirmed the following:
- The midonet plugin is using the Maven Shade plugin to put a bunch of
dependencies into itself.
- The plugin hosted in this repository was last updated in 2013.
- Most importantly: removing all the guava stuff out of the
ept for com/google/common/base/Equivalence.class. The Equivalence class
is being loaded from the midonet jar for some reason, and that version does
not have the method needed. Thus, the error.
This is because Tomcat apparently does not load jars in alphabetical order
anymore, starting with version 8.
]
> Sent: Friday, March 27, 2015 10:41 AM
> To: dev
> Subject: Re: midonet test failures
>
> :)
>
> so you did do a clean etc, didn't you?
>
> thanks for allerting us
>
> On Fri, Mar 27, 2015 at 3:24 PM, Roger Crerie wrote:
>> Now that my OWM3 test failures
Sorry for the false alarm . The mvn clean seems to have done the trick.
Roger
-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent: Friday, March 27, 2015 10:41 AM
To: dev
Subject: Re: midonet test failures
:)
so you did do a clean etc, didn't you?
t
:)
so you did do a clean etc, didn't you?
thanks for allerting us
On Fri, Mar 27, 2015 at 3:24 PM, Roger Crerie wrote:
> Now that my OWM3 test failures are fixed I figured I would also alert the
> world to failures I am seeing on the midonet tests. Again I am building in
&g
Now that my OWM3 test failures are fixed I figured I would also alert the world
to failures I am seeing on the midonet tests. Again I am building in Cygwin on
a windows 7 system. I am attaching a text file of the errors I am seeing.
Roger
[INFO] Scanning for projects...
[INFO
/heads/master
from Dave Cahill
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=28af817 ]
CLOUDSTACK-4466: Fix DHCP capability breaks in 4.2 for MidoNet
A recent code change in NetworkManager causes NullPointerExceptions when DHCP
capability list is null.
The commit which made the
Yang.
Changes
---
Hi Sheng,
I checked and this still applies cleanly to master - would you mind applying it?
Thanks,
Dave.
Bugs: CLOUDSTACK-4466
Repository: cloudstack-git
Description
---
Changes in this patch are entirely confined to the MidoNet plugin itself.
A recent code change
Yang.
Changes
---
Rebased patch against master so that it can be applied there.
Bugs: CLOUDSTACK-4466
Repository: cloudstack-git
Description
---
Changes in this patch are entirely confined to the MidoNet plugin itself.
A recent code change in NetworkManager causes
ository: cloudstack-git
>
>
> Description
> ---
>
> Changes in this patch are entirely confined to the MidoNet plugin itself.
>
> A recent code change in NetworkManager causes NullPointerExceptions when DHCP
> capability list is null.
> The commit which made t
Done
From: Sheng Yang [mailto:sh...@yasker.org]
Sent: Tuesday, August 27, 2013 1:29 PM
To: Animesh Chaturvedi;
Subject: [ACS42] CLOUDSTACK-4466: Fix DHCP capability breaks in 4.2 for MidoNet
Hi Animesh,
Please cherry-pick the following commit from 4.2-forward branch.
commit
Hi Animesh,
Please cherry-pick the following commit from 4.2-forward branch.
commit a55c75bbd201e53f0aca3e8f8f9dee08cd132a95
Author: Dave Cahill
Date: Tue Aug 27 11:55:49 2013 -0700
CLOUDSTACK-4466: Fix DHCP capability breaks in 4.2 for MidoNet
A recent code change in NetworkManager
/heads/4.2 from
Dave Cahill
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=41d2fb3 ]
CLOUDSTACK-4466: Fix DHCP capability breaks in 4.2 for MidoNet
A recent code change in NetworkManager causes NullPointerExceptions when DHCP
capability list is null.
The commit which made the
t: Re: Review Request 13759: Fix CLOUDSTACK-4466 - DHCP capability
> breaks in 4.2 for MidoNet
>
>
>
> > On Aug. 27, 2013, 7:08 p.m., Sheng Yang wrote:
> > > Ship It!
>
> I've pushed to 4.2-forwarding.
>
> But Dave, could you rebase to master? I canno
and Hugo Trippaers.
>
>
> Bugs: CLOUDSTACK-4466
>
>
> Repository: cloudstack-git
>
>
> Description
> ---
>
> Changes in this patch are entirely confined to the MidoNet plugin itself.
>
> A recent code change in NetworkManager causes NullPointerExcepti
/heads/4.2-forward from Dave Cahill
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a55c75b ]
CLOUDSTACK-4466: Fix DHCP capability breaks in 4.2 for MidoNet
A recent code change in NetworkManager causes NullPointerExceptions when DHCP
capability list is null.
The commit which made the
a.m.)
>
>
> Review request for cloudstack and Hugo Trippaers.
>
>
> Bugs: CLOUDSTACK-4466
>
>
> Repository: cloudstack-git
>
>
> Description
> ---
>
> Changes in this patch are entirely confined to the MidoNet plugin itself.
>
> A rec
Trippaers.
Bugs: CLOUDSTACK-4466
Repository: cloudstack-git
Description
---
Changes in this patch are entirely confined to the MidoNet plugin itself.
A recent code change in NetworkManager causes NullPointerExceptions when DHCP
capability list is null.
The commit which made the
-git
Description
---
Changes in this patch are entirely confined to the MidoNet plugin itself.
A recent code change in NetworkManager causes NullPointerExceptions when DHCP
capability list is null.
The commit which made the NetworkManager change also changed the VirtualRouter
to not use
m: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> >> > Sent: Tuesday, August 13, 2013 1:48 PM
> >> > To: dev@cloudstack.apache.org
> >> > Subject: Re: Build failure in 4.2 with Midokura Midonet
> >> >
> >> > I ran
&g
inal Message-
>> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> > Sent: Tuesday, August 13, 2013 1:48 PM
>> > To: dev@cloudstack.apache.org
>> > Subject: Re: Build failure in 4.2 with Midokura Midonet
>> >
>> > I ran
>&g
1 - 100 of 151 matches
Mail list logo
