Agustin,
As Cornelious posted there are openSUSE 12.2 and older AMIs available
for AWS, but the 12.1 and 12.2 ones are not found in the large
collection of AMIs found at:
https://aws.amazon.com/amis/
I think it would be nice if 12.2 and 12.3 AMIs could be found there.
Further, AMIs can be built via SuseStudio, but I don't find the
instructions very enlightening:
http://susestudio.com/help/use/amazon-ec2.html
James Tan is apparently an inside resource you could call on. He's
created the base 12.2 AMIs here:
http://susestudio.com/a/n0rKOx/amazon-machine-image-ami-12-2-32bit
susestudio has a straight forward distro upgrade process, thus in
theory at least it should be straight forward to convert those AMIs to
12.3 and re-release.
Greg
http://susestudio.com/help/use/amazon-ec2.html
On Mon, May 6, 2013 at 4:03 AM, Agustin Benito Bethencourt
Hi,
we have a meeting tomorrow in the openSUSE Team to start taking steps to identify and correct the current situation in the mid-term.
Today there are relevant third party channels in which our distribution need to be in order to have a chance to be used outside our circles. In some of these channels it is easy to have our distro and other require more work, agreements, support, etc. We call them Showstoppers (Duncan dixit).
In the ideal situation, we should have a list of those places, what to do to include openSUSE, who is in charge of including it and deadlines associated with the post-release milestone.
So the plan is to learn the following months so we can have some results in 13.1. We would like to see the marketing team involved on this together with us as part of the Release work, but first we need to identify the problem correctly.
On Friday, May 03, 2013 09:35:03 AM Greg Freemyer wrote:
All,
I've been looking into AWS the last day or so. I found a huge number of preconfigured VM images to choose from:
But nothing with openSUSE 12.1/12.2/12.3.
https://aws.amazon.com/search?searchQuery=opensuse&searchPath=amis&x=-894&y= -95
Either I'm missing something, or that is something that could easily be maintained in susestudio and uploaded to AWS shortly after each release.
Can any provide insight into why that isn't already happening?
Greg -- Agustin Benito Bethencourt openSUSE Team Lead at SUSE abebe@suse.com
-- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org