[Gluster-infra] Deciding on how we access servers

[Michael Scherer]

Hi,

so I was adding a formula to deploy ssh keys to the root account on our
servers, and wondered what kind of policy we want in term of access. 

before deciding, we need to have a clear list of what we have. 

Then, a list of who access them and why, then from here get some generic
groups, and then decide how much we want, with what kind of audit or
protection against various threat ( ie, 2 FA or not, what sudo policy,
etc, etc ).

So before anyone start to propose any policy, we need first a list. 

Justin started that on
https://www.gluster.org/community/documentation/index.php/Jenkins_Infrastructure

Out of the current list, theses are the non documented ones :

backups.cloud.gluster.org
bulk15
bulk5
bulk8
download.gluster.org
gluster-sonar
gluster-swift2
nbslave70.cloud.gluster.org
nbslave71.cloud.gluster.org
nbslave72.cloud.gluster.org
nbslave73.cloud.gluster.org
nbslave74.cloud.gluster.org
nbslave75.cloud.gluster.org
nbslave76.cloud.gluster.org
nbslave77.cloud.gluster.org
nbslave78.cloud.gluster.org

I already posted to say that some of theses are running older EOL fedora
version, i didn't checked again. 

Could people comment and add them to the wiki page ?


-- 
Michael Scherer
Open Source and Standards, Sysadmin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://www.gluster.org/pipermail/gluster-infra/attachments/20150305/e5c7c8ea/attachment.sig>