Greg/Chris, Please create a second discovery server, same configuration as the MOZDISCOVER1. Is it possible to get 30 min of resource time on the tail end of this build to help install a the java app on the box? Regards, Jason
Really light on details, so let's pull this all together: mozdiscover1.private.scl3 came from (currently unreadable) RITM0041033. Currently exists as 1 core, 4G, default disk. Stay with RHEL6 for consistency against prod. Per emails with Jas this is a dev box, and as such I'm going with a name to indicate that, so there's no collision in the prod naming identity later. mozdiscover-dev1.private.scl3 created. Added the same people to sudoers here as in prod, added to nagios. Closing this out. If your people need help with installing something, just set up a meeting and we'll go through it. But since it's their project I want to make sure they have the expertise in their product.
Assignee: server-ops-virtualization → gcox
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
Summary: Additional Discovery VM (MOZDISCOVER2) → Dev ServiceNow Discovery VM
Greg- thanks for jumping on this so fast. James- Does another bug needed to be opened for the FW rules or can we use this existing one? Thanks, Jason
You need to log in before you can comment on or make changes to this bug.