Tsuru - Serve it yourself.
Submitted by Rohit Nair (@sobertooth) on Wednesday, 2 April 2014
Through this session we would like to emphasize on how scaling infrastructure can be done seamlessly with the usage of containers and also focus on better ways of deployment, build and testing.
Tsuru is a open source PAAS system. It helps Sysads to create generic infrastructure and platform in place which comes into life once the developer pushes the code. This self servicing mechanism will be useful to reduce the layers like config management. Since Tsuru leverages the features of docker, it supports both - isolation and scaling. For not so adventurous sysads, who are not ready to risk a software which is in heavy development in production, tsuru can be integrated with the build system, the testing infrastructure can be containers which can be spawned and stopped as needed.
The platform(say Apache, nginx, rails) will be a prebuilt docker image. On tsuru create an app specifying the platform required. The app will be given a domain name. Once the user pushes the code which is to be run on the platform, tsuru creates the container, does a checkout of the code. Hipache is used as a reverse proxy. Tsuru associates the domain name of the app in Hipache with the container. The containers can be increased on the fly and the Hipache will be updated accordingly.
To run services like redis, mysql Tsuru uses rest api to contact our server for info of the services. These info are set as Env Variables on the containers which will be used by the code. It's our logic to provide different instances of services for different apps, or share same instance of services.
Docker, Linux containers (LXC).
Currenly working with Directi as a Senior System Adminstrator.
Known for including humour in everything. Even Tsuru.