Planning to implement following solution. 1. Define "shell_type" as a property in Cartridge Definition. Possible values can be "bash", "sh", "cmd", etc.
2. Dynamically create a customization script based on "shell_type" in vCloud IaaS implementation. I will try to implement this in an extensible way (without code modifications) for any shell_type. Thanks! Best Regards, On Thu, Mar 13, 2014 at 10:32 AM, Isuru Perera <isu...@wso2.com> wrote: > Thanks Udara for the information. > > So, it seems we have to go ahead with the use of customization script in > vCloud. > > Next problem is that the script is dependent on the target Cartridge OS. > > Please let me know if you have any suggestions to solve this problem. > > > On Thu, Mar 13, 2014 at 7:44 AM, Udara Liyanage <ud...@wso2.com> wrote: > >> AFIR the metadata is read by a init script inside the instance, not the >> cartridge agent. >> In EC2 and Openstack we can pass the user data using jclouds API. However >> it can not be done in VCloud scenario. In VCloud custom metadata can be >> stored in VApp. However in order retrieve username/password are needed. >> >> I'v written to some blog post where they suggest to go via script as >> Isuru is trying. >> >> >> >> Touched, not typed. Erroneous words are a feature, not a typo. >> > > > > -- > Isuru Perera > Senior Software Engineer | WSO2, Inc. | http://wso2.com/ > Lean . Enterprise . Middleware > > about.me/chrishantha > -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha
