Architect Roles across OpenMRS

Part 5: DevOps Architect

About our Infrastructure:

We are looking for someone to help us maintain, upgrade, and improve our growing infrastructure. If you’re passionate about anticipating developer needs and preparing for scale, you’re looking in the right place. Some technologies we are currently using: Ansible, Puppet, Terraform, OpenStack, Docker, nginx, the Atlassian suite (Bamboo, Confluence, Jira), Discourse, Wordpress, OAuth2, SAML, LDAP, and MySQL.

Role Overview:

  • Responsible for proactively leveraging tools to make managing our infrastructure as easy as possible.
  • Prepare OpenMRS to be ready for Cloud. This includes working closely with the backend lead to help design OpenMRS so that it can leverage current best practices for deploying to the cloud.
  • Serve as a devops expert for implementers, to provide guidance on deploying and maintaining openmrs.
  • Security: Strong awareness of security issues, especially as it relates to keeping our infrastructure secure.
  • Maintain community infrastructure:
    • Maintain critical tools the community relies on (and their related servers) such as Discourse, Atlassian suite: Confluence, Jira, Bamboo (without this we can’t release software), openmrs.org, all om.rs links, demo & qa environments, JetStream server uptime
    • Supports & ensure successful maintenance of all OpenMRS login services such as our LDAP Server
    • Respond to and troubleshoot downtimes of community assets

Skills Required:

  • Puppet and especially Ansible experience (as configuration tools for infrastructure maintenance)
  • Terraform experience (for setting up new servers)
  • Docker expertise
  • Atlassian experience (specifically Confluence, Bamboo, and Jira)
  • LDAP, OAuth2 experience; some knowledge of SAML (for authentication maintenance and improvements)
  • Knowledge of scripting languages commonly used for infrastructure maintenance such as Bash, Python or Ruby
2 Likes