Opened 11 years ago

Last modified 4 years ago

#500 new enhancement

Proposal: Global Config File

Reported by: fitz Owned by: mmludin08
Priority: major Milestone:
Component: Both Version:
Keywords: Cc:
Blocked By: Blocking: 646
Estimated Hours: 0 Total Hours: 0


Add something like /etc/bccd.conf to contain defaults, constants, and other misc values used by BCCD scripts. As part of this effort, we could also work to define a standard structure for all BCCD scripts to work within, possibly through the use of custom BCCD Perl modules.

This would be an excellent project for an intern, new student, or anyone wishing to start development as it doesn't require much up-front knowledge of the inner workings of the BCCD. But since it requires small changes to a large number of scripts, those involved would certainly learn a lot about the BCCD. (They could help with documentation while they're at it too.)

First run at a list of values to go into this config file (amend as you see fit):

  • pkbcast port number
  • pkbcast interval
  • root mpd (for MPICH2, yes/no)
    • If yes, port number for headnode's mpd
  • network driver(s) in use
  • auto allowall (yes/no)
  • allowall interval
  • assumed hostname for the headnode
  • default queue name (for whenever we get a scheduler)
  • revision/date
  • stage (live/liberated)
  • Common network settings
    • BCCD interface
    • PXE interface
    • dhcpd (yes/no)
    • NAT info
  • Logging
    • Filename
    • Level

Change History (5)

comment:1 Changed 10 years ago by fitz

  • Type changed from defect to enhancement

comment:2 Changed 10 years ago by fitz

  • Owner set to fitz
  • Status changed from new to assigned

comment:3 Changed 9 years ago by skylar

  • Blocking set to 646

comment:4 Changed 4 years ago by mmludin08

  • Owner changed from fitz to mmludin08
  • Status changed from assigned to new

Is this still relevant? I know we don't have a bccd.conf file. I support the idea of having a standard structure for all the bccd scripts.

still not sure why its blocking #646?

I think I am going to keep it open, as it does seem like a nice and valuable project.

comment:5 Changed 4 years ago by skylar

I think it could still be relevant. Let's see where the build process improvements end up.

Note: See TracTickets for help on using tickets.