VT VAPOR:Progress Report

From EGIWiki
Jump to: navigation, search

Contents

Progress Report

VT Reporting guidelines

Reporting period: April 7th to 25th 2014 - LAST REPORT

The project was officially completed on April 15th 2014, as a result this is the last progress report. VAPOR final project report can be found in D8.1 Final Report on Additional Funded Activities to Advance EGI's Strategic Goals.

The main developer, Flavien Forestier, finished his contract on April 10th. From now on, the project manager, Franck Michel, will perform maintenance and bug fixing, but no more new feature will be developed.

Progress

A bug was found in the Dark data and lost files management. It's been fixed and set in production.

The migration of VAPOR MySQL database from I3S to the MySQL farm of the IN2P3 Computing Center in Lyon has been tested successfully. A discussion is going on as to the possibility to also use an instance of the data integration Lavoisier service at IN2P3 Computing Center, in addition to the one at I3S. This would help gain stability and performance.

Reporting period: April 7th to 25th 2014

The project was officially terminated on April 15th 2014, as a result this is the last progress report.

The main developer, Flavien Forestier, finished his contract on April 10th. From now on, the project manager, Franck Michel, will perform maintenance and bug fixing, but no more new feature will be developed.

Progress

A bug was found in the Dark data and lost files management. It's been fixed and set in production.

The migration of VAPOR MySQL database from I3S to the MySQL farm of the IN2P3 Computing Center in Lyon has been tested successfully. A discussion is going on as to the possibility to also use an instance of the data integration Lavoisier service at IN2P3 Computing Center, in addition to the one at I3S. This would help gain stability and performance.


Reporting period: Mar. 24th to April 4st 2014

