Cloud Zone is brought to you in partnership with:

Eric D. Schabell has been working within software development since 1998 for many different organizations such as IBM, Radboud University Nijmegen, SNS Bank and smaller software companies. He has been involved in different roles within Open Source projects such as Sourcemage Linux, eGroupWare, DocConversion, cmlFramework and is still helping out in the JBoss jBPM project focusing as lead on the jBPM Migration project. Since 2009 he has been actively evangelising JBoss products and is a huge fan of OpenShift (PaaS). He is employed as JBoss Technology Evangelist for Red Hat, is a guest lecturer at the Radboud University Nijmegen and enjoys writing on various topics. Eric D. is a DZone MVB and is not an employee of DZone and has posted 80 posts at DZone. You can read more from them at their website. View Full User Profile

OpenShift Enterprise: High Availability Reference Architecture

01.29.2013
| 3179 views |
  • submit to reddit
As stated on the Red Hat OpenShift Enterprise (OSE) site, "OpenShift Enterprise is a comprehensive enterprise development platform for the cloud era. It provides everything you need to develop and execute enterprise applications—delivered in your choice of private or public cloud."
Scott Collier has been working on putting together a high availability reference architecture for installing OSE on-premise or hybrid Pass solution. This solution includes a demo of deploying a JBoss mobile project to the final architecture. This reference architecture is available at the Online Resource Library (limited version) and in the Customer Portal (full version). 
Here is a preview to get you started!
OpenShift Enterprise reference architecture
The OpenShift Enterprise (OSE) reference architecture is broken up into three parts. The first part is the product and Reference Architecture environment overview. The second part consists of deploying OSE in a distributed fashion. The third part covers a few operations and management activities. In addition, all configuration files that were modified to build out this OpenShift Enterprise infrastructure will be included on the Red Hat customer portal.
Part I:
  1. Component overview
  2. Environment overview
    • Software required
    • Hardware required
Part II:
  1. Deploy the Broker Support Nodes
    • Mongo replicated set
    • ActiveMQ network of brokers cluster
  2. Deploy the Brokers
    • Use Microsoft Active Directory as authentication mechanism
    • Deploy OpenShift Enterprise Console
  3. Deploy three OpenShift Enterprise nodes
  4. Deploy the Red Hat Load Balancer Add-On
    • Configure the appropriate load balancing algorithms and appropriate
  5. checker scripts
Part III:
  1. Configure the OpenShift Enterprise client tools
  2. Confirm proper OpenShift Enterprise infrastructure operation
  3. Deploy PHP applications via command line
  4. Deploy PHP applications via OpenShift Enterprise Console
  5. Deploy Java applications via JBoss Developer Studio version 5
  6. Deploy Java applications via JBoss Developer Studio version 6
  7. Application scaling
  8. Deploying applications with Jenkins Continuous Integration System
  9. Node / Gear / District management
Published at DZone with permission of Eric D. Schabell, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)