Friday, July 27, 2012

Public AMIs based on openSUSE 12.1

Yes openSUSE 12.1 has been out for some time already, and 12.2 will be out in a couple of months. But hey it's better late then never. So we are happy to annouce the release of the public openSUSE 12.1 AMIs in all seven Amazon EC2 regions, in both 32-bit (x86) and 64-bit (x86_64) variants.

Create a New instance screen with openSUSE AMIs.

You can use the AWS web console's "Quick Launch Wizard", select "More Amazon Machine Images", and click "Continue". This brings you to the "Create New Instance" page where you can filter for openSUSE AMIs under the "Platform" column on the left.

The AMIs we release will now follow the same naming scheme as the SLES AMIs:
"openSUSE-<openSUSE ver>-v<Studio image ver>.<arch>". For example, the 32-bit version is named "openSUSE-12.1-v3.0.0.i386", while the 64-bit is "openSUSE-12.1-v3.0.0.x86_64".

We now have a dedicated account for hosting these public AMIs, with a owner ID of 056126556840, so you can verify that to ensure that it is published by the Studio team and can be trusted.

Note that the AMIs are EBS backed only as there's not much demand for instance-store backed ones.

The AMI sources are available in SUSE Gallery, for both the 32-bit and 64-bit versions. The full list of AMI IDs for each corresponding region is also listed there, which comes in handy if you're launching instances directly with the AWS API. The scripts used to upload, test and make public these Studio built images to each region is open-sourced at Github.

Run openSUSE 12.1 in EC2 (using run-and-connect).

Do try these public openSUSE 12.1 AMIs out and have a lot of fun!

Thursday, July 12, 2012

We’re dropping API v1 soon

As you may know, SUSE Studio has a RESTful API. The first version (“v1”) was available since the very beginning. Later we added an improved version (“v2”) that allowed access to appliance configuration and new features such as SUSE Gallery.

The API v2 has been available for more than a year and our server logs show that most users already switched to this version. Therefore we decided to drop support for the API v1. We will do this one month from now to give you some time to adapt. On 13 August 2012 we will publish another announcement and remove the old API version.

I still use the API v1 — what should I do?

Don’t panic ;-) The API v2 is mostly an extension (a superset) of v1 so almost all code that works with v1 should work with v2 without any modification. The only important incompatibility between v1 and v2 is that HTTP status error codes returned in certain situations may be different (v2 is more consistent in this regard).

We recommend that you just try pointing your code to the new version and test that everything works. You can do it easily by replacing the URL prefix by

If you encounter any problems after switching to the new API version, have a look at the API documentation. If that does not help, you can ask on our forum (linked with a mailing list) and we will try to help.

Studio API from Ruby

If you are using Studio API from Ruby, you can make your life easier by using the studio_api gem. It wraps the API into nice objects and works with API v2 smoothly. There are also some other libraries and clients available.

Have ideas for a new version?

We are already thinking about the API v3. If you are a Studio API user, now is the time to have your voice heard and help us determine how the new version should look like! We are mainly interested in hearing answers to the following questions:
  • What do you use the current API for?
  • What features do you miss?
  • Did you find some parts of the API hard to understand or use?
  • Are there any big pain points you’d like to get fixed?
Leave the answers in comments to this blog post. We will use them as a guide when preparing the API v3 design and feature set. Thanks!
© 2013 SUSE