SPIKE: Python 2 to Python 3

[libdgg]

NOTES from meeting CB, AC, AZ, BC, DG 2021-11-09

• Applications: open emory, keep, finding aids, PIDman
• Libraries: eulindexer, eulfedora (think these are python 3 compatible)
• python 2 is past EOL
• the dependent libraries have upgraded to python 3
• ability fix issues that arise is at risk
• you can have 2 and 3 on the same system
• on core systems servers we wanted to run 2.7 - specific version for specific needs
• how do we test these changes before moving to production? test instances for the applications? we have qa servers so we could setup test environments if we don't have them
• roll back - we have multiple versions - freeze backup for version 2 so we could redeploy to roll back. hopper runs python 2 so doing a test on that might be possible. we have about 10 versions (automatically cleans up the oldest version)
• open emory would be a good app to start with
• beth setup environment for python 3 and zo would be working on the code to use python 3. both will look at the infrastructure.
• note in the future we would need to look at upgrading servers. however, we would ideally like to look at migrating out of our servers to AWS
• ideally we would be moving out of these applications into hyrax applications but there are other blockers. we have repo environment but it does not include AV which is not ready at the moment. we could move digitized books but the process to move things would take longer than updating python. we have PIDman (we don't have a good way since we need to be able to move stuff first and finding aids will go away if we implement archivesspace. Given all that we should plan to do the python upgrade.
• Avalon for AV items? The one we have built is explicit for use only for course reserves for AV materials that we can not stream/deliver via any other online service. It is also setup to work with Canvas. If we were to use Avalon for another purpose it would likely be a separate instance.

[rotated8]

11/23 Update: Will decompose this ticket into new, smaller, focused tickets, centered around ansible work. Then this ticket can close.

We'll use libqas001 for this work.