Talking with Frank W friday morning, I got convinced that a Black list only is enough

The black list is ANDed with possible user's white list. The black list can be ignored with an option. We foresee the following use cases
  • default: we black list T0*,T1*,T3*,specific T2's that do not work
  • normal users see no difference
  • users who want to use sites A,B,C,D, use a white list, if one of those is a bad T2 (as above) it is removed
  • users who thinks they know better, use remove_default_black_list=1 and provide their own white or black
    • there must be an (easy) way for users to see what the default black list is, so they can adapt

Why I want a default Black List AND a default White List in Crab

* there are many sites that
    • are all reacheable via grid
    • have phedex
    • host data that are in global scope DBS

  • 1. some are good T2's were we are happy to support users
    • i.e. they are in AnaOps-maintained white list
    • e.g. are OK according to FacOps and have no problem today

  • 2. some are sites that should better not be used
    • plainly non functional
    • T1's

  • 3. world is not only black or white, there is a (large) gray area of wanna-be T2's and T3's

therefore

  • 1. so we want a default white list
    • users are free to add specific sites to it (taking their chances)
    • there could be an option to ignore it (take more chances) i.e. use white and gray

  • 2. we we want a default black list
    • so that users can ignor the default white list but still get some "protection"
    • only pain seekers will want to remove the black list

implementation

  • if there is no option to ignore the default white list (preferred)
    • start from the default white list (replace it with user's white list if indicated) and remove sites in black list
  • if we want to allow ignoring the default white list
    • do same thing as done now
  • we also have the option to put/use BDII tags (like we do for CMSSW version) which may simplify our requirement list and possibly speed up matchmaking, besides readable config. files are always a bonus

-- StefanoBelforte - 29-Oct-2009

Edit | Attach | Watch | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r4 - 2009-11-02 - unknown
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 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