Closed Bug 565057 Opened 15 years ago Closed 15 years ago

Please set up some hostnames

Categories

(mozilla.org Graveyard :: Server Operations, task)

x86
macOS
task
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jhford, Assigned: jlaz)

Details

Please set up the following hostnames. Ideally, the same hostname will be available when plugged into the build network or the office wired (non-build) network. They don't need to have the same IP for both networks. mobile-image01 00:0F:FE:F7:B8:55 mobile-image02 00:0F:FE:FA:7A:E6
Assignee: server-ops → jlazaro
bumping up in priority as I am going to need to start sshing into these machines remotely
Severity: normal → critical
mobile-image01 given 10.250.50.176 mobile-image02 given 10.250.50.177 should be reachable to both networks mv.mozilla.com/build.mozilla.org let me know if this works
(In reply to comment #2) > mobile-image01 given 10.250.50.176 > mobile-image02 given 10.250.50.177 > > should be reachable to both networks mv.mozilla.com/build.mozilla.org > > let me know if this works It does not work. 10.250.50.NNN is build-vlan if i remember correctly. These machines are currently hooked up to the office network. I am guessing that we would need to have a DHCP address assigned to the machines in the office network as well as the build network. If we can't have mobile-image01.build.mozilla.org point to a different address than mobile-image01.mv.mozilla.com can we set up different hostnames for when they are on the build network? something like mobile-image01-bld.build.mozilla.org for when they are plugged into the build network would work. Alternatively, if setting up hostnames this way is too much of a hassle, can we just have static ips for each network? The reason I need them set up for both networks is that they might be in the RF room (build vlan) or at a desk in the office.
I think I've set it correctly this time.. mobile-image01 should resolve to 10.250.1.176 when connected to the mv/office network mobile-image02 should resolve to 10.250.1.177 when connected to the mv/office network mobile-image01 should resolve to 10.250.50.176 when connected to the build network mobile-image02 should resolve to 10.250.50.177 when connected to the build network will probably need to reboot these devices to pick up their new IPs -jlazaro
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.