Adjust records in MSPileup DB for support partial pileup data placement

[vkuznet]

Impact of the new feature
Prepare MSPIleup database for handling partial pileup data placement

Is your feature request related to a problem? Please describe.
At the moment all existing documents in MSPileup DB contains empty transition record list. The new MSPileup code base requires to have full transition record at the time we need to update it. Current the code creates it on its own but we need to adjust existing records to align with it.

Describe the solution you'd like
Create a new script and run it on production cmsweb cluster within MSPileup MongoDB. It should have the following logic:

• Get list of existing pileup records in MongoDB
• Loop over records
• For each record extract pileup name and
• Create new transition record with the following content: {‘containerFraction’:1, ‘customDID’: , ‘updateTime’: gmtimeSeconds(), ‘userDN’: }
• We must use WM robot DN for userDN value, e.g. /DC=ch/DC=cern/OU=Organic Units/OU=Users/CN=cmsunified/CN=658085/CN=Robot: CMS Unified account
• We must use gmtimeSeconds() function or properly determine number seconds since epoch in GMT time zone

Describe alternatives you've considered
None

Additional context

[klannon]

@vkuznet Can you please update the project fields for this issue so that it's properly tracked? This looks like new High priority issue that was created for the partial pileup feature.