dmwm / PHEDEX

CMS data-placement suite
8 stars 18 forks source link

Some Phedex feature requests from DataOps #445

Closed ericvaandering closed 10 years ago

ericvaandering commented 10 years ago

Original Savannah ticket 45921 reported by None on Wed Jan 14 15:56:28 2009.

Hi,

As promised, I give a few minor requests from DataOps. I split it into 2 categories, one for the webpage, and one related to subscriptions.

Request for developers:

Webpage: These have a bit higher priority than the 2nd set, since they are more immediately useful to us. I'm not sure if these are not already available - if they are please let me know.

1) Webpage: I would like to have an option similar to "Show interesting rows", but for columns. Specifically, for some given dataset, I would like to see all the sites which have replicas of files. Currently I have to know which sites contain files and specifically check those ones or select to see all sites in order to determine which sites have replicas by eye.

2) Webpage: Is it possible to show pending subscriptions on the subscriptions page, in addition to approved ones. And also provide a link to the corresponding request. This is useful in the case where we know a particular subscription needs to be complete, but where we are not sure whether the subscription is pending or whether no subscription has been requested yet.

Subscriptions:

3) Subscription Deletion: In the case where we have some old subscription of a complete dataset, and one wants to delete a particular block for that subscription, we want to be able to request deletion of that block, and after it is done we want phedex to automatically convert the original dataset-type subscription into a set of block-type subscriptions for those blocks which had been left remaining at that site. Currently, Nicolo tested this and we saw that it would simply delete the original dataset-type subscription.

4) Subscription Merging: We would like the ability to merge block-type subscriptions with dataset-type subscriptions under certain conditions. An example would be a case where a block-type subscription is made for half of the blocks of some dataset. And then later we subscribe the 2nd half. At this point all of the blocks are subscribed, and it would be useful to merge these 2 block-type subscriptions into 1 entire dataset subscription.

ericvaandering commented 10 years ago

Comment by sixie on Thu Jan 15 07:39:00 2009

One more feature which I would label as higher priority than the rest:

For subscription requests: Can we have phedex check whether links from sites containing replicas of the datasets to the site requesting the dataset exist at the time of the request? Then we could either give a warning to the data manager to disapprove the subscription, or just disallow that request, depending on how restrictive one wants to be.

This is motivated from several incomplete subscriptions that I'm seeing for which the links to the site do not exist by design. ie. it's trying to request a dataset which is only on the Tier0, to be transferred to a T2. This type of request should be disapproved in my opinion.

ericvaandering commented 10 years ago

Closed by egeland on Thu Jan 22 04:42:49 2009

ericvaandering commented 10 years ago

Comment by egeland on Thu Jan 22 04:42:49 2009

Si,

In the future, please put all distinct feature requests in a separate item. It will make the management easier for us.

I am closing this one and will make separate requests.