Skip to content
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

ansible: update Joyent hosted IP addresses #2568

Merged
merged 3 commits into from
Mar 22, 2021

Conversation

richardlau
Copy link
Member

@richardlau richardlau commented Mar 12, 2021

Refs: #2552

cc @mhdawson @jbergstroem

Some oddities:

@jbergstroem
Copy link
Member

infra-joyent-debian10-x64-1/grafana (from the table) doesn't appear to match anything in the inventory.

It was never added to inventory; perhaps add it as part of the list?

@richardlau
Copy link
Member Author

infra-joyent-debian10-x64-1/grafana (from the table) doesn't appear to match anything in the inventory.

It was never added to inventory; perhaps add it as part of the list?

done.

@mhdawson
Copy link
Member

In terms of test-joyent-ubuntu1604_arm_cross-x64-1 and release-joyent-ubuntu1604_arm_cross-x64-1 I noticed that after the fact. I think we should just confirm with @rvagg and then spin those down.

For test-joyent-ubuntu1804_docker-x64-1 we may have missed that since the machine do not show up in the CI (instead the container ones do. Luckily we have a number of equivalent machines so nothing is blocked but we might have lower capacity than we want for the docker based testing. At this point I think we should look to add an additional docker host on one of the other infra's versus trying to bring that one back.

Copy link
Member

@mhdawson mhdawson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

This host was not migrated with the recent Joyent datacenter closure.
@richardlau
Copy link
Member Author

I've removed test-joyent-ubuntu1804_docker-x64-1 from the inventory -- the old host is gone and we don't currently have a new one. I'll open a separate issue(s) to track removing the associated containers from Jenkins (we still have the equivalents at SoftLayer and DigitalOcean) and whether we want to replace it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants