Dear All,
Please find attached the GridPP Project Management Board
Meeting minutes for the 378th and 379th meetings. The latest minutes can
be found each week in:
http://www.gridpp.ac.uk/php/pmb/minutes.php?latest
as well as being listed with other minutes at:
http://www.gridpp.ac.uk/php/pmb/minutes.php
Cheers, Dave.
--
________________________________________________________________________
Prof. David Britton GridPP Project Leader
Rm 480, Kelvin Building Telephone: +44 141 330 5454
Dept of Physics and Astronomy Telefax: +44-141-330 5881
University of Glasgow EMail: [log in to unmask]
G12 8QQ, UK
________________________________________________________________________
GridPP PMB Minutes 378 (22.02.10)
=================================
Present: John Gordon (Chair), Sarah Pearce remote), Andrew Sansum, Tony Doyle, Jeremy Coles,
Roger Jones, Dave Colling, Robin Middleton, Pete Clarke, (Suzanne Scott, Minutes)
Apologies: David Britton, David Kelsey, Steve Lloyd, Tony Cass, Glenn Patrick, Neil Geddes
1. GridPP4 Proposal - latest status
====================================
JG advised that various actions had been left by DB in relation to v10.0. Submission of the
proposal would happen on 24th. DB would return tomorrow, and SL would update the current
version of the proposal tonight, following any comments today.
It was noted that in the 'Wider Computing Context' former section 12, the beginning paragraphs
had been cut. These could be used within an outline, or as part of a covering letter. The
remainder of the section was now included within a Cloud Computing part in section 7.
In relation to the Tier-2 posts, RJ had sent comments back to DB in relation to the work packages.
DC would also do likewise later today. PC had done the case for Edinburgh, and had sent this to
DB, copied to SL. RJ noted that he took issue with the two Tier-2 Co-ordinators as they seemed to
be justified differently, he had sent his comments to DB. Was TD happy about the ScotGrid post
descriptions? TD noted yes. DK had sent comments to DB on RALPP T2.
JG advised that the meeting would go through the document, dealing with each comment in turn.
The following was agreed:
SL1 - SS to do a page of Acronyms
SP2 - agreed to change to 'Computing in the LHC era'
SP4 - change to '10's' of PetaBytes (this may be mentioned later on in the document also, should
be changed there too)
SP5 - remove 'international' and 'national'
SP6 - change to EGI both times
SP8 - leave as is, but change 'One' UK Tier-2 site to 'A' UK Tier-2 site; and delete sentence after
STEP09.
SP10 - change to 'File Transfer Services'
SP11 - JC to re-write this WP-C section as description, rather than a list
SP12 - add 'Computing' Resource Review Board (CRRB); and in the following paragraph, use the
acronym only
SP13 - move highlighted text to the beginning of section 6.5 (omit 'also)
comment P15 - let DB deal with this feedback (TD noted that a footnote might be better)
SL17 - Alice and Atlas in the table should be in CAPS
On Page 10 (table at top) TD noted that a footnote is required re CPU (KHS06). Move the footnote
on p12 re HEPSPEC to this page.
SP18 - split up these paragraphs into two sections, entitled: 'Group Analysis Sites' and 'Generic
Support' - it was suggested to leave to DB to do.
SP19 - move sentence to beginning of para that starts 'The location of potential EGI funded ...' on
p18
Table 4 (on p17) to be moved to the end of the Tier-2 effort section (on p18)
SP20 - leave as is
SP21 - not sure, DB to decide
SP22/SL23 - fine as is, deleted section could be used in covering letter or in an outline
SL24 - change figure to 100k
SP25 - sentence should be trimmed to be: 'A number of security and privacy issues remain'.
SP27 - list does justify the post, so leave as is
SP28 - omit highlighted text
SP30 - omit highlighted text
SP32 - delete highlighted text, sentence should read: '... GridPP will provide an effective ...'.
SP33 - delete highlighted text; the sentence above should be amended to read: 'The planned posts
will share the operation of the monitoring ...'.
SL34 - leave as is
SP35 - leave as is
SL36 - the meeting supported deleting the highlighted text - DB to decide
SP37 - delete the highlighted text
SP38 - leave as is, SP will provide an added sentence
SL39 - use revised quote if one has been agreed - DB to advise
SP40 - leave as is
SL41 - SP will proof-read these post descriptions on wednesday
P42 - DB to decide, but generally it reads ok as is
SL43 - delete entire sentence that ends in 'assigned'
SP44 - risk register is ok - it prints landscape
PC advised that the proposal seemed in good shape overall. JG noted that any other comments on
10.4 should be advised to SL today; anything new should be circulated to the PMB.
Appendices 21: Project Milestones
---------------------------------
SP had checked if we could just do an annual list, and had been advised yes. JG noted that we
could add that after one whole cycle, the milestones would be reviewed. TD noted that
deployment issues were missing from here. JG asked about the User Board. TD suggested that a
broader operations plan was needed. SP asked whether no 6 should be changed to an operations
plan? There ensued a discussion on the Tier-1 and general review dates. AS had hoped for late
April for a review as the procurement cycle needed feedback from the previous year. It was
agreed that SP should add a GridPP Operations Plan in September, in preparation for the OC
meeting.
ACTION
378.1 SP to add a GridPP Operations Plan within Project Milestones, in September in preparation
for the OC meeting.
Following the above review of points, the document would be handed back to SL this afternoon.
Week's Notes
============
1. GridPP3-4 bridging posts - SP advised that she had the information she needed from TD, but
was awaiting information from DC. He would provide the info this afternoon.
2. Tier-2 JeS forms - STFC had said that grant letters would be sent out today for the Tier-2
hardware, but it appeared that a flat profile had been produced from the JeS forms, and this was
being queried, which meant that the grant letters were delayed.
STANDING ITEMS
==============
SI-1 Tier-1 Manager's Report
-----------------------------
AS reported as follows:
Fabric:
1) The problem lot of disk servers have now passed our acceptance tests and are available for
deployment.
2) FY09 procurements:
- Delivery of the disk servers is scheduled for Mid February with a second tranche from one
supplier on March 4th.
- CPU deliveries are scheduled for mid-February (problems leading to delays to one tranche have
been resolved but we are waiting for a new delivery date).
We are finalising delivery details, but expect several deliveries this week.
3) A meeting to review plans for the UPS supply is scheduled for Tuesday.
4) An initial meeting to plan the FY10 procurements is scheduled for Tuesday. Our intention is to
place orders in September for a December delivery.
5) Planning is underway to commence the migration of CMS to T10KB tape drives.
Service:
1) SAM test availability for the ops VO was 100%.
2) We are experiencing load-related problems on an ATLAS NFS software server. We are
investigating the cause and possible solutions.
SI-2 ATLAS weekly review & plans
---------------------------------
RJ had nothing to report.
SI-3 CMS weekly review & plans
-------------------------------
DC had nothing to report.
SI-4 LHCb weekly review & plans
--------------------------------
GP was absent.
SI-5 Production Manager's Report
---------------------------------
JC reported as follows:
1) With the transition to EGI, EGEE tools and services are being
reviewed. Those that are not widely used are being removed. This is
the case for the site weekly reports – they were part of the CIC
portal for Resource Centres. There is now a consultation about the
dteam VO. The deployment team are keen to keep this VO as it is a
common core that allows help with testing and debugging between
countries. Other transition areas require further understanding. One
that might be of particular concern to GridPP is that of the
operational security tools (such as Pakiti, the secure mail lists and
wiki).
2) The APEL status has much improved in the last week. The database
is now recovered but running “at risk”. Updates can be tracked via
http://goc.grid.sinica.edu.tw/gocwiki/ApelIssues-Jan_Feb_2010
Looking at GridPP site results for January and February there is a
need to check whether gaps are real. For example RAL Tier-1 has a gap
in the last week of January, Oxford and Cambridge that week plus the
start of February, and Manchester misses a large section, and Sheffield,
Durham and ECDF seem to have stopped in January. The message from
APEL support read: “After our integrity checks, we can guarantee that
99.8% of the data have been restored, and we have no reason to think
that the remaining 0.2% have been lost. We however advise all sites to
check their data on the accounting portal and report any
inconsistencies through a GGUS ticket.”
3) As required for any site that schedules a downtime of longer than
1 month, the site UKI-LT2-RHUL has been moved to the status
“suspended”. Once the machine room move has completed and services are
fully available the site will need to be retested to regain certified
status.
4) This week UKI is taking part in a trial of a new Nagios regional
dashboard. This will be run in parallel with the current dashboard to
evaluate it and provide feedback before it is moved into full use. The
plan is to move to a CERN run regional Nagios on 1st March (i.e. move
away from the SAM submission framework – availability will still be
SAM based). Also from 1st March ROCs will be deploying their own
(latest) Nagios that once validated will (from the end of March) take
over from the CERN run regional Nagios.
5) The WLCG Tier-2 availability report for January is now
available:
https://twiki.cern.ch/twiki/bin/viewfile/LCG/SamMbReports?filename=Tier2_Reliab_201001.pd
f
Results overall are down on the previous month (likely due to more
interventions). The (reliability:availability) figures are: London
(96%:95%); NorthGrid (91%:91%); ScotGrid (97%:97%) and SouthGrid (92%:
72%). The SouthGrid figures are due to Oxford cooling problems (late
December until mid-January) and RAL-PPD which has had several outages
due to building power supply interventions and a reconfiguration of
dCache nodes.
6) It was previously reported that benchmarking on SL5 required
further guidance. As it turns out the HEPiX guidelines can be followed
and will lead to a consistent benchmark value. The issue was that
certain libraries were required to run the suite in 32-bit
compatibility mode.
SI-6 LCG Management Board Report
---------------------------------
There was no report.
SI-7 Dissemination
-------------------
SP advised that the STFC event for First Physics would take place in March in London (to coincide
with the CERN event). RJ asked whether there was a Tier-1 inauguration event happening on 30th
March, in the middle of IoP? Yes, however feedback on this had been given. JG noted an action on
DB to resolve the PPRP representation at the meeting in Glasgow - probably not all PMB members
would be required, and some should stay at RHUL as GridPP24 was running simultaneously.
ACTION
378.2 DB to resolve the PPRP representation at the meeting in Glasgow - probably not all PMB
members would be required, and some should stay at RHUL as GridPP24 was running
simultaneously.
REVIEW OF ACTIONS
=================
354.2 JC to consult with site admins on a framework policy for releases, with a mechanism for
escalation, plus a mechanism for monitoring. JC reported that the consultation happened. There
were a few suggestions in the deployment team about how to progress in this area. It needs
writing up and an implementation plan. Ongoing.
366.8 AS to confirm that the Tier-1 proposes to use Tape-based storage in the period 2011 - 2015.
AS noted this depended on money costs. DB advised this related to long-term plans and power
capacity. Physical footprint space? Alternatives? Early action on AS required. AS had sent tech
questions round the team and would forward inputs when available. AS noted that alternative
further costings were required. AS to progress. Ongoing.
367.2 RM to fill-in the grey boxes on DB's UK NGI diagram of a minimal NGI, as to what NGS
would be doing in the areas listed. Ongoing.
RM reported that he had met with Andy Richards, but there was more work to be done and
nothing definitive had been decided. There were ongoing discussions about EGI effort but no
direct answer. DB noted that the PPRP needed to ensure they were not funding beyond the
GridPP remit, and that GridPP were not under threat if NGS4 did not get funded. DB advised that
this issue was important, and information on a UK NGI and NGS remits, would be needed by Wed
24th February when the final version is submitted.
DB would circulate the version of the proposal to SL on Friday, who would have the token until DB
returned. Comments to SL next week.
RM reported that there wasn't enough information available at present to carry out this action.
However for the GridPP4 proposal, RM would speak to Andy Richards and provide a draft to SL by
Wednesday. Ongoing.
375.2 DB to co-ordinate post descriptions for the Tier-2 posts, which should be as unique as
possible in order to present a strong case. Done, item closed.
375.3 TD to do the data posts. TD would do this by Friday and forward to SL. Done, item closed.
375.4 PMB ALL: those relevant to do their own post descriptors. Done, item closed.
375.5 DB to do the Admin Asst post. SS/TD would do this and forward to SL. Done, item closed.
375.9 RM to provide a skeleton outline plan, including post details, of GridPP/NGS convergence.
[Previous action background: SP to work with the working group on the following issues in
relation to GridPP/NGS convergence:
1. identify Institutes
2. identify manpower
3. decide who is bidding for what
- a draft transition plan would be made available by the end of the year; GridPP4 requirements
would also be considered. SP was waiting on
the Working Group to reply to her. A meeting had been held before Christmas re a transition plan.
SP was awaiting a skeleton outline plan from RM, allocating people to sections. This action to be
re-allocated to RM. Done for SP - action closed.]
RM reported that this action was on hold, but ongoing, until a clearer picture emerged. RM noted
that a draft plan was almost finished.
376.1 SP to feed-in management information to SL whilst DB is away (for the proposal document
and in line with RMR information required). Done, item closed.
376.4 All: Risk Register owners to send text comments to SP by the end of the week, including
numbers if possible, but 'low', 'medium' or 'high' was also fine, and the table would be checked at
the next PMB. Done, item closed.
377.1 Re DB's UK NGI diagram of a minimal NGI, as to what NGS would be doing in the areas
listed, RM would speak to Andy Richards and provide a draft to SL by Wednesday for the GridPP4
proposal.
ACTIONS AS AT 22.02.10
======================
354.2 JC to consult with site admins on a framework policy for releases, with a mechanism for
escalation, plus a mechanism for monitoring. JC reported that the consultation happened. There
were a few suggestions in the deployment team about how to progress in this area. It needs
writing up and an implementation plan.
366.8 AS to confirm that the Tier-1 proposes to use Tape-based storage in the period 2011 - 2015.
AS noted this depended on money costs. DB advised this related to long-term plans and power
capacity. Physical footprint space? Alternatives? Early action on AS required. AS had sent tech
questions round the team and would forward inputs when available. AS noted that alternative
further costings were required. AS to progress.
367.2 RM to fill-in the grey boxes on DB's UK NGI diagram of a minimal NGI, as to what NGS
would be doing in the areas listed. RM reported that there wasn't enough information available at
present to carry out this action, but he had met with Andy Richards.
375.9 RM to provide a skeleton outline plan, including post details, of GridPP/NGS convergence.
RM reported that a draft plan would be available soon.
377.1 Re DB's UK NGI diagram of a minimal NGI, as to what NGS would be doing in the areas
listed, RM would speak to Andy Richards and provide a draft to SL by Wednesday for the GridPP4
proposal. This did not now appear to be required for the proposal.
378.1 SP to add a GridPP Operations Plan within Project Milestones, noted for September in
preparation for the OC meeting.
378.2 DB to resolve the PPRP representation at the meeting in Glasgow - probably not all PMB
members would be required, and some should stay at RHUL as GridPP24 was running
simultaneously.
INACTIVE CATEGORY
=================
359.4 JC to follow up dTeam actions from the DB, as follows:
---------------------------
05.02 dTeam to try and sort out CPU shares and priority resources, at
Glasgow first (perhaps by raising the job priority in Panda).
---------------------------
JC would check the situation with Graeme Stewart (who was currently on annual leave).
JC followed up with Graeme and the other experiments. A test was
started but this area has been deemed low priority and further
progress is not expected for some time. ATLAS see no issues with
contention. LHCb are not intending to pursue anything in this area. A
CMS discussion has started but again it does not appear to be urgent.
If the experiments are not pushing this internally then there is
nothing for the deployment team to follow up!
It was noted there was no priority in ATLAS at present, this will be pending for a while. Move to
inactive as it is a long-term action.
---------------------
The next PMB would take place on Monday 1st March at 12:55 pm, chaired by DB.
GridPP PMB Minutes 379 (01.03.10)
=================================
Present: David Britton (Chair), Steve Lloyd, Tony Cass, Glenn Patrick, John Gordon, Sarah Pearce,
Andrew Sansum, Tony Doyle, Jeremy Coles, Dave Colling, Robin Middleton, Pete Clarke (Suzanne
Scott, Minutes)
Apologies: David Kelsey, Roger Jones, Neil Geddes
1. GridPP4 Proposal: next steps
================================
DB reported that the GridPP4 proposal had been submitted last week, as planned, by 5.00 pm on
24th February. DB advised that next steps included the PPRP meeting on 15th April in Glasgow,
as a consequence of which, a number of people will miss the 2nd day of the RHUL meeting.
Between now and then, DB noted that we had to:
a) do some financial planning - led by SP;
b) understand the CERN hardware paper - the CPU was a good costing match but the disk was not
easy to understand - AS to deal with this;
c) more depth required to the Work Breakdown Schedule (WBS) - SP to do;
d) the area of EGI/NGI/NGS needed to be addressed - our arguments need to be refined and
strategy agreed - some background work was needed on this. In relation to Action 367.2, DB
advised RM that now would be a good point to progress this over the next week in order that a
strategy can be developed.
ACTIONS:
379.1 Re GridPP4 proposal and forthcoming PPRP meeting: SP to begin work on 'background'
financial planning.
379.2 Re GridPP4 proposal and forthcoming PPRP meeting: AS to look at the CERN hardware
paper and work on the CPU and disk costings.
379.3 Re GridPP4 proposal and forthcoming PPRP meeting: SP to add more detailed information
to the WBS.
379.4 Re GridPP4 proposal and forthcoming PPRP meeting: RM to progress the EGI/NGI/NGS
model for next week's PMB (in relation to Actions 367.2 & 375.9).
DB advised that his paper on NGI within the GridPP4 Proposal needed to be expanded with new
information, and circulated. An outline on effort was required. RM/SP would assimilate the
information and circulate a new updated paper before next week's PMB. This would be a
transition document addressing the possibility that:
1. There would be no NGI;
2. There would be no future funding for NGS.
ACTION
379.5 RM/SP to assimilate the information in DB's paper on NGI within the GridPP4 Proposal, and
circulate a new updated paper before next week's PMB. This would be a transition document
addressing the possibility that:
1. There would be no NGI;
2. There would be no future funding for NGS.
DB would prepare a talk for the PPRP covering all these subjects. TD advised that Robin Tasker
would be giving a talk on networking at an upcoming JANET meeting. PC advised that next week
there was a JANET OPN meeting, on Monday or Tuesday. TD noted that if the OC documents could
be released as public, then RT could use them. This was agreed.
ACTION
379.6 SL to ensure that the OC documents are made publicly available.
In addition, DB advised that there would be a site visit at RAL around 12-14 May, which was three
weeks following the PPRP meeting. There were no other issues for discussion on the GridPP4
proposal.
2. GridPP24 Agenda
===================
DB had circulated a draft Agenda for GridPP24 at RHUL. DB noted that the meeting theme was
'Data'. SP asked about the inclusion of KE? DB advised that first data should be flowing by April,
the proposal was that Day 1 would incorporate (during 2nd session) talks from the Experiments
on data-taking. The first session would focus on the GridPP4 proposal. SP would summarise the
current status of GridPP3. DB advised that there was room for a headline talk focussed on LHC.
Last time we had Roger Bailey - were there any suggestions for an external speaker? SL could give
a talk? TD thought that someone from CERN would be relevant. DC suggested asking Lyn Evans?
TD commented that it wasn't about the machine so much as about the response to CERN
computing. Would TC be willing to do this? DB noted that the space available straddles steady
data-taking/long-term plans/issues/headlines ... it was about the big picture. TC would think
about it. DB considered that the big picture from someone at the Tier-0 would be useful, giving
scene-setting. On the first day in the afternoon, there would be a CASTOR discussion for the
longer-term. Other Tier-1s were dropping CASTOR, and there were upgrade issues to discuss.
What planning is required to address issues historically seen, etc? The issue of CASTOR needed to
be raised as it is the highest risk in GridPP4. DB asked for opinions from the PMB. AS agreed that
it was sensible to discuss this. DB asked if Matt Viljoen could speak? AS noted yes.
On Day Two, it was noted that those attending the PPRP in Glasgow were those who usually
attend the OC: DB, SL, TD, SP, JG. DB noted there would be the normal site reports on Day Two,
from the Tier-2s. DC would chair the first session. DB would ask the Tier-2s who they wanted to
send as speakers. There would then follow a report from the Storage Workshop (JJ or Wahid
Bhimji). JC would chair the session after coffee. It was agreed that WB, Sam Skipsey, Brian, and JJ
should be on the panel.
For the closing session, RJ could chair if possible. This would cover Tier-1 status (AS or deputy).
Something about EGEE/EGI landscape including NGI was required (not JG), probably RM or NG, or
Andy Richards could deal with this. The slot afterwards could possibly be taken by Will Venters,
talking about Cloud Computing, or Tier-2 questionnaire/incidents, or KE/EI. JG also noted that
sites and shared resources with Universities from a tech point of view, would also be a good
subject to discuss. DB agreed this would be good, but possibly better discussed at Ambleside.
For the DB on Friday, DB and TD did not intend to fly back to RHUL, but SL would. DB would ask
SL for the Deployment Board Agenda. DB would check on sponsorship arrangements.
3. Week's Notes
================
a) Re the GridPP3-4 bridging posts - SP had sent an email to Tony Medland, but had received no
reply as yet.
b) Tier-2 JeS Forms - first grants had now been awarded; new JeS forms were required, but the
funding was assuming a flat spend profile, which was not suitable, and STFC didn't want to change
that.
STANDING ITEMS
==============
SI-1 Tier-1 Manager's Report
-----------------------------
AS reported as follows:
Fabric:
1) FY09 procurements:
- All disk and CPU from one supplier has been delivered.
- 40 of 60 disk servers have been delivered by the second supplier, the remaining disk servers and
all of the CPU will be delivered this week.
2) UPS supplier. Building Projects Group have reviewed the change made (additional cable) to the
UPS supply. There was a 50% improvement in the 3KHz noise. However they have concluded that
adding additional cable is unlikely to meet our requirements for the UPS. They are working on
alternative solutions.
3) The humidification system is now installed in R89.
Service:
1) SAM test availability for the ops VO was 100%.
2) We experienced load-related problems on Monday and Tuesday on an ATLAS software NFS
server. A number of interventions were made to try and address the problem and eventually we
had to stop ATLAS jobs and start with a different job mix. We gradually re-opened the ATLAS job
cap limit through Wednesday and Thursday. Although the problem ceased to manifest we are
unclear whether the cause was a pathological set of ATLAS jobs or a problem in our
capacity/configuration.
SI-2 ATLAS weekly review & plans
---------------------------------
RJ was absent.
SI-3 CMS weekly review & plans
-------------------------------
DC reported that things were on hold, waiting at present.
SI-4 LHCb weekly review & plans
--------------------------------
GP reported a couple of disk server problems last week at the Tier-1. There had been an
incompatibility between root and dCache which was now resolved. They were waiting on data.
SI-5 Production Manager's Report
---------------------------------
JC reported as follows:
1) The DNS for gridpp.ac.uk was down for much of the weekend with
the result that many sites have failed all SAM tests for this period
and the GridPP website has been unavailable. An investigation is
underway as to why the secondary DNS servers have not worked - a post-
mortem report will be available later this week. The problem was known
about over the weekend but could not be solved remotely and there is
no 'on-call' at Manchester. Sites running their own top-level BDII have
been less affected. As yet there have been no user complaints but
anyone using lcg-utils is likely to have been affected as are VOs
running on the GridPP VOMS (no new proxy creation during the period).
Sites want to know the implication for their monthly availability/
reliability figures.
2) Following the APEL outage many GridPP sites have found a need to
republish data for parts of January/February. Checking today it is
evident that several sites still need to republish and others need to
resolve issues to start publishing again.
3) UKQCD have raised a question about merging VO lists – they have
some overlap with and desire to share some data with the international ILDG VO. One
way forward may be to have a single VO and make use of groups/roles.
Will this affect the VO shares? (A question to Glenn / the UB). It was reported that Wahid Bhimji
was looking into this. PC reported that these were two separate VOs and they would want to
share data, but not want to be considered as a single VO. JC would pursue this issue.
ACTION
379.7 JC to follow-up the issue of merging VO lists and ILDG VO.
4) Regional portal testing (using regional Nagios in place of SAM)
last week concluded that there were no showstoppers and deployment
into production of the new dashboards will proceed from today. Bugs/
issues identified by the UKI ROD team have been addressed.
SI-6 LCG Management Board Report
---------------------------------
There was no report.
SI-7 Dissemination Report
--------------------------
SP reported that info on the CERN event was awaited.
AOB
===
JG noted three issues:
1. The Tier-1 was not correctly reporting use of biomed. Biomed had a VO called 'bio', but there
was also a separate VO called 'bio' - and incorrect reporting was affecting the percentage level of
use. JG was flagging this as an issue.
2. JG asked about the definition of seed resources in the work breakdown - Camont had used
1.1%, were there any other VOs we can add to the seed money total? DB suggested phenogrid?
No, they were not applicable here. However, NanoCMOS and Lumerical would certainly be
included. JG was advised to contact Dug McNab at Glasgow for exact details.
3. JG asked about the Chair for NGS - suggestions please. DB noted that GridPP needed to keep a
correct distance in relation to this.
REVIEW OF ACTIONS
=================
354.2 JC to consult with site admins on a framework policy for releases, with a mechanism for
escalation, plus a mechanism for monitoring. JC reported that the consultation happened. There
were a few suggestions in the deployment team about how to progress in this area. It needs
writing up and an implementation plan. Ongoing.
366.8 AS to confirm that the Tier-1 proposes to use Tape-based storage in the period 2011 - 2015.
AS noted this depended on money costs. DB advised this related to long-term plans and power
capacity. Physical footprint space? Alternatives? Early action on AS required. AS had sent tech
questions round the team and would forward inputs when available. AS noted that alternative
further costings were required. AS to progress. Ongoing.
367.2 RM to fill-in the grey boxes on DB's UK NGI diagram of a minimal NGI, as to what NGS
would be doing in the areas listed. RM reported that there wasn't enough information available at
present to carry out this action, but he had met with Andy Richards. Ongoing.
375.9 RM to provide a skeleton outline plan, including post details, of GridPP/NGS convergence.
RM reported that a draft plan would be available soon. Ongoing.
377.1 Re DB's UK NGI diagram of a minimal NGI, as to what NGS would be doing in the areas
listed, RM would speak to Andy Richards and provide a draft to SL by Wednesday for the GridPP4
proposal. This did not now appear to be required for the proposal. Done, item closed.
378.1 SP to add a GridPP Operations Plan within Project Milestones, noted for September in
preparation for the OC meeting. Done, item closed.
378.2 DB to resolve the PPRP representation at the meeting in Glasgow - probably not all PMB
members would be required, and some should stay at RHUL as GridPP24 was running
simultaneously. Done, item closed.
ACTIONS AS AT 01.03.10
======================
354.2 JC to consult with site admins on a framework policy for releases, with a mechanism for
escalation, plus a mechanism for monitoring. JC reported that the consultation happened. There
were a few suggestions in the deployment team about how to progress in this area. It needs
writing up and an implementation plan. JC to progress.
366.8 AS to confirm that the Tier-1 proposes to use Tape-based storage in the period 2011 - 2015.
DB advised this related to long-term plans and power capacity. Physical footprint space?
Alternatives? AS had sent tech questions round the team and would forward inputs when
available. AS noted that alternative further costings were required. AS to progress.
367.2 RM to fill-in the grey boxes on DB's UK NGI diagram of a minimal NGI, as to what NGS
would be doing in the areas listed. RM reported that there wasn't enough information available at
present to carry out this action, but he had met with Andy Richards. RM/SP to circulate a
document.
375.9 RM to provide a skeleton outline plan, including post details, of GridPP/NGS convergence.
RM reported that a draft plan would be available soon. RM/SP to circulate a document
379.1 Re GridPP4 proposal and forthcoming PPRP meeting: SP to begin work on 'background'
financial planning.
379.2 Re GridPP4 proposal and forthcoming PPRP meeting: AS to look at the CERN hardware
paper and work on the CPU and disk costings.
379.3 Re GridPP4 proposal and forthcoming PPRP meeting: SP to add more detailed information
to the WBS.
379.4 Re GridPP4 proposal and forthcoming PPRP meeting: RM to progress the EGI/NGI/NGS
model for next week's PMB (in relation to Actions 367.2 & 375.9).
379.5 RM/SP to assimilate the information in DB's paper on NGI within the GridPP4 Proposal, and
circulate a new updated paper before next week's PMB. This would be a transition document
addressing the possibility that:
1. There would be no NGI;
2. There would be no future funding for NGS.
379.6 SL to ensure that the OC documents are made publicly available [done following the
meeting].
379.7 JC to follow-up the issue of merging VO lists and ILDG VO.
INACTIVE CATEGORY
=================
359.4 JC to follow up dTeam actions from the DB, as follows:
---------------------------
05.02 dTeam to try and sort out CPU shares and priority resources, at
Glasgow first (perhaps by raising the job priority in Panda).
---------------------------
JC would check the situation with Graeme Stewart (who was currently on annual leave).
JC followed up with Graeme and the other experiments. A test was
started but this area has been deemed low priority and further
progress is not expected for some time. ATLAS see no issues with
contention. LHCb are not intending to pursue anything in this area. A
CMS discussion has started but again it does not appear to be urgent.
If the experiments are not pushing this internally then there is
nothing for the deployment team to follow up!
It was noted there was no priority in ATLAS at present, this will be pending for a while. Move to
inactive as it is a long-term action.
---------------------
The next PMB would take place on Monday 8th March at 12:55 pm.
|
