Way too much interesting projects, not enough time! Never enough.
My next one will be a lot more public than what I’m used to – should be quite a commotion created around it.
Another upcoming project will require me to direct upon all kind of teams… got hardware suppliers, financial contributors, software developers. Some very interesting aspect in leading all this.
In the mean time, I’ll post some pictures (soon).
projets!
good stuff to come
Stuff moving pretty fast:
In the next few days, Laboratoires Phoenix (my corp.) will be unveiling new services to the current holder of premium account – those are normally people with whom I already have a business relationship. We are speaking of computer-based monitoring from locations around the world, human-based monitoring and generic maintenance.
Since I already have a very decent job (“CloudMaster @ PraizedMedia” / Operation specialist), the income generated by Laboratoire Phoenix are reinvested in infrastructure to help Canadian start-up. There is already quite a few people that have shown interest. If you have an interesting project feel free to reach me on pascal.charest@gmail.com ; If I’m interested and have free time I can contribute servers, bandwidth and even do some free-of-charge consulting. My network of contact can also be of use.
Since I’m speaking about myself (;-)) : I have also been asked to draft/compose a 8-10 pages articles on “initiation au cloud computing” to be published at 25k+ printed version in Europe. On the same subject, I’ve been selected to contribute a chapter to an upcoming guide @ O’Reilly. Life could be harder ;-) – but this is meant as an early “warning” – if anyone is interested in developing a career as technical writer, feel free to get in touch with me. Author can easily become co-author ;-).
Cloudbursting
Cloudbursting
Technical term referring to the transition to a dynamic state of a network infrastructure as an events mitigation process. It entail to both asynchronous and synchronous expansion toward or inside a computer cloud. Each such burst is followed by a period of quiescence before the next burst occurs.
Event such as high workload and extreme traffic spike can cause a correctly configured environment to cloudburst.
The term seem to have been used first, in July 2008, by William Fellows (Principal Analyst @ 451group) in a report and pushed forward by Jeffrey Barr (Technology evangelist of Amazon AWS) on a blog in august 2008.
This is my personal definition, yet I think it summarize the process. Anything that needs to be added ?