Closed Bug 1265758 Opened 4 years ago Closed 4 years ago

Add acccess to the following accounts to dev-master2 and aws-manager

Categories

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

task
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: vciobancai, Assigned: vciobancai)

Details

Attachments

(3 files, 1 obsolete file)

The followings accounts: ashiue, gchang, and ihsiao needs access to dev-master2
Attached patch bug1265758_moco-nodes.pp (obsolete) — Splinter Review
Attachment #8742901 - Flags: review?(arich)
Assignee: relops → vlad.ciobancai
Attachment #8742901 - Attachment is patch: true
Attachment #8742901 - Attachment mime type: text/x-patch → text/plain
They shouldn't need root or cltbld access to start. User accounts on dev-master2 should be enough to get staging masters setup. 

Other access they'll need:
* slavealloc: *should* be gated by releng_vpn access
* database: for adding masters to db, can be granted via our private repo
Comment on attachment 8742901 [details] [diff] [review]
bug1265758_moco-nodes.pp

Review of attachment 8742901 [details] [diff] [review]:
-----------------------------------------------------------------

Given comment 2, I think we just want the realize of the user accounts.
Attachment #8742901 - Flags: review?(arich) → review-
Updated the patch
Attachment #8742901 - Attachment is obsolete: true
Attachment #8743142 - Flags: review?(arich)
Attachment #8743142 - Flags: review?(arich) → review+
Attachment #8743142 - Flags: checked-in+
I land the change in to the default branch, Amy can you please merge from default to production because we do not have access?
The change has been laded by Kim in to the production
I checked the dev-master2 and the following accounts ashiue, gchang, and ihsiao have been created
Summary: Add acccess to the following accounts to dev-master2 → Add acccess to the following accounts to dev-master2 and aws-manager
As discussed at the buildduty meeting today, we should also grant access to aws-manager to avoid another unnecessary round of access delays. We *know* they're going to need this access.
Attachment #8743387 - Flags: review?(kmoir)
Attachment #8743387 - Flags: review?(kmoir) → review+
https://hg.mozilla.org/build/puppet/rev/0cfc2dbe2f0b31ec41d049508e491b13954687bc
Bug 1265758 - grant access to aws-manager for ashiue, gchang, and ihsiao - r=kmoir
(In reply to Chris Cooper [:coop] from comment #9)
> https://hg.mozilla.org/build/puppet/rev/
> 0cfc2dbe2f0b31ec41d049508e491b13954687bc
> Bug 1265758 - grant access to aws-manager for ashiue, gchang, and ihsiao -
> r=kmoir

Hi Chris,

Thanks, now we can login to dev-master2 and aws-manager2, however, we don't have permission to create dir under /builds/buildbot/ on dev-master2 and switch to buildduty on aws-manager2.

Do we miss anything?
Flags: needinfo?(coop)
On dev-master2 in the following path /builds/buildbot/ I created directories for your account's and I setup the permissions to be used 

[root@dev-master2.bb.releng.use1.mozilla.com buildbot]# ls -lth /builds/buildbot/
total 88K
drwxr-xr-x  2 ihsiao         ihsiao         4.0K Apr 21 01:23 ihsiao
drwxr-xr-x  2 gchang         gchang         4.0K Apr 21 01:22 gchang
drwxr-xr-x  2 ashiue         ashiue         4.0K Apr 21 01:22 ashiue
Attached you can find the patch that update buildduty account by adding custom users for access.

I tested the change on puppetserver 02 and worked
Attachment #8743716 - Flags: review?(kmoir)
Attachment #8743716 - Flags: review?(kmoir) → review+
Attachment #8743716 - Flags: checked-in+
Can somebody push the change from default to production for puppet repository ?
merged
Now the team have access on aws-manager via buildduty user
Flags: needinfo?(coop)
The team received access to dev-master2 and aws-manager2
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.