Nice-to-have Colima doc improvements

[jristau1984]

• Resolve questions below, which may result in additional ticketing.
• Develop and communicate any updated setting recommendations (maybe split out as a separate ticket)

Questions/Thoughts:

• Should the doc mentioned Docker Devstack at all (e.g. uninstall, etc.)? Should it be less about migration, and just about colima setup?

• Do we still want to work out ideal settings for memory and cpu, etc.? Should this move to a separate ticket?

• There is an outstanding comment at the bottom that may result in a new recommendation that should be incorporated? See https://2u-internal.atlassian.net/wiki/spaces/AT/pages/860553280/Docker+Replacement+Recommendation?focusedCommentId=863961154

Need to deal with Alex's data migration documentation.

• Are his changes changes that can and need to be landed, or was it just about Docker Devstack migration?
• Why do we have mysql57 and mysql8 through devstack. Is mysql7 still needed?

[jristau1984]

@dianakhuang please confirm that the questions in the description have been addressed, and close this out.

[UsamaSadiq]

Initial findings on the issue:

Should the doc mention Docker Devstack at all (e.g., uninstall, etc.)? Should it be less about migration and more about Colima setup?

The document should primarily focus on Colima setup since it’s the intended direction. The current document already has extracted the instructions to migrate from Docker Devstack into another separate guide so this point can be taken as already implemented.

Do we still want to work out ideal settings for memory, CPU, etc.? Should this move to a separate ticket?

After consulting within arbi-bom team, the current memory, CPU settings mentioned in the document are working fine for everyone. Since there is no issue currently being reported by any team regarding devstack performance using Colima, we can keep the default settings as is.
If a need arises to tweak and test default settings later on, that can be done in a separate ticket.

Should the outstanding comment at the bottom of the linked page be incorporated?

The discussions which happened in the mentioned document have already been incorporated into the final colima runbook so we can consider the current run book as the final version.

Need to deal with Alex's data migration documentation.

The migration issue mentioned by Alex can already be handled by the setup instructions provided in the document so we don't need to add any additional information in the run book.

Why do we have MySQL 5.7 and MySQL 8 through Devstack? Is MySQL 5.7 still needed?

MySQL 5.7 reached its end of life in Oct 2023 so it should be removed from devstack now. SRE/Arbi-bom team can take on this effort to do this discovery. edx-platform has already stopped running migrations checks on MySQL 5.7 so we can start removing the support for MySQL 5.7 from devstack as well.

[UsamaSadiq]

@jristau1984 The only thing needed under this issue is to remove MySQL 5.7 from devstack and configuration. Please let me know if I should create a ticket for arbi-bom team or give a headsup to the SRE team for this?

[jristau1984]

Let's get a new ticket on the Arbi-BOM board, and help SRE out where we can. Thanks!

[UsamaSadiq]

Created follow up ticket on Arbi-BOM project board.