Project is due to end on 15th of April. As already mentioned previously, the user community features (users database, user's life cycle management) will not be started by the end of the project this time.

Progress

Plans for next period

Start migrating the MySQL database of VAPOR from the I3S instance to a MySQL farm of servers of the IN2P3 Computing Center in Lyon.

Main developer, Flavien Forestier will be finishing his contract on April 10th. Passed this date, the project manager Franck Michel, will perform maintenance and bug fixing, but no more new feature will be developed.

Problems we encounter, but can solve

none.

Problems and issues we need external help with

None.

Reporting period: Mar. 10th to 21st 2014

Project is due to end on 15th of April. As already mentioned previously, the user community features (users database, user's life cycle management) will not be started by the end of the project this time.

Progress

Plans for next period

Problems we encounter, but can solve

none.

Problems and issues we need external help with

None.

Reporting period: Feb. 24th to Mar. 7th 2014

Project is due to end on 15th of April, marked by the leaving of Flavien Forestier, developer. As already said previously in emails to the partners, the user community features (users database, user's life cycle management) will not be started by the end of the project in mid-April.

Progress

Plans for next period

Problems we encounter, but can solve

none.

Problems and issues we need external help with

None.

Reporting period: Feb. 10th 21st 2014

Progress

At last, we managed to get in touch with the right person, Maria Alandes Pradillo from CERN, to help us find out how to build the gsiftp url to access an SE, and when it is applicable or not (mentioned as a problem in the last report).

Plans for next period

Problems we encounter, but can solve

none.

Problems and issues we need external help with

None.

Reporting period: Jan. 27th to Feb. 7th 2014

Progress

Plans for next period

Problems we encounter, but can solve

We cannot get sufficient information as to how to build the URL that allows to access a Storage Element with gsiftp protocol. This is needed to complete the feature about Dark data and lost files. It is surprisingly difficult to find out what information to use from a top BDII to build this URL.

Action: we have discussions with GFAL2 API developers about this, but they not GridFTP experts. A discussion with some french site admins did not help much. Now going to GGUS: https://ggus.eu/ws/ticket_info.php?ticket=101086

Problems and issues we need external help with

None.

Reporting period: Jan. 13th to 24th 2014

Progress

Plans for next period

Problems we encounter, but can solve

None.

Problems and issues we need external help with

None.

Reporting period: Dec. 9th 2013 to Jan. 10th 2014

Progress

During this long period, rather few has happened due to the Christmas vacation (main developer was on leave from Dec. 9th to Jan 2nd).

Nevertheless, a first version of VAPOR has been finalized and set on line on Dec. 22nd 2013. It supports the biomed VO, and biomed technical support team is now encouraged to use it. The web application is hosted as the Computing Center in Lyon (IN2P3), while the data collecting services are hosted at the production server in I3S in Sophia Antipolis.

Other tasks performed:

Plans for next period

Problems we encounter, but can solve

None.

Problems and issues we need external help with

None.

Reporting period: Nov. 26th to Dec. 9th

Progress

Plans for next period

Very few should now happen until the end of the month as the main developer will be on leave from Dec. 9th to 31st.

Problems we encounter, but can solve

None.

Problems and issues we need external help with

None.

Reporting period: Nov. 12th to Nov. 25th 2013

Progress

Plans for next period

Problems we encounter, but can solve

None.

Problems and issues we need external help with

None.

Reporting period: Oct. 30th to Nov. 11th 2013

Progress

Plans for next period

Problems we encounter, but can solve

None.

Problems and issues we need external help with

None.

Reporting period: Oct. 16th to 29th 2013

Progress

Plans for next period

Problems we encounter, but can solve

None.

Problems and issues we need external help with

None.

Reporting period: Oct. 2nd to 15th 2013

Progress

in addition to look and feel and ergonomic improvements (tooltips, styles, use cookies to remember columns selected by user etc.).

Plans for next period

A few minor issues need to be fixed on pages described above, along with an overall review of the consistency in terms of GUI, styles etc. Developments: start development of the VO Data Management features: dealing with storage elements filling up.

Problems we encounter, but can solve

None.

Problems and issues we need external help with

None.

Reporting period: Sep. 18th to Oct. 1st 2013

Progress

Plans for next period

Problems we encounter, but can solve

The lack of experience of the main developer is being handled and things are improving. Continuous support is being provided.

Problems and issues we need external help with

None.

Reporting period: Sept. 4th to 17th 2013

Progress

Plans for next period

Problems we encounter, but can solve

The lack of experience of the main developer is being handled and things are improving, although the code production and quality remain lower than expected. Action: heavy support is being provided.

Problems and issues we need external help with

None.

Reporting period: Aug. 21st - Sept. 3rd

Progress

Plans for next period

Problems we encounter, but can solve

Problems and issues we need external help with

None.

Reporting period: Aug. 7th to 20th

Progress

Plans for next period

Problems we encounter, but can solve

Lack of experience of the main developer in terms of development good practices and application design. This has slown down the activity but this is handled.

Problems and issues we need external help with

None.

Reporting period: July 24th - Aug. 6th

Progress

Development:

Plans for next period

Complete VO Operations management features (resources availability): reports on running and waiting jobs, and ratio R(R/W); white list of CEs Continue work on VO Data management (dark data).

Problems we encounter, but can solve

Lack of experience of the main developer in terms of development good practices and application design. This has slown down the activity but this is handled.

Problems and issues we need external help with

None.

Reporting period: Jun. 26th - Jul. 23rd

Progress

Low activity due to summer vacation period: 2 weeks vacation for Flavien Forestier (developer) and 3.5 weeks for Franck Michel (project manager) => 10 days work for Flavien and 2 days for Franck.

Plans for next period

Problems we encounter, but can solve

None.

Problems and issues we need external help with

None.

Reporting period: June 19th to 25th

Exceptionally this is a one-week report as I'll be on vacation starting end of this week.

Progress

Plans for next period

Very few will be done in the next period due to summer vacations of Franck Michel (back 22 July), and Flavien Forestier (VAPOR developer, back 15 July).

Problems we encounter, but can solve

none.

Problems and issues we need external help with

none.

Reporting period: June 5th to 18th

Progress

Plans for next period

Problems we encounter, but can solve

The work on the VO data management procedures has been started in Lyon with discussions with LFC manager. Further work will be postponed later during the summer.

Problems and issues we need external help with

Reporting period: May 22nd - June 5th

Progress

Plans for next period

Problems we encounter, but can solve

Difficulty to find someone among partners to start working on the VO data management procedures. Call to be organised with partners CNRS Creatis and CNRS IPHC.

Problems and issues we need external help with

None.

Reporting period: May 8th to 21st

Progress

Plans for next period

Problems we encounter, but can solve

None.

Problems and issues we need external help with

None.

Reporting period: Apr. 22nd - May 7th

Progress

Plans for next period

Problems we encounter, but can solve

None.

Problems and issues we need external help with

None.

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Print/export