Feedback on SAM3

This page will contain the feedback on the usage of SAM3, and any issues found that might affect the transition from SAM2 to SAM3.

Please, answer the following questions:

  1. Do you see any show stoppers for the SAM2 to SAM3 migration?
  2. Are there any special steps required to announce the change to the community?
  3. How many profiles do you currently have?
    • Do you need all of them ?
  4. How much overlap do you need with the four systems (SAM2/SAM3, preprod/prod) running in parallel?
  5. Could you please specify any links from SAM2 and mywlcg that are used through the programmatic interface?


  1. No.
  2. The change will be announced on the usual list for reaching site contacts.
  3. 4 profiles. 3 are needed, while ALICE_GENERAL could be useful in the future.
  4. 1 month of overlap ought to be sufficient.


  1. No.
  2. From previous meetings there is nothing more precise than having september wlcg report to be done via SAM3, which means going into production not later than by october end-ish. The differences are understood and agreed upon so there is no real issue. From ATLAS side an announcement in a suited ADC meeting is an action to be done. It is to be taken into account that some sites responsible will need some detailed explanation upon new reports issuing in the first months.
  3. 8 profiles. Only ATLAS_CRITICAL is needed for A/R. ATLAS_GENERAL (which can be renamed to ATLAS) would be rather kept for it's displaying all the tests at once. Others can be dropped.
  4. 1 Month.
  5. RESTful queries for json like this and in general it would be useful to keep all the web queries for retrieving json that are present in
    SAM2 link SAM 3 link
    Metric history in profile
    here. FYI, CMS and LHCb are already doing something similar, retrieving the output of a metric for all sites


  1. No
  2. Inform CMS Computing Operations (through WLCG Operations or at CMS CompOps meeting)
  3. Currently 7, but only the CMS_CRITICAL and CMS_CRITICAL_FULL profiles are needed for availability. The other profiles are there for technical reasons in SAM2 and can/should be retired in SAM3.
  4. Estimate 1 month for comparisons.
  5. SAM2 link SAM 3 link
    availabilityResults here
    Summary view


    1. No
    2. Will be done via LHCb computing operations, nothing needed from WLCG
    3. LHCB_CRITICAL is in use for operations monitoring, a second would be useful to test probes not yet introduced into CRITICAL
    4. 1 month should be fine
    5. None, from wlcg-mon we use the probe information for the WN-cvmfs test to display results in the dashboard (from a summary all probes going down to the individual probe logs)


    1. SAM2 link SAM 3 link
      Nagios plugin

    -- PabloSaiz - 10 Sep 2014

Edit | Attach | Watch | Print version | History: r10 < r9 < r8 < r7 < r6 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r10 - 2014-10-10 - PabloSaiz
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LCG All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback