On Tue, 2017-09-12 at 08:11 +0200, Ivan Necas wrote: > In order to be able to assign the template to the OS, you need first > go to the template's associations tab, and add the OS there. > Then it should make it possible to set that in the OS. > > I'm not sure why the default user_data template is not cloud-init, > but I deffer the question to someone else.
Ivan, for your education :P - user-data comes in two flavours, that's all there is to it :D The first is cloud-init style specfications which are acted on by a variety of providers on the image. The second is a shell script executed as root by the cloud-init process as it boots. You can find out more here: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/user-data.html#user- data-shell-scripts Mike - so, I'm glad your EC2 instances are working, since that's what I'd hope. However, as Ivan noted, the VMware customization spec is *very* limited, and many people on here have had issues getting it to work. THis is sadly a limitation VMware chooses to place on itself, and there's not much we can do about it (except get VMware customers to pressure them to change it :P). Here's a link from a while ago from someone who says they got it working: https://groups.google.com/d/msg/foreman-users/d6Yc9uiK9oo/RZ9I MPo9AwAJ. In general, search the list for "vmware customization" should get you a few otehr hits too. Hope it helps! Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
