Hello,
Thanks for your answer. Well i've the same feeling : it would be great
but need some works to have a per device custom properties : database
schema upgrade, code interfaces modifications, ... and I'm not a java
dev.
Regards,
2012/12/2 Dan Kenigsberg <danken(a)redhat.com>:
On Fri, Nov 30, 2012 at 02:15:31PM +0100, Benoit ML wrote:
> Hello Evrybody,
>
> Is there a way to add custom properties for a nic ? and use it in vdsm_hooks ?
>
> The objectife is to redefine some network parameters of a vnic at the
> vm boot ... (such per vnic bandwitchs, per vnic vlan, and so on) and
> maybe use openvswitch ...
I would very much like to see something like that, but at the moment,
custom properties exist only in the VM level.
You could hack around it by defining nicproperties that accepts a
nested dictionary of {nicID: {property: value}, }
But it would be a cruel and unusual punishment to edit it.
Not long ago, Itzik and Mark discussed the need of per-nic custom
properties on Gerrit. At least on the Vdsm side, it would rather easy to
define: I suggest that each "device" definition would have a
"custom"
attribute, similar to the per-vm one. This should be a dictionary
holding unicode key/value pairs, that would be passed as
<devalias>_<customname> environment variables to the hook script.
I know Engine much less, but I do not suppose it would be hard to model
something like this there.
Dan.
--
--
Benoit