Copy that. We’ll move into working on the JIRA migration. We’ll use the latest version on the new one as well. We’ll make sure that it’s done within next week. Since we are doing this first, are we going to use a mysql instance in the same server or are we to create a new separate mysql for JIRA. Are there any specific versions we need to consider for JIRA, mysql and other dependencies for JIRA?
P.S: Sparsha is suffering from viral fever for the past couple of weeks and is recovering. He’ll be back with us next week.
I don’t mind the data migration or the upgrade being manual, they are one-off tasks. But after the migration, I do expect I’d be able to recreate JIRA VM without manual intervention.
JIRA appears to be down now so I cannot tell what’s the version we have now :D. But I’d like you to upgrade to whatever is the latest version. We need a plan on how to migrate (the data, how long will be the outage, how much time the upgrade will take, the steps and so on).
I’m running mysql 5.6, let me know if it’s not compatible.
I can’t think of any other dependency. Maybe crowd? Let us know what’s the version it needs.
@cintiadr so under 2.1 – everything is dockerized – so just deploy the docker-compose file. We’d need to take a mongodump of the old server and copy the LDAP data directory – which is the volume that the container uses…there’d be a period where there’d be no identity system…since it’s a pain in the butt keeping data consistency due to DNS propagation times…It might be wise to lower the TTL for both old and new records to 5 minutes.
@cintiadr : Sure. I can start working on the confluence migration from the old server to the new one. If you can add my key’s to the boxes that would be great. I can look around on how it’s setup and start working on the same.
Let me know if you disagree with anything. Let me also know if the mysql config is not what you need. Please use any docker image or ansible role you prefer.
Do we still have plans on deploying 2.1?
Regardless, if you test the data migration and crowd upgrade and you are happy with the result, we can schedule it. We just have to make sure crowd is compatible with your current JIRA and Confluence versions.
It would be better to schedule the migration on a weekend. Just write down the checklist/plan first
Done. I will need to give you access to ansible repo too.
I assigned both sonar and mdsbuilder to you.
I assume you’d prefer to make them in docker.
Let me know about when you’d like the hosts ready.
Looking at the pull request, I will need to create a new role only for that, which is probably going to be in another repository to avoid having so many loose files and accumulate tech debt on that. Leave the rest with me, I will continue JIRA from here.