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

Do we need to replace test-joyent-ubuntu1804_docker-x64-1? #2573

Closed
richardlau opened this issue Mar 15, 2021 · 7 comments
Closed

Do we need to replace test-joyent-ubuntu1804_docker-x64-1? #2573

richardlau opened this issue Mar 15, 2021 · 7 comments

Comments

@richardlau
Copy link
Member

test-joyent-ubuntu1804_docker-x64-1 was not migrated during the recent Joyent datacenter closure (#2552) and we do not have a replacement. We still have the equivalent containers hosted on Digital Ocean and IBM (SoftLayer) -- do we feel that is adequate or should we look at adding another set of containers to replace the ones that used to be hosted by Joyent?

@rvagg
Copy link
Member

rvagg commented Mar 16, 2021

I don't think it's adequate and there will likely be bottlenecks with this - possibly OOMs from too many jobs on a single host and disks filling up from all the jenkins workspaces needed for parallel work. We could wait and see what happens, but we expanded to 3 to avoid these problems previously.

@mhdawson
Copy link
Member

I'd agree it would be good to find another host. @rvagg do you know how big a machine we need off hand ?

@rvagg
Copy link
Member

rvagg commented Mar 31, 2021

No, but it can scale and we could add a bunch of smaller machines to make up the deficiency if that were easier (I'm not sure that is any easier!). We define how many of these containers are built and started in the inventory (the one in secrets IIRC). So we have had smaller ones and larger ones, I don't recall if we equalised recently, but we did have to give some slack to the softlayer host a while back because it had a slightly different CPU/memory profile than the others and struggled, so that just meant taking out one or two clones.

@richardlau
Copy link
Member Author

At the moment we're equalized at 5 containers on each host, including the softlayer host.

@github-actions
Copy link

This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.

@github-actions github-actions bot added the stale label Jan 26, 2022
@mmarchini
Copy link
Contributor

has this been an issue in the past 10 months? If not we might be fine having those containers on only two locations

@github-actions github-actions bot removed the stale label Jan 27, 2022
@github-actions
Copy link

This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.

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

No branches or pull requests

4 participants