Closed Bug 945762 Opened 11 years ago Closed 11 years ago

please give the vpn_sheriff group access to slaveapi prod & dev instances

Categories

(Infrastructure & Operations :: Infrastructure: OpenVPN, task)

x86_64
Linux
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: jabba)

Details

We'd like them to be able to access all current functionality. We may implement some ACLs within slaveapi in the future if we need finer grained access, or maybe something else. For now though, it would be really helpful for them to be able to reboot or shutdown buildslave processes.

Sheriffs, I'll give you a quick run through once this is done - there's still a couple of caveats.
Please add access to slaveapi{-dev,}1.srv.releng.scl3.mozilla.com for the vpn_sheriff group.
Assignee: relops → infra
Component: RelOps → Infrastructure: OpenVPN
QA Contact: arich → jdow
Summary: please give sheriffs access to slaveapi prod & dev instances → please give the vpn_sheriff group access to slaveapi prod & dev instances
Can you give me a list of all IPs that are needed?
dmitchell@admin1a ~ $ for f in slaveapi{-dev,}1.srv.releng.scl3.mozilla.com; do host $f; done
slaveapi-dev1.srv.releng.scl3.mozilla.com has address 10.26.48.17
slaveapi1.srv.releng.scl3.mozilla.com has address 10.26.48.16
oh! sorry, I didn't realize that you were already clarifying that in comment 1. Thought there were some other machines plus those in comment 1. Sorry!

This is done now, I added those two IPs.
Assignee: infra → jdow
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
No worries.  Explicit is better than implicit (c.f. Zen of Python)
You need to log in before you can comment on or make changes to this bug.