tomazmuraus
Netflix to Use StackStorm for IT Automation Under Cassandra
Avoiding DDoS attacks caused by large HTTP request bodies
Introducing choir.io
I want to add some context to this.
Our current abstraction provides a relatively simple API which is guaranteed to work across multiple providers.
If you want to access provider specific functionality we offer so called extension methods and arguments. This is similar to how jclouds and other cross-provider libraries handle that as well.
We support over 30 providers and for the more popular ones this means you can usually access most of the native cloud functionality through the base API + extension methods.
Doing that will obviously make it harder and more work to switch between different providers so we always put up a disclaimer and make sure our users are aware of that.
We are trying to standardize as many APIs as possible and promote extension methods to the to top level API (proposals and patches are always very welcome and appreciated!), but sadly in a lot of cases this is not possible. Usually this is because the provider APIs are too different and the glue code needed to make it work would be to complex.
In the end it's a trade-off, pretty much like everything else in life and a lot of other things in CS (CAP anyone?).
If you want good portability and easily switch between providers you will stick to the base API. If you don't care so much about the portability you will also use the extension API.
Side note: Even though official provider client libraries exists, a lot of people still tend to use Libcloud with extension methods.
Usually the reason is that we support a variety of Python versions and we have a stricter testing policy which tends to result in less buggy code.
Opscode wiki and ticket tracker has been compromised
Work visa and moving from the US back to your home country
Deconstructing the `CAP theorem' for CM and DevOps
Rackspace Launches Service Registry
In any case, you should have a look at Libcloud (http://libcloud.apache.org/), jclouds (http://jclouds.org), deltacloud (http://deltacloud.apache.org/) and other libraries. Deltacloud exposes a similar functionality through an HTTP interface. We have recently also started working on "Libcloud REST" which will expose all the Libcloud functionality through an HTTP interface which means you will be able to talk to it through an arbitrary language which can speak HTTP.
The title might be a bit misleading, but a first commit to Whiskey was actually made about a year ago (https://github.com/cloudkick/whiskey/commits/master?page=12), before Mocha existed.
Designing Network Protocols
Then the script would work with multiple providers, not just Amazon.
1. downloading a tarball 2. unpacking it 3. running "scons install"
Scons (our built tool of choice) is an extra dependency, but this shouldn't be a problem since it's a prerequisite for Node.js itself (platform on which Cast is built).
Node wasn't ever really meant to be used for CPU intensive tasks - especially the ones like this which you can fairly easy parallelize.
I have read it online about a year ago, but I still ordered my copy from Amazon.
Files still first need to be transfered to the cloud first before you can sync them over LAN.
At least it was like this the last time I have looked at it (a few months ago).
There are some forks with a parallel support, but all of the ones which I have tried are pretty buggy / incomplete.
I have signed up for a Fabric PyCon sprint, hopefully I can help with adding / finishing the parallel support.
I have been using mine for about a year now and I also use a YubiKey PAM module to log in into my Ubuntu workstation.
If you search google a bit I am pretty sure you will find a discount code to get it even cheaper :)
Currently, our test suite is not that large and it takes around 6-8 minutes to complete, but with testing every minute counts (testing is generally not that fun and a slow test suite just makes it more painful).
We have a two types of tests:
- Twisted tests - this tests runs asynchronously and finish pretty fast so they are generally not that problematic - Django tests - Django tests don't run in parallel so they are pretty slow. Recently, I was playing around with the Django test runner and I have made some modification to it to run the tests in parallel. Now the Django tests finish around 50% faster.
The only problem with this solution is that it is a "hack" and it requires some modifications to the Django core (I guess I should play more with the nose parallel test runner).
We also use some other "tricks" which make tests run faster - for example, MySQL data directory on a test server is stored on a ram disk.
Writing Cloudkick Query Language parser using Waxeye, some PyPy benchmarks
The datata sheet claims, it can read temperature between -55°C - 150°C, but I never tested its limit so I have now idea how far you can actually push it :)
In any case, like HeyLaughingBoy have said, if you want something which goes higher, check thermocouples.
I will still need to clone a repo if I need to quickly find or grep for something, but it's definitely way more useful for reading through the code then the default github file browser.
If you are interested in this kind of stuff, check Lyle's website[1]. He has many good articles about this kind of stuff.
[1]: http://www.bodyrecomposition.com/fat-loss/the-energy-balance...