1286671 - Please deploy 1 VM (webqa-docker1) for Web QA

Status: RESOLVED FIXED

(Infrastructure & Operations :: Virtualization, task)

Description

[Stephen Donner [:stephend] Not actively reading bugmail]

If you would, please deploy the following VM:

Hostname: webqa-docker1
FQDN: webqa-docker1.qa.scl3.mozilla.com
Specifications: CentOS-7, 8GB RAM, 2 cores, 80GB (or so) HDD

(This is a working prototype of what I've stood up on my own in Digital Ocean, with very similar specs, based on https://blog.mozilla.org/webqa/2016/06/28/dockerized-owasp-zap-security-scanning-in-jenkins-part-two/ and which I hope and expect will see much more use, internally.)

The following should have sudo access:
* Stephen Donner
* Dave Hunt
* Simon Bennetts

For now (and likely the foreseeable future), there are no plans of making this instance publicly accessible.  It -- much like https://mana.mozilla.org/wiki/display/QA/webqa-ci-staging1.qa.scl3.mozilla.com -- will remain behind VPN.

Backups won't be necessary at this stage, but a snapshot of "just got it out of the virtualization team's hands" state would be greatly appreciated, as I'll be installing and configuring Docker (daemon w/SELinux), Jenkins 2.x, and a few needed plugins.

Comment 1

[Stephen Donner [:stephend] Not actively reading bugmail]

(P.S., in case it matters/helps, I've spoken to :adamm and :claudijd this morning, and they're fine with it, and we'll get an RRA going once it's up and configured more fully: https://wiki.mozilla.org/Security/Risk_management/Rapid_Risk_Assessment.)

Comment 2

[Greg Cox [:gcox]]

VM created, puppetized, and snapshotted.  Because of the VPN piece I'd like to say it's an unreliable snapshot that I should redo before handing over (i.e. I think I made a hash of the puppet node definition by guessing).

TODO: wait on VPN, clean puppet node definition in misc.pp to match, run puppet, take another cold snapshot.

Comment 3

[Greg Cox [:gcox]]

todo-steps done.  I think this is ready to go.  Yell if there are issues.