Choose timezone
Your profile timezone:
PASTE meeting
→
Europe/Zurich
2-R-014 (CERN)
2-R-014
CERN
Description
CERN, bat 2 R-014
To join the telephone conference, click here: https://audioconf.cern.ch/call/0165202
To dial in to the conference:
a. Dial +41 22 7676000
b. Enter access code 0165202
PASTE Meeting, 11th January 2011, CERNPASTE Meeting,PASTE Meeting, 11th January 2011, CERN
Chair: A.Tsaregorodtsev
Minutes: F.Stagni
CERN: F.Stagni, R.Santinelli, J.Closier, E.Lanciotti, V.Romanovsky, K.Ciba, S.Reuser, Z.Mathe, P.Charpentier
Phone: A.Tsaregorodtsev, A.Zhelezov
0. Development tasks:
We're not going through the savannah tasks list today.
DIRAC certification testings is a field that needs developing. The certification test that we have now creates 3 production. What is missing is an automatic checker, because right now we make a lot of checks "by hand". Federico might write these tests, working closely with a "certification manager". The certification tests should start from the request, and test all the process involved, the complete "production workflow".
Peter will identify who will be the certification manager. Meanwhile, he agreed on starting to write a document that decribes which operations should be taken to certify a release. After this procedure is clear, it should first of all be applied. Then Federico will start implementing what can be automated. Would it be a good idea using or modifying the existing validation test? Probably yes, Federico will look at it (probably will start to do it not before the next week).
It has also been discussed the possibility to extend the tests to the cases of the user level functionalities: command lines and APIs. Joel has already made some work in this field, and will continue on this path.
Together, certification of the production and user activities, will form a (almost) complete suite of tests.
1. Production Issues
Priority for LHCb: MC can't be stopped, and there are quite a lot of requests that are already done but not processed. What is going to be launched are the largest ones.
Vladimir is going to understand how many MC we can launch, at which pace it goes. Tomorrow morning he'll give us some perspectives.
Replication problem: it is understood. A patch release has to be made, at least to fix the problem with the replication. It also seems that there is some hot-fix, committed by Ricardo, that has not been committed, or that have not been put in a tag. Should this be go in the patch release also?
2. DIRAC Release Update
We have to decide which possibile windows we have to deploy the new release. A possibility is just after Moriond (2nd week of March) and before La Thuile. Alternatively, we could try to deploy it one week before Moriond. In principle, if this last window will be available, DIRAC has to be ready.
LHCbDIRAC will be released as v6r0, while DIRAC could be released as v5r12. Also, the WebPortal needs to be released.
The pre-release cycle started before xmas, we are already at pre-release 10 or 11. Tests have been done, but not everything have been tested. A lot of certification testings still have to run. Alexey will update the web-portal, integration with the bookkeeping has to be assured. Proper tags have to be made also for the web portal. Another pre-release will be compiled this afternoon. After, tests should start: Peter will take care of them; Federico, Vladimir and Andrei will help. There is no rush to start the actual tests: so it is not needed to start them this week.
Philippe wants that all the implications for the new release are written down, so that the actual deployement is not traumatic.
3. DIRAC Tasks
NTR
4. AOB
CHEP papers: only Federico (and Roberto) and Philippe have sent the paper. Recently also the spanish guys sent their paper. Those papers that will not have gone through the internal LHCb review will not be sent.
11th January 2011, PASTEPASTE PASTE Meeting, 11th January 2011, CERN
Chair: A.Tsaregorodtsev
Minutes: F.Stagni
CERN: F.Stagni, R.Santinelli, J.Closier, E.Lanciotti, V.Romanovsky, K.Ciba, S.Reuser, Z.Mathe, P.Charpentier
Phone: A.Tsaregorodtsev, A.Zhelezov
0. Development tasks:
We're not going through the savannah tasks list today.
DIRAC certification testings is a field that needs developing. The certification test that we have now creates 3 production. What is missing is an automatic checker, because right now we make a lot of checks "by hand". Federico might write these tests, working closely with a "certification manager". The certification tests should start from the request, and test all the process involved, the complete "production workflow".
Peter will identify who will be the certification manager. Meanwhile, he agreed on starting to write a document that decribes which operations should be taken to certify a release. After this procedure is clear, it should first of all be applied. Then Federico will start implementing what can be automated. Would it be a good idea using or modifying the existing validation test? Probably yes, Federico will look at it (probably will start to do it not before the next week).
It has also been discussed the possibility to extend the tests to the cases of the user level functionalities: command lines and APIs. Joel has already made some work in this field, and will continue on this path.
Together, certification of the production and user activities, will form a (almost) complete suite of tests.
1. Production Issues
Priority for LHCb: MC can't be stopped, and there are quite a lot of requests that are already done but not processed. What is going to be launched are the largest ones.
Vladimir is going to understand how many MC we can launch, at which pace it goes. Tomorrow morning he'll give us some perspectives.
Replication problem: it is understood. A patch release has to be made, at least to fix the problem with the replication. It also seems that there is some hot-fix, committed by Ricardo, that has not been committed, or that have not been put in a tag. Should this be go in the patch release also?
2. DIRAC Release Update
We have to decide which possibile windows we have to deploy the new release. A possibility is just after Moriond (2nd week of March) and before La Thuile. Alternatively, we could try to deploy it one week before Moriond. In principle, if this last window will be available, DIRAC has to be ready.
LHCbDIRAC will be released as v6r0, while DIRAC could be released as v5r12. Also, the WebPortal needs to be released.
The pre-release cycle started before xmas, we are already at pre-release 10 or 11. Tests have been done, but not everything have been tested. A lot of certification testings still have to run. Alexey will update the web-portal, integration with the bookkeeping has to be assured. Proper tags have to be made also for the web portal. Another pre-release will be compiled this afternoon. After, tests should start: Peter will take care of them; Federico, Vladimir and Andrei will help. There is no rush to start the actual tests: so it is not needed to start them this week.
Philippe wants that all the implications for the new release are written down, so that the actual deployement is not traumatic.
3. DIRAC Tasks
NTR
4. AOB
CHEP papers: only Federico (and Roberto) and Philippe have sent the paper. Recently also the spanish guys sent their paper. Those papers that will not have gone through the internal LHCb review will not be sent.
Meeting, 11th January 2011, CERN
Chair: A.Tsaregorodtsev
Minutes: F.Stagni
CERN: F.Stagni, R.Santinelli, J.Closier, E.Lanciotti, V.Romanovsky, K.Ciba, S.Reuser, Z.Mathe, P.Charpentier
Phone: A.Tsaregorodtsev, A.Zhelezov
0. Development tasks:
We're not going through the savannah tasks list today.
DIRAC certification testings is a field that needs developing. The certification test that we have now creates 3 production. What is missing is an automatic checker, because right now we make a lot of checks "by hand". Federico might write these tests, working closely with a "certification manager". The certification tests should start from the request, and test all the process involved, the complete "production workflow".
Peter will identify who will be the certification manager. Meanwhile, he agreed on starting to write a document that decribes which operations should be taken to certify a release. After this procedure is clear, it should first of all be applied. Then Federico will start implementing what can be automated. Would it be a good idea using or modifying the existing validation test? Probably yes, Federico will look at it (probably will start to do it not before the next week).
It has also been discussed the possibility to extend the tests to the cases of the user level functionalities: command lines and APIs. Joel has already made some work in this field, and will continue on this path.
Together, certification of the production and user activities, will form a (almost) complete suite of tests.
1. Production Issues
Priority for LHCb: MC can't be stopped, and there are quite a lot of requests that are already done but not processed. What is going to be launched are the largest ones.
Vladimir is going to understand how many MC we can launch, at which pace it goes. Tomorrow morning he'll give us some perspectives.
Replication problem: it is understood. A patch release has to be made, at least to fix the problem with the replication. It also seems that there is some hot-fix, committed by Ricardo, that has not been committed, or that have not been put in a tag. Should this be go in the patch release also?
2. DIRAC Release Update
We have to decide which possibile windows we have to deploy the new release. A possibility is just after Moriond (2nd week of March) and before La Thuile. Alternatively, we could try to deploy it one week before Moriond. In principle, if this last window will be available, DIRAC has to be ready.
LHCbDIRAC will be released as v6r0, while DIRAC could be released as v5r12. Also, the WebPortal needs to be released.
The pre-release cycle started before xmas, we are already at pre-release 10 or 11. Tests have been done, but not everything have been tested. A lot of certification testings still have to run. Alexey will update the web-portal, integration with the bookkeeping has to be assured. Proper tags have to be made also for the web portal. Another pre-release will be compiled this afternoon. After, tests should start: Peter will take care of them; Federico, Vladimir and Andrei will help. There is no rush to start the actual tests: so it is not needed to start them this week.
Philippe wants that all the implications for the new release are written down, so that the actual deployement is not traumatic.
3. DIRAC Tasks
NTR
4. AOB
CHEP papers: only Federico (and Roberto) and Philippe have sent the paper. Recently also the spanish guys sent their paper. Those papers that will not have gone through the internal LHCb review will not be sent.
Meeting, 11th January 2011, CERN
Chair: A.Tsaregorodtsev
Minutes: F.Stagni
CERN: F.Stagni, R.Santinelli, J.Closier, E.Lanciotti, V.Romanovsky, K.Ciba, S.Reuser, Z.Mathe, P.Charpentier
Phone: A.Tsaregorodtsev, A.Zhelezov
0. Development tasks:
We're not going through the savannah tasks list today.
DIRAC certification testings is a field that needs developing. The certification test that we have now creates 3 production. What is missing is an automatic checker, because right now we make a lot of checks "by hand". Federico might write these tests, working closely with a "certification manager". The certification tests should start from the request, and test all the process involved, the complete "production workflow".
Peter will identify who will be the certification manager. Meanwhile, he agreed on starting to write a document that decribes which operations should be taken to certify a release. After this procedure is clear, it should first of all be applied. Then Federico will start implementing what can be automated. Would it be a good idea using or modifying the existing validation test? Probably yes, Federico will look at it (probably will start to do it not before the next week).
It has also been discussed the possibility to extend the tests to the cases of the user level functionalities: command lines and APIs. Joel has already made some work in this field, and will continue on this path.
Together, certification of the production and user activities, will form a (almost) complete suite of tests.
1. Production Issues
Priority for LHCb: MC can't be stopped, and there are quite a lot of requests that are already done but not processed. What is going to be launched are the largest ones.
Vladimir is going to understand how many MC we can launch, at which pace it goes. Tomorrow morning he'll give us some perspectives.
Replication problem: it is understood. A patch release has to be made, at least to fix the problem with the replication. It also seems that there is some hot-fix, committed by Ricardo, that has not been committed, or that have not been put in a tag. Should this be go in the patch release also?
2. DIRAC Release Update
We have to decide which possibile windows we have to deploy the new release. A possibility is just after Moriond (2nd week of March) and before La Thuile. Alternatively, we could try to deploy it one week before Moriond. In principle, if this last window will be available, DIRAC has to be ready.
LHCbDIRAC will be released as v6r0, while DIRAC could be released as v5r12. Also, the WebPortal needs to be released.
The pre-release cycle started before xmas, we are already at pre-release 10 or 11. Tests have been done, but not everything have been tested. A lot of certification testings still have to run. Alexey will update the web-portal, integration with the bookkeeping has to be assured. Proper tags have to be made also for the web portal. Another pre-release will be compiled this afternoon. After, tests should start: Peter will take care of them; Federico, Vladimir and Andrei will help. There is no rush to start the actual tests: so it is not needed to start them this week.
Philippe wants that all the implications for the new release are written down, so that the actual deployement is not traumatic.
3. DIRAC Tasks
NTR
4. AOB
CHEP papers: only Federico (and Roberto) and Philippe have sent the paper. Recently also the spanish guys sent their paper. Those papers that will not have gone through the internal LHCb review will not be sent.
CERN
Chair: A.Tsaregorodtsev
Minutes: F.Stagni
CERN: F.Stagni, R.Santinelli, J.Closier, E.Lanciotti, V.Romanovsky, K.Ciba, S.Reuser, Z.Mathe, P.Charpentier
Phone: A.Tsaregorodtsev, A.Zhelezov
0. Development tasks:
We're not going through the savannah tasks list today.
DIRAC certification testings is a field that needs developing. The certification test that we have now creates 3 production. What is missing is an automatic checker, because right now we make a lot of checks "by hand". Federico might write these tests, working closely with a "certification manager". The certification tests should start from the request, and test all the process involved, the complete "production workflow".
Peter will identify who will be the certification manager. Meanwhile, he agreed on starting to write a document that decribes which operations should be taken to certify a release. After this procedure is clear, it should first of all be applied. Then Federico will start implementing what can be automated. Would it be a good idea using or modifying the existing validation test? Probably yes, Federico will look at it (probably will start to do it not before the next week).
It has also been discussed the possibility to extend the tests to the cases of the user level functionalities: command lines and APIs. Joel has already made some work in this field, and will continue on this path.
Together, certification of the production and user activities, will form a (almost) complete suite of tests.
1. Production Issues
Priority for LHCb: MC can't be stopped, and there are quite a lot of requests that are already done but not processed. What is going to be launched are the largest ones.
Vladimir is going to understand how many MC we can launch, at which pace it goes. Tomorrow morning he'll give us some perspectives.
Replication problem: it is understood. A patch release has to be made, at least to fix the problem with the replication. It also seems that there is some hot-fix, committed by Ricardo, that has not been committed, or that have not been put in a tag. Should this be go in the patch release also?
2. DIRAC Release Update
We have to decide which possibile windows we have to deploy the new release. A possibility is just after Moriond (2nd week of March) and before La Thuile. Alternatively, we could try to deploy it one week before Moriond. In principle, if this last window will be available, DIRAC has to be ready.
LHCbDIRAC will be released as v6r0, while DIRAC could be released as v5r12. Also, the WebPortal needs to be released.
The pre-release cycle started before xmas, we are already at pre-release 10 or 11. Tests have been done, but not everything have been tested. A lot of certification testings still have to run. Alexey will update the web-portal, integration with the bookkeeping has to be assured. Proper tags have to be made also for the web portal. Another pre-release will be compiled this afternoon. After, tests should start: Peter will take care of them; Federico, Vladimir and Andrei will help. There is no rush to start the actual tests: so it is not needed to start them this week.
Philippe wants that all the implications for the new release are written down, so that the actual deployement is not traumatic.
3. DIRAC Tasks
NTR
4. AOB
CHEP papers: only Federico (and Roberto) and Philippe have sent the paper. Recently also the spanish guys sent their paper. Those papers that will not have gone through the internal LHCb review will not be sent.
Chair: A.Tsaregorodtsev
Minutes: F.Stagni
CERN: F.Stagni, R.Santinelli, J.Closier, E.Lanciotti, V.Romanovsky, K.Ciba, S.Reuser, Z.Mathe, P.Charpentier
Phone: A.Tsaregorodtsev, A.Zhelezov
0. Development tasks:
We're not going through the savannah tasks list today.
DIRAC certification testings is a field that needs developing. The certification test that we have now creates 3 production. What is missing is an automatic checker, because right now we make a lot of checks "by hand". Federico might write these tests, working closely with a "certification manager". The certification tests should start from the request, and test all the process involved, the complete "production workflow".
Peter will identify who will be the certification manager. Meanwhile, he agreed on starting to write a document that decribes which operations should be taken to certify a release. After this procedure is clear, it should first of all be applied. Then Federico will start implementing what can be automated. Would it be a good idea using or modifying the existing validation test? Probably yes, Federico will look at it (probably will start to do it not before the next week).
It has also been discussed the possibility to extend the tests to the cases of the user level functionalities: command lines and APIs. Joel has already made some work in this field, and will continue on this path.
Together, certification of the production and user activities, will form a (almost) complete suite of tests.
1. Production Issues
Priority for LHCb: MC can't be stopped, and there are quite a lot of requests that are already done but not processed. What is going to be launched are the largest ones.
Vladimir is going to understand how many MC we can launch, at which pace it goes. Tomorrow morning he'll give us some perspectives.
Replication problem: it is understood. A patch release has to be made, at least to fix the problem with the replication. It also seems that there is some hot-fix, committed by Ricardo, that has not been committed, or that have not been put in a tag. Should this be go in the patch release also?
2. DIRAC Release Update
We have to decide which possibile windows we have to deploy the new release. A possibility is just after Moriond (2nd week of March) and before La Thuile. Alternatively, we could try to deploy it one week before Moriond. In principle, if this last window will be available, DIRAC has to be ready.
LHCbDIRAC will be released as v6r0, while DIRAC could be released as v5r12. Also, the WebPortal needs to be released.
The pre-release cycle started before xmas, we are already at pre-release 10 or 11. Tests have been done, but not everything have been tested. A lot of certification testings still have to run. Alexey will update the web-portal, integration with the bookkeeping has to be assured. Proper tags have to be made also for the web portal. Another pre-release will be compiled this afternoon. After, tests should start: Peter will take care of them; Federico, Vladimir and Andrei will help. There is no rush to start the actual tests: so it is not needed to start them this week.
Philippe wants that all the implications for the new release are written down, so that the actual deployement is not traumatic.
3. DIRAC Tasks
NTR
4. AOB
CHEP papers: only Federico (and Roberto) and Philippe have sent the paper. Recently also the spanish guys sent their paper. Those papers that will not have gone through the internal LHCb review will not be sent.
There are minutes attached to this event.
Show them.