Facilitating the spread of knowledge and innovation in professional software development



Choose your language

InfoQ Homepage Presentations OpenStack Extensions: Challenges and Lessons Learned in the Development and Governance of Extensible REST Services

OpenStack Extensions: Challenges and Lessons Learned in the Development and Governance of Extensible REST Services



Jorge Williams shares some of the challenges and lessons learned while adding extensions to OpenStack.


Jorge Williams is a Principal Architect in the Rackspace Cloud Integration Team where he develops tools and services to solve integration problems. He has aided in the design and development of the Repose HTTP proxy, the Cloud Servers API, the OpenStack Compute and Identity APIs, and the OpenStack extension mechanism.

About the conference

The World’s Largest Conference Dedicated to SOA, Cloud Computing & Service Technologies.

Recorded at:

Mar 08, 2013

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • I am confused

    by Jean-Jacques Dubray,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    REST was sold to us because WS-* was too complex and all you would need was to expand the resource space or use hypermedia as you see fit. In particular, people like Steve Vinoski or Bill Burke kept telling us that because the interface to resources was "Uniform" you would be building non-breakable distributed application.

    Now, you are telling us that because "RESTful" services can't support namespaces, we have to create a central registry of some kind of contract metadata. You are telling that extensibility is really hard to reach.

    To me, HTTP headers sound like an obscure non RESTful kludge for dealing with extensions.

    Looks like you could have done all this work with WS-* in a fraction of the time. Am I mistaken?

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p


Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.