Re: [vdsm] what does custom option mean when vmcreate ?
On Fri, Jan 03, 2014 at 07:55:02AM -0500, Martin Perina wrote:
>
>
> - Original Message -
> > From: "Eli Mesika"
> > To: "Dan Kenigsberg"
> > Cc: "Michal Skrivanek" , ilvov...@gmail.com,
> > "bigclouds" ,
> > vdsm-devel@lists.fedorahosted.org, "Martin Perina"
> > Sent: Friday, January 3, 2014 1:30:14 PM
> > Subject: Re: [vdsm] what does custom option mean when vmcreate ?
> >
> >
> >
> > - Original Message -
> > > From: "Dan Kenigsberg"
> > > To: "Michal Skrivanek" , emes...@redhat.com,
> > > ilvov...@gmail.com
> > > Cc: "bigclouds" , vdsm-devel@lists.fedorahosted.org
> > > Sent: Friday, January 3, 2014 12:42:54 PM
> > > Subject: Re: [vdsm] what does custom option mean when vmcreate ?
> > >
> > > On Fri, Jan 03, 2014 at 11:25:04AM +0100, Michal Skrivanek wrote:
> > > >
> > > > On 26 Dec 2013, at 07:32, bigclouds wrote:
> > > >
> > > > > the paramters received when vmCreate has a long part called custom,
> > > > > do we use custom infomation? what does the long key
> > > > > device_* means?
> > > >
> > > > custom properties for devices
> > > > see the UI Custom Properties tab in Edit VM
> > >
> > > I think that bigclouds meant the bizarre-looking properties that are
> > > sent by Engine automatically, with no human interventions, per VmDevice
> > > that
> > > is
> > > reported by Vdsm but not managed by Engine:
> > >
> > > 'device_82934f8e-7470-4c46-b9ed-d1c73fb17477device_87f6330a-278d-4b2a-9674-db58eb0e7023device_a19855be-70a9-49d0-9ea4-ee746b2d9739':
> > > 'VmDevice {vmId=46914913-8bcf-4fa0-b1fb-3680ca8b6c16,
> > > deviceId=a19855be-70a9-49d0-9ea4-ee746b2d9739, device=virtio-serial,
> > > type=CONTROLLER, bootOrder=0, specParams={}, address={bus=0x00,
> > > domain=0x, type=pci, slot=0x06, function=0x0}, managed=false,
> > > plugged=true, readOnly=false, deviceAlias=virtio-serial0,
> > > customProperties={}, snapshotId=null}'
> > >
> > > It was an attempt for future-compatibility, by (ab)using the custom
> > > properties
> > > interface. Certainly Eli or Igor can explain the motivation better.
> >
> > This was added later by Martin P at commit hash
> > a9723b34c13ee55bd81ddf6e8032901b090a6dc3
> > Martin can you please elaborate on that? Thanks
> >
> >
>
> Hi,
>
> Device Custom Properties is a 3.3 feature by which you can specify
> custom properties for specific device types using same format as
> for VM properties (more info on [1]).
>
> AFAIK only vNIC devices is currently using this feature.
>
> Martin
>
> [1] http://www.ovirt.org/Features/Device_Custom_Properties
No, that's not what I was refering to. I believe that bigclouds refered
to a much older per-Vm custom properties. bigclouds, could you dump the
vmCreate line you refer to?
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] what does custom option mean when vmcreate ?
- Original Message -
> From: "Eli Mesika"
> To: "Dan Kenigsberg"
> Cc: "Michal Skrivanek" , ilvov...@gmail.com,
> "bigclouds" ,
> vdsm-devel@lists.fedorahosted.org, "Martin Perina"
> Sent: Friday, January 3, 2014 1:30:14 PM
> Subject: Re: [vdsm] what does custom option mean when vmcreate ?
>
>
>
> - Original Message -
> > From: "Dan Kenigsberg"
> > To: "Michal Skrivanek" , emes...@redhat.com,
> > ilvov...@gmail.com
> > Cc: "bigclouds" , vdsm-devel@lists.fedorahosted.org
> > Sent: Friday, January 3, 2014 12:42:54 PM
> > Subject: Re: [vdsm] what does custom option mean when vmcreate ?
> >
> > On Fri, Jan 03, 2014 at 11:25:04AM +0100, Michal Skrivanek wrote:
> > >
> > > On 26 Dec 2013, at 07:32, bigclouds wrote:
> > >
> > > > the paramters received when vmCreate has a long part called custom,
> > > > do we use custom infomation? what does the long key
> > > > device_* means?
> > >
> > > custom properties for devices
> > > see the UI Custom Properties tab in Edit VM
> >
> > I think that bigclouds meant the bizarre-looking properties that are
> > sent by Engine automatically, with no human interventions, per VmDevice
> > that
> > is
> > reported by Vdsm but not managed by Engine:
> >
> > 'device_82934f8e-7470-4c46-b9ed-d1c73fb17477device_87f6330a-278d-4b2a-9674-db58eb0e7023device_a19855be-70a9-49d0-9ea4-ee746b2d9739':
> > 'VmDevice {vmId=46914913-8bcf-4fa0-b1fb-3680ca8b6c16,
> > deviceId=a19855be-70a9-49d0-9ea4-ee746b2d9739, device=virtio-serial,
> > type=CONTROLLER, bootOrder=0, specParams={}, address={bus=0x00,
> > domain=0x, type=pci, slot=0x06, function=0x0}, managed=false,
> > plugged=true, readOnly=false, deviceAlias=virtio-serial0,
> > customProperties={}, snapshotId=null}'
> >
> > It was an attempt for future-compatibility, by (ab)using the custom
> > properties
> > interface. Certainly Eli or Igor can explain the motivation better.
>
> This was added later by Martin P at commit hash
> a9723b34c13ee55bd81ddf6e8032901b090a6dc3
> Martin can you please elaborate on that? Thanks
>
>
Hi,
Device Custom Properties is a 3.3 feature by which you can specify
custom properties for specific device types using same format as
for VM properties (more info on [1]).
AFAIK only vNIC devices is currently using this feature.
Martin
[1] http://www.ovirt.org/Features/Device_Custom_Properties
> >
> > Dan.
> >
>
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] what does custom option mean when vmcreate ?
- Original Message -
> From: "Dan Kenigsberg"
> To: "Michal Skrivanek" , emes...@redhat.com,
> ilvov...@gmail.com
> Cc: "bigclouds" , vdsm-devel@lists.fedorahosted.org
> Sent: Friday, January 3, 2014 12:42:54 PM
> Subject: Re: [vdsm] what does custom option mean when vmcreate ?
>
> On Fri, Jan 03, 2014 at 11:25:04AM +0100, Michal Skrivanek wrote:
> >
> > On 26 Dec 2013, at 07:32, bigclouds wrote:
> >
> > > the paramters received when vmCreate has a long part called custom,
> > > do we use custom infomation? what does the long key
> > > device_* means?
> >
> > custom properties for devices
> > see the UI Custom Properties tab in Edit VM
>
> I think that bigclouds meant the bizarre-looking properties that are
> sent by Engine automatically, with no human interventions, per VmDevice that
> is
> reported by Vdsm but not managed by Engine:
>
> 'device_82934f8e-7470-4c46-b9ed-d1c73fb17477device_87f6330a-278d-4b2a-9674-db58eb0e7023device_a19855be-70a9-49d0-9ea4-ee746b2d9739':
> 'VmDevice {vmId=46914913-8bcf-4fa0-b1fb-3680ca8b6c16,
> deviceId=a19855be-70a9-49d0-9ea4-ee746b2d9739, device=virtio-serial,
> type=CONTROLLER, bootOrder=0, specParams={}, address={bus=0x00,
> domain=0x, type=pci, slot=0x06, function=0x0}, managed=false,
> plugged=true, readOnly=false, deviceAlias=virtio-serial0,
> customProperties={}, snapshotId=null}'
>
> It was an attempt for future-compatibility, by (ab)using the custom
> properties
> interface. Certainly Eli or Igor can explain the motivation better.
This was added later by Martin P at commit hash
a9723b34c13ee55bd81ddf6e8032901b090a6dc3
Martin can you please elaborate on that? Thanks
>
> Dan.
>
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] what does custom option mean when vmcreate ?
On Fri, Jan 03, 2014 at 11:25:04AM +0100, Michal Skrivanek wrote:
>
> On 26 Dec 2013, at 07:32, bigclouds wrote:
>
> > the paramters received when vmCreate has a long part called custom,
> > do we use custom infomation? what does the long key
> > device_* means?
>
> custom properties for devices
> see the UI Custom Properties tab in Edit VM
I think that bigclouds meant the bizarre-looking properties that are
sent by Engine automatically, with no human interventions, per VmDevice that is
reported by Vdsm but not managed by Engine:
'device_82934f8e-7470-4c46-b9ed-d1c73fb17477device_87f6330a-278d-4b2a-9674-db58eb0e7023device_a19855be-70a9-49d0-9ea4-ee746b2d9739':
'VmDevice {vmId=46914913-8bcf-4fa0-b1fb-3680ca8b6c16,
deviceId=a19855be-70a9-49d0-9ea4-ee746b2d9739, device=virtio-serial,
type=CONTROLLER, bootOrder=0, specParams={}, address={bus=0x00, domain=0x,
type=pci, slot=0x06, function=0x0}, managed=false, plugged=true,
readOnly=false, deviceAlias=virtio-serial0, customProperties={},
snapshotId=null}'
It was an attempt for future-compatibility, by (ab)using the custom properties
interface. Certainly Eli or Igor can explain the motivation better.
Dan.
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] what does custom option mean when vmcreate ?
On 26 Dec 2013, at 07:32, bigclouds wrote: > the paramters received when vmCreate has a long part called custom, > do we use custom infomation? what does the long key > device_* means? custom properties for devices see the UI Custom Properties tab in Edit VM Thanks, michal > > thanks > > > ___ > vdsm-devel mailing list > vdsm-devel@lists.fedorahosted.org > https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] what does custom option mean when vmcreate ?
the paramters received when vmCreate has a long part called custom, do we use custom infomation? what does the long key device_* means? thanks___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
