-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replacing machines from Joyent data center #2552
Comments
Just chipping in, me and Michael have been doing most of the effort up to now with lots of help from a person at Joyent. I will tomorrow review the |
@richardlau can you take care of the libuv side - making sure team is aware and removing smartos 15,16 from the CI before Wednesday. |
I've done https://ci.nodejs.org/view/libuv/job/libuv-test-commit-smartos/ (see libuv/libuv#3121). As noted in libuv/libuv#3121 (comment) the only other libuv job runs https://ci.nodejs.org/job/node-test-commit/ so ends up running https://ci.nodejs.org/job/node-test-commit-smartos/ which will need to be updated but that's a Node.js, not libuv, job. FWIW these are the hits for https://github.com/nodejs/jenkins-config-release
https://github.com/nodejs/jenkins-config-test
Anything in a description is benign (although we can tidy up for appearances) but any @mhdawson I think node-test-node-addon-api has been superseded... https://ci.nodejs.org/job/node-test-node-addon-api/ is currently disabled. Perhaps it can be removed entirely? Let me know if you'd like/need me to update the Node.js release and test jobs. |
Also FWIW in terms of release machines we build Node.js 10 releases on build/jenkins/scripts/VersionSelectorScript.groovy Lines 83 to 91 in 3d9672e
|
Yes, I figure out we don't use 15 and 16 which is why I asked that we bring over smartos17 but not those 2. (did not look like there were enough IPs to bring them all over) |
Deleted. |
@richardlau can you take care of removing the references from the rest of the places you mentioned. |
I delete the job related to |
Small update based on last nights work: we only have one machine left to migrate which is going to be done today. |
I've removed the release and test smartos 15 and 16 machines from secrets and opened a PR to remove from the ansible inventory: #2554 |
I've also removed the release and test smartos 15 and 16 machines from the CI. |
Update: the backup machine completed the jobs successfully. I've had to remove the bits where we try to backup our mysql for benchmarks due to that machine not being available any longer. This should conclude the migration. Next steps is opening PR(s) to update our repo. |
We've turned off all of the old machines and the Joyent data-center is being de-commissioned today. We'll know soon if we updated/migrated everything that was needed :) |
Kicked off test builds on smartos only to validate the replacement release machines: |
Did some basic tests (
No issues to report, so I'm happy the new release machines look okay. |
Based on the table in the description I've opened #2568 to update the ansible inventory. |
@mhdawson @jbergstroem the one remaining task here is
I'm guessing at this point that the current "process" if we need to do any of that for the Joyent machines is to contact @bahamat? I can update the outdated notes in the secrets repo and close this off, otherwise I'd suggest we open another issue if it's something we want to keep open. |
@richardlau +1. Lets just document and close this out. |
I've updated the notes for the Joyent machines in the secrets repo. |
We found out late Friday that the machines in the Joyent data center needed to be moved by next week. These have been moved:
The smartos machines below 17 will not be moved over.
We'll need to:
ones that we current release on for smartos)
The text was updated successfully, but these errors were encountered: