Discussion on VAPOR features with COMPCHEM VO
→
Europe/Paris
Discussion with COMPCHEM VO about VAPOR features
1. Intro
COMPCHEM to remind its activity, the organisation of the VO, and the support model
~50 users. VO Manager: Osvaldo Gervasi. Dupty Manager: Alessandro Costantini. VO community leader: Antonio Lagana.
Today COMPCHEM is not part of a VRC but existing collaboration with Gaussioan VO. Also in the process of assessing the interest of making a VRC: https://wiki.egi.eu/wiki/Towards_a_CMMST_VRC
VO comparable with biomed for several reasons:
No proper tools apart from GRIF. Tools used are all standard: VOMS, GGUS, VOID card, etc. Too many tools available to control the resources allocated to a VO.
2. Review the initial list of features that has been defined in VAPOR.
VO users management : Users database, Identification of users behind robot certificates, User life cycle management
COMPCHEM shares the concern about the acknowledgement of resource usage and has to deal with it too. Today, the VO reminds users of that when they contact the VO manager.
Useful features would be to select a user from the VOMS and send him an email (to be integrated into the VO Operations Dashboard).
COMPCHEM LFC server is managed by INFN: what if they stop it?
=> official position is that LHCb will continue to use LFC, therefore LFC support will continue as part of the DPM project. In the VAPOR specification, we consider that VOs using LFC will continue to do so in the middle term.
Mailing list: COMPCHEM manages it manually, using sendmail aliases, an automatic sync of the mailing list with the base of users would be useful.
VO Operations management for VO support teams
Resource status indicators, statistical reports:
- Report GOCDB and BDII status
COMPCHEM does not have its own VO Nagios, so this is probably not very interesting for the moment.
- Advertise critical resources downtimes
Today this is done manually by the COMPCHEM VO Manager. Like it is in biomed => would be interesting.
- Monitor resources availability - 2 aspects:
VO Data Management: file migration and cleaning procedures
- Remove old files
The X month grace period must be stated in the AUP => this must not be surprise for the user. The X should be long enough, maybe default value of 12 months.
- Deal with SEs filling up
Could be fantastic!
- Consistency between LFC and SEs: zombie & ghost files
COMPCHEM does not care about that today, but that has to be addressed.
Only one LFC used in the VO, there is no other custom file catalog => this makes it simpler to ensure consistency. As opposed to biomed in which some users use custom fiel catalogs.
Community Accounting
Not rediscussed.
3. Would COMPCHEM consider using VAPOR
COMPCHEM wishes to help scope the features of VAPOR, be a beta-tester to experiment the interest, and possibly use it in the longer term.
1. Intro
COMPCHEM to remind its activity, the organisation of the VO, and the support model
~50 users. VO Manager: Osvaldo Gervasi. Dupty Manager: Alessandro Costantini. VO community leader: Antonio Lagana.
Today COMPCHEM is not part of a VRC but existing collaboration with Gaussioan VO. Also in the process of assessing the interest of making a VRC: https://wiki.egi.eu/wiki/Towards_a_CMMST_VRC
VO comparable with biomed for several reasons:
- Activity: 12 to 15 CPU hours/y.
- Fragmented user groups. No central ticketing support, GGUS used occasionally, or users contact the VO managers directly.
- Submission: WMS CLI for most users. Some 10 to 15 users use framework GRIF (http://www.hpc.unipg.it/): job submission, data placement. Set of ~10 applications compiled and usable in GRIF. Monitoring of the user's activity (hows many jobs, how much time) => ranking of service, and ranking of users: helps understand the work carried out. GRIF users have their own grid certificate, but using GRIF they all use the same robot certificate.
- Support team: only one person, VO manager.
- Resources allocation: opportunistic (Italy, France, UK, Greece, Spain), and agreements with some sites (Italy).
No proper tools apart from GRIF. Tools used are all standard: VOMS, GGUS, VOID card, etc. Too many tools available to control the resources allocated to a VO.
2. Review the initial list of features that has been defined in VAPOR.
VO users management : Users database, Identification of users behind robot certificates, User life cycle management
COMPCHEM shares the concern about the acknowledgement of resource usage and has to deal with it too. Today, the VO reminds users of that when they contact the VO manager.
Useful features would be to select a user from the VOMS and send him an email (to be integrated into the VO Operations Dashboard).
COMPCHEM LFC server is managed by INFN: what if they stop it?
=> official position is that LHCb will continue to use LFC, therefore LFC support will continue as part of the DPM project. In the VAPOR specification, we consider that VOs using LFC will continue to do so in the middle term.
Mailing list: COMPCHEM manages it manually, using sendmail aliases, an automatic sync of the mailing list with the base of users would be useful.
VO Operations management for VO support teams
Resource status indicators, statistical reports:
- Report GOCDB and BDII status
COMPCHEM does not have its own VO Nagios, so this is probably not very interesting for the moment.
- Advertise critical resources downtimes
Today this is done manually by the COMPCHEM VO Manager. Like it is in biomed => would be interesting.
- Monitor resources availability - 2 aspects:
- monitoring to detect when there are problems: recurring errors on some resources, peak of activity on some sites that hardly run jobs in opportunistic mode.
- It could be great if the VAPOR could provide a list of CEs that "work fine" at a given moment (feature called "Status of jobs submitted on CEs supporting the VO"). The problem is to use this list of CEs to feed different submission systems used in COMPCHEM, that are developed by the users themselves.
VO Data Management: file migration and cleaning procedures
- Remove old files
The X month grace period must be stated in the AUP => this must not be surprise for the user. The X should be long enough, maybe default value of 12 months.
- Deal with SEs filling up
Could be fantastic!
- Consistency between LFC and SEs: zombie & ghost files
COMPCHEM does not care about that today, but that has to be addressed.
Only one LFC used in the VO, there is no other custom file catalog => this makes it simpler to ensure consistency. As opposed to biomed in which some users use custom fiel catalogs.
Community Accounting
Not rediscussed.
3. Would COMPCHEM consider using VAPOR
COMPCHEM wishes to help scope the features of VAPOR, be a beta-tester to experiment the interest, and possibly use it in the longer term.
There are minutes attached to this event.
Show them.
