Solum, the missing link between IaaS and PaaS

March 18, 2014 3:36 pm Published by Leave your thoughts

When talking about PaaS, one of the main concerns is that it forces users to adapt the code of their application to the restrictions put forward by the PaaS providers. Providers like Heroku or AppEngine and PaaS solutions, CloudFoundry or Openshift, eased the integration with their platform, but you still have to make a substantial effort in order to integrate those restrictions. Once your application is integrated you enjoy the benefits of PaaS, including continuous delivery, the ability to go from code to production in minutes using automated provisioning, automated scaling, and freedom from thinking about the system infrastructure. You can focus on application development and be creative; the platform will do the rest.

However what happens if you have a legacy system that you’re still struggling to move to the Cloud? Such legacy hasn’t been built for automatic deployment using a configuration management system like the cattle’s we’re hearing so much about. No, it’s a big old pet that you’ve been rebooting with love every time it got a cold. The system was written a long time ago by an external contractor, and a good part of your information system depends on it, and it works. You worry because by today’s coding standards the code is rubbish. The time has come for you to move to the cloud, and it seems your only hope for moving this beast is to import your VM and hope for the best! So when some new guy is trying to explain you that all the delivery system has been streamlined and that from now on all the old systems will be migrated to the PaaS and be deployed through a process that will go through a software factory and have to be retrofitted to conform to the platform restrictions… you almost scream.

We strongly believe Solum has a way to help you.

  • Solum provides you with more flexibility than traditional PaaS solutions. With Openstack, we don’t have to draw a line between IaaS and PaaS anymore. Both can coexist in the same place, you can import your legacy and benefit from a fully integrated PaaS solution with your developers continuous integration system. This is another form of the term hybrid cloud.
  • Container technologies are on the rise, but if you don’t want to run in containers (Did I heard someone say Windows?) Solum provide both options: you can either deploy in a container or in a good old VM!
  • When writing new applications for the cloud, easily integrate your software development process with the cloud using CI/CD capability from Solum. This boosts developer productivity.
  • Solum contributors work closely with the OASIS Cloud Application Management for Platforms (CAMP) specification Technical Committee.
  • Solum is fully integrated with OpenStack and thus you benefit from all the core components and services of the OpenStack platform you’re running on, Keystone, Trove, and others to come.
  • Solum is not reinventing the wheel while it’s reusing the expertise provided by the many contributors in OpenStack, by leveraging Heat, Glance, Nova… You’re already running in an OpenStack Cloud? Welcome home.

Decoupling legacy architecture from the underlying infrastructure is not an easy task. But the benefits from doing so are great. Yes, business will drive PaaS adoption as it has driven IaaS adoption. Meanwhile there’s a gap between IaaS and PaaS that is still not easy to cross. Solum will make this gap easier to cross as it will allow both worlds to coexist. You’ll be able to migrate your old architecture than decouple it brick by brick moving them up the stack benefiting from all the advantages we’ve talked about.

This article has been cross posted in french on the Numergy’s blog : https://www.numergy.com/developpeurs-blog/openstack-solum-le-chainon-manquant-entre-le-iaas-et-le-paas/

Categorised in:

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>