add an entry and remove one. It
> looks like most External DHCP providers are going to use the standard
> Plugin prepare/release interface, like I have for our solution.
> -Soheil
>
> From: Sheng Yang [sh...@yasker.org]
> Sent: Friday, Septem
From: Sheng Yang [sh...@yasker.org]
Sent: Friday, September 13, 2013 4:23 PM
To:
Subject: Re: DhcpServiceProvider
In the original implementation, the new dhcp entry would automatically
override the old one, so the old entry hasn't been removed explicitly.
But stil
In the original implementation, the new dhcp entry would automatically
override the old one, so the old entry hasn't been removed explicitly.
But still, it would be better to get it done explicitly of course.
--Sheng
On Fri, Sep 13, 2013 at 1:20 PM, Chiradeep Vittal <
chiradeep.vit...@citrix.co
Soheil, agree that it needs to moved to NetworkElement and also needs
complementary remove()
It seems half-thought-out.
On 9/13/13 11:31 AM, "Soheil Eizadi" wrote:
>Posting my questions again... -Soheil
>
>From: Soheil Eizadi [seiz...@infoblox.com]
>Sent:
Posting my questions again... -Soheil
From: Soheil Eizadi [seiz...@infoblox.com]
Sent: Friday, September 06, 2013 3:13 PM
To: dev@cloudstack.apache.org
Subject: DhcpServiceProvider
I had not looked at the DhcpServiceProvider NetworkElement before, but after
