tobias haas: htasc htasc: a technical advisory subcommittee for hepccc tobias haas chairperson of...

10

Click here to load reader

Upload: marjory-cook

Post on 20-Jan-2018

212 views

Category:

Documents


0 download

DESCRIPTION

Tobias Haas: HTASC History HTASC was founded in 1995 on the initiative of the George Kalmus, then Chairman of HEPCCC. HTASC was founded in 1995 on the initiative of the George Kalmus, then Chairman of HEPCCC. Mandate: Mandate: The HEP-CCC Technical Advisory Subcommittee (HTASC) is a subcommittee of HEP-CCC. The HEP-CCC Technical Advisory Subcommittee (HTASC) is a subcommittee of HEP-CCC. Each member of Restricted ECFA nominates a member of HTASC (implicitly for his country). Each member of Restricted ECFA nominates a member of HTASC (implicitly for his country). It should provide the HEP-CCC with advice on: It should provide the HEP-CCC with advice on: future requirements in all areas of computing and networking. future requirements in all areas of computing and networking. The technical solutions to current and future computing and networking problems. The technical solutions to current and future computing and networking problems. This advice should be in the form of clear recommendations with the technical, financial, strategic and "political" implications spelled out. This advice should be in the form of clear recommendations with the technical, financial, strategic and "political" implications spelled out. The areas to be examined by the HTASC may be at the request of the HEPCCC or may be initiated by the HTASC itself. The areas to be examined by the HTASC may be at the request of the HEPCCC or may be initiated by the HTASC itself. In order to carry out this mission, the HTASC may form specialist panels. These panels should be working groups with specific goals and time scales. Their role and composition should be endorsed by the HTASC and brought to the HEP-CCC for confirmation. Their mandate should be re-examined regularly (e.g. every 2 years). In order to carry out this mission, the HTASC may form specialist panels. These panels should be working groups with specific goals and time scales. Their role and composition should be endorsed by the HTASC and brought to the HEP-CCC for confirmation. Their mandate should be re-examined regularly (e.g. every 2 years). The HTASC replaces the HEPnet Technical Committee (HTC) and also the HEPnet Requirement Committee (HRC). The HTASC replaces the HEPnet Technical Committee (HTC) and also the HEPnet Requirement Committee (HRC). The chairman is nominated for three years. The chairman is nominated for three years.

TRANSCRIPT

Page 1: Tobias Haas: HTASC HTASC: A Technical Advisory Subcommittee for HEPCCC Tobias Haas Chairperson of HTASC…

Tobias Haas: HTASCTobias Haas: HTASC

HTASC:HTASC:A Technical Advisory A Technical Advisory

Subcommittee for HEPCCCSubcommittee for HEPCCC

Tobias HaasTobias HaasChairperson of HTASCChairperson of HTASC

11stst iHEPCCC, 17 May, 2004 iHEPCCC, 17 May, 2004

Page 2: Tobias Haas: HTASC HTASC: A Technical Advisory Subcommittee for HEPCCC Tobias Haas Chairperson of HTASC…

Tobias Haas: HTASCTobias Haas: HTASC

This PresentationThis PresentationFunctioning of HTASCFunctioning of HTASC

MandateMandateHistoryHistoryMembershipMembershipTopicsTopics

My personal view on HTASCMy personal view on HTASC

Page 3: Tobias Haas: HTASC HTASC: A Technical Advisory Subcommittee for HEPCCC Tobias Haas Chairperson of HTASC…

Tobias Haas: HTASCTobias Haas: HTASC

HistoryHistory HTASC was founded in 1995 on the initiative of the George Kalmus, then HTASC was founded in 1995 on the initiative of the George Kalmus, then

Chairman of HEPCCC.Chairman of HEPCCC. Mandate:Mandate:

The HEP-CCC Technical Advisory Subcommittee (HTASC) is a subcommittee of The HEP-CCC Technical Advisory Subcommittee (HTASC) is a subcommittee of HEP-CCC. HEP-CCC.

Each member of Restricted ECFA nominates a member of HTASC (implicitly for Each member of Restricted ECFA nominates a member of HTASC (implicitly for his country). his country).

It should provide the HEP-CCC with advice on: It should provide the HEP-CCC with advice on: future requirements in all areas of computing and networking. future requirements in all areas of computing and networking. The technical solutions to current and future computing and networking problems. The technical solutions to current and future computing and networking problems. This advice should be in the form of clear recommendations with the technical, This advice should be in the form of clear recommendations with the technical,

financial, strategic and "political" implications spelled out. financial, strategic and "political" implications spelled out. The areas to be examined by the HTASC may be at the request of the HEPCCC or The areas to be examined by the HTASC may be at the request of the HEPCCC or

may be initiated by the HTASC itself. may be initiated by the HTASC itself. In order to carry out this mission, the HTASC may form specialist panels . These In order to carry out this mission, the HTASC may form specialist panels . These

panels should be working groups with specific goals and time scales. Their role and panels should be working groups with specific goals and time scales. Their role and composition should be endorsed by the HTASC and brought to the HEP-CCC for composition should be endorsed by the HTASC and brought to the HEP-CCC for confirmation. Their mandate should be re-examined regularly (e.g. every 2 years). confirmation. Their mandate should be re-examined regularly (e.g. every 2 years).

The HTASC replaces the HEPnet Technical Committee (HTC) and also the HEPnet The HTASC replaces the HEPnet Technical Committee (HTC) and also the HEPnet Requirement Committee (HRC). Requirement Committee (HRC).

The chairman is nominated for three years.The chairman is nominated for three years.

Page 4: Tobias Haas: HTASC HTASC: A Technical Advisory Subcommittee for HEPCCC Tobias Haas Chairperson of HTASC…

Tobias Haas: HTASCTobias Haas: HTASC

HistoryHistory Chair:Chair:

M. Kasemann (1995 – 1998)M. Kasemann (1995 – 1998) D. Kelsey (1998 – 2001 )D. Kelsey (1998 – 2001 ) T. Haas (2001 – present )T. Haas (2001 – present )

Membership:Membership: Currently 19 members.Currently 19 members.

Meetings:Meetings: 3 times a year, usually ahead of HEPCCC3 times a year, usually ahead of HEPCCC 26 Meetings were held since 199526 Meetings were held since 1995 Attendance usually 10 – 15 Attendance usually 10 – 15

Page 5: Tobias Haas: HTASC HTASC: A Technical Advisory Subcommittee for HEPCCC Tobias Haas Chairperson of HTASC…

Tobias Haas: HTASCTobias Haas: HTASC

Current MembershipCurrent Membership Chairperson: Chairperson: Tobias HaasTobias Haas Austria: Austria: Gerhard Gerhard WalzelWalzel Belgium: Belgium: Rosette Rosette VandenbrouckeVandenbroucke CERN: CERN: Jürgen KnoblochJürgen Knobloch

(Scientific Secretary)(Scientific Secretary) Czech republic: Czech republic: Milos Milos LokajicekLokajicek Denmark: Denmark: BjornBjorn S. Nilsson S. Nilsson France: France: Francois EtienneFrancois Etienne Germany: Germany: Rainer Rainer MankelMankel Greece: Greece: Emmanuel Emmanuel FloratosFloratos Hungary: Hungary: JozsefJozsef KadlecsikKadlecsik Italy: Italy: Gian Piero SiroliGian Piero Siroli

(Webmaster)(Webmaster) Netherlands: Netherlands: ElsEls de Wolf de Wolf

Norway: Norway: OlaOla BorrebakBorrebak Poland: Poland: Grzegorz Grzegorz PolokPolok Portugal: Portugal: Jorge GomesJorge Gomes Slovakia: Slovakia: Peter Peter ChochulaChochula Spain: Spain: NicanorNicanor ColinoColino Switzerland: Christophorus GrabSwitzerland: Christophorus Grab United Kingdom: Dave BaileyUnited Kingdom: Dave Bailey Observers:Observers:

United States: Irwin GainesUnited States: Irwin Gaines Japan: Setsuya KawabataJapan: Setsuya Kawabata

Page 6: Tobias Haas: HTASC HTASC: A Technical Advisory Subcommittee for HEPCCC Tobias Haas Chairperson of HTASC…

Tobias Haas: HTASCTobias Haas: HTASC

TopicsTopics International Network International Network

Monitoring (95)Monitoring (95) EU 4EU 4thth Framework Project Framework Project

Proposals (95)Proposals (95) Mail Servers (96)Mail Servers (96) Distributed Editing of Papers Distributed Editing of Papers

(96 – 98)(96 – 98) Win (NT/2K/XP coordination Win (NT/2K/XP coordination

(96 – 04)(96 – 04) SW Licensing (96)SW Licensing (96) Wide Area Filesystems like Wide Area Filesystems like

AFS/DFS (97/01/02)AFS/DFS (97/01/02) Programming Languages (97)Programming Languages (97) Network Security (99/02)Network Security (99/02) Y2K (99)Y2K (99)

Videoconferencing (99-04)Videoconferencing (99-04) OO Technology (99)OO Technology (99) Differenciated Network Differenciated Network

Services (QoS) (00)Services (QoS) (00) LDAP (00)LDAP (00) Regional Centers (00)Regional Centers (00) X.509 Certificates (00)X.509 Certificates (00) Cost and Size of NRENs (02)Cost and Size of NRENs (02) Traveling Physicist (03)Traveling Physicist (03) Cooperation of Tier2 Centers Cooperation of Tier2 Centers

(03) (03)

Page 7: Tobias Haas: HTASC HTASC: A Technical Advisory Subcommittee for HEPCCC Tobias Haas Chairperson of HTASC…

Tobias Haas: HTASCTobias Haas: HTASC

Documentation and Documentation and Interaction with HEPCCCInteraction with HEPCCC

All info available on the WEB:All info available on the WEB: Home: http://htasc.pi.infn.it/Home: http://htasc.pi.infn.it/

MandateMandate MembershipMembership Meeting Dates/VenuesMeeting Dates/Venues DocumentsDocuments

Meeting Agendae: Meeting Agendae: http://agenda.cern.ch/displayLevel.php?fid=57http://agenda.cern.ch/displayLevel.php?fid=57

Chairman of HTASC is a member of HEPCCC Chairman of HTASC is a member of HEPCCC and reports at every meeting on HTASC and reports at every meeting on HTASC activities.activities.

Page 8: Tobias Haas: HTASC HTASC: A Technical Advisory Subcommittee for HEPCCC Tobias Haas Chairperson of HTASC…

Tobias Haas: HTASCTobias Haas: HTASC

My View on HTASC … My View on HTASC … What is good:What is good:

HTASC is a HTASC is a standingstanding committee: committee: The threshold for getting a discussion on a specific topic is The threshold for getting a discussion on a specific topic is

small.small. HTASC has generally reacted to HEPCCC requests HTASC has generally reacted to HEPCCC requests

in a in a timelytimely fashion. fashion. HTASC has been able to provide HEPCCC with HTASC has been able to provide HEPCCC with

qualifiedqualified advice in an extremely wide range of advice in an extremely wide range of computing topicscomputing topics

HTASC has also been able to HTASC has also been able to feed information “down”feed information “down” from HEPCCC in particular to smaller countries not as from HEPCCC in particular to smaller countries not as well connected to the HEP computing mainstream. well connected to the HEP computing mainstream. This has been the prime This has been the prime motivationmotivation for many for many members to participate.members to participate.

Page 9: Tobias Haas: HTASC HTASC: A Technical Advisory Subcommittee for HEPCCC Tobias Haas Chairperson of HTASC…

Tobias Haas: HTASCTobias Haas: HTASC

… … my View on HTASCmy View on HTASC What is bad:What is bad:

The true cost of sending a request to HTASC is not The true cost of sending a request to HTASC is not accounted for.accounted for.

HTASC spends significant resources:HTASC spends significant resources: time spent by members and in particular the chairperson.time spent by members and in particular the chairperson. traveltravel

HTASC can solicit contributions by good will only: HTASC can solicit contributions by good will only: Cannot even pay travel cost to invited experts. This Cannot even pay travel cost to invited experts. This limits the reach on expert knowledge.limits the reach on expert knowledge.

Page 10: Tobias Haas: HTASC HTASC: A Technical Advisory Subcommittee for HEPCCC Tobias Haas Chairperson of HTASC…

Tobias Haas: HTASCTobias Haas: HTASC

My personal SummaryMy personal SummaryA body like HTASC can be very useful but A body like HTASC can be very useful but

its cost must be considered with careits cost must be considered with careThe motivation for people to serve on The motivation for people to serve on

HTASC must be kept in mind:HTASC must be kept in mind:Added value for the members:Added value for the members:

Information feed downInformation feed down