Opened 12 years ago

Last modified 11 years ago

#310 new enhancement

Move sql to a more stable distro

Reported by: adehnert Owned by:
Priority: normal Milestone:
Component: sql Keywords:
Cc:

Description

Fedora gets desupported frequently, and we mostly don't care about recent software on sql.mit.edu. We should switch to a distro with longer support cycles.

I'd be a fan of Debian or Ubuntu LTS, though RHEL, Oracle Linux, or CentOS are other options.

Change History (7)

comment:1 Changed 12 years ago by adehnert

See also -c scripts -i sql on 29 July 2012.

comment:2 follow-up: Changed 12 years ago by achernya

sql currently has mysql 5.1.48; Debian Squeeze has 5.1.63 and the RHEL family (as of 6.3) has 5.1.61.

I would favor moving to RHEL since we have a license for it from MIT, over CentOS and probably Oracle Linux. Additionally, upgrades throughout the 6.x family are fully supported, meaning we may end up getting security updates longer than if we went with Debian.

I feel like moving to Debian may be a bit disruptive, although it would be consistent with running Debian on metal throughout the rest of the project.

comment:3 in reply to: ↑ 2 Changed 12 years ago by adehnert

Replying to achernya:

sql currently has mysql 5.1.48; Debian Squeeze has 5.1.63 and the RHEL family (as of 6.3) has 5.1.61.

Incidentally, this appears to not quite be true: AFAICT, kitchen-sink has 5.1.51 and sliced-bread has 5.1.48.

Ubuntu Precise, for reference, has 5.5.24.

comment:4 Changed 12 years ago by achernya

Due to maintenance today, both sql servers now have 5.1.56. However, (thankfully) this does not change the upgrade path mentioned earlier.

comment:5 Changed 11 years ago by adehnert

Consensus (per -c scripts -i trac-#310 c. 2012-10-30) appears to be Debian.

comment:6 Changed 11 years ago by achernya

primary-key is now installed with Debian Squeeze, and acting as a slave to sliced-bread.

comment:7 Changed 11 years ago by achernya

foreign-key is also now installed, but does not yet have any data. Once foreign-key is added to the cluster and the remctl pony is written, switchover to the new sql servers can be done.

Note: See TracTickets for help on using tickets.