This turned out to be a major open cloud gab fest! In addition to Dell OpenStack leads (Greg and I), we had the Nova Project Technical Lead (PTL, Vish Ishaya, @vish), HP’s Cloud Architect (Alex Howells, @nixgeek), Opscode OpenStack cookbook master (Matt Ray, @mattray). We were joined by several other Chef Summit attendees with OpenStack interest including a pair of engineers from Spain.
We’d planned to demo using Knife-OpenStack against the Crowbar Diablo build. Unfortunately, the knife-openstack is out of date (August 15th?!). We need Keystone support. Anyone up for that?
There’s no way I can recapture everything that was said, but here are some highlights I jotted down the on the way home.
After the miss with Keystone and the Diablo release, solving the project dependency problem is an important problem. Vish talked at length about the ambiguity challenge of Keystone being required and also incubated. He said we were not formal enough around new projects even though we had dependencies on them. Future releases, new projects (specifically, Quantum) will not be allowed to be dependencies.
The focus for Essex is on quality and stability. The plan is for Essex to be a long-term supported (LTS) release tied to the Ubuntu LTS. That’s putting pressure on all the projects to ensure quality, lock features early, and avoid unproven dependencies.
There is a lot of activity around storage and companies are creating volume plug-ins for Nova. Vish said he knew of at least four.
Networking has a lot of activity. Quantum has a lot of activity, but may not emerge as a core project in time for Essex. There was general agreement that Quantum is “the killer app” for OpenStack and will take cloud to the next level. The Quantum Open vSwitch implementaiton is completely open source and free. Some other plugins may require proprietary hardware and/or software, but there is definitely a (very) viable and completely open source option for Quantum networking.
HP has some serious cloud mojo going on. Alex talked about defects they have found and submitted fixes back to core. He also hinted about some interesting storage and networking IP that’s going into their OpenStack deployment. Based on his comments, I don’t expect those to become public so I’m going to limit my observations about them here.
We talked about hypervisors for a while. KVM and XenServer (via XAPI) were the primary topics. We did talk about LXE & OpenVZ as popular approaches too. Vish said that some of the XenServer work is using Xen Storage Manager to manage SAN images.
Vish is seeing a constant rise in committers. It’s hard to judge because some committers appear to be individuals acting on behalf of teams (10 to 20 people).
Based on our last meetup, it appears deployment is a hot topic, so we’ll kick off with that – bring your experiences, opinions, and thoughts! We’ll also open the floor to other OpenStack topics that would be discussed – open technical and business discussions – no commercials please!
We’ll also talk about organizing future OpenStack meet ups! If your company is interested in sponsoring a future meetup, find Joseph George at the meetup and he can work with you on details.
While I was in Seattle for Azure training preparing for Dell’s Azure Appliance , Dave @McCrory suggested that we also attend the Seattle Cloud Camp (SCC Tweets). This event was very well attended (200 people!). With heavy attendance by Amazon (at their HQ), Microsoft (in the ‘hood), and Google, there was a substantial cloud vendor presence (>25% from those vendors alone). Notable omission: VMware.
My reflection about the event by segment.
Most of the opening sessions were too light for the audience. I thought we were past the “what is cloud” level, sigh.
Of note, the Amazon security presentation by Steve Rileywas fun and entertaining.
Picking on a Dell competitor specifically: calling your cloud solution “WAS” is a branding #fail (not that DCSWA much is better).
Unpanel of self-appointed cloud extroverts experts:
The unpanel covered some decent topics (@adronbh captured them on twitter), unfortunately none of the answers really stood out to me. Except for NoSQL.
The unpanel discussion about NoSQL drew 2 answers. 1) It’s not NoSQL, it’s eventually consistent instead of strictly consistent. (note: I’ve been calling it “Storage++”) 2) We’ll see more and more choices in this area as we tune the models for utility then we’ll see some consolidation. The suggestion was that NoSQL would follow the same explosion/contraction pattern of SQL databases.
Session on Cloud APIs (my suggested topic)
The Cloud API topic was well attended (30+). The vast overwhelming majority or the attendees were using Amazon.
There was some interest in having “standard” APIs for cloud functions was not well received because it was felt to stifle innovation. We are still to early.
It was postulated but not generally agreed that cloud aggregation (DeltaCloud, RightScale, etc) is workable. This was considered a reason to not require standard clouds.
CloudCamp sponsor, Skytap, has their own API. These APIs are value added and provide extra abstraction levels.
It was said that there are a LOT (50 now, 500 soon) smaller hosts that want to enter the cloud space. These hosts will need an API – some are inventing their own.
I brought up the concept discussed at OpenStack that the logical abstraction for cloud network APIs is a “vlan.” This created confusion because some thought that I meant actual 802.1q tags. NO! I just meant that is was the ABSTRACTION of a VLAN connecting VMs together.
There was agreement from the clouderati in the room that cloud networking was f’ed up, but most people were not ready to discuss.
Cloud APIs have some basics that are working (semantics around VMs) but still have lots of wholes. Notably: networking, application, services, and identity)
Session on Google App Engine (GAE)
GAE is got a lot going on, especially in the social/mobile space.
Do not think a lack of news about GAE means that they are going slow, it’s just the opposite. It looks like they are totally kicking ass with a very focused strategy. I suspect that they are just waiting for the market to catch-up.
GAE understands what a “platform” really is. They talk about their platform as the SERVICES that they are offering. The code is just code. The services are impressive and include identity, mail, analysis, SQL (business only), map (as in Map-Reduce), prediction (yes, prediction!), storage, etc. The total list was nearly 20 distinct services.