In the cloud computing, alongside of the hosting monsters such as amazon or google, there is the Openstack Platform. Openstack is not a single software, it is more a galaxy of components aim to control the infrastructure, such as hardware pools, storage, network. The management can then be done via a Web based interface or via a bunch of RESTful API. I would like to evaluate its identity service named keystone and use it as a AuthN and AuthZ backend for my simple_iaas example.

In a previous post I have explained how to develop a very simple API server. Without the associated documentation, the API will be useless. Let’s see how we can use swagger-ui in this project to generate a beautiful documentation. Note I’m blogging and experimenting, of course, in the “real” life, it’s a lot better to code the API interface before implementing the middleware. About Swagger Swagger is a framework. On top of the swagger project is composed of several tools.

Abstracts Recently, I’ve been looking at the principles of a middleware layer and especially on how a RESTFULL API could glue different IT services together. I am reading more and more about the “API economy” I’ve also seen this excellent video made by Mat Ryer about how to code an API in GO and why go would be the perfect language to code such a portal. The problem I’m facing is that in the organization I’m working for, the developments are heterogeneous and therefore you can find ruby teams as well as python teams and myself as a go team (That will change in the future anyway) The key point is that I would like my middleware to serve as an entry point to the services provided by the department.