Re: [libvirt] [PATCH v2 1/4] virInterface: Expose link state & speed

2014-06-11 Thread Daniel P. Berrange
On Wed, Jun 11, 2014 at 06:46:25AM -0400, John Ferlan wrote: > > > On 06/11/2014 05:19 AM, Michal Privoznik wrote: > > On 11.06.2014 03:13, John Ferlan wrote: > >> > >> > >> On 06/05/2014 11:39 AM, Michal Privoznik wrote: > >>> Currently it is not possible to determine the speed of an interface >

Re: [libvirt] [PATCH v2 1/4] virInterface: Expose link state & speed

2014-06-11 Thread John Ferlan
On 06/11/2014 05:19 AM, Michal Privoznik wrote: > On 11.06.2014 03:13, John Ferlan wrote: >> >> >> On 06/05/2014 11:39 AM, Michal Privoznik wrote: >>> Currently it is not possible to determine the speed of an interface >>> and whether a link is actually detected from the API. Orchestrating >>> pl

Re: [libvirt] [PATCH v2 1/4] virInterface: Expose link state & speed

2014-06-11 Thread Laine Stump
On 06/11/2014 01:11 PM, Daniel P. Berrange wrote: > On Wed, Jun 11, 2014 at 01:04:02PM +0300, Laine Stump wrote: >> I had thought that what was required was the ability to roundtrip the >> *inactive* xml back into a define, not the status XML. If it's really a >> requirement that we be able to feed

Re: [libvirt] [PATCH v2 1/4] virInterface: Expose link state & speed

2014-06-11 Thread Daniel P. Berrange
On Wed, Jun 11, 2014 at 01:04:02PM +0300, Laine Stump wrote: > On 06/11/2014 12:28 PM, Daniel P. Berrange wrote: > > On Wed, Jun 11, 2014 at 11:19:14AM +0200, Michal Privoznik wrote: > >> On 11.06.2014 03:13, John Ferlan wrote: > >>> > >>> On 06/05/2014 11:39 AM, Michal Privoznik wrote: > Curr

Re: [libvirt] [PATCH v2 1/4] virInterface: Expose link state & speed

2014-06-11 Thread Laine Stump
On 06/11/2014 12:28 PM, Daniel P. Berrange wrote: > On Wed, Jun 11, 2014 at 11:19:14AM +0200, Michal Privoznik wrote: >> On 11.06.2014 03:13, John Ferlan wrote: >>> >>> On 06/05/2014 11:39 AM, Michal Privoznik wrote: Currently it is not possible to determine the speed of an interface and

Re: [libvirt] [PATCH v2 1/4] virInterface: Expose link state & speed

2014-06-11 Thread Daniel P. Berrange
On Wed, Jun 11, 2014 at 11:19:14AM +0200, Michal Privoznik wrote: > On 11.06.2014 03:13, John Ferlan wrote: > > > > > >On 06/05/2014 11:39 AM, Michal Privoznik wrote: > >>Currently it is not possible to determine the speed of an interface > >>and whether a link is actually detected from the API. Or

Re: [libvirt] [PATCH v2 1/4] virInterface: Expose link state & speed

2014-06-11 Thread Michal Privoznik
On 11.06.2014 03:13, John Ferlan wrote: On 06/05/2014 11:39 AM, Michal Privoznik wrote: Currently it is not possible to determine the speed of an interface and whether a link is actually detected from the API. Orchestrating platforms want to be able to determine when the link has failed and wh

Re: [libvirt] [PATCH v2 1/4] virInterface: Expose link state & speed

2014-06-10 Thread John Ferlan
On 06/05/2014 11:39 AM, Michal Privoznik wrote: > Currently it is not possible to determine the speed of an interface > and whether a link is actually detected from the API. Orchestrating > platforms want to be able to determine when the link has failed and > where multiple speeds may be availabl

[libvirt] [PATCH v2 1/4] virInterface: Expose link state & speed

2014-06-05 Thread Michal Privoznik
Currently it is not possible to determine the speed of an interface and whether a link is actually detected from the API. Orchestrating platforms want to be able to determine when the link has failed and where multiple speeds may be available which one the interface is actually connected at. This c