1 / 8

EMIR integration in BDII

EMIR integration in BDII. Maria Alandes Pradillo (CERN) Information System Product Team. Approach. Service. EMIR server. g info : cron job (every hour) queries EMI resource information service and produces json output EMIR service publisher reads json and publishes in EMIR server.

tobit
Download Presentation

EMIR integration in BDII

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. EMIR integration in BDII Maria AlandesPradillo (CERN) Information System Product Team

  2. Approach Service EMIR server • ginfo: cron job (every hour) queries EMI resource information service and produces json output • EMIR service publisher reads json and publishes in EMIR server emir-serp /var/cache/emir/services/service.json EMI resource information service ginfo Information System Product Team - EMIR Integration

  3. What is needed? (I) • Dependencies • ginfo • Available in EPEL • Information System client for GLUE 2 • Command: yum install ginfo • emir-serp • Available in EMI • EMIR service publisher • Command: yum install emir-serp Information System Product Team - EMIR Integration

  4. What is needed? (II) • Configuration • YAIM function available in glite-yaim-bdii • config_emir_serp • YAIM variables to be defined in site-info.def • BDII_EMIR_ENABLE=yes • BDII_EMIR_HOST=http://emitbdsr1.cern.ch:9126 (for testing) • Make sure BDII is started • Run: /opt/glite/yaim/bin/yaim -r -s site-info.def -n node_type-f config_emir_serp Information System Product Team - EMIR Integration

  5. Known Issues • ginfo • Some mandatory attributes expected by EMIR are missing in the json output • Fix under development will be soon available in EPEL • EMIR service publisher • Not very robust • Service stopped if: • EMIR server cannot be contacted • Json output contains mistakes Information System Product Team - EMIR Integration

  6. Try a different approach • Documentation • https://twiki.cern.ch/twiki/bin/view/EMI/SERP • No need to use ginfo • Create your own json file • You can use ginfo to get a template for your service Information System Product Team - EMIR Integration

  7. EMIR rollout task status • Development tracker: https://savannah.cern.ch/task/?group=emi-dev • 20 tasks “In progress” or “Not started” • 3 tasks “Done” (BDII top, BDII site and Unicore UVOS) Information System Product Team - EMIR Integration

  8. Thank you EMI is partially funded by the European Commission under Grant Agreement INFSO-RI-261611 Information System Product Team - EMIR Integration

More Related