Skip to content
This repository has been archived by the owner on Aug 29, 2018. It is now read-only.

Latest commit

 

History

History
36 lines (30 loc) · 1.91 KB

README_OSE.asciidoc

File metadata and controls

36 lines (30 loc) · 1.91 KB

Openshift Enterprise Specific notes

If you wish to perform an Openshift Enterprise install you should set ose_version appropriately as this will assist in ensuring supported configurations. Currently any value other than undef has the same effect, however version specific parameters may be introduced in the future.

While this module will assist in providing supported configruations please refer to Openshift Enterprise Deployment Guide for current prerequisites and supported configuration details.

Constraints imposed :

  • Red Hat Enterprise Linux 6 version 6.5 or later

  • Broker and Node roles are mutually exclusive

  • Broker HA load balancing must be external to OSE nodes and therefore can not be configured via this module

  • Avahi and Route53 DNS plugins are not supported

  • ActiveMQ, if clustered, requires 2+ nodes

  • MongoDB replicasets must 3+(2*n) nodes

  • 10gen-mms-agent and phpmyadmin cartridges are not included in Openshift Enterprise and therefore have been removed from the list of default cartridges

oo-admin-yum-validator

If ose_version is set then oo-admin-yum-validator with the ---fixall flag will be run prior to installing OSE packages. Once oo-admin-yum-validator has run successfully puppet will not run it again. If you modify your yum configuration after oo-admin-yum-validator has been executed you should you should re-run oo-admin-yum-validator to ensure proper repo priorities and package exclusions.

Yum repositories

Configuring yum repositories via this module is not currently supported. Please ensure subscriptions and/or yum repositories are configured per the deployment guide. https://access.redhat.com/documentation/en-US/OpenShift_Enterprise/2/html/Deployment_Guide/Red_Hat_Subscription_Requirements.html

TODO

  • Use stored configs to push node dns changes from broker without sharing secrets to nodes

  • Stored configs for districts

  • Broker API key, rsync key?