Move cicd.rtx.ai to `us-east-1`

[amykglen]

this came up at the KG2 rollout party today

it's been taking the cicd.rtx.ai instance a really long time to download databases, and we imagine a big part of that is because it is still in us-west-2 while arax-databases.rtx.ai is in us-east-1.

at some point we should probably move cicd.rtx.ai to us-east-1 as well

[saramsey]

making an AMI now....

[saramsey]

excellent idea Amy and Sundar!

[saramsey]

copying the AMI to us-east-1 now...

[saramsey]

OK, the AMI has been copied, but we are now waiting on availability of an elastic IP address

I've sent a request to COE IT to get the elastic IP address limit raised, for the us-east-1 region.

[saramsey]

Request to raise the quota has been logged via the AWS CLI:

following these instructions from AWS: https://repost.aws/knowledge-center/request-service-quota-increase-cli

[saramsey]

I anticipate we should have a response from AWS within a day or so.

[saramsey]

OK, we got our quota raised:

[saramsey]

I can now ssh into cicd2.rtx.ai in us-east-1:

[saramsey]

OK, I believe I have set up the new CI/CD server in us-east-1 with hostname cicd.rtx.ai (the old CI/CD server in us-west-2 has been stopped, and its hostname is now cicd-old.rtx.ai). I ran /home/ubuntu/actions-runner/run.sh inside a screen session on that instance, as user ubuntu . It seems happy?

(base) ubuntu@ip-172-31-42-117:~/actions-runner$ ./run.sh

√ Connected to GitHub

Current runner version: '2.320.0'
2024-10-22 20:09:53Z: Listening for Jobs

[saramsey]

Running a manually triggered Test Build now on the new cicd.rtx.ai...

[saramsey]

Test Build completed successfully. Closing this issue.

[saramsey]

The cicd-old.rtx.ai instance in us-west-2 has been terminated.