CloudSigma has been one of the most difficult-to-test providers to the date for me.
Mainly because they have several differences with the average Cloud provider and the common way to perform of the vast majority of projects I’ve evaluated, and because the user interface is a bit ambiguous.
I’ll explain those differences and how to perform with CloudSigma.
First of all I want to thank to the Company and to the Customer Support that has been very nice.
CloudSigma assigned one of the support representatives to me, and she has been replying all my in deep questions, they provided 200 € in free credit so I can evaluate their platform at full level, they have provided a lot of technical information on their internals and platform, and have forwarded the bugs I’ve found to their Engineers and kept up me up to date on the development cycle and when they were going to fix the bugs I reported.
I have to clarify that I have found bugs in all the Cloud platforms I’ve tested, and in fact that’s one of my skills, finding bugs, that my employers love so much, but the main difference is that CloudSigma has been the only provider that has informed me about when they would fix the bugs and provided details on the Sprint (agile) and on the schedule for the deployment of the fixes.
I’ve evaluated their API and reported doubts and missing info on the documentation, and they have been transparent to reply all my questions and to recognize the points that I reported to improve. So big congratulations to their wonderful team, and for the good attitude.
For the development lovers I would say that their user interface is new, and works with Html5 WebSockets.
CloudSigma allows you to work with subscription and with burst mode. In burst mode you can pre-charge money to your account and work. To start an instance in burst mode you have to have enough credit to run the instance for 5 days.
One of the differences is that you can create an instance without a disk. This is a bit confusing the first time.
You have to create an instance, then assign a disk.
The disk can be assigned from, and that’s very good, one ISO Raw image that you upload.
It can be even created from a Marketplace’s image.
You can clone and use from the Marketplace OpenBSD, RedHat, Slackware, Debian, Ubuntu… pre-installed images (although Ubuntu 13.10 Server was not still in the list, I must say that after the publication of this article it was immediately added. Great!) or you can assign installation CD’s in ISO format and do a clean install. You can also use Windows and Sql Server images.
There are images, in the marketplace, for the drivers.
A positive thing also is that you have all the variety of Linux Desktops. So if you want to install Ubuntu 13.10 Desktop, Debian, or Fedora… you can do it and access through VNC.
In the other hand you can move the main or system disk from one server to another, that’s pretty cool.
The disks are SSD, and that’s very good for performance. You can create a Hard disk from 1 GB to 3 TB SSD.
CloudSigma platform is different from providers that have fixed instance-size, and here you can define how many Ghz (processor frequency) and how many RAM GB you want.
That’s a very interesting feature, as if you want a really powerful instance, but you don’t need much RAM, then you don’t have to pay for it!. Also if you want to create a cluster of Cassandra servers with not much CPU but a lot of RAM you can do it.
You can stop your server and change the amounts later and restart. That easy.
That’s really a very cool provisioning feature.
In terms of Zones CloudSigma has Datacenters in Zurich (Europe) and Las Vegas (USA), they run double 10GigE lines and they offer hybrid private patching (direct cable) that is a direct connection from your co-location servers to the public cloud, eliminating the need of a VPN and offering the possibility to contract advanced tools for security, backups…
As me they believe that hybrid cloud is key.
CloudSigma is a Cloud provider that remembers a lot to a familiar company. They have advanced services, but the relation with the customers is exquisite. They care about the companies being happy there like if it was a very small company. Some of my friend’s Start ups work with CloudSigma and they’re very satisfied.
I found and they confirmed, that are running on latest AMD 6380 processors (16 cores from 2.5 Ghz to 3.4 Ghz with Turbo) and they can offer up to 80 Ghz (80 virtual cores at 1 Ghz) but unless I’m missing something I don’t see the maths working (3.4 * 16 = 54.4 Ghz).
The RAM can be from 1 GB to 128 GB, that’s very good.
Another cool feature is that you can balance the number of cores seen by the guest OS, and play with the Ghz of that cores. So you can have 80 cores at 1 Ghz or 37 cores at 2.16 Ghz.
This is a very cool feature.
However, in the other hand the CPU performance detected by CMIPS is not always the same. It varies a lot from one test to the next and the next.
For a full 80 Ghz (37 cores at 2.16 Ghz each) instance, I got measurements from astonishing 17136 to 8539 CMIPS. That is shocking as I got 10770 to 8530 CMIPS with a 52 Ghz (24 virtual cores) instance.
I believe that this is related to AMD power-consumption features, and not related to CloudSigma itself, but right now I’m not sure and I would need a lot more testing to be.
Please note 17136 is the highest score achieved, even better than the powerful Amazon Compute Optimized CC2 Cluster 8xlarge.
In CloudSigma you can also use all the available bandwidth. Your instances are only limited by the ability of the server to handle network packets. So you don’t have a limit like in the case of other Cloud providers capping the outbound to 150 Mbits or more depending on the instance size.
Launching instances with CloudSigma is really really fast. The drive images are cloned at light speed (10 GB 3 seconds), and the servers are created in seconds and started even faster. Unlikely other Cloud providers the servers are created stopped.
Another cool feature is the incorporated costs estimation:
The image shows the price for a 80 Ghz instance, with 1 GB of RAM.
As you can see prices per subscription are cheaper than with the burst mode.
In fact, CloudSigma has the most clear and predictable pricing model. You can check everything from the profile:
Using a pre-installed image has the advantage that all the drivers are pre-installed.
Another confusing option is the public key option, that you can define when you create your instance or modify it later. As I’ve been using images from the Marketplace, that are user (cloudsigma) and password based, not certificate-based, it seems like this is not an useful option for this scenario and is really confusing.
You can access their API from here: https://zrh.cloudsigma.com/docs/
Something that I dislike from the user interface is that the STOP button has no warning. You press STOP and you immediately stop the instance (like power off), and shutdown has a 90 seconds count down.
After you have created an instance, assigned the disk, and started it, you have to:
– Edit the instance Properties
– Go to menu Actions
– Select Open VNC
This opens a set of options at the bottom of the same section
– Log in via SSH or via the embedded VNC client (very nice)
The VNC client works well, unfortunately the key map from the keyboard is different, so I am not able to use certain characters like # or | that are generated with AltGr.
This is a problem for the default password of Ubuntu 12.04 Server, that user a #.
Specially painful with the laptop.
But you can access via ssh instead, and the keyboard mapping is right.
Then you must change the password for the user cloudsigma, via ssh it kicks you out after, and you must relogin with the new password.
The network polices (firewall) can be applied to several servers, but if they’re changed the new ones don’t apply until restart.
Fortunately you can access through the VNC web client (QEMU) even if you messed it up and blocked all the firewall ports.
You can see in real time your bandwidth consumption.
Pingback: CMIPS v.1.03 benchmarks updated with CloudSigma and Azure | CMIPS