Drupal is an open source content management platform powering millions of websites and applications. It’s built, used, and supported by an active and diverse community of people around the world. For more information on Drupal, please see the official site at: http://drupal.org/
UMassOnline had been using a homegrown CMS/CRM that was built using ColdFusion since 2001. There were many hacks and customizations which made support, maintenance and upgrades very difficult and time consuming. In addition, the data center that supported the environment was facing a lack of support, which meant that while we could support the application, the physical servers have no disaster recovery. In summer of 2012, UMassOnline Marketing and Technology Teams began developing a plan to move away from the homegrown system to a more robust Web Content Management System.
Drupal is currently being used as the Web Content Management System for UMassOnline.net. At this time, the site https://login.umassonline.net is currently using Coldfusion and is still hosted at 474 Main Street data center. The login pages should be moved to Blackboard by Fall 2013.
Login Pages: https://login.umassonline.net ( still hosted on CF7 at Main St, pending move to Learn hosted pages )
As an open source platform there are no licensing fees, however the development, deployment and support of Drupal does include other expenses.
UMOL is currently hosting Drupal through Amazon Web Services.
Environment and Technical Specifications
Environments are hosted on Amazon EC2
Configuration (shared across environments)
- Red Hat Enterprise Linux
- Drupal 7
- MySQL 5
- PHP 5
Current Instance Use (subject to change)
1.70 GB memory, 32/64-bit, 2 units, Moderate I/O, 10 GB EBS storage
3.75 GB memory, 32/64-bit, 2 units, Moderate I/O, 10 GB EBS storage
15 GB memory, 64-bit, 13 units, Moderate I/O, 10 GB EBS storage, Reverse HTTP proxy front-end caching
Business Continuity Strategy
In the event of an emergency, UMassOnline is prepared to restore backups of our system - both database and system.
A full database backup is taken and stored on the server each morning at 4:45AM EST.
A full system snaphot is taken and stored in the AWS Console each morning at 12:30AM EST.
For each campus Go-Live, a full database backup is taken and stored on a separate server in case of emergency. Amazon has the ability to spin up new instances on different servers so that we know that our site can back in "production" within 24 hours of the initial incident. XML (campus go-live) is stored in logs on the server so that the raw XML can be recovered if ever needed.
For Escalation information, see here.
UMassOnline has put together documentation outlining training for use on the UMassOnline.net development site. That information can be found in the Knowledgebase.
Restore steps TBD.