Saturday, April 30, 2016

Cloud MSP to ISV: The new Era of PaaS

      As working with Cloud Managed service provider, We manage Public and private cloud infrastructure with platform such as Apache, IIS, Ngnix etc. Either MSP or customer developers application and entire management and monitoring becomes the same story as on premise infrastructure.

     Lately i was playing with openshift origin ( Private PaaS ) in my test environment and i really find great opportunities for MSPs where instead of managing IaaS (monitoring and managing headache) traditional way MSPs can deploy PaaS and manage the same infrastructure and application with self serviced application deployment with their own Platform as a service on top of any public/private cloud infrastructure (IaaS).

Lets dive in to the question "How?"

    Openshift Origin allows to build high level application platform (eg. Magento, Wordpress etc.) as well as low level platform such as PHP, Java, Go, Python etc. and various database as service (eg. MySQL).

openshift origin also allows to build custom cartridge (platform) and integrate different cartridge with different platform.

   Openshift application runs on gears (Containers) build from basic security building block SELinux.
SELinux provides a high level of isolation between applications running within OpenShift Origin because each gear and its contents are uniquely labeled.

    cgroups (Control Groups) allow you to allocate processor, memory, and input and output (I/O) resources among applications and Kernel namespaces separate groups of processes so that they cannot see resources in other groups.

    Following characteristics makes MSPs to become ISVs
      1) Multi tenancy
      2) Public, private, virtual and bare metal support
      3) Self service portal for developers to deploy application
      4) Integration with code repos (Git), CI/CD and existing automation tool for developer.
      5) Integrated and Custom DNS.
    I know that above description was crappy lame basic description for any techi. but hold on for the cool stuff. Since its high level overview post i wanna show how easy it is

  Step 1: Select your platform.



Step 2: Select your platform. Here i am selecting wordpress for simplicity.

Step 3: Enter the DNS URL, Git repo, Bla Bla Bla...

Step 4: Select the scaling policy (load balance with HAProxy) and create application

  Well there are few caveat with PaaS implementation and application requirements, so hang on for in depth technical post.