Hi, can anyone confirm if using API, instead of writing all commands in the "startup-script" value, is it possible to write startup script and pass location of the script in the metadata ?
Regards, Pratik. On Mon, Oct 9, 2017 at 12:28 PM, Pratik Bandarkar < [email protected]> wrote: > Hi Markos, > > Thanks for your reply. > > > > On Mon, Oct 9, 2017 at 11:58 AM, Markos Gogoulos <[email protected]> > wrote: > >> Hi Pratik, >> >> libcloud function that creates a VM on GCP (aka create_node() on >> libcloud/libcloud/compute/drivers/gce.py) accepts an ex_metadata >> dictionary >> that can contain the startup script. It expects something like this: >> >> metadata = { >> 'startup-script': '#!/bin/bash\ntouch /tmp/hello', >> } >> >> or if you also specify an ssh key to be deployed on the VM >> >> key = "ssh-rsa AAAAB3Nz.... (rest of a pub key)" >> metadata = { >> 'startup-script': '#!/bin/bash\ntouch /tmp/hello', >> 'sshKeys': 'user:%s' % key >> } >> >> >> not sure though if this is supported by saltstack. >> > Saltstack does support specifying "startup-script" in "metadata". But, > instead of writing all commands in the "startup-script" value, is it > possible to write startup script and pass location of the script in the > metadata ? > > Regards, > Pratik. > >> >> Cheers, >> Markos >> >> >> On Fri, Oct 6, 2017 at 8:27 PM, Pratik Bandarkar < >> [email protected] >> > wrote: >> >> > To be more specific, does it provide "--metadata-from-file" option to >> > specify startup script file? >> > >> > Regards, >> > Pratik. >> > >> > >> > >> > On Fri, Oct 6, 2017 at 5:36 PM, Pratik Bandarkar < >> > [email protected] >> > > wrote: >> > >> > > Hi, >> > > >> > > I am using saltstack for deployment of instances on top of GCE. I >> would >> > > like to know if we can provide startup/cloud-init script while >> spawning >> > an >> > > instance? Does libcloud support this functionality for saltstack? >> > > >> > > Regards, >> > > Pratik. >> > > >> > >> > >
