dmwm/sitedb

sitedb's Issues

intra-federation site pledges percentage split

Hi,
Jose asked and suggested this thing :
How can specify in siteDB that each site contributes with 50% of the resources of the federation?

Are we looking into in this type of feature, that makes easier for intra-federation operators, allowing to specify percentage split of federation pledges ?

Also need to think about use cases :
Then site is removed from federation
Then site is added to federation (fetched from rebus)
Allow it change per year, or per Site?

Change left navigation tab

As discussed with Diego

Change Savannah links to ggus

Documentation update

Update documentation about new API calls and add all examples how to get, delete, put data using curl

Document to specify that disk is to be used for a processing site

from a discussion in HN https://hypernews.cern.ch/HyperNews/CMS/get/comp-ops/3982/1/1.html
We need a list similar to https://cmsweb.cern.ch/sitedb/data/prod/data-processing which specifies “if you want to run something at X (processing site), put your data in Y (phedex node name)”
If that already exists, all the better

Deletion of site does not cleanup cms_name

Whenever a site is removed from sitedb, its CMS alias name does not get deleted from the cms_name table.

If we then try adding the site with the same cms_name, it will fail to register that alias for the site. In the end, you have a site without a CMS alias name.

So far, whenever someone removes a site, I have to do the following surgery cleanup:

select * from cms_name where id not in (select cms_name_id from site_cms_name_map);

    ID NAME
---------- ----------------------------------------------------------------------------------------------------
     3 T1_DE_FZK
       801 T2_CH_CAF
       113 T2_PT_LIP_Lisbon
       142 T3_DE_Karlsruhe
      1341 T3_IT_Padova
       923 TX_UN_Fake

6 rows selected.

delete from cms_name where id not in (select cms_name_id from site_cms_name_map);

The bug is very easy to reproduce: just add a new site under the dev instance, remove it, then try adding again.