Custom Query (1552 matches)

About

We are migrating from the Peer1 VM to the FreeBSD host. This story is required to track progress as there are many things to do.

Trac migration

• ☑ Change DNS A/AAAA records
• ☑ Restore latest (29.11.19) backups
• ☑ Restore MySQL database
• ☑ Create new SSL keys
• ☑ Restore nginx configuration
• ☑ Restore trac data to the new server
• ☑ Restore SVN sync from the sf.net to trac (done, every 3m)
• ☑ Create system service to start trac on server restart, validate it
• ☑ Fix loading plugins in the trac/plugins dir
• ☑ Re-enable re-captcha plugin
• ☑ Check if new user registration is working properly
• ☑ Fix man pages and docbook HTML renderer
• ☑ Check if SMTP is working
• ☑ Re-enable TracTocMacro plugin

Related services

• ☑ Restore SVN mirroring to the GitHub (sync2git process)
• ☑ Restore builds.smartmontools.org website
• ☑ Re-Enable doxygen docs generation
• ☑ Create new user to store the backups, sync content to another locations and provide access to another members
• ☑ Switch to mailgun as external SMTP server

Long-term changes

• ☐ Think about moving trac to VM or docker containers to allow fast relocation if needed
• ☐ Check if documentation is up to date. Setup export of it to the backups.
• ☐ Create DR documentation and put it with a backups

Following changes needs to be done in the DNS:

1. Add TXT record for the trac subdomain with value v=spf1 include:eu.mailgun.org ~all

2. Add TXT record for the pic._domainkey.trac subdomain with value:

   k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2rH/qvQa4DxM/HUs5LgdDF3vRxOu63YsSM/qNW9rhJSoCdRA6jno+/1NpKhJxOLcHxOUlyn+qnTM1bReCG6MVgxvgCTAQ8Wx9xqW6ULoj+sAVj6HPh3dAyYkqfYPhZx3culN0JtSO2ASSBUDLxJQJHsmrRr31XgZZNCR36jpdel/AYBwE3awLhl918Xl3IEELjdm/GjFrwz9t98ohfQGFp1PBUfEtz/b4SjiOnjWzBDpLTI0xFY1HnX4mfDiAT3XmqYXxVHVw79jI3jWxtQpdrB5gUq80VUEd0MloFa41F6sEkyg0ZqFJzocjlGUISV7IZOTlIuT45DFfvWL9ivZ+wIDAQAB
   

3. Add 2 MX records for the trac subdomain, with values:
   • mxa.eu.mailgun.org, priority 10
   • mxb.eu.mailgun.org, priority 10

4. Add CNAME record for the email.trac subdomain with value eu.mailgun.org

5. Remove sphere subdomain records, as it is not in use anymore.

Problem description

Our trac is using Py2 which is EOL ~1yr already

We are using EdgeWall trac to manage smartmontools project, as well as few plugins which are written on Py27, which is ​EOL from January 1, 2020 already. As result py2 is no longer receiving any fixes (including security) and is getting slowly removed from the upstream packages. E.g. in the FreeBSD which we are using to host this instance, trac is already marked as "depricated" and soon will be removed due to py27 dependency.

Upstream project is slowly moving to py3, however it is still in "development" branch only (Trac-1.5.2-py3-none-any.whl). Even after removal from the upstream i will be able to continue to host this trac instance (e.g. using jail and installation using pip2), but it will take more efforts and will give us more and more security concerns.

Installed plugins

Plugins for trac are also written on py2 and will require upgrade or rewrite

Possible options

1. Start testing Trac 1.5/Devel to see how much efforts would take to move trac to it. Problem is that there is no timeline yet, and plugins still need to be ported (at least TracAccountManager which is very critical to us).
2. Use other options, e.g. Github, which now provides WIKI, pages and other. Gitlab could be used as an alternative. Downside is that we will have to port our existing pages and wiki to it, however, that should be a one time job. This would also significantly change our release procedure.
3. Do nothing and support trac/py2 as much as we can, e.g. using jail and self-built py. However, this is insecure and will not help us in the long term