On Tue, Apr 15, 2008 at 02:23:53PM -0700, Ryan Scott wrote:
> Daniel P. Berrange wrote:
> >On Tue, Apr 15, 2008 at 11:31:32AM -0700, Ryan Scott wrote:
> >> I'd like to get some comments on the following...
> >>
> >> We would like to use libvirt to store some properties related to a
> >>domain.
On Wed, Apr 16, 2008 at 12:13:09PM +0100, John Levon wrote:
> On Wed, Apr 16, 2008 at 03:58:16AM -0400, Daniel Veillard wrote:
>
> > > One thing we have in mind is driver/software version numbers. For
> > > example, the control tools may change the domain configuration based on
> > > whether a
On Wed, Apr 16, 2008 at 08:34:23AM -0400, Daniel Veillard wrote:
> > want to be able to associate textual descriptions of the asset, or
> > define ownership. All of these are higher-level values that don't
> > necessarily have any meaning to the v12n technology itself. More
> > crucially they can
On Wed, Apr 16, 2008 at 12:13:09PM +0100, John Levon wrote:
> On Wed, Apr 16, 2008 at 03:58:16AM -0400, Daniel Veillard wrote:
>
> > > One thing we have in mind is driver/software version numbers. For
> > > example, the control tools may change the domain configuration based on
> > > whether a
On Wed, Apr 16, 2008 at 03:58:16AM -0400, Daniel Veillard wrote:
> > One thing we have in mind is driver/software version numbers. For
> > example, the control tools may change the domain configuration based on
> > whether a certain driver has the support for a new feature. If we
> > create t
On Tue, Apr 15, 2008 at 02:23:53PM -0700, Ryan Scott wrote:
> Daniel P. Berrange wrote:
> >On Tue, Apr 15, 2008 at 11:31:32AM -0700, Ryan Scott wrote:
> >> I'd like to get some comments on the following...
> >>
> >> We would like to use libvirt to store some properties related to a
> >>domain.
Henri Cook wrote:
My first thought as a layman is that libvirt should only contain
information related to the actual running of the virtual machine i.e.
not things that might concern say, customer data (this may not be your
use case).
I would say that's up to the end user to manage with their ow
Daniel P. Berrange wrote:
On Tue, Apr 15, 2008 at 11:31:32AM -0700, Ryan Scott wrote:
I'd like to get some comments on the following...
We would like to use libvirt to store some properties related to a
domain. This can be done by adding a simple get/set API as follows:
What are the pro
On Tue, Apr 15, 2008 at 11:31:32AM -0700, Ryan Scott wrote:
>
> I'd like to get some comments on the following...
>
> We would like to use libvirt to store some properties related to a
> domain. This can be done by adding a simple get/set API as follows:
>
> /*
> * Domain property get/set
My first thought as a layman is that libvirt should only contain
information related to the actual running of the virtual machine i.e.
not things that might concern say, customer data (this may not be your
use case).
I would say that's up to the end user to manage with their own
databases, cross r
On Tue, Apr 15, 2008 at 11:31:32AM -0700, Ryan Scott wrote:
>
> I'd like to get some comments on the following...
>
> We would like to use libvirt to store some properties related to a
> domain. This can be done by adding a simple get/set API as follows:
What are the properties ? I'm not
I'd like to get some comments on the following...
We would like to use libvirt to store some properties related to a
domain. This can be done by adding a simple get/set API as follows:
/*
* Domain property get/set interfaces
*
* For GetProp, the return value must be freed by the calle
12 matches
Mail list logo
