1112637 - Create VM: selenium-hub1.qa.scl3.mozilla.com

Status: RESOLVED FIXED

(Infrastructure & Operations :: Virtualization, task)

Description

[Dave Hunt [:davehunt] [he/him] ⌚BST]

We currently have a VM in PHX that was set up to be a Selenium Grid hub instance, but it's never been used. We now have a Jenkins instance in SCL3 and have a need once more for a dedicated VM for Selenium Grid. Is it possible to simply move this VM?

The Selenium Grid hub will be running on port 4444, which will need to be reachable from webqa-ci1.qa.scl3.mozilla.com. It will also need to be able to communicate with the Selenium server nodes, which will be running on port 5555 on selenium[1-6].qa.scl3.mozilla.com and selenium-[3,4,5,7].qa.mtv2.mozilla.com. I will raise separate NetOps requests for these routes.

Comment 1

[Chris Knowles [:cknowles]]

If we're crossing datacenters, it's probably better to just delete the old VM and spin up the new VM.

This looks to be related to the creation bug 727353.

So, standard questions apply for this create (and if you're truly getting rid of the old, please file a bug at your convenience once you're ready to decom it)

Name: selenium-hub1.qa.scl3.mozilla.com
OS: RHEL6
Disk: ??
CPU: ??
RAM: ??

Sudoers access: ??

Let me know so we can move forward on this.

Comment 2

[Dave Hunt [:davehunt] [he/him] ⌚BST]

(In reply to Chris Knowles [:cknowles] from comment #1)
> If we're crossing datacenters, it's probably better to just delete the old VM and spin up the new VM.

Thanks Chris, that makes sense to me.

> Name: selenium-hub1.qa.scl3.mozilla.com
> OS: RHEL6
> Disk: ??
> CPU: ??
> RAM: ??

Let's go for the following, should be enough for a Selenium Grid hub instance:

Disk: 40GB
CPU: 2 cores
RAM: 4GB

> Sudoers access: ??

dhunt, stephend, bsilverberg

Comment 3

[Chris Knowles [:cknowles]]

Alright, I'll work on getting that spun up.

I'm still having trouble finding bsilverberg for VPN access.  I will inquire with some of our folks.

Comment 4

[Chris Knowles [:cknowles]]

Alright, that VM is up, and should be accessible, I'm still looking to chase down bsilverberg's access...

Comment 5

[Chris Knowles [:cknowles]]

Alright, discovered the concern.  Apparently bsilverberg wasn't a POSIX user, which prevented the normal systems from picking him up.  

This has been changed.  And his account has sudoers access.  

However, the account for bsilverberg doesn't have a public SSH key on record, so he can't log in.  

Bob, if you can go to https://login.mozilla.com/ and upload your public key, that should get you access.