1 / 12

Web Interface to the LEAF Toolsuite

Bill, Ulrich, Vasco, Veronique ELFms Meeting 14.11.2005. Web Interface to the LEAF Toolsuite. LEAF Toolsuite Requirements. See http://isscvs.cern.ch:8180/cgi-bin/viewcvs-all.cgi/elfms/quattor/cdb2sql-exper/schemas/Documentation/?cvsroot=elfms CDBWeb_Requirements.doc. LEAF Architecture.

gracie
Télécharger la présentation

Web Interface to the LEAF Toolsuite

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Bill, Ulrich, Vasco, Veronique ELFms Meeting 14.11.2005 Web Interface to the LEAF Toolsuite

  2. LEAF Toolsuite Requirements • See http://isscvs.cern.ch:8180/cgi-bin/viewcvs-all.cgi/elfms/quattor/cdb2sql-exper/schemas/Documentation/?cvsroot=elfms CDBWeb_Requirements.doc

  3. LEAF Architecture

  4. First Use Case: “View Clusters” • Exercise for Vasco • Replace manually-maintained Web pages • (such as lxdev nodes usage, list of FS clusters, …) • CDB cluster info up-to-date • Possible applications: • tool for generating e-mails (see further) • …

  5. “View Cluster” Web page • See demonstration by Vasco: • https://oraweb.cern.ch/pls/cdbsql/web.main“Other searches””View Clusters” • Used fields: • /system/cluster/name • /system/cluster/subname • /system/cluster/description • /system/cluster/itsection • /system/cluster/itcontact • /system/cluster/usercontact • /system/quattor_managed • /system/function

  6. CDBAutoNotifyContacts.pl Usage: try CDBAutoNotifyContacts.pl -h Required arguments: • --cluster_name cluster (eg. lxgate) • --os osversion (eg. Slc3) • --subject 'subject text' • --message 'path_to_body_text_as_file' Variables: The message text and subject may contain the variables ###NODES### will be replaced by the list of nodes ###SIGNATURE### signature for the body text, can be set on the command line Notes By default, the script will only print out stuff and send nothing. Sending is activated only by explicitly setting the debug level on the command line to a value of 0 (zero).

  7. CDBAutoNotifyContacts History and idea • LXGATE cluster reboot: 24 machines, different (groups of) contacts persons to be notified of reboot • Idea: CDB contains IT and user contacts • Wrote a script to use this information, regroup the contacts and send exactly one notification mail per user contact group, containing a list of their machines Status • In CVS, first version released on AFS today • Relies on correct user contact information in CDB!

  8. Related Issues/Tools • LANDB-CDB synchronisation (for “responsible” fields for “lxnoq” hosts) • Work in progress with NetOps colleagues • Yet another DB for LCG users: • http://grid-deployment.web.cern.ch/grid-deployment/cgi-bin/nodes-status.cgi • They should be able to use/update info from/in CDB •  “CDBUpdate” tools: • Modify user & IT contacts, … for a list of hosts • …

  9. Next developments (1) • Add Warranty: LEAFAddWarranty --help --contract_id=<id> --vendor=<vendor> --intervention_delay=<intervention_delay> --repair_delay=<repair_delay> --commencement_date=<commencement_date> --duration=<duration> --details=<details> [--files] [--server=<server>] [--testconnection] • From PAN to CDBW:  body to be rewritten

  10. Next Developments (2) • Web interface for modifying profile-level configuration parameters:LEAFChangeProfile --help -newtype=<newtype> #for changing pro_type_<cluster>OR/AND -newresources=<newresources> #for changing LSF resource stringOR/AND -path=<path> -data=<data> #for changing arbitrary string field eg.: -path="/system/cluster/usercontact“ -data="myemail,hisemail" or : -path="/system/cluster/itcontact" -data="email" or : -path="/system/contract" -data="E" -rack=<rackname> OR -firsthost=<firsthost> -lasthost=<lasthost> OR -list=<host1,host2,...,hostN> [-cluster=<clustername>] [--cdbcfgfile=<cdbcfgfile_location>] [--server=<server>] [--testconnection]

  11. Next Developments (3) • GUI for cluster creation • “lxnoq” subclusters • Normal clusters • In both cases, perl script prototypes have been implemented (and used). Create user-defined templates from a questionnaire: • pro_software_<cluster> • pro_system_<cluster> • pro_type_<cluster>_<os>

  12. Further plans • See requirement document • Priorities adjusted with time and demand

More Related