OSG Council Monthly Teleconference
- Date: April 8th, 2008
- Time: 10:00 AM Pacific Time
- Attending: Michael Ernst (BNL), Rob Quick (EB-Operations), Brad Abbott (DZero), Ruth Pordes (OSG Director), Dick Greenwood (DOSAR), Craig Stewart (Indiana University), Kent Blackburn (OSG Council Chair)
Agenda/Minutes
Status from the OSG Executive Director
- March metric to the JOT and Council will be sent out before the Council Meeting and will speak to this.
- Bi-weekly report to the Council sent out before the meeting and will invite feedback.
Minutes:
Ruth's bi-weekly report was circulated to the OSG Council and OSG Executive Board email lists this morning. They are available at the URL, or from the OSG Council Website under the "Executive Director Reports" Section for April 8th, 2008.
- Kent and Paul have asked that the Executive Director continue to send reports to the Council on a bi-weekly basis.
- Engage VO has ramped up to roughly 30,000 CPU-HR/Day
- Don't expect that the limit for Engage has been reached
- Have held 4 first round quarterly meetings with major scientific stackholders
- March metrics report to the Joint Oversight Team (JOT) attached to email and at the URL above
Ruth pointed out that both ATLAS and CMS are raming up with their CCRC preparations for this May. The impact of this on Engage was not fully understood at this point.
Michael Ernst added that this ramping up has already begun with data production as part of the preparation. ATLAS would very much like to use any resources available. ATLAS will be exercising the full analysis chain in June. Currently US ATLAS has the largest Tier 1 center, making up about 24% of the capacity. The analysis chain would involve every stage from CERN to through the Tier 1, out to the Tier 2s and onto the physicists desktops. ATLAS will know much more at about usage model by the end of June. One of the difficult issues expected to face is data replication.
Formation of "ad-hoc" subcommittee on "At-Large VO Representation"
Purpose: Review the current VO membership of the OSG, compare this with the current representation of the OSG Council members and make a recommendation for a process to appoint the two open "At-Large" representatives. The time line should assure that "At-Large" representatives have been appointed and available for participation no later than by the time of our next face-to-face Council Meeting in approximately 6 months (~September 2008). An important element of this process should be to contact VOs without current representation in order to understand their views of and needs from the OSG Council.
Members: Bill Kramer, Shaowen Wang, Dick Greenwood, Tom Furlani (NYSGrid), Ruth Pordes (ex-officio), ...
Minutes:
Agreed that this "ad-hoc" subcommittee had the appropriate size and composition to be able to move forward with organizing a kick-off meeting and to be able to work towards the goal of appointing two "At-Large" representatives by the time of the next Face-to-Face meeting in September. Subcommittee membership will include either Kent or Paul or both.
- Kent will send out an email to the members of the subcommittee suggesting a kick-off meeting in a few days for sometime in the next week to 10 days.
Formation of "ad-hoc subcommittee on "Re-Organization of OSG Council"
Purpose: Review and make recommendations regarding the organization of the OSG Council. The subcommittee will be charged with making recommendations for changes that are seen to be advantageous to the strategic planning of the Open Science Grid and should include a careful review of the relationship between the OSG Executive Team, The OSG Executive Board and the OSG Council. Additionally, the organizational classification of the OSG representatives could be improved to better capture our membership roles. The subcommittee will be asked to present their findings and make a recommendation at the next face-to-face OSG Council Meeting in approximately 6 months (~September 2008).
Members: Jerome Lauret, Ruth Pordes (ex-officio), ...
Minutes:
Agreed that this "ad-hoc" subcommittee did not have sufficient membership to move forward even with either Kent or Paul or both on board given the importance of the subject matter.
- Kent will send out an email to the council requesting additional members this week.
Council Recommendation for the continued support of MonALISA? at the OSG GOC
Rob Quick of the OSG Grid Operations Center (GOC) has requested that the OSG Council make a decision whether or not to continue to run the
MonALISA? Service at the GOC.
The two most recent emails that have reached the Council co-Chairs on this subject are provided below.
Minutes:
Rob Quick (OSG Executive Board - Operations/GOC) provided the link above to MonALISA? above. Rob proceeded to describe what was provided by MonALISA? and what effort was involved, using the link above as a reference:
- currently provides a very nice interface to data from roughly 25% of the OSG (12 sites reporting to it)
- roughly half of these sites are full reporters and the other half are partial reporters
- Rob pointed out that the active nodes and idle nodes presentation was quite nice for site administrators
Some of the issues that have been reported with MonALISA? are:
- the Java processes in MonALISA? tend to be rather heavy weight, demanding lots of resources from the gatekeeper
- users are unsure of the accuracy of the data being presented with some discrepancies being identified in the past
Rob reported the server at the GOC for MonALISA? was not being supported at a high level so very little effort going into it at present. He estimated that to keep it up would take about 10% of a person, doing maintenance and answering user questions. It also needs hardware and response to issues for the service including security. Michael Ernst felt that this would go up substantially if this was a supported service with a user base to field questions and request from.
Rob asked if anyone new about the network resource allocation to be determined by MonALISA? that Harvey mentioned in his email. Michael Ernst replied that they were using it for a very dedicated reason within their VO.
Michael hesitates to make a call for OSG to focus on MonALISA? give all the other activites that are of a higher priority. Ruth pointed out that CMS management has sent email of a similar stance and that Kent should review these.
Dick was asked to speak as a representative of a community (DOSAR) of proponent for MonaLISA?. Dick said that users within DOSAR have been doing Monte Carlos and the community grew up using MonaLISA? for doing this work. They find the presentation to be very nice. Rob agreed that it had nice presentation.
Kent asked if there were any other services provideing this information. Rob reported that the same information is being collected by CEMon with probes but that the presentation was simple text.
Kent stated that he had first heard about deprecating the MonALISA? service at the All-Hands Meeting in San Diego a little over a year ago. He asked Rob what had been the time line since then. Rob provided the following:
- With the OSG 0.6.0 release, MonALISA? was no longer a default component
- On March 12th 2008 an email was sent out proposing to shutdown the server at the GOC on April 15th 2008
Kent stated that as he saw it we had three fundimental options:
- Discontinue the MonaLISA? service at any level of support, shutting it down at the GOC
- Continue to let it run as is without support other than the existing hardware and power
- Make a commitment to fully support at the cost discussed today
The council responded to these with a preference towards item (2) above. It was pointed out that this would involve simply waiting for this box to die or have to be shutdown for other reasons such as security risks.
The question was raised as to whether or not a VO with sufficient interest in establishing and maintaining this service could easily stand up the service themselves. Rob thought that this was a possibility. It was pointed out that any VO that wanted to do this would need to work closely with Rob and Mine Altunay (OSG Security Officer) to assure a smooth transition. The offer to VOs to stand-up a replacement MonaLISA? service should go out to the OSG Council mailing list. In conclusion, the council representatives on call agreed to the recommentation:
The MonALISA? service/server at the GOC would continue to run until such time as the machine dies or must be turned off due to other external factors such as security risks, etc. The GOC would not replace or restore this service/server after such a failure. A VO is welcome to stand up a replacement MonALISA? service using their own resources but must work with Rob Quick of the GOC and Mine Altunay of Security to assure a smooth, safe and reliable transition.
* Kent will send out an email to the council regarding the recommendation for MonALISA? from the Council
AOB
Minutes:
Kent recognized that there were suggestions for reducing the frequency of Council meetings suggested in Chapel Hill, but he would like to assure a smooth transition from the previous Council Chair to the new Council co-Chairs by continueing for the time being with the monthly telecons on the same schedule, particularly with all the important activities that are currently in the works. The frequency can be revisited after the transition period has been successfully crossed. This was acceptable to all on the call.
--
KentBlackburn - 31 Mar 2008
Topic revision: r12 - 16 Dec 2008 - 16:26:05 -
KyleGross