Hi, Your suggested change seems to work.
I now get the following code in the guest customisation script, when I look it up in the vcloud GUI: #!/bin/sh mkdir -p /tmp/payload echo “SERVICE_NAME=foo,HOST_NAME=<...snip...>,MIN_COUNT=1" > /tmp/payload/launch-params /root/bin/init-vcloud.sh > /tmp/puppet_log Somehow, in my cartridge, the /tmp/payload directory was missing, despite this script sitting on the VM. I need to debug that a bit more, hopefully it’s just an issue with my setup. I’ll report back when I know more. Thanks and best regards, Michiel On 10 Nov 2014, at 14:36, Michiel Blokzijl (mblokzij) <mblok...@cisco.com> wrote: > Sure, I’ll look into it. I’ll let you know how it goes. > > Thanks for all the help! > > Michiel > > On 10 Nov 2014, at 07:02, Udara Liyanage <ud...@wso2.com> wrote: > >> Hi Michel, >> >> Could you try with the proposed change and try again. >> >> On Mon, Nov 10, 2014 at 12:22 PM, Isuru Perera <isu...@wso2.com> wrote: >> Hi Udara, >> >> As you mentioned, we should be using the API for the customization script. >> >> I missed this API when implementing the support for passing payload. >> >> Shall we change the code and test? >> >> Michiel, As I know, from the beginning, we have been passing the payload >> from a script. As Udara found out, we have actually implemented it using the >> runScript option, rather than using the customizationScript API. >> >> We must fix that in VCloudIaas.java >> >> I hope that in this way, we can avoid the ssh session with the VM. >> >> Thanks! >> >> Best Regards, >> >> On Mon, Nov 10, 2014 at 11:58 AM, Udara Liyanage <ud...@wso2.com> wrote: >> Hi Isuru, Nirmal, >> >> I have have doubt whether we are really using the customization script. >> Currently code call the runScript() as below. >> >> template.getOptions().runScript(customizationScript); >> >> Aren't we executing as a script as Michel mentioned ? >> >> Isn't below is the correct way of doing? >> >> template.getOptions().as(VCloudTemplateOptions.class).customizationScript(customizationScript); >> >> >> On Mon, Nov 10, 2014 at 8:46 AM, Udara Liyanage <ud...@wso2.com> wrote: >> Hi, >> >> Yes metadata is passed via guest customization script from Stratos side. >> However Jclouds execute the customization script using ssh. >> >> Please refer to setDynamicPayload() of [1] for implementation >> >> [1] >> https://github.com/apache/stratos/blob/master/components/org.apache.stratos.cloud.controller/src/main/java/org/apache/stratos/cloud/controller/iaases/VCloudIaas.java >> >> >> >> Touched, not typed. Erroneous words are a feature, not a typo. >> >> >> >> >> -- >> >> Udara Liyanage >> Software Engineer >> WSO2, Inc.: http://wso2.com >> lean. enterprise. middleware >> >> web: http://udaraliyanage.wordpress.com >> phone: +94 71 443 6897 >> >> >> >> -- >> Isuru Perera >> Senior Software Engineer | WSO2, Inc. | http://wso2.com/ >> Lean . Enterprise . Middleware >> >> about.me/chrishantha >> >> >> >> -- >> >> Udara Liyanage >> Software Engineer >> WSO2, Inc.: http://wso2.com >> lean. enterprise. middleware >> >> web: http://udaraliyanage.wordpress.com >> phone: +94 71 443 6897 >
signature.asc
Description: Message signed with OpenPGP using GPGMail
