Make old conference websites static, and switch off servers

[datapythonista]

I think this is the list of conference sites that we can switch off, after making them static (listing Rackspace service name):

• dask2021
• eindhoven2021
• global2021
• jupytercon2020

[aterrel]

@martey is this done?

[aterrel]

@mattnumfocus or @martey do you have any updates on this work?

[aterrel]

deleting network for these sites, to do a scream test. Deleting the dns records for the following

• summit.dask.org: 104.130.13.112
• eindhoven2021: already gone
• global2021: no dns record will delete server May 10
• jupyter2020 doesn't seem to have a dns record, removing network 104.239.163.133

[aterrel]

https://cfp.jupytercon.com/2020/schedule/general-sessions/ definitely goes down without that machine. But does anyone know....

[aterrel]

No one screamed, Andy to back up and turn off

[martey]

Sorry for the lack of updates on my part. Rackspace sent this email last week (emphasis mine):

As part of our commitment to delivering high-quality services and maintaining industry standards, we wanted to inform you of an upcoming adjustment in pricing for your Rackspace OpenStack Public Cloud services. Effective September 13, 2024, there will be a 22% price increase for your Rackspace OpenStack Public Cloud services. This adjustment is necessary to ensure we can continue delivering the exceptional service and support you expect.

There are currently three conference site servers (dask2021, global2021, and jupytercon2020) on the account. I will ensure that their content is all archived and that the servers are deleted by Friday. I will confirm here when that is done.

The Rackspace account has eight servers on it in total though, so I don't know how much the three conference servers are contributing to the bill.

[aterrel]

Thanks @martey I'll do an audit this week and turn off the servers that passed the scream test. I think I might have not done that fully.

[martey]

Hi @aterrel,

As I mentioned in our meeting earlier today, I took a look at the nginx configuration on "pydata.org-2". There are only two sites referenced there - Global 2021 and the main pydata.org site.

After several misfires, I was able to create a custom CloudFlare worker for Global 2021 (that redirects directly from CloudFlare to the global2021 Rackspace server). I have changed pydata.org's DNS record from an A record pointing at pydata.org-2 to a CNAME pointing at the WordPress site.

There shouldn't be any more web traffic going through pydata.org-2 (other than people improperly caching the site's DNS). I am going to wait about 24 hours to ensure that this is the case (by checking the access logs on pydata.org-2 and the error logs on the WordPress site). If there are no problems, I will delete the pydata.org-2 Rackspace server.

I am still working on the other three conference site servers, but since the pydata.org-2 server is bigger than all three servers combined, I assume it is more expensive.

[martey]

pydata.org-2 has been deleted. Just in case we realize later that there were files on the server that are needed, I saved an image of it in the Rackspace control panel.

[aterrel]

assigning to @adavies as he finishes the audit and #48