SDKs are a vital resource for any ecosystem and SDKs for OpenStack are proliferating. The OpenStack Grizzly Summit has a few sessions dedicated to SDKs that I wanted to highlight.
- On Monday @ 11:00 am I’ll be leading the session SDK Documentation Discussion. Some of the topics/questions we’re going to address are: 1. What SDKs are you using and why? 2. How do we track SDKs that support OpenStack? 3. Where do we track SDKs that support OpenStack? 4. What criteria do we use to allow an SDK to claim OpenStack support? 5. When documenting the SDK API at the function level, do you duplicate info from api.openstack.org or do you just link to it? Are there other options? 6. What’s missing from the documentation of the SDKs you’re using?
- On Tuesday @ 11:50 am Rob Hirschfeld from Dell will be leading the session Quantum Fog! Networking for Programmatic Overlays 1. Fog is the leading Ruby abstraction library for the OpenStack API and it’s embedded in several ecosystem products. With the addition of Quantum, there is a need to extend Fog’s models to comprehend cloud networking.
- On Thursday @ 3:20 pm I’ll be leading the workshop Control the Clouds: Developer Experience with jclouds 1. jclouds is the leading Java cross-cloud toolkit for the OpenStack API and already has a broad adoption base. In this workshop, you will learn how to write code that can control any cloud with jclouds.
Coda
Contributing to and supporting an open source SDK should not be taken lightly. The OpenStack community needs to consider throwing its weight behind a select number of SDKs to in order to provide the best developer experience, the highest possible quality/support, and to limit fragmentation. Please join us at the sessions above and let’s find out how the OpenStack community can achieve this.