Full name: Brian Wolff
Labs username/wikitech username: Brian_Wolff
Preferred shell username: bawolff
SSH Public key:
Reason: Security patch deployment
Description
Description
Reason: Security patch deployment
Details
Details
Related Changes in Gerrit:
Related Objects
Related Objects
- Mentioned In
- rOPUP2f9d8e8144ba: admin: add bawolff to deployers group
rOPUP42a1d0dc3fa6: admin: add bawolff to deployers group
rOPUP7713ee1ed217: admin: create shell user for bawolff
rOPUP9d9d4564f5cd: admin: create shell user for bawolff
rOPUPe7eb41986b40: admin: add bawolff to deployers group
rOPUP75d7a78cad6a: admin: create shell user for bawolff
Event Timeline
Comment Actions
@Bawolff Please update the description with the information requested at https://wikitech.wikimedia.org/wiki/Requesting_shell_access, and after you have signed L3 (which I think you already have).
Comment Actions
To deploy security patches he should get full access given by deployment rights, which includes all mw* servers etc.
Comment Actions
@Krenair, thanks. I was just about to update the ticket specifying just that.
For future reference, that is essentially what is meant by the second bullet point at https://wikitech.wikimedia.org/wiki/How_to_deploy_code#Deployment_requirements, correct?
Comment Actions
"deployment access" means the ability to actually use the deployment commands on tin/mira to sync MW code (not just the ability to log in to those hosts), as well as the ability run stuff as MW on terbium and the app servers, and restart apache, HHVM, etc.
Comment Actions
@Bawolff Please read and sign L3 and attach a (new) SSH public key to this ticket. Thank you!
Comment Actions
Change 297456 had a related patch set uploaded (by Dzahn):
admin: create shell user for bawolff
Comment Actions
Change 297457 had a related patch set uploaded (by Dzahn):
admin: add bawolff to deployers group
Comment Actions
Approved by Release-Engineering-Team for MW deploy access. Just needs ops review since it's sudo :)
Comment Actions
FYI, we didn't have an ops meeting on Monday, this will be discussed on next weeks's meeting.
Comment Actions
on bast1001:
Notice: /Stage[main]/Admin/Admin::Hashuser[bawolff]/Admin::User[bawolff]/User[bawolff]/ensure: created
Notice: /Stage[main]/Admin/Admin::Hashuser[bawolff]/Admin::User[bawolff]/File[/home/bawolff]/ensure: created
on tin.eqiad.wmnet:
Notice: /Stage[main]/Admin/Admin::Hashuser[bawolff]/Admin::User[bawolff]/File[/home/bawolff]/ensure: created
on mira.codfw.wmnet:
Notice: /Stage[main]/Admin/Admin::Hashuser[bawolff]/Admin::User[bawolff]/Ssh::Userkey[bawolff]/File[/etc/ssh/userkeys/bawolff]/ensure: created
@Bawolff See above ^, your user (and key) has been created on bast1001 (and when puppet runs will also be on bast2001, bast3001 and bast4001). as well as on the deployment servers tin.eqiad.wmnet and mira.codfw.wmnet.
you can use any of the 4 bastions, probably you want the one closest to you (https://wikitech.wikimedia.org/wiki/Bastion)
please see this link https://wikitech.wikimedia.org/wiki/SSH_access for a config example to get your SSH client to connect via one of the bastion hosts to the deployment servers.
If any issues please let us know on IRC or simply reopen this ticket.
Comment Actions
Mentioned in SAL [2016-07-11T18:08:29Z] <mutante> welcome new mediawiki deployer Brian Wolff (T138635)
Comment Actions
P.S.Yes, and the maintenance script hosts are included too. i checked your user exists there now.
in eqiad, terbium.eqiad.wmnet
in codfw, wasat.codfw.wmnet