On Mon, Mar 30, 2009 at 3:42 PM, Mark V wrote:

On Tue, Mar 31, 2009 at 3:52 AM, Stephen Shaw wrote:

...

Lets make openSUSE more visible and vote up suse on the eucalyptus poll. http://www.micropoll.com/akira/mpview/564200-152224

Interesting - actually I started laughing ;)

I'm not sure that inflating this poll will be helpful to community credibility.  For several reasons.

1) The AWS developer forums show (judging by some thread view counts) there _may_ have been some reasonable interest in running openSUSE on EC2, or 'in-the-cloud'.  However, the common experience seems to be a dead-end.     I think that huge numbers in the above poll will be 'seen through'; see the 'other poll' below. More helpful would be to have some of the issues I mention below resolved, i.e get openSUSE running on the 'real' EC2 first.

...

The long and short is that eucalyptus is a private internal ec2 cloud.

2) I think people would be 'intrigued' if they saw openSUSE ranked highly by 'current and potential Eucalyptus users' - I assume most real potential Eucalyptus user is a current EC2 user.... reason: According to the elasticFox listing here are some real world counts (the other poll) of public images the 'community' have made- 'search term' (count): ubuntu (266) fedora (48) suse (2) (1 is 10.2 the has an ambiguous name)

and more vendor specific: redhat (12) canonical (4) novell (0)

Some relevant issues: 1) Have openSUSE public kernel and ramdisk images be available on EC2.  At the moment the only ones are named 'sles-beta-ibm'... do they go private after the beta?  None of these kernel images are those mentioned in the KIWI docs. None of the kernel images mentioned in the KIWI docs are available on EC2, nor have they ever been from my periodic checking and from the AWS forum posts.

2) Have one basic 32bit and 64 bit openSUSE AMI available, from this point the 'community' can build additional public images using KIWI, etc. without upload  (bandwidth), storage, etc. issues.

3) Once the above two components are in place one could then contemplate some community efforts that would be needed to use openSUSE in the cloud, e.g. openSUSE is currently absent from Chef (a configuration sys-admin framework), it absent for the obvious reason ;)

I'd like to have used openSUSE, and KIWI seems to be a very valuable addition, but so far the whole exercise has been as fruitful as banging ones head on concrete.

So, without being to harsh, I think you may be placing the cart before the horse - of course it could turn out that openSUSE is widely run on private-EC2's but not the actual EC2.

Mark

One of the real problems with this is that we can't get openSUSE/SLE on amazon ec2, so the numbers aren't going to be fair. You might wonder why the crap Novell hasn't gotten on top of this, they have! :) Unfortunately, from what I understand is that the version of xen we use is too new to work on ec2. So this is of no fault of Novell, but the systems and versions that amazon is using :( Stephen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org