| | 1 | = SDSC Meeting on 02AUG07 = |
| | 2 | |
| | 3 | Here is a summary of our previous [wiki:CADAC/Telecon26JUL07 telecon], and the basic agenda for our meeting with SDSC. |
| | 4 | |
| | 5 | = Contents = |
| | 6 | |
| | 7 | 1. Our telecon last Thursday. |
| | 8 | 2. Tentative agenda for meeting with SDSC. |
| | 9 | |
| | 10 | == Telecon Summary == |
| | 11 | |
| | 12 | === TODO Summary === |
| | 13 | |
| | 14 | 1. Write up policies on data access, archive structure and contributed software. |
| | 15 | 2. Write up instructions on getting SRB clients and putting, getting data. |
| | 16 | 3. Put up a website with general information, the policies and instructions. |
| | 17 | 4. Mike will announce the CADAC at the end of the first day of the workshop. |
| | 18 | |
| | 19 | === Decisions === |
| | 20 | |
| | 21 | Please check my original email for what the summary of each topic was. |
| | 22 | |
| | 23 | 1. Data access policy |
| | 24 | |
| | 25 | Data contained within the archive (i.e., in the SRB vault on GPFS), will be readable by all CADAC members, and writable by the contributor. |
| | 26 | |
| | 27 | 2. Archive Structure |
| | 28 | |
| | 29 | Data will be stored by contributor, e.g., /home/padoan.cadac. Each user will be responsible for organizing their data, and documenting the organization of the data. |
| | 30 | |
| | 31 | 3. Web site |
| | 32 | |
| | 33 | Website needs the following: |
| | 34 | |
| | 35 | * Information from the LRAC |
| | 36 | * Policies |
| | 37 | * Instructions |
| | 38 | * Member list |
| | 39 | |
| | 40 | Timeline: If the website is presentable by August 7th, we can start making announcements. |
| | 41 | |
| | 42 | Update: Jake has just hacked apart the LRAC proposal, so we have the foundation of a site. I've poked around in the web site files, but I'm waiting for permissions to write to it. Once I do, I'm going to go for temporarily hiding the current portal, since it's totally insecure. Jake and I can add content by hand for now. |
| | 43 | |
| | 44 | 4. User support responsibility |
| | 45 | |
| | 46 | This will be largely split between Jake and SDSC. And we need to draw at least a fuzzy line between the two. Tentatively, Paolo will help support Jake at about 25%. See also the bullet in the agenda for the next meeting. |
| | 47 | |
| | 48 | 5. Organizing contributed software |
| | 49 | |
| | 50 | Users will place contributed software in a "cadac" directory in their home directory, like /users/ucsd/padoan/cadac. The directory should be group readable and executable. Again, documentation in the directory is a good idea. |
| | 51 | |
| | 52 | 6. User accounts |
| | 53 | |
| | 54 | Paolo has the ability to add users under the startup SU's, and we can add users to the SRB at any time. See SDSC agenda for our other questions. |
| | 55 | |
| | 56 | == SDSC Meeting Agenda == |
| | 57 | |
| | 58 | 1. CADAC Group |
| | 59 | |
| | 60 | We need a group account on DataStar and the SDSC TeraGrid machines for the CADAC users. Currently, the srbVault is showing up under uic221, which is Mike's group. |
| | 61 | |
| | 62 | 2. Level of support |
| | 63 | |
| | 64 | Where do we draw the fuzzy line between standard SDSC support requests, and CADAC specific stuff? |
| | 65 | |
| | 66 | 3. Adding new users |
| | 67 | |
| | 68 | * What is the fastest and simplest method for adding users? |
| | 69 | * How do we ensure that users are added to the SRB? |
| | 70 | |
| | 71 | 4. Mailing list |
| | 72 | |
| | 73 | How do we set up an archived mailing list for CADAC users? |
