Assign to deputy.

I can't ssh to any of these devservers, are they set up?

Also, if they are production server, why name the last one -test?

I have no idea which devservers these are or control over them. All I did was add them to the shadow config as requested.

Reassigning to request originator.

These are back online with their respective IPs. They can now be accessed. Is there anything further that needs to be done to add them to production?

@dshi, the test devserver will be used for testing VMs with multiple vCPUs.

What's the status on these? Are they live? Shall we mark this fixed?

Not yet, let me whip up a cl to add these devservers.

https://chrome-internal-review.googlesource.com/#/c/295915/

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/chromeos-admin/+/340fcf5f1e84672fcfda87578cc058f8bb9ff9b9

commit 340fcf5f1e84672fcfda87578cc058f8bb9ff9b9
Author: Kevin Cheng <kevcheng@chromium.org>
Date: Wed Oct 12 17:08:27 2016

Sorry, to follow the same naming convention, let's go ahead and change the name of:

100.115.99.236 - chromeos9-infra-devserver-test

TO:

100.115.99.236 - chromeos9-infra-devserver6

Any updates on this?

*friendly ping*

https://chrome-internal-review.googlesource.com/297683