[one-users] Accessing custom attributes from drivers

[Tino Vazquez]

Hi there,

I agree with you that this is a bit cumbersome.

Could you please elaborate a bit more on why do you need to
user-defined attributes in a TM script?

Regards,

-Tino

--
Constantino Vázquez, Grid & Virtualization Technology
Engineer/Researcher: http://www.dsa-research.org/tinova
DSA Research Group: http://dsa-research.org
Globus GridWay Metascheduler: http://www.GridWay.org
OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org



2010/4/20 SZÉKELYI Szabolcs <szekelyi at niif.hu>:
> Hi ONE world,
>
> the ability of adding user-defined attributes to VM configuration is a nice
> feature, but...
>
> Suppose I need the value of a custom attribute in a TM script. Currently the
> only way of accessing it is to parse the command line parameters to determine
> the VID then feeding it to onevm, parsing its output as well, looking for the
> attribute name. This method, in my opinion, can be called anything but fancy
> and reliable.
>
> Is there a better way of accessing there parameters from drivers and MADs?
>
> Thanks,
> --
> cc
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>