Hi,

In the compute service api there is a template option 'userMetaData', but this 
data is merged with the tags in the CloudStack adapter. [1]
In the CloudStack specific options there is also a 'userData' property [2] . Is 
there plan to be able to populate this via the general template options and 
embed this in the CloudStackTemplateOptions?
That specific property is very useful for our provisioning because it becomes 
available via a simple VM local REST api [3]. This way we can figure out what 
to install on the VM without having to consult CloudStack for the  tags, since 
these are not available via that local api.

This is for me the only reason I now have to use the CloudStack specific 
compute api so I don't benefit from all the high level goodies.

- Irmo

[1] 
https://github.com/jclouds/jclouds/blob/master/apis/cloudstack/src/main/java/org/jclouds/cloudstack/compute/strategy/CloudStackComputeServiceAdapter.java#L256
[2] 
https://github.com/jclouds/jclouds/blob/master/apis/cloudstack/src/main/java/org/jclouds/cloudstack/compute/options/CloudStackTemplateOptions.java
[3] http://cloudstack-administration.readthedocs.org/en/latest/api.html





=========== The Leonteq Mail Gateway made the following annotation ===========

This e-mail is confidential. If you are not the intended recipient, you should

not copy it, re-transmit it, use it or disclose its contents, but should

return it to the sender immediately and delete the copy from your system.

Leonteq Securities is not responsible for, nor endorses, any opinion,

recommendation, conclusion, solicitation, offer or agreement or any

information contained in this communication.

Leonteq Securities cannot accept any responsibility for the accuracy or

completeness of this message as it has been transmitted over a public network.

If you suspect that the message may have been intercepted or amended, please

call the sender. Should you require any further information, please contact

the Compliance Manager on [email protected]<mailto:[email protected]>.



==============================================================================

Reply via email to