After 9 months of hard work, we are very proud to present to you the new Scalr, complete with a new engine and user interface. We’ll detail each new feature with a dedicated post, and here’s the summary:
- New! Scalarizr. Allows you add a node to be managed by Scalr. Supported os: Ubuntu 8.04, Ubuntu 10.04, Debian 5, CentOS 5, Fedora 8, Fedora 12, Fedora 13 (This list will be extended within the next releases)
- New! DNS manager. Increased stability and speed, decreased number bugs and fails.
- New! Apache virtualhosts manager.
- New! API 2.0. Added methods for creating DNS zones and Server snapshots. Please note that this API replaces and is not compatible with the previous API.
- Replaced “Synchronize to all” with “Create server image” instead. New object – BundleTask.
- Improved EBS (network storage) and ELB (load balancer service) management, fixing tons of issues.
- Improved MySQL status page.
- Improved Scaling algorithms and logging. You can now see why your role was scaled. Up or down.
- Improved UI. Faster, with a new page for checking all information about servers and farm roles.
- AWS platform changes: Added Asia-Pacific region, and RDS (mysql service) as cloud platform.
- Scalr will show warnings in UI if issues have been posted on status.aws.amazon.com.
We rewrote about half of Scalr source code, about 15.000 lines of code. A large amount of bugs were fixed in the process, and it is now possible to add support for new cloud platforms.
This is juge. Thank you for the great work and the great service provided. I hope you will stay independant and be able to develop whatever you have in your roadmap.
Congratulations!
Thank you!
Thanks, but this also broke my stuff. Now all scripts (even if I specify 1000s timeout) timeout the next second I run them. Also, you changed server IDs and many other things that our system relied on with no advance communication about these changes!
Sorry about that. Let us know at support.scalr.net if you have technical issues.
Good news, but the first thing I did was head to download it and the latest download is still 1.2 :(
How about you release the source for new versions on google code a month ahead of deploying them to the scalr.net service – that way we can help you shake out the bugs before you deploy to the service and potentially disrupt people’s production systems?
I manage three clients and have accounts & farms for their production systems on the Scalr service and it makes me nervous that you’re pushing major updates to the code managing customer’s critical production systems without warning or advanced testing.
Still great news all the same. Let us know when it gets released.
Regards,
-David.
“and it is now possible to add support for new cloud platforms”
I like that part, because I am a Rackspace user :)
Thanks, Scalr looks really good!
Regards
Willem
Thanks for the complement – are you a Rackspace Cloud user, or regular Rackspace?
I’m debating whether to go with Rackspace Cloud on a new project, I’d love to roll out Scalr with it. Any plans on supporting RS Cloud?
Also, is there a timeframe on releasing the 2.0 code?
Cheers.
We won’t release until the code is stable; if we do before it’ll mean more time spent on updates.
We will support Rackspace Cloud, see our roadmap here: wiki.scalr.net/Roadmap
Pingback: New in Scalr 2.0: Server Snapshots « The Official Scalr blog
I’m just new to scalr and going to install 2.0. I wanna know that will it be provide scalability to Eucalyptus cloud too…!
Thanks