Adding the "site" keyword to JDL

[jgaida]

To make it less confusing for G5K users, we might want to accept the keyword "site" in place of "clusters" in JDL:

    "clusters": {
         "nancy": {},
     "grenoble": {},
     "luxembourg": {},
     "lyon": {},
     "nantes": {},
     "rennes": {},
     "sophia": {}
     },

    "sites": {
         "nancy": {},
     "grenoble": {},
     "luxembourg": {},
     "lyon": {},
     "nantes": {},
     "rennes": {},
     "sophia": {}
     },

This does not have any impact for CIMENT.

[bzizou]

I don't like the idea of "less confusing for g5k users". It is a pure g5k point of view... But if we have a "site concept" (see #28 ), a cluster could be the name of a site to refer every clusters of a site. For example, we could mix clusters and sites:

"clusters": {
     "nancy": {},
     "genepi": {},
     "luxembourg": {},
 },

[jgaida]

And if you have both a cluster and the cluster site on the JDL? ie: "grenoble": {} "genepi": {}

[bzizou]

Well in that case, the smallest wins: apply the "grenoble" part to every clusters except for those listed, so "genepi" is an exception.

[jgaida]

Alternative 1: Global JDL settings are overridden by Cluster Settings, so it can be the same between grenoble and genepi, ie: for the genepi cluster, apply "grenoble" options, unless there are overriden by genepi-specific settings.

Alternative 2 (too complex?) :

"sites": {
     "grenoble": {
        "exec_file": "$HOME/path/script"
        "clusters": { 
           "genepi" : {
               "exec_file": "$HOME/path/script"
            }
      },
     "luxembourg": {},
 },