[opensuse-cloud] to fiddle with boot set up or not?
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
On Wednesday 19 March 2014 17:58:32 Robert Schweikert wrote:
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.
So providing a cloud-init package for general consumption in the distro is one thing. Having some "cloud-ready" openSUSE images available is another. For the latter, I think we all agree "the magic" should just work. In the former case we'll only annoy people. Pardon my ignorance, but I don't think we publish cloud images at software.opensuse.org yet, right? -- Viele Grüße, Sascha Peilicke -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
On 03/20/2014 05:20 AM, Sascha Peilicke wrote:
On Wednesday 19 March 2014 17:58:32 Robert Schweikert wrote:
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.
So providing a cloud-init package for general consumption in the distro is one thing. Having some "cloud-ready" openSUSE images available is another. For the latter, I think we all agree "the magic" should just work. In the former case we'll only annoy people. Pardon my ignorance, but I don't think we publish cloud images at software.opensuse.org yet, right?
Well we publish images through the Cloud:Images repo and those images have the cloud-init and WALinuxAgent services enabled. Later, 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
On Thursday 20 March 2014 08:45:10 Robert Schweikert wrote:
On 03/20/2014 05:20 AM, Sascha Peilicke wrote:
On Wednesday 19 March 2014 17:58:32 Robert Schweikert wrote:
[...] So providing a cloud-init package for general consumption in the distro is one thing. Having some "cloud-ready" openSUSE images available is another. For the latter, I think we all agree "the magic" should just work. In the former case we'll only annoy people. Pardon my ignorance, but I don't think we publish cloud images at software.opensuse.org yet, right?
Well we publish images through the Cloud:Images repo and those images have the cloud-init and WALinuxAgent services enabled.
I don't see an "images" repo over at [0]. So I assume you're building in Studio? Still, I think you should try to add them to software.o.o so that they are more visible [1]. Tom can certainly help here. [0] https://build.opensuse.org/project/repositories/Cloud:Tools [1] https://github.com/openSUSE/software-o-o -- Viele Grüße, Sascha Peilicke -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
On 03/20/2014 09:00 AM, Sascha Peilicke wrote:
On Thursday 20 March 2014 08:45:10 Robert Schweikert wrote:
On 03/20/2014 05:20 AM, Sascha Peilicke wrote:
On Wednesday 19 March 2014 17:58:32 Robert Schweikert wrote:
[...] So providing a cloud-init package for general consumption in the distro is one thing. Having some "cloud-ready" openSUSE images available is another. For the latter, I think we all agree "the magic" should just work. In the former case we'll only annoy people. Pardon my ignorance, but I don't think we publish cloud images at software.opensuse.org yet, right?
Well we publish images through the Cloud:Images repo and those images have the cloud-init and WALinuxAgent services enabled.
I don't see an "images" repo over at [0].
Yup, that is correct.
So I assume you're building in Studio?
Nope. The repo is Cloud:Images [2], not Cloud:Tools
Still, I think you should try to add them to software.o.o so that they are more visible [1].
Makes sense to me. However, I do generally suck at web design or putting anything on a web page ins a reasonably nice way.
Tom can certainly help here.
[0] https://build.opensuse.org/project/repositories/Cloud:Tools [1] https://github.com/openSUSE/software-o-o
[2] http://download.opensuse.org/repositories/Cloud:/Images/images/ -- 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
On Thursday 20 March 2014 09:08:40 Robert Schweikert wrote:
On 03/20/2014 09:00 AM, Sascha Peilicke wrote:
On Thursday 20 March 2014 08:45:10 Robert Schweikert wrote:
On 03/20/2014 05:20 AM, Sascha Peilicke wrote:
On Wednesday 19 March 2014 17:58:32 Robert Schweikert wrote:
[...]
So providing a cloud-init package for general consumption in the distro is one thing. Having some "cloud-ready" openSUSE images available is another. For the latter, I think we all agree "the magic" should just work. In the former case we'll only annoy people. Pardon my ignorance, but I don't think we publish cloud images at software.opensuse.org yet, right?
Well we publish images through the Cloud:Images repo and those images have the cloud-init and WALinuxAgent services enabled.
I don't see an "images" repo over at [0].
Yup, that is correct.
So I assume you're building in Studio?
Nope. The repo is Cloud:Images [2], not Cloud:Tools
D'oh! My bad.
Still, I think you should try to add them to software.o.o so that they are more visible [1].
Makes sense to me. However, I do generally suck at web design or putting anything on a web page ins a reasonably nice way.
Tom can certainly help here. ^^^ :-)
-- Viele Grüße, Sascha Peilicke -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
participants (2)
-
Robert Schweikert -
Sascha Peilicke