change 1 request parameter value in block

[franzoni]

typical example of use case is : we need to change the priority of 200 requests.
This need may apply to other parameters of requests too: evaluate which other parameters.

[anorkus]

doesn't multiple edit of requests gives this feature?

[franzoni]

investigations lead to:

[more adequate subject, continuing/wrapping up the existing thread]

Hello all,

changing priority-block of a large number of request can be done with mcm through actions and an input text file containing the root requests, see:

https://twiki.cern.ch/twiki/bin/view/CMS/PdmVMcMProdManager#Priority_Increase_change

It will be even easier when actions will be selectable through non-root requests, see open mcm issue [1]

Concerning:

    is there any way to sync the priority numbers in ReqMgr and McM?

the mcm database receives updated values from the reqmgr via the stats db.
A fraction of the 59 requests which were de-prioritized over the past days have received the updated priority value, when a change in their status triggered the update. With the current logic implemented in stats, such prio update won't occur as long as requests are in submitted status: we do want updates in that case, see feature requests [2].

While there are a few of the 59 requests for which the status is unclear to us (e.g. [3]), to our understanding the priorities updated directly in reqmgr will propagate back to McM, eventually.

Cheers,
Antanas and Giovanni

[1] #629

[2] cms-PdmV/stats#2

[3] this request https://cms-pdmv.cern.ch/mcm/requests?prepid=HIG-Summer12-02052&page=0&shown=127
is "submitted" in McM while it's "normal-archived" in reqmgr