It all started with Dockerizing an old version of Confluence with Docker Datacenter
In my role as Cloud Architect I often hear, “Docker sounds great but it won’t work for my application.” In my experience Docker can improve the state of many applications including legacy and vendor solutions. The first production workload at Cornell on Docker was the University’s wiki which is run on Atlassian’s Confluence in April 2015.
Our installation of Confluence is an interesting intersection of legacy and vendor solution. We have customized the code, to work with our single sign on solution, as well as a custom synchronization with LDAP for group management. When we started the project to move Confluence to the cloud the infrastructure, the software was old, compiled from the source and was being hand maintained.
The stack looked like this:
- Apache 2.2.10
- OpenSSL 0.9.8H
- Java 1.6 (EOL 2/13)
- Confluence 5.6.5
This presented us with a number of challenges including:
- The version of Java stopped receiving public updates in February of 2013.
- Multiple vulnerabilities reported in the OpenSSL and Apache versions we were using.
- The last upgrade project for Confluence took six months.
- We had multiple environments for development, testing and production and over time these servers had fallen out of sync.
- The engineers who had originally set up these servers and made customizations, have left the University. When we looked how we might add high availability or whether a disaster, we found it too difficult to replicate the environment.
Read the entire article here, It all started with Dockerizing an old version of Confluence with Docker Datacenter
via the fine folks at Docker.