Sep 11, 2015
Please enjoy
seen from Russia
seen from Australia
seen from China
seen from Malaysia
seen from Türkiye
seen from China
seen from India
seen from United States
seen from Russia
seen from France
seen from United States
seen from China
seen from Australia
seen from United States
seen from Romania
seen from United States
seen from Malaysia
seen from United States
seen from China
seen from Saudi Arabia
Please enjoy
♅ GRISFX ♅ : https://soundcloud.com/musicgrey DOUJINSHI : https://soundcloud.com/doujinshi
Mherman - Moods
Video by Pspsy
Josef XVI feat Mherman
Why Disney Interactive dug into a few open-source toolboxes for its cloud
Disney Interactive took a bit from OpenStack and a bit from Cloudstack to build a cloud optimized for its needs, an executive said at CloudBeat today. http://goo.gl/Nb6dFW #Playistic
Amazon API compatibility - nice to have
I'm still at CloudBeat. I moderated the final session yesterday, refereeing a discussion involving Mårten Mickos of Eucalyptus, Randy Bias of Cloudscaling, Alex Freedland of Mirantis, and Ben Carpenter of Eucalyptus customer Rafter. Jordan Novet did a good write-up, and Michael O'Donnell has some nice pictures.
The conversation was great, but a little truncated by the time available. We should do it again, and take some more time to go deeper.
As moderator, of course, I had no opinions of my own (right?). But I can't help thinking that some degree of AWS compatibility would be nice to have. Interoperability (writes someone who once had 'Interoperability Focus' as a job title) is always worthwhile if it doesn't introduce too much complexity or delay into a process or workflow.
But, although it's nice to have, I'm unpersuaded that AWS compatibility is essential. If the majority of customers valued AWS interoperability as much as we sometimes suggest, Eucalyptus (an AWS-compatible purveyor of private cloud software) and Cloudscaling (an OpenStack-based private cloud solution, which makes much of its AWS compatibility) would surely completely dominate their market segment?
Both companies are interesting, and both companies are doing fine. But they're not blowing their competition out of the water with their AWS compatibility. Are they?
APIs - fundamental Lego, or Emperor's new clothes?
I'm at CloudBeat today and tomorrow, moderating a few sessions, talking to a load of people, and generally feeling pretty good about an event that's taken months to put together. If you're in town, there's still time to register for this afternoon and tomorrow... :-)
Lots of the talk is about APIs, and the importance of offering them or using them in building rich and compelling sets of interconnected services.
That I get, and the rhetoric is mostly pretty compelling. But contrast that with something Bechtel's Christian Reilly said at dinner last night - every enterprise thinks it's special, and different. Every enterprise takes an application like Oracle or SAP and tweaks, modifies, adjusts, and generally messes about with it.
How do we convey that in our standardised APIs? Or is the 'consistent' experience we promise maybe not so consistent after all? An API wrapped around with provisos and exceptions and metadata and data catalogues, and uncertainties maybe isn't the great panacea we all thought we were getting...
Act now to get 4 VentureBeat events for one low price
VentureBeat is announcing a new events package that will enable you to attend four of our signature events for a fraction of the price. http://goo.gl/8Yrpve #Playistic