On 15/08/13 19:32, Daniel P. Berrange wrote:
On Wed, Aug 14, 2013 at 04:57:51AM +0530, Nehal J. Wani wrote:
On Wed, Aug 14, 2013 at 4:29 AM, Eric Blake ebl...@redhat.com wrote:
On 08/13/2013 04:48 PM, Eric Blake wrote:
virNetworkGetDHCPLeaseForMAC(virNetworkPtr network,
On Wed, Aug 14, 2013 at 04:57:51AM +0530, Nehal J. Wani wrote:
On Wed, Aug 14, 2013 at 4:29 AM, Eric Blake ebl...@redhat.com wrote:
On 08/13/2013 04:48 PM, Eric Blake wrote:
virNetworkGetDHCPLeaseForMAC(virNetworkPtr network,
unsigned char *macaddr,
On 07/25/2013 03:35 AM, Daniel P. Berrange wrote:
NACK,
As I explained on IRC, the hypervisor drivers have no business accessing
the dnsmasq lease files from the bridge driver. This is considered to be
a private implementation detail.
At a conceptual level, what you're after here is a
On 08/13/2013 04:48 PM, Eric Blake wrote:
virNetworkGetDHCPLeaseForMAC(virNetworkPtr network,
unsigned char *macaddr,
I personally think the public API should stick to stringized
representations. Yes, it's less friendly to machine code, but
internally,
On Wed, Aug 14, 2013 at 4:29 AM, Eric Blake ebl...@redhat.com wrote:
On 08/13/2013 04:48 PM, Eric Blake wrote:
virNetworkGetDHCPLeaseForMAC(virNetworkPtr network,
unsigned char *macaddr,
I personally think the public API should stick to stringized
Currently, there is no API which returns configuration/state paths of the
network driver.
Although it is a private implementation of the network driver, I don't see
any harm in
making the locations public because although the locations might change,
there will always
be a location for these files.
On Thu, Jul 25, 2013 at 02:02:36PM +0530, Nehal J. Wani wrote:
Currently, there is no API which returns configuration/state paths of the
network driver.
Although it is a private implementation of the network driver, I don't see
any harm in
making the locations public because although the
On 25/07/13 17:35, Daniel P. Berrange wrote:
On Thu, Jul 25, 2013 at 02:02:36PM +0530, Nehal J. Wani wrote:
Currently, there is no API which returns configuration/state paths of the
network driver.
Although it is a private implementation of the network driver, I don't see
any harm in
making the
On Thu, Jul 25, 2013 at 06:43:00PM +0800, Osier Yang wrote:
On 25/07/13 17:35, Daniel P. Berrange wrote:
On Thu, Jul 25, 2013 at 02:02:36PM +0530, Nehal J. Wani wrote:
Currently, there is no API which returns configuration/state paths of the
network driver.
Although it is a private
On 25/07/13 18:53, Daniel P. Berrange wrote:
On Thu, Jul 25, 2013 at 06:43:00PM +0800, Osier Yang wrote:
On 25/07/13 17:35, Daniel P. Berrange wrote:
On Thu, Jul 25, 2013 at 02:02:36PM +0530, Nehal J. Wani wrote:
Currently, there is no API which returns configuration/state paths of the
On Thu, Jul 25, 2013 at 07:01:05PM +0800, Osier Yang wrote:
On 25/07/13 18:53, Daniel P. Berrange wrote:
On Thu, Jul 25, 2013 at 06:43:00PM +0800, Osier Yang wrote:
On 25/07/13 17:35, Daniel P. Berrange wrote:
On Thu, Jul 25, 2013 at 02:02:36PM +0530, Nehal J. Wani wrote:
Currently, there is
On 25/07/13 19:13, Daniel P. Berrange wrote:
On Thu, Jul 25, 2013 at 07:01:05PM +0800, Osier Yang wrote:
On 25/07/13 18:53, Daniel P. Berrange wrote:
On Thu, Jul 25, 2013 at 06:43:00PM +0800, Osier Yang wrote:
On 25/07/13 17:35, Daniel P. Berrange wrote:
On Thu, Jul 25, 2013 at 02:02:36PM
On 25/07/13 19:21, Osier Yang wrote:
On 25/07/13 19:13, Daniel P. Berrange wrote:
On Thu, Jul 25, 2013 at 07:01:05PM +0800, Osier Yang wrote:
On 25/07/13 18:53, Daniel P. Berrange wrote:
On Thu, Jul 25, 2013 at 06:43:00PM +0800, Osier Yang wrote:
On 25/07/13 17:35, Daniel P. Berrange wrote:
On Thu, Jul 25, 2013 at 07:37:22PM +0800, Osier Yang wrote:
On 25/07/13 19:21, Osier Yang wrote:
On 25/07/13 19:13, Daniel P. Berrange wrote:
On Thu, Jul 25, 2013 at 07:01:05PM +0800, Osier Yang wrote:
On 25/07/13 18:53, Daniel P. Berrange wrote:
On Thu, Jul 25, 2013 at 06:43:00PM +0800,
14 matches
Mail list logo