Tags:
tag this topic
create new tag
view all tags
<!-- keep this as a security measure: * Set ALLOWTOPICCHANGE = Main.TWikiAdminGroup,Main.LCGAdminGroup * Set ALLOWTOPICRENAME = Main.TWikiAdminGroup,Main.LCGAdminGroup #uncomment this if you want the page only be viewable by the internal people # * Set ALLOWTOPICVIEW = Main.TWikiAdminGroup,Main.LCGAdminGroup,Main.ChippComputingBoardGroup --> ---+ Communication Channels between CSCS and CHIPP ---++ Twiki Advantages: * can optimally present information, full layout control * multiple people can collaborate on the same page * change record (including who) and playback of old page versions * authn/authz * can set mail notifications or RSS news feeds Disadvantages * takes a bit longer then the average email * needs discipline to keep some order in the pages (try to keep a minimum of pages) * %BLUE%Pablo: multiple colaboration is clumsy%ENDCOLOR% Usage: * main information portal for users * main documentation portal for admins and users * principal place for finding all quasi-static information on the system * *VOs must specify their requirements in relation to the local Grid services on a wiki page*, so that this information is accessible for the CSCS admins. This is needed, since the CSCS admins cannot be expected to follow the internal VO discussions, and often even do not have access to the restricted CERN VO twiki areas or indico * [[CMSInfoPages#CMS_Requirements][Example from CMS]] that certainly could be improved * %RED%Sigve: ATLAS should have this link https://cic.gridops.org/index.php?section=vo&vo=atlas .%ENDCOLOR% * %RED%Sigve: This will be Marc's duty since he is following the ATLAS FZK Clould meetings.%ENDCOLOR% * log book of events (for admins, but also for VOs, if wanted. e.g. look at the CMSSiteLog) * %BLUE%Pablo: we think it's a great tool for documentation, issues reports, operations, minutes, resource description, but not for organization or interactive work%ENDCOLOR%<span style="color: #0000ff" class="Apple-style-span"> </span> ---++ Trouble tickets (grid-rt@cscs.ch) Advantages: * tracked with open/closed status, so issues are not lost * all changes to the ticket are tracked Disadvantage: * Information spread over multiple entries * only submitter and local admins see the issues Usage: * submission of support requests and bug reports by the VO site contacts. They should also have access to the web front end. * Do we want users to submit to this, too? Or rather have all users use the GGUS or go via site contacts? * requests, e.g. for the installation of a machine or a service * %BLUE%Pablo: preferred over IRC for bugs/issue/requests, because has better tracking/logging.%ENDCOLOR% * %RED%Sigve: I would like to have only one ticket portal for our sites in Switzerland. Can grid-rt@cscs.ch "subscribe" to http://rt.smscg.ch/ ? %ENDCOLOR% ---++ Mailing lists Advantages: * small effort * people can filter or put triggers in their clients * archived Disadvantages * information scattered throughout threads * bad to locate information * %RED%Sigve: Which lists do we actually have now ? With the 2 below I think I would be on 5 lists from cscs. Then there is also the smscg lists which contain the main ARC expertise in Switzerland. Is it possible to have less lists ?%ENDCOLOR% | tier2-users_at_cscs.ch | used for broadcasting downtimes and generally technically relevant messages for users who rely on the local resources of the PHOENIX cluster (e.g. on the storage accessibility | | {$VO}-users_at_cscs.ch | subscribed to tier2-users list, also may receive VO specific messages and can be used for discussions among users (VO site contacts read it, too) | | %BLUE%voreps_at_cscs.ch%ENDCOLOR% | %BLUE%Where the VO Representatives and their deputies can be reached for announcements, issues and requests from CSCS side %ENDCOLOR% | ---++ Chat Advantages: * interactive, fast %BLUE%(Pablo: for simple things)%ENDCOLOR% * logged, so historic information is available Disadvantages: * information is scattered, searching through chat logs is a pain * bad if there are multiple simultaneous discussions going on * %BLUE%Pablo: discussions can get really slow%ENDCOLOR% CSCS admins and VO-contacts try to be present on the chat. Usage: * emergencies %BLUE%Pablo: We can also use the phone, maybe we should make a small phone directory%ENDCOLOR% * request for fast information * working together on a service, debugging * discussions %BLUE%(Pablo: no please)%ENDCOLOR% * %RED%Sigve: For other work I usually use Skype chat. Then one can also easily make a phone discussion among several participants. Don't know if that would be an alternative for us.%ENDCOLOR% ---++ EVO/Phone Meetings %BLUE%Pablo: We don't think there's a good system above to have discussions. It would be great if we can fix a day every second week when we can join an EVO meeting and discuss whatever needs to be discussed. Either that, or a phone meeting, involving all VO Reps and CSCS. %ENDCOLOR% -- Main.DerekFeichtinger - 2010-06-30
E
dit
|
A
ttach
|
Watch
|
P
rint version
|
H
istory
: r5
<
r4
<
r3
<
r2
<
r1
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r5 - 2014-02-12
-
PabloFernandez
LCGTier2
Log In
(Topic)
LCGTier2 Web
Create New Topic
Index
Search
Changes
Notifications
Statistics
Preferences
Users
Entry point / Contact
RoadMap
ATLAS Pages
CMS Pages
CMS User Howto
CHIPP CB
Outreach
Technical
Cluster details
Services
Hardware and OS
Tools & Tips
Monitoring
Logs
Maintenances
Meetings
Tests
Issues
Blog
Home
Site map
CmsTier3 web
LCGTier2 web
PhaseC web
Main web
Sandbox web
TWiki web
LCGTier2 Web
Users
Groups
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
P
P
View
Raw View
Print version
Find backlinks
History
More topic actions
Edit
Raw edit
Attach file or image
Edit topic preference settings
Set new parent
More topic actions
Warning: Can't find topic "".""
Account
Log In
E
dit
A
ttach
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback