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  June 2005

TB-SUPPORT June 2005

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: farm admin software

From:

Alex Martin <[log in to unmask]>

Reply-To:

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

Date:

Wed, 22 Jun 2005 15:39:34 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (123 lines)

Our solution has many similar features:

1)  We keep kickstart files and set of configuration scripts in a subversion 
     repository.   The configuration scripts are intended to be run both 
     during installation and hourly (staggered across all nodes!) from a cron 
     job and hopefullly always leave the node in the same state for a 
     given tagged release.     

2)  We keep hardware info, network info  and the required/installed s/w
     release info in a mysql database.   This infomation is used to decide
     which versions of files and also which hardware/network dependent
     settings are presented to a client node.   (This is achieve via apache 
     and the perl Mason package)

3)   We maintain our own  RPM repositories  and  test any major changes
      before propagation via yum.


In practical terms if we need to make a minor change,  we can simply tag the 
new release,  test it on one node,  and if one is happy, set this to be the 
required version on all nodes,  then sit back and wait for an hour.    
Major changes are achieved in a similar way,  but via reinstallation.



The current deficiencies are:


1)  The system isn't synced with the pbs...at the moment if we need to do a
     major upgrade we pick a time when there is only a few jobs running,
     reinstall idle nodes  and mark busy nodes as unavailable (then go back 
     and fix them later).  I think this can be automated.

2)  The RPM repository (or prehaps just their headers)  should also really 
     be keep in the subversion repostory.  
    

3)  The Grid s/w is a bit of pain to integrate...but bit easier now with
     yaim...also its a pain to have to handle one-off machines (CE/SE/MON
     nodes etc)...also I never really worked out how integration configuation 
     scripts for the machine that does the configuations!
          




On Wednesday 22 June 2005 12:32, David McBride wrote:
> Hi,
>
> On the large end-user (500node+) desktop systems I've looked after we
> developede two seperate sets of tools:
>
>  * a set of maintenance scripts that get executed on system boot and
> periodically via cron
>  * a remote control tool for immediate ad-hoc changes to sets of
> machines.
>
> The maintenance scripts are responsible from taking a box which has (at
> least) a minimal bootstrap image (ie a filesystem, init, glibc, perl,
> and other basics) and configuring it for use.  This includes package
> installation/upgrade, user account creation, kerberos configuration,
> service configuration etc.  Configuration data is stored in a central
> PostgreSQL database or on-disk files exported via NFS.
>
> The package manager tool used to use a locally developed solution, but
> was replaced with apt-rpm when it became available/stable.  We maintain
> a local package repository and add updates when we've tested them and
> are satisfied they work.
>
> The maint scripts, whilst also reponsible for most of the original
> installation, are also used to maintain the current state of
> already-installed machines -- checking that local passwd and group files
> are up-to-date, updating any packages available for installation, etc.
>
> The maint scripts can be as simple or as complicated as you like.
>
> Our remote control tool is also useful, but fills a different niche --
> its function is to execute any arbitrary command on any arbitrary subset
> of hosts quickly and securely via SSH.  User authentication is automated
> using Kerberos (even as root), but public/private keypairs should also
> work nicely.  My tool invokes commands across hosts in parallel, which
> is useful for large numbers of hosts.
>
> (The script I wrote to do this is available online under the GPL; see
> http://www.doc.ic.ac.uk/~dwm/Code/auto-checkout/remote--main/remote.pl)
>
> This tool is very useful when you need to make a single operational
> change quickly; for example, if:
>
> * The air-con's failed in the undergrad lab and you need to shutdown all
> the even-numbered machines to reduce the temperature. (`remote
> 'lab.*[02468]$'`)
> * There's an urgent security fix that needs to be rolled out, but the
> maint scripts won't fire until tomorrow. (`remote . maint --scr=apt`)
> * You want to find out where a user is physically sitting because
> they're late for an exam (`remote . "ps auxf > ~/tmp/`hostname`"`)
>
> In addition to all of this, they're also looking at live monitoring
> tools, watchdogs, that are responsible for continuous local environment
> checking.  Things like monitoring the CPU temperature, checking that NFS
> mounts are intact and valid, etc.  But this is just an idea in the works
> at the moment.
>
> I don't look after our current production farms, but I understand our
> admin uses similar ideas -- boot from network server by default,
> standard install scripts that setup/refresh the local environment,
> remote update of userlists/gridmapfiles via SSH, etc.
>
> Hope this helps..
>
> Cheers,
> David

-- 
------------------------------------------------------------------------------
|                                                                            |
|  Dr. Alex Martin                                                           |
|  e-Mail:   [log in to unmask]        Queen Mary, University of London,  |
|  Phone :   +44-(0)20-7882-5033          Mile End Road,                     |
|  Fax   :   +44-(0)20-8981-9465          London, UK   E1 4NS                |
|                                                                            |
------------------------------------------------------------------------------

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

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