[opensuse-project] Amazon AWS pre-configured openSUSE images?
All, I've been looking into AWS the last day or so. I found a huge number of preconfigured VM images to choose from: https://aws.amazon.com/amis/ 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 -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
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
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
On Friday 03 May 2013 15:35:03 Greg Freemyer wrote:
Can any provide insight into why that isn't already happening?
There are openSUSE AMIs listed here:
http://en.opensuse.org/Derivatives
--
Cornelius Schumacher
On Mon, May 6, 2013 at 5:08 AM, Cornelius Schumacher
On Friday 03 May 2013 15:35:03 Greg Freemyer wrote:
Can any provide insight into why that isn't already happening?
There are openSUSE AMIs listed here: http://en.opensuse.org/Derivatives
-- Cornelius Schumacher
Cornelius, There is a comment that states the older opensuse AMI images were being charged by AWS as if they need a SUSE Enterprise license. http://blog.susestudio.com/2012/10/public-opensuse-122-amazon-ec2-amis.html Do you know if that has been resolved? Greg -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
On Mon, May 6, 2013 at 10:50 AM, Greg Freemyer
On Mon, May 6, 2013 at 5:08 AM, Cornelius Schumacher
wrote: On Friday 03 May 2013 15:35:03 Greg Freemyer wrote:
Can any provide insight into why that isn't already happening?
There are openSUSE AMIs listed here: http://en.opensuse.org/Derivatives
-- Cornelius Schumacher
Cornelius,
There is a comment that states the older opensuse AMI images were being charged by AWS as if they need a SUSE Enterprise license.
http://blog.susestudio.com/2012/10/public-opensuse-122-amazon-ec2-amis.html
Do you know if that has been resolved?
Greg
Answering my own question. My first "19 hours" of usage of the above VM instance on AWS has been billed. Since I just joined I am still in the first year where they give you two free "micro instances". The openSUSE instance was billed at $0.00, so it is not being treated as if a SLES license is required. fyi: The 2 free are in different areas of AWS and I'm not sure of how they are broken up. I can say the Linux instance created via the above link is not in the same area as the Windows Server 2008 with SQL I setup. I found the Windows server to need a $20/day environment to even try to be useful. (ie. The micro instance was useless, so I bumped to a "small" instance and it was merely almost useless.) The free openSUSE instance seems to be usable from what I have done so far. Mind you I'm only accessing via SSH and doing some zypper / yast activity so far. It is certainly not for a high i/o user, but even though I installed a bunch of packages via zypper, I only did 40,000 i/o's and you get 1M/month for free. Greg -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
On Monday 06 May 2013 16:50:27 Greg Freemyer wrote:
There is a comment that states the older opensuse AMI images were being charged by AWS as if they need a SUSE Enterprise license.
http://blog.susestudio.com/2012/10/public-opensuse-122-amazon-ec2-amis.html
Do you know if that has been resolved?
The openSUSE images should not be charged like SLE. There might be a tiny one-
time charging, when starting images, depending on how you deploy them, because
Studio uses the same mechanism as for SLE to deploy them. But I'm not aware of
a general issue with charging for openSUSE images.
--
Cornelius Schumacher
On Fri, May 17, 2013 at 9:40 AM, Cornelius Schumacher
On Monday 06 May 2013 16:50:27 Greg Freemyer wrote:
There is a comment that states the older opensuse AMI images were being charged by AWS as if they need a SUSE Enterprise license.
http://blog.susestudio.com/2012/10/public-opensuse-122-amazon-ec2-amis.html
Do you know if that has been resolved?
The openSUSE images should not be charged like SLE. There might be a tiny one- time charging, when starting images, depending on how you deploy them, because Studio uses the same mechanism as for SLE to deploy them. But I'm not aware of a general issue with charging for openSUSE images.
I can confirm that the above AMI fits within the AWS free tier and instance I launched on May 6 has accumulated $0.00 is charges. There was not a one time charge of any kind. Greg -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
participants (3)
-
Agustin Benito Bethencourt
-
Cornelius Schumacher
-
Greg Freemyer