Hi, This is basically an opinion poll with respect to cloud-init and WALinuxAgent. The current cloud-init package does not "force" itself into the boot process when installed, i.e. the services needed to make cloud-init do what it is supposed to do are not enabled by default when simply installing the package. The same is true for WALinuxAgent, the Azure initialization code. This is obviously a packaging decision and I am comfortable with this as it is easy enough to enable the services during image building with kiwi or SUSE Studio. However, there appears to exist an expectation by users of Studio that when cloud-init is installed it will magically work when the image that got created gets booted in a cloud environment. While I am perfectly happy with the way WALinuxAgent and cloud-init work, i.e. not forcing themselves into the boot process I also want to be sensitive to user expectations (and of course cut down on potential bug reports.) With this as background the question is simple. What is the general sentiment on this list, should WALinuxAgent and cloud-init insert themselves into the boot process when the package gets installed or not? Reasonable arguments can be made either way IMHO, and I'd like to here as many as possible to make a decision. Thanks for helping out. Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead Public Cloud Architect rjschwei@suse.com rschweik@ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org