Move build, test and staging to HKG

[darkk]

That's at least following VMs that are used in non-interactive way, so I see no reason for them to be in AMS:

• debuilder.infra.ooni.io
• ubuilder.infra.ooni.io
• staging.measurements.ooni.io
• ooni-probe-demo / demo.probe.ooni.io (do we need both?)
• ooni-fdroid-build (BTW, does it need 6G ram?)

Following VMs test raise the question: is it some daily test procedure or just an single-shot on-demand vm that was not deleted?

• oonibackend-stress-test
• apk-build-test
• test-qemu
• ooni-backend-testing
• ooniprobe-test

[hellais]

I added some notes in the comment section on eclipsis to signal which VMs I own can be deleted. Some were machines setup during the collaboration with the designer, that I forgot to delete after they were no longer needed.

[hellais]

The ones that I have not setup and am not sure about their specs or their exact purpose are:

• ooni-fdroid-build

• apk-build-test
  (are these two not the same thing?)

• test-qemu

I believe @anadahz set those ones up, so maybe he can answer.

[anadahz]

I added some notes in the comments section on eclipsis for the VMs that I created/own.
@bassosimone may have more info about the VM ooni-fdroid-build.

Deleted the following VMs:

• apk-build-test
• ooniprobe-test

[darkk]

I stopped several VMs as @hellais marked them as "maybe discontinue" on 2017-04-25

• ooni-proxy-dc.infra.ooni.io
• ooni-backend-testing.infra.ooni.io
• oonibackend-stress-test.infra.ooni.io
• ooni-probe-demo.infra.ooni.io
• lepidopter-update-test.infra.ooni.io
• ooniprobe-app.infra.ooni.io

Ping me ASAP if any of the FQDNs sounds like a useful asset to you. 9Gb of RAM freed in various locations.

[darkk]

debuilder.infra.ooni.io

Bites the dust. #135

[darkk]

@irl FYI, I'm also stopping ubuilder.infra.ooni.io as there were no activity at that host since ~2017-04-24. It seems to me, the VM is taking resources for no reason at the DC that has no spare resources :)
I assume that you may be interested as your key was there.
If the host is useful and build process can't be replaced with travis, the host should be re-deployed at HKG.

[darkk]

FTR, @bassosimone @hellais and @anadahz claim to have no access to following hosts, I assume they may be safely stopped and dropped after grace period:

• ooni-fdroid-build.infra.ooni.io
• vpn-gate-runner.infra.ooni.io

[darkk]

vpn-gate-runner and ooni-fdroid-build are gone.

[bassosimone]

@darkk the reaper :-)

[hellais]

@darkk where they on AMS or WDC? If there are hosts on these to DC we should not delete them, but rather lock the resources for services that are waiting for resources there.

[darkk]

where they on AMS or WDC

HKG and WDC.

but rather lock the resources for services that are waiting for resources there

What a tragedy, I've already removed them.

[hellais]

What a tragedy, I've already removed them.

heh, no big deal, WDC is not that important, but let's be careful for the precious AMS 😛

[darkk]

That round is kinda done. Next one is #175