This document describes how to create a private PaaS service for local development of OpenShift Origin. We will be building the PaaS using source OpenShift Origin nightly RPMs Vagrant, and Puppet.
Public and private cloud offerings are enabling innovations to help make life easier for developers. In this session you’ll learn how to build your own Platform as a Service (PaaS), with the open source code (OpenShift Origin) Red Hat uses to power its OpenShift Online. OpenShift is a free, auto-scaling PaaS based on Red Hat Enterprise Linux and built on top on Amazon EC2. We will cover some of the basic pieces of the architecture, what we do with Linux kernel "magic" and SELinux, and how you can run it yourself. Resources for getting started will pointed out and referenced. We are also looking for active members to help us improve our community – everyone from doc writers to developers to unit testers are welcome.
I found several free readers, and Tiny Tiny RSS seemed like a really good option. The developer hosts an online version of the reader, which I used for quite a while. (The online service is soon going to be discontinued.) I was quite content with that option, but when OpenShift was launched, I thought I’d try hosting tt-rss myself: it initially began as an experiment to using OpenShift. Then, when I moved this blog to OpenShift, I realised it didn’t really take much effort to host the blog, and that I could switch my primary instance of tt-rss from the developer-hosted instance to my own. It turned out to be really easy, and here I’ll share my recipe.
This time I’m going to talk about the service OpenShift Origin uses to publish user’s applications: The Domain Name System or DNS.
Users interested in creating cartridges or adding fundamental features to OpenShift should read this document. A “fundamental” feature is hard to define but one example would be the difference between PHP and WordPress. WordPress requires PHP to run. It uses the PHP cartridge and in that way, php is a fundamental feature required for wordpress to run. PHP would be a cartridge but wordpress would be an application. WordPress also needs MySQL to run, so in that scenario PHP and MySQL would both be cartridges but WordPress (even if one wanted to package it and provide it to others) would not be a cartridge.
In this blog post I’ll share my experience migrating an existing application built for Heroku to OpenShift. Hopefully this blog post will give ideas on how to migrate your own application while showing how easy it can be. Every application is different so the steps you may need to perform may be different.
You now have a multi-node open-source PaaS.
You can start adding new functionality to the core OpenShift Origin code or start writing your own cartridges and help make OpenShift the best PaaS platform.
CloudBees is a deployment platform specifically for Java apps
Cloud Foundry is an innovative, multi-language platform that is officially open source, but whose caretaker is virtualization leader VMware.
DotCloud is an independent, multi-language platform that boasts simple, command-line-based deployment of apps and databases using Amazon AWS cloud.
Elastic Beanstalk is operated by Amazon Web Services, the undisputed cloud infrastructure leader.
Engine Yard offers managed deployments of apps using Ruby on Rails and PHP
Force.com is the proprietary cloud platform from Salesforce.com.
Google App Engine is a simplified, but also inexpensive, deployment platform for applications in Java, Python or the open-source language Go.
Heroku is Salesforce platform for non-proprietary technologies.
Longjump is one of the first cloud platforms in the field (as early as 2008!) and includes a model/view/controller (MVC) implementation of Java designed to let developers build componentized apps arou
(Full Story: Why You Should Build Your Apps on a Cloud Platform)
Right now, API-based infrastructure-as-a-service offerings like that from Amazon Web Services and SysOps (or DevOps) tools are developers best friends in the cloud. Application-lifecycle platforms such as Cloud Foundry and Red Hat OpenShift are poised to reach critical mass in 2012, whereas so-called NoOps platforms such as AppFog and Heroku will reach that point in 2013.