Participated in MSPJ Migration Competition 2017winter

My name is Sashihara and I am an infrastructure engineer.

Ito and Teraoka from our company also posted articles, and I also participated in Migration Competition 2017.

By the way, the winning prize 250,000 yen ! ! !

 

The venue was in Tokyo and it started in the morning, so I went to Tokyo the night before.
The yakiniku and wine we had that night were delicious.

The content of the day was about migrating Redmine from AWS to Azure.

After that, we formed a team of three people, and my team had flowers in both hands.
It ended up being 1 man (me) + 2 women. I did it

Roughly speaking, the requirements are like this

I would like to completely migrate the current environment to the new environment.
I would like a report on the implementation details and results.
When stopping the system, we need to notify users, so we would like to hear from you.
It's an old environment that I've been using for a long time, so I'd like it to be updated.
If possible, I would like to switch so that it does not affect users.
I would appreciate it if you had some information about the server if possible.
If possible, I would like to be able to take backups since I don't have any backups at the moment.If
possible, I would like to make the system redundant as the number of users will increase in the future.
If possible, I would be happy if the necessary information for handing over to a new infrastructure engineer is compiled.

So, after discussing this with the team, we decided that the most important thing to do was to upgrade and migrate, so we decided to proceed with that policy.

However, one of the requirements is redundancy, and I thought it would be troublesome to add it later, although it would be possible.

• L.B.
• WEB*2 units
• DB (master/slave)
• Azure File Storage (for attached images)

Like that

I thought there would be no problem with migration as long as the data (DB and attachments) could be moved properly.

1. For now, let's get Redmine running in the new environment.
2. then move the data

We proceeded in this manner.

I was able to make the transition even though I got stuck in some places.

Since the versions of MySQL and Redmine themselves were also changed, I was worried that there would be no problems after migrating only the DB data, but I was able to migrate without any problems. good. . .

What are the examination results?

I couldn't win. . .

The migration should have been complete, but when I looked at the logs later, I was wondering why, and there was a 404 error.

I made a mistake in the URL. . .

I was also given a URL to review the requirements that I received separately, but that URL and the URL of the migrated environment were different (whether /redmine was present or not).

I'm really sorry to those who were on the team with me. .

summary

Personally, I had never used Azure much, so it was a very good experience and I enjoyed it.

Also, be sure to read the documentation!

Thank you to all the organizers and participants for your hard work!

I hear there will be another one next time, so I definitely want to participate!