JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for TB-SUPPORT Archives


TB-SUPPORT Archives

TB-SUPPORT Archives


TB-SUPPORT@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

TB-SUPPORT Home

TB-SUPPORT Home

TB-SUPPORT  November 2015

TB-SUPPORT November 2015

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Pilot accounts for everyone

From:

Ewan MacMahon <[log in to unmask]>

Reply-To:

Testbed Support for GridPP member institutes <[log in to unmask]>

Date:

Tue, 10 Nov 2015 16:19:02 +0000

Content-Type:

multipart/mixed

Parts/Attachments:

Parts/Attachments

text/plain (56 lines) , argus_policy_file1 (56 lines) , groups.conf (56 lines) , users.conf (56 lines)


Hi all.

I thought I'd follow up this morning's discussion about enabling pilot accounts for all VOs with some possibly helpful examples from the Oxford site. Everyone's existing config is almost certainly different already, so you might not want to use our pool account names, and you almost certainly don't want to use our numeric uid and gids, so this is very much a source of inspiration, not a set of configs to just use. And when I say 'inspiration', I mainly mean 'illustration of just how tediously straightforward this is'.

The key principles to bear in mind are that:

- You can forget about storage entirely; pilots are a purely CPU side thing.
- So that means dealing with CEs, batch servers, worker nodes, ARGUS server.
- You already have pilot accounts for the LHC VOs, so all you really need to do is copy the relevant bits for them and change the names.
- It's good to make this a one time thing if you can, so now is also a good time to review your supported VO list, add some new ones like cernatschool.org, hyperk.org and lsst, and drop any old and dead ones like Hone, Dzero, CDF and superB, which might also free up some account IDs.

Below is a more detailed memoir of what I did on our systems and suggestions based on it, but really, if you start from the principle that you already have pilot enabled VOs and then just copy anything that says 'pilot' for all the other VOs, you're basically there.

Ewan


----------------------------------


So, for our change I started with a test worker node and deleted the old VOs, and re-YAIMed it, then manually removed all the old accounts from /etc/passwd, /etc/group, their shadows, and their home directories, then re-YAIMed it again to make sure nothing came back from the dead.

For each VO I added a set of pilot pool accounts (we've got twenty each) with unique UIDs, and memberships in the VO pilot group, and the main VO group (I'm not completely sure how important this is now, but given that the principle was always to copy from what we had and not overthink it, that's what I did). SO, for example, a cernatschool pilot account entry in users.conf looks like this:

36200:cernschpilot000:3650,3600:cernschpilot,cernatschool:cernatschool.org:pilot:

which breaks down as:

uid : accountname : primary gid,secondary gid : primary group,secondary group : VO name : flag to make pilot roles map to this

and as opposed to a normal pool account looking like this:
 
36003:cernsch001:3600:cernatschool:cernatschool.org::

In practice I did this by copying an existing chunk of config, selecting it in vim, and doing simple regex substitutions to change the names. It's a bit of a faff, but once it's done, it's done.

Then the corresponding bits in groups.conf should look like this:

"/cernatschool.org/ROLE=pilot":::pilot:
"/cernatschool.org/ROLE=lcgadmin":::sgm:
"/cernatschool.org/ROLE=production":::prd:
"/cernatschool.org"::::

of which the top line is new and handles the mapping of proxies with the pilot role to the 'pilot' flagged accounts. Then it can be YAIMed again, and after a couple of rounds of it pointing out that you've left the VO out of the 'VOS' variable in the main site-info.def, and then out of the vo.d directory, it'll all work and you'll have a load of new pilot accounts on the worker node. Rinse/repeat/puppet for the rest of the worker nodes. There is some glExec config that needs updating, but if you're using YAIM it does it for you. 

Next up, ARGUS server. I'm moderately confident it doesn't need YAIMing for this, but I think I maybe did it anyway. Don't forget to put the central banning config back in if it nukes it, there will be a test later. The main bit is the policy, which you should have a copy of in a file somewhere. For each section that you need (any/all of the worker node (i.e. glExec) section, an ARC section and a Cream CE section), just make sure that all the VOs are included. Our policy file is attached, but really, this is just a matter of cut/paste/search-and-replace-the-VO-name. Then remove all the policy by doing 'pap-admin rap', and apply the policy from the file with 'pap-admin apf name_of_file'.

At the time I did this we didn't have any Cream CEs or any torque left, but it would probably be a matter YAIMing them to create the pool accounts, and making sure that the new VOs have permissions to submit to the queues.

For our condor batch system and ARC CEs the pool accounts were created by manually copying the relevant chunks of /etc/passwd, /etc/group and their shadows from one of the YAIMed worker nodes, and then creating the home directories. If you've done the obviously sensible thing that we never have and put all your pool accounts into something like NIS or LDAP you can obviously skip this step in favour of feeling smugly well organised and farsighted.

Finally the arc.conf also has a list of authorized VOs that might need updating if you've added whole new ones, but not if you've just added the pilot support to existing VOs.

Then, once you're done, poke Daniela to test it.

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager