BEgridPreparations

From Begrid Wiki
Revision as of 09:12, 9 June 2021 by Maintenance script (talk | contribs) (Created page with " == What is needed to join BEgrid == Site Administrators have to provide the Centralised BEgrid managers a list of configuration details prior to the setup. This allows new...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

What is needed to join BEgrid

Site Administrators have to provide the Centralised BEgrid managers a list of configuration details prior to the setup. This allows new people to step in at a fair low level of required knowledge. This initial default setup will be provided as a black box. As the administrators become more familiar with Quattor, Grid middleware or cluster management, they can use this default configuration for further customisations.

Default layout of BEgrid site

For any new site or any normal site, the default setup should be fine. As the site grows or requirements change, administrators can change the layout to improve the results.

The default site configuration consists of:

  • One cluster split in a glite 3.0 part and a glite 3.1 part, and one shared site entry.
  • The workernodes are behind a NAT
    • They will have their own subnet called wn; the IP range of the subnet will be 192.168.0.0/255.255.0.0
    • The workernodes will use as FQDN nodeX-Y.wn.public_domainname.be with corresponding IP address 192.168.X.Y

Required hardware to get started

  • Overhead: machine for at least a NAT and BC (we advice to use the same one)
    • The insatllation forsees a method using virtualisation for this, so in principle also other machines can be added (eg a MON box). Ofcourse this machine needs enough memory and diskspace for this.
  • Minimal grid setup: 1 CE + 1 WN
  • Make sure all machines can pxeboot the SL3/4 kernels.
    • If not, contact the begrid-tech mailing list for additional help.
  • The BEgrid Client needs some diskspace for caching (at least 30GB).
  • Local admin installation tool: we advise eclipse on desktop.
  • The CE will act as a NFS server for the WNs for MPI jobs. Normal jobs will run on the WNs local disk.

Required information to collect

Please send these informations to bulanzaATNOSPAMhelios.iihe.ac.be

  • Administrator(s) certificate DN for subversion access
  • Administrator(s) must be registered in betest for wiki write access and code browsing.
  • Network configuration planned to be used:
    • Total number of available public IP addresses (if lower than 4)
    • Public:
      • IP range
      • default gateway
      • domain name
      • DNS server
      • NTP server (default: BELNET NTP server)
    • Private: default IP range is 192.168.0.0/255.255.0.0
      • DNS server (default: private interface of BEgrid client)
      • gateway (this should be the private interface of your NAT)
    • For each machine:
      • Hostnames/IP adress
      • role (workernodes should have a generic name. We propose nodeX-Y.wn.<public_domainname> corresponding to IP 192.168.X.Y . We also advise that people use a new 192.168.X.0 subnet for each different hardware type.)
  • Physical description of a few boxes (the admins will have to complete all remaining machines)
      • MAC adresses, linux naming (ie eth0, eth1), linux driver name
      • CPU description (type, SMP or not, x64_86 capable)
      • disk type (as seen under linux (eg hda or sda) and amount of diskspace
      • amount of memory
  • Filesystem layout (if you have special needs, which can be important for storage boxes)
    • Defaults:
        • WN: / (10GB), /var (5GB), /scratch (on the rest), swap (on 2*RAM_SIZE)
        • non-WN: / (10GB), /var (on the rest), swap (on 1*RAM_SIZE) (storage on separate partition)
  • Quattor
    • Name and IP address of Begrid client
      • Also the private address
    • Sindes will be used by default.
  • GRID

Required open ports

Use this list ? http://glite.cvs.cern.ch/cgi-bin/glite.cgi/org.glite.site-info.ports/doc/middleware-ports.txt?view=markup

In case you are using a NAT or firewall the following incomming ports are needed: (This list needs double checking from someone else)

  • Computing Element
    • EDG: TCP port 2119
    • GJM: TCP ports 20000->25000
    • Grid FTP: TCP port 2811
    • Logger: TCP port 9002
    • MDS: TCP port 2135
    • Mercury Monitor: TCP port 3570
    • BDDI: UDP and TCP port 2170
    • Synchronous CE Mon: 8443
  • WN
    • None (from the internet)
  • RB
    • LandB_PORTS: TCP port 9000 and 9001
    • Locallogger: TCP port 9002
    • Grid FTP: TCP port 2811
    • GJM: TCP port 20000->25000
    • GRAM: TCP port 7772
    • CondorG: TCP port 7771
  • SE
    • HTTP: TCP port 80
    • GRID_FTP: TCP port 2811
    • MDS: TCP port 2135
    • RFIO: TCP port 3147
    • SE Apache: TCP port 6375
    • SE (tomcat): TCP port 8080 and 8443
    • GJM: TCP port 20000->25000
  • BEgridClient
    • None
  • UI
    • SSH (standard port 22, but can be any)


Back to BEgrid_And_Quattor page


Template:TracNotice