Created attachment 636322 [details] b2gbld pubkey This account should be like the existing 'ffxbld' account, but have its own primary group. We'll want to change the ownership on /pub/mozilla.org/b2g later, but please don't do that just yet - I need to deploy the keys first. I've attached the public one.
Created attachment 636323 [details] b2gtry key Looks like we need a separate account for try builds too.
Summary: please create a 'b2gbld' account on ftp/stage/upload1 → please create 'b2gbld' and 'b2gtry' accounts on ftp/stage/upload1
Assignee: server-ops → server-ops-infra
Component: Server Operations → Server Operations: Infrastructure
QA Contact: phong → jdow
A "b2gbld" user already exists in LDAP with this key: ...FgqiOEY6qXwTaD0speC1Fc8D34qV+0ETfrw8QDZ3ajkNHaIIphQ== email@example.com The user exists on upload1, but not realized on the ftp nodes. Can use the same user and add this second key? Or what's the deal with this existing user?
"b2gtry" user and group has been created on upload1.dmz.scl3, with the attached ssh key. Looking at ftp* nodes, 'ffxbld' doesn't exist there, so this doesn't need to happen. Waiting a reply for my questions in comment 2.
OK, hang on. That must be used by ateam for the builds they're doing. I need to coordinate with them to figure out what to do here.
Ok, we're going to share the account with ateam. Please add the attached 'b2gbld pubkey' to b2gbld's authorized_keys file. Also, please add ffxbld's public key to this file; we need this in order to transition over to using this account properly.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Component: Server Operations: Infrastructure → Infrastructure: Other
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.