Closed Bug 1455030 Opened 6 years ago Closed 6 years ago

please create a new linux signing server

Categories

(Infrastructure & Operations :: RelOps: General, task)

task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: bhearsum, Assigned: dhouse)

References

Details

I'm working on upgrading Python and Python dependencies over in bug 1450035 and I'm hopinig to use a new (read: not in production) Linux signing server to verify some of the work I've been doing. We can also put this machine in production afterwards, assuming we don't need the resources for something else. I'm proposing signing7.srv.releng.scl3.mozilla.com for the name, and it would be best for it to be configured exactly the same as the other Linux signing servers.
Hi Ben, Do you need for the new signing server to be in scl3, or can we add it to mdc1 or mdc2? Here is what we currently have: mdc1 signing7 10.49.48.29 signing8 10.49.48.35 signing9 10.49.48.42 mdc2 signing10 10.51.48.29 signing11 10.51.48.30 signing12 10.51.48.31 scl3 signing4 10.26.48.29 signing5 10.26.48.35 signing6 10.26.48.42 So I'd suggest naming it signing13.srv.releng.mdc1 [10.49.48.30] or, if it needs to be in scl3, "signing13.srv.releng.scl3" [10.26.48.30]
Flags: needinfo?(bhearsum)
(In reply to Dave House [:dhouse] from comment #1) > Hi Ben, > > Do you need for the new signing server to be in scl3, or can we add it to > mdc1 or mdc2? > > Here is what we currently have: > mdc1 > signing7 10.49.48.29 > signing8 10.49.48.35 > signing9 10.49.48.42 > > mdc2 > signing10 10.51.48.29 > signing11 10.51.48.30 > signing12 10.51.48.31 > > scl3 > signing4 10.26.48.29 > signing5 10.26.48.35 > signing6 10.26.48.42 > > So I'd suggest naming it signing13.srv.releng.mdc1 [10.49.48.30] or, if it > needs to be in scl3, "signing13.srv.releng.scl3" [10.26.48.30] I didn't realize we had mdc signing servers! I have no strong preference for datacenter or name - take your pick!
Flags: needinfo?(bhearsum)
Thx! I'll request a new vm to be created for signing13.srv.releng.mdc1 [10.49.48.30]
Depends on: 1455424
Ben, signing13.srv.releng.mdc1.mozilla.com is kickstarted and running: https://papertrailapp.com/systems/1799470591/events I need to update the firewall configurations next.
(In reply to Dave House [:dhouse] from comment #4) > Ben, signing13.srv.releng.mdc1.mozilla.com is kickstarted and running: > https://papertrailapp.com/systems/1799470591/events > > I need to update the firewall configurations next. I did not find any specific ip entries for signing servers in the puppet fw module (ip ranges that include this new ip are in there for the releng networks): https://hg.mozilla.org/build/puppet/file/tip/modules/fw/manifests/networks.pp I'll make a bug requesting the new signing13 be added to the network firewalls.
Hi Ben, This new signing server is ready for you to use. It was added into the firewall rules in bug 1456217 signing13.srv.releng.mdc1.mozilla.com [10.49.48.30]
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
(In reply to Dave House [:dhouse] from comment #6) > Hi Ben, > > This new signing server is ready for you to use. It was added into the > firewall rules in bug 1456217 > > signing13.srv.releng.mdc1.mozilla.com [10.49.48.30] I'm in - thank you!
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.