On Feb 16, 2015, at 11:32 PM, Andrei Mikhailovsky <and...@arhont.com> wrote:
> I think i've made some progress with user_data. I've used the template > example for coreos and clodstack (as previously described here). This should > successfully create a coreos instance with the ssh keys that you've supplied > when creating an instance (using cloudmonkey or api). > Hi Andrei, it works like for any template/VM. > You can supply user_data when creating an instance (again, cloudmonkey or > api) or alternatively, you can modify the db directly and update the > user_data column in the user_vm table. Yikes :) never touch the db for things like this Cloudmonkey or any API client is your friend (libcloud, jclouds, CS). For libcloud check: http://docs.libcloud.apache.org/en/latest/compute/drivers/cloudstack.html And here is a good example that I wrote for coreOS user data: https://github.com/runseb/kubernetes-exoscale/blob/master/deploy/etcd.py libcloud takes care of the base64 encoding. There is also CS which works very well, but you have to code more: https://github.com/exoscale/cs In my ansible-kubernetes recipes I pass user-data to coreOS: https://github.com/runseb/ansible-kubernetes underlyingly the ansible cloudstack module uses the python cs package. > The user_data should be base64 encoded. Here is an example that i've used to > get etcd and fleet started at boot: > > #cloud-config > > coreos: > units: > > - name: etcd.service > command: start > - name: fleet.service > command: start > > etcd: > name: <server-name> > discovery: https://discovery.etcd.io/<token> > addr: <private_ip>:4001 > peer-addr: <private_ip>:7001 > > You need to change the values between <> to suite your environment. > > I've read that there should be variable $private_ipv4 to automatically inject > your private IP, however, it doesn't seem to work for some reason. Will need > to investigate further > try with $public_ipv4 > Andrei > > ----- Original Message ----- > >> From: "Nux!" <n...@li.nux.ro> >> To: users@cloudstack.apache.org >> Sent: Monday, 16 February, 2015 10:06:07 PM >> Subject: Re: CoreOS/Docker - a new blog series > >> Andrei, > >> Do you know which files need to be modified in CoreOS and with what? > >> Lucian > >> -- >> Sent from the Delta quadrant using Borg technology! > >> Nux! >> www.nux.ro > >> ----- Original Message ----- >>> From: "Andrei Mikhailovsky" <and...@arhont.com> >>> To: users@cloudstack.apache.org >>> Sent: Monday, 16 February, 2015 21:23:58 >>> Subject: Re: CoreOS/Docker - a new blog series > >>> Has anyone tried using user_data in CloudStack to feed the >>> cloud-config stuff to >>> CoreOS? If so, could you please provide some examples? >>> >>> Cheers >>> >>> ----- Original Message ----- >>> >>>> From: "ilya musayev" <ilya.mailing.li...@gmail.com> >>>> To: users@cloudstack.apache.org >>>> Sent: Monday, 16 February, 2015 7:30:12 PM >>>> Subject: Re: CoreOS/Docker - a new blog series >>> >>>> Phil, >>> >>>> Please create twitter links and i will re-tweet. >>> >>>> Regards >>>> ilya >>>> On 2/14/15 3:15 PM, Phillip Kent wrote: >>>>> dear all, >>>>> >>>>> I am editing a new series of blog posts on CoreOS and Docker >>>>> with >>>>> CloudStack API, Cloudmonkey and so on. Please have a look at the >>>>> first >>>>> two parts: >>>>> >>>>> http://cloudstore.interoute.com/main/knowledge-centre/blog/coreos-docker-vdc-part1 >>>>> http://cloudstore.interoute.com/main/knowledge-centre/blog/coreos-docker-vdc-part2 >>>>> >>>>> These are written for an end user perspective. We have started >>>>> *very* >>>>> simple (single CoreOS VM with docker CLI) and will be working >>>>> towards >>>>> more complex topics as our own knowledge develops. >>>>> >>>>> We will also be evaluating Red Hat Atomic and Ubuntu Snappy as >>>>> container platforms in the next few months. >>>>> >>>>> You can keep in touch with new blog posts by following >>>>> https://twitter.com/Interoute or >>>>> https://www.facebook.com/pages/Interoute/161759680529086 >>>>> >>>>> - Phillip
