8 posts • joined 17 Feb 2012
Re: as one of those unicorns (No you are not...)
You admit yourself you work for small companies.
Here the issue is to find skills on massively scalable systems which, by itself. is outdated on the medium term because more and more applications will rely on loosely coupled resources in the future. DCs will still host 1000s of machines but they might need less orchestration because it will be built in software
Typos like "OpenSack" and "full of date" give me strange feelings.
Nimbula was a donkey in its native implementation, I wonder if Oracle did the miracle to make a horse of it.
Re: Beyond API
Nimbula for sure. Their Director product delivers exactly what is said: API and Cloud Orchestration.
However, in the very beginning Nimbula's underlying Cloud implementation had nothing to do with OpenStack and, honestly speaking, it wasn't that great. It's not clear to me what they contributed by joining the OpenStack community but eventual Oracle's contribution should now be seen in this context.
Re: What is an object store?
I am in for the convergence.
However I am displeased these systems defuse one of the reasons modern object storage is used: economics of scalability.
I am no EMC expert...
...But I have some experience with object storage of other vendors/sources.
As far as my (limited?) experience is concerned I met just one vendor delivering a product whose maturity doesn't involve extra gimmicks from the part of administrators or data consumers.
Guus, in the name of data governance we can invoke no matter what good motivation for making life difficult to provoke collateral damage; nevertheless I suppose that a company investing in Atmos has done a comparable effort in choosing some responsible personnel administering it.
We don't know if this guy is switching, perhaps, from a test to a production environment, I , personally, would like to be informed, before I buy, that there is an overhead in deploying the system, it adds up to my TCO.
Thumbs up for the Register to report this.
Stop comparing Amazon with your DC
Amazon SLA defines each of their instances in ECUs. Sometime ago it was equivalent to a 2Ghz Athlon core.
Any performance variance is more than what one has paid for.
And, no: the processor has nothing to do with the speed of an instance. You got hosted in the same rack of some fanatic about big-data and you are toasted. Regardless of the cool new CPU you might have obtained.
So, the "study" can only affirm that Amazon uses different processors and that it maintains its machines somewhat updated. Whenever performance is a concern Amazon sells Reserved Instances but, not surprisingly, the price is on the high side.
Stop at comparing Amazon with an on-premise infrastructure. The Cloud is a model that allows fast deployment and better scalability (then add your business reason here).
- It doesn't cost less
- It doesn't do everything
- It will never solve the issue of data confidentiality but, eventually, it will make us get used not to worry about it.
Multi-CDN is the trend now...
Have a look at another French company (mon Dieu): CleverScale; they provide a multi-CDN management tool with log aggregation.
@Jeff11, yes, it seems a marginal advantage to benefit from having 25ms latency (for most of the Internet it is), but there's more about that: think offloading under variable loads. Old-school CDNs are much more efficient and easy to maintain than a distributed architecture on the Cloud.
Nevertheless: not the cheapest solution around.
- Tricked by satire? Get all your news from Facebook? You're in luck, dummy
- Feature TV transport tech, part 1: From server to sofa at the touch of a button
- Google straps on Jetpac: An app to find hipsters, women in foreign cities
- Updated Microsoft Azure goes TITSUP (Total Inability To Support Usual Performance)
- The Return of BSOD: Does ANYONE trust Microsoft patches?