IT Services Provided

Infrastructure list

Community-managed

Production Tiers

Tier 1:

The most used and relevant services for the community. A large portion of the active community would consider 1h long outage during business time a bad experience, and would prevent them doing their work. These are the most critical systems that affect most of our community, most of the time.

• JIRA
• Wiki (Confluence)
• Talk
• OpenMRS ID Dashboard
• Maven repository

Tier 2:

These services can be down quite possibly for a couple of hours before it actually blocks someone.

• Continuous Integration (Bamboo)
• Public website
• Public Demo and main OpenMRS environments
• yourls / link shortener

Tier 3:

Similar to Tier 2, but a smaller percentage of the community would be affected.

• Module Repository/Addons
• OpenConcept Lab

Tier 4:

Either affects a very small percentage of the community, or accessed/used much less frequently.

• All other OpenMRS environments
• OpenMRS.org
• Atlas
• Chat bots
• mdsbuilder
• Addons (stg) *
• OpenConcept Lab (stg and qa) *
• Quizgrader
• Javadoc storage
  
  

Third-party systems

• Github
• Dockerhub
• Twitter
• YouTube
• Facebook
• Sourceforge
• Bintray
• Notes
• RSS aggregator

System availability

Our key systems are monitored 24x7 by the third-party service Pingdom. If you see a current outage, don't worry. The infrastructure team has already been alerted.

• View (and bookmark) the status dashboard: http://status.openmrs.org/

Requesting resources

OpenMRS.org e-mail

E-mail is managed by Google Apps. Check Requesting an OpenMRS email if you need one.

Mailing lists and groups

Communication is done by https://talk.openmrs.org

JIRA issue tracking, Wiki or CI

Raise a request in https://help.openmrs.org/