Project

General

Profile

POMS release notes draft

Release Notes

v1_1_0

New Features

Ability to get reports about how effective/efficient are the campaigns and assure POMS is alive #13699

Split "Located" state into "Successful"/"Failed" We should have the potential for Submissions/Jobs to be Failed vs Succeded.Feature #14751: (is that not in place?)

Feature #14752: Add job log parser to get final job info

--------
Working

Allow specification of completion requirements in order to launch dependant task #12751
The runtime,memory, and disk were included in the Campaign Def/Campaign info #12966
The job efficiency per campaign page is also included into landscape. #14377
Monitor internal components #14473
Poms should keep a list of job launches requested while job launches are "held" #14659
POMS hold job launches when services are "red" on dashboard.
Add a script to extract VO Role=Production user info. #14747

Currently POMS use project descriptions Feature 14504, Integrate with SAM feature #14503 --
"why is my job not running?" screen for a campaign. lets you do the jobsub_q --better-analyze for jobs, and look at their Condor joblog, last-matched stuff, etc. #12965

Improvements

The HTML templates were renamed to line up with the URL's, so they are easier to find. #12933

--------
Working

Improve in the labeling of the job status, now the table describe the complete jobs with the total number, number of jobs located and number of jobs non-located.. #14477
A complete refurbish of the POMS code in order to split in modules by functionality, having independent test units. #12934
The Campaign Info page was updated for new fields added to Campaign(Layers), LaunchTemplates, etc. #14531

A better split types was added allowing the user to ... #13707

Bugs Fixed

--------
Working

The code for pending campaigns made a query that didn't work if you did the whole campaign. Furthermore, the generation of these dimension strings was factored out to common routines #13889
POMS use elasticsearch condor events for obtain complete information about the jobs and prevent incomplete data as happens with jobsub_fetchlog #14248
When the jobs dropped out of the queue condor_q no longer suffices. Now it is stored into the elasticsearch logs. #14376 Get all poms data accessible for landspace

############

v2_0_0

New Features

Improvements

Bugs Fixed

Feature #14270: Allow users to run arbitrary executables/scripts and workloads through the system via arbitrary launch scripts/executables
Feature #14271: Support the model of sending data to jobs
Feature #14272: Supports data externally pre-staged manually at sites (i.e. different site local caches)
Feature #14273: Provide a "campaign-layer" status view with the following types of information: * overall percentage done (of the campaign) * resubmission/failure rates * efficiency
Feature #14274: Have appropriate permissions and privileges implemented to authorize each operation

The job efficiency per campaign page is also included into landscape. #14377
Monitor internal components and assure POMS is alive #14473

v3_0_0

New Features

Improvements

Bugs Fixed

Feature #14287: More detailed overall campaign-at-a-glance status page (campaign workflow summary,overall percentage done, resubmission / total failure rates, efficiency
Feature #14288: Support sending jobs to known data caches (i.e. steering to sites).
Feature #14289: Support automatic pre-staging of data to sites.
Feature #14290: Have appropriate permissions and privileges implemented to authorize each operation and assign priority.
Feature #14291: Be able to interface with multiple Data Management Systems via modular API's.

POMS use elasticsearch condor events for obtain complete information about the jobs and prevent incomplete data as happens with jobsub_fetchlog #14248