ITSM roadmap for 2024

Owned by Cintia Del Rio
Last updated: Aug 28, 2024
3 min read

 

It seems that there are three big themes to be picked up next in this space:

 

  1. Cleaning up tasks from ID and Atlassian migration https://openmrs.atlassian.net/browse/ITSMOLD-4325

    1. https://openmrs.atlassian.net/browse/ITSMOLD-4328 : a requirement to sunset

    2. https://openmrs.atlassian.net/browse/ITSMOLD-4324 : if openldap is choosen to be kept, we will need to upgrade it

    3. https://openmrs.atlassian.net/browse/ITSMOLD-4231 : if openlap is chosen to stay, we need to get those certificates to automatically restart the container in a way that will actually pick the new certificate. We may go with a cron task, may be easier than the letsencrypt hook. Potentially the ldap upgrade will help here

    4. Verify the future of login of https://atlas.openmrs.org, that used to use our old ID. This system may be considered for sunset as well

    5. Delete older machines. I expect jira, confluence, id and crowd to not be needed anymore. That also includes their databases and database storage. That would include as well removing ansible code, archiving ID repo, the lot

    6. Update documentation related to how we do our ID now: OpenMRS ID

    7. Improve monitoring for this area

  2. Bamboo stability

    1. bamboo is likely due to an upgrade! It may be a huge one

    2. We may look if we can change any configuration on predator to make builds more stable https://marketplace.atlassian.com/apps/1212736/predator-plugin-for-bamboo?tab=overview&hosting=server

    3. https://openmrs.atlassian.net/browse/ITSMOLD-4322 : Bamboo server and agents seem to run out of disk every so often due to logs. We can look at logrotate carefully

    4. https://openmrs.atlassian.net/browse/ITSMOLD-4316 : Bamboo backups may not be working as desired

    5. Check monitoring for those instances. Do they need more resources? Check build waiting time, do you need more agents? If we are willing to pay AWS, we could have elastic agents (not sure if desired)

    6. Any other build improvements for reliability needed

  3. Monitoring love

    1. Datadog seems to be notifying things non stop. Do some machines need some more memory/CPU/disk? Do we need to do some cleanup?

    2. https://openmrs.atlassian.net/browse/ITSMOLD-4149 : having datadog monitoring for unhealthy containers could be rather useful. For unhealthy containers, we may want to automatically restart them or something

    3. https://openmrs.atlassian.net/browse/ITSMOLD-4319 : do all machines that need backup are deploying it as expected? Do we have good monitoring for them?

    4. https://openmrs.atlassian.net/browse/ITSMOLD-4228 Pingdom is a paid integration. If our datadog isn’t as noisy anymore, we could potentially replace it altogether with slack, unless we actually want any folks on call

 

Miscellaneous tasks that could be picked as well

 

 

Suggested

  • Upgrading terraform (i.e., our infra was built with 0.12.31, current version is 1.9.3) lest we hit a point where functionality starts breaking and we’re forced to upgrade quickly.

  • Making our SSO more robust (we’ve managed to get KeyCloak working, but I’m not sure we’re fully divested from the old OpenMRS ID code, don’t have clear/easy mechanisms for granting permissions, don’t have an easy ± (semi-)automated way to mark accounts as spam

  • Better supporting our dev and CI processes (e.g., make sure devs reliably have the environments they need, fix issues with permissions getting messed up via docker on CI, etc.)

And there’s a long tail of other nice-to-haves (e.g., fixing things that are occasionally breaking like LetsEncrypt upgrades), though some of those might get fixed with upgrades.

Resources:

Â