Skip to end of metadata
Go to start of metadata

Environments and Rice Versions

last updated: 2015-05-12

EnvironmentApplicationVersionNotes
env1rice-sampleapp2.5.3build by rice-2.5-build-nightly, currently not really used
env2rice-sampleapp2.6.02.6 AFT
env3  not working - being setup for rice-sampleapp JDK8 AFTs
env4krad-sampleapp2.6.02.6 AFT

env5

rice-sampleapp2.6.0rice-rest
env6rice-sampleapp2.5.2demo.rice.kuali.org
env10rice-sampleapp2.1.102.1 development
env12rice-sampleapp2.5.32.5 AFT
env13krad-sampleapp2.5.2krad.rice.kuali.org
env14krad-sampleapp2.5.32.5 AFT
    

 

Spinning Up new Environments

Real-Time List of Current Environments

Amazon RDS Instances and Rice

Name

Endpoint

JDBC URL

Notes

oracle

oracle.rice.kuali.org

jdbc:oracle:thin:@oracle.rice.kuali.org:1521:ORACLE

No issues.  Default RDS settings worked out of the box with Rice

mysql

mysql.rice.kuali.org

jdbc:mysql://mysql.rice.kuali.org/

Does not work out of the box with Rice. Required modifying MySQL default behavior with the parameter lower_case_table_names=1. Appears to be an extremely simple issue with views containing mixed case references to table names, ie one table is referenced uppercase and others lowercase.

 * Rice's 1.0 line was never upgraded to the point where it is able to provide the basic application metadata required for real time display.  Even though the current Real Time List of Current Environments page was thrown together in 4 hours as a favor to a former Rice project manager to provide an awesome improvement to a 100% manual process (ie Rice team members manually editing this wiki page), it still has the following characteristics:

  1. It automatically shrinks and grows in response to environments being added or removed
  2. It provides DNS monitoring (ie if DNS routing is an issue the page makes this obvious)
  3. It provides server monitoring (ie, if the server behind env9 goes offline the page makes this obvious)
  4. It provides Tomcat monitoring (ie, if Tomcat shuts down for some reason, the page makes this obvious)
  5. It provides Java heap monitoring
  6. For Kuali applications that have been integrated with DevOps it provides ridiculously detailed information about the app running in the environment
  7. It provides a simple way for Rice Team members to label the purpose of each environment (thanks to a feature request from Claus!)
  8. It works the same way across 3 different project teams (KS, Rice, and OLE)

A discussion with Martin Taylor yielded agreement on a new feature request (displaying the most recent HTTP status code as a column on the page).  As long as Tomcat is still up, this column will always display correctly (even on Rice 1.0, with no work required from Rice) and provides a quick way to determine application health.