Page Comparison

...

1. Cleaning up tasks from the Atlassian suite migration

   1. 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

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

   3. Improve monitoring for this area

   4. Define if OpenLDAP is what we want in the future. The main concern here is cost. If we go with other solutions, we may need to define the lifecycle of those users, so we limit ourselves to a sensible number of accounts at a time.

   5. Jira Legacy
      server System Jira serverId dd5f38d5-f8f4-3f41-9551-b59f4841491c key ITSMOLD-4324

      : if ldap openldap is choosen to be kept, we will need to upgrade it

   6. Jira Legacy
      server System Jira serverId dd5f38d5-f8f4-3f41-9551-b59f4841491c key ITSMOLD-4231

      : if LDAP 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

   7. 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

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. Jira Legacy
      server System Jira serverId dd5f38d5-f8f4-3f41-9551-b59f4841491c key 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. Jira Legacy
      server System Jira serverId dd5f38d5-f8f4-3f41-9551-b59f4841491c key 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. Jira Legacy
      server System Jira serverId dd5f38d5-f8f4-3f41-9551-b59f4841491c key 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. Jira Legacy
      server System Jira serverId dd5f38d5-f8f4-3f41-9551-b59f4841491c key ITSMOLD-4319

      : do all machines that need backup are deploying it as expected? Do we have good monitoring for them?

   4. Jira Legacy
      server System Jira serverId dd5f38d5-f8f4-3f41-9551-b59f4841491c key 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

...