Please deploy the following VM: Hostname: webqa-ci-staging1 FQDN: webqa-ci-staging1.qa.scl3.mozilla.com Specification: RHEL 6, 16GB RAM, 4 cores, 250G HDD We'd like to have a staging instance of webqa-ci1 (bug 1110213) for us to test jobs and updates to plugins/Jenkins. The following should have sudo access: * Stephen Donner * Bob Silverberg * Dave Hunt Unlike webqa-ci1 there is no intention of making this instance publicly accessible. Users will need to connect to the VPN to access it.
Alright, that VM is created, initial puppetization done, node definition added to misc.pp in r103174 to give Donner, Silverberg and Hunt access. Do you want any nagios monitoring? (being a staging box, I wasn't certain.)
Assignee: server-ops-virtualization → cknowles
(In reply to Chris Knowles [:cknowles] from comment #1) > Alright, that VM is created, initial puppetization done, node definition > added to misc.pp in r103174 to give Donner, Silverberg and Hunt access. Thanks Chris. > Do you want any nagios monitoring? (being a staging box, I wasn't certain.) I wasn't sure either. It might be a good idea. Is there a cost to having monitoring?
There is no cost, but since it pages people if there's a problem, there needs to be available documentation on what to do if it's down. If there's nothing you need from the MOC on alerts, then there's really no use to having it alert.
Let's go ahead and set up basic nagios monitoring with alerts configured as they have been for webqa-ci1. Is there anything else you need from me Chris?
monitoring added in r103294 - should take effect shortly. And no, that answers everything outstanding from my end, thanks! Let me know if there's other needs with this deployment.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.