MNDeployment #6544: TERN Australia (powered by AEKOS)
TERN - GMN upgrade from 2.4.2 to 3.0.4
#1 Updated by Amy Forrester over 4 years ago
We run two instances of GMN. We have one for production and then another non-production that we test things on. I've added a 'dahl' user to both instances, with sudo access, and the firewall is open so Roger should be able to do his thing. The details of the VMs are:
Some notes for Roger: both instances should be nearly identical. I try to keep non-prod in sync with prod but it will no doubt have diverged a little. GMN is the only thing running on each VM so if you need to restart, go ahead. Both VMs are also horribly outdated, running Ubuntu 14.04. Please don't judge us, we're spread pretty thin when it comes to ops. Lastly, the /etc directory is a git repo on both machines. I've done a commit just after adding your user so if you need to revert for any reason, use your git-fu and you'll be fine.
#4 Updated by Amy Forrester over 4 years ago
TERN sticking with the existing DNS names. Updated the DNS entries to point to the new VMs.
* reuse the existing SSL cert, but expires in a few weeks (in the process of getting a new one and will install that when it arrives)
The DNS entries are:
dataone-dev.tern.org.au => 220.127.116.11
dataone.tern.org.au => 18.104.22.168
#5 Updated by Amy Forrester over 4 years ago
- % Done changed from 0 to 100
- Status changed from New to Closed
9/1/18: The servers is up and running. Everything looks good. -Roger
I did the same install on your dev box, and loaded it with a copy of your production science objects.
I checked if your dev instance is still registered in the dev environment, and it's not. That's not surprising since we sometimes completely wipe out and repopulate the dev environments.
Don't hesitate to ask if there's anything else I can help with!