The present applications were designed at "before the cloud".
As those applications are not intended for cloud, they need other tools such as Chef, Puppet, Ansible, Serf, etc to utilize the cloud power.
Thus the systems tend to become more complex on the cloud. We must think the "after the cloud" application now.
The after the cloud application we think satisfies below.
- The application logic determines amount of required resources by itself.
- The application logic iterates allocations/releases of resources from cloud.
- Those allocations/releases behave like creation/deletion of process.
We named the application with such behavior OpenStack Native Application .
In order to achieve "OpenStack Native , we developed a new software called RACK(Real Application Centric Kernel).
RACK enables an application to control VMs like a linux process.
It provides an application with PID, parent-child relationship, Fork / Kill VMs capabilities, interVM communication and message exchange without VM s IP address.
Ultimately, RACK enables you to implement a large scale distributed system in a variety of programming languages on OpenStack.
- wiki(for further details)
- https://wiki.openstack.org/wiki/RACK
- github
- https://github.com/stackforge/rack
In this session, We would like to share the concept, the architecture, the road map and some demonstrations of RACK, and we would like to get your feedbacks.
Thank you!