[one-users] Accessing custom attributes from drivers

[Székelyi Szabolcs]

Hi Tino,

On Friday 14 May 2010 19:59:21 Tino Vazquez wrote:
> 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?

Our plans are that we store the VMs' images on an iSCSI storage, one iSCSI 
target per VM. Since we don't want our VM images to be accessible from the 
whole wide world, we plan to employ username/password based authentication 
offered by the iSCSI protocol.

Different VMs will be owned by different organizations, and we plan to provide 
direct access to the iSCSI targets in case a user wants to migrate data off 
his disks for example.

In our case, the iSCSI username and password associated with a particular VM 
would be examples of such attributes.

Cheers,
-- 
cc

> 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