DEMO: Fabric installation

1
DEMOFabric installation configuration tools

• Marco Serra Maite Barroso
• 29/10/2001

2
Image installation tool

• Boot server setup
• DHCP package
• TFTP package
• Etherboot package
• Kernel 2.2.x statically compiled
• YARD MKNBI packages (these provide the
  mechanism to construct out of the kernel a simple
  root filesystem and the needed Linux image to be
  loaded into the RAM of the new node)
• All this apckages are provided and auotomatically
  INSTALLED and CONFIGURED

3
Creation of images

• Choose reference machine testbed010
• Add repository to /root/.rhosts in reference
  machine
• Install configure rsh to work between server
  and reference machine
• Install configure anonymous ftp
• Execute /opt/image-install/config/configure
• Execute /opt/image-install/execs/creation/execute_
  image_production.exe ref_machine
• Produces image, create links, and copy programs
  config files to the repository 15min as a
  result a link to the image copy is created in the
  server /home/ftp/reference_machinename

4
Node installation

• Install and configure CCM (http//hep-proj-grid-fa
  bric-config.web.cern.ch/hep-proj-grid-fabric-confi
  g/documents/user-guide.html)
• Start needed daemons
• /opt/ccm/bin/ccmd debug 1
• /opt/image-install/execs/configuration_mgt/update-
  bs-config
• Modify configuration file /opt/image-install/confi
  g/boot-server1.xml adding host_name, MAC address,
  IP address, networkcard, ref_node
• Execute /opt/ccmd/bin/fetch config
  ///boot-server1.xml This config info is so
  moved to the CCM, who will execute the changes
  and the new machine installation will start at
  next reboot

5
LCFG server setup

• LCFG server setup, main steps
• Download and install LCFG server packages
• Set up and start DHCP
• Set up and start Web server
• Define UDP ports for LCFG services
• Start server (mkxprof) daemon.
• Create repository structure and populate it
  download needed RPMS (RH6.2 updates, IN2P3
  repository).
• Check/change RPMS configuration files

6
Repository structure configuration

• /opt/local/Linux/6.2/RPMS/
• LCFG
• Release (RH62)
• Updates (RH62 updates)
• Applications (CERNLIB)
• Globus
• Edgconfig
• Security (certificates)
• External
• /opt/local/Linux/6.2/rpmcfg/
• External.h, globus.h -gt list or rpms to be
  installed
• Client included the needed xxx.h files
• The client file is included in the
  /var/obj/conf/profile/source/client.h source file

7
LCFG client setup

• Changes to be done in the server to install a
  new client, testbed007
• Edit /etc/dhcpd.conf to add new machine info
• host testbed007
• hardware ethernet xxxxxxxxxxxx
• fixed-address testbed007.cern.ch
• option root-path "/ir62"
• option option-151 "http//lcfg_server_url"
  
• Restart dhcpd daemon
• Add client name on the file /var/obj/conf/profile/
  source/profile.clients
• Make an LCFG installation floppy, given a
  formatted 1.44 Mbyte diskette. Download the image
  boot_nfs_080301 and execute
• dd ifboot_nfs_080301 of/dev/fd0 bs5120
• Boot with floppy

8
Managing your configuration with LCFG (1)

• Use-case a service (example gdmp, ssh, ) with
  parameters in
• /etc/inetd.conf or /etc/services or
• It is easy to create a header file service.h
  which include all the configuration (port
  number/network protocol/scripts/) and insert
  this in the node profile on the LCFG server
• When there is a change in the configuration the
  client is automatically updated (if explicitly
  required from sys. admin. ) via the LCFG object
  inet (this object also restarts the inetd demon)
• In this way all changes for a service are
  centrally managed in the LCFG server and it is
  also possible to use templates with different
  implementations for different nodes
• If the configuration of a service is not stored
  and it is only manually inserted after a LCFG
  update it WILL BE LOST!

9
Managing your configuration with LCFG (2)

• Use-case distribute configuration files
  (example httpd.conf, globus.conf, bashrc,
  rc.local, ) to all the clients
• It is possible to copy files in any client
  directories using the LCFG filecopy object
• On the LCFG server this is centrally managed in
  the single node profile and it is possible to
  start cron jobs for periodically update
• If after a configuration update it is also
  necessary to restart a service(s) on several
  clients, the best solution is to create an LCFG
  object part of the central resource management
  (like the inet object).