Changes between Initial Version and Version 1 of Gec7ClusterCAgenda


Ignore:
Timestamp:
03/04/10 19:42:37 (14 years ago)
Author:
ricci@cs.utah.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Gec7ClusterCAgenda

    v1 v1  
     1= GEC7 Cluster C Agenda =
     2
     3'''Note: This agenda is still a draft'''
     4
     5== Tuesday ==
     6
     7Our cluster time on Tuesday will be used for:
     8
     9 * Status reports: short (5 minute) reports about project status
     10
     11 * A 'cluster demo session'
     12
     13   Because it's hard for those giving demos in the demo session to go around
     14   and see others' demos, and because it's particularly important for cluster
     15   members to see each others' demos, we'll be using this time as a sort of
     16   "dress rehearsal": a chance to present our demos, one at a time, to each
     17   other.
     18
     19== Wednesday ==
     20
     21
     22The Cluster C meeting on Wednesday will be focused discussion around three
     23technical topics. All discussions are expected to be highly interactive; each
     24topic will be introduced by a short talk, and then turned over to the attendees
     25for discussion.
     26
     27 * ProtoGENI Credentials: Discussion leader - Rob Ricci
     28
     29   Rob will present the current state of credentials in ProtoGENI: the
     30   types of credentials that are currently supported and which operations
     31   require which credentials. He will also discuss some of ProtoGENI's
     32   recent work . The purpose of this discussion will be to find where
     33   ABAC can fit in, and what additional credentials and permissions other
     34   cluster members are interested in.
     35
     36 * Measurement Projects: '''discussion leaders needed'''
     37
     38   Some good conversations have started among the projects doing measurement in
     39   our cluster. We'll continue these, devoting some of our cluster meeting
     40   time to the topic.
     41
     42   The main goals are:
     43
     44     1. Agree on specific projects that the measurement groups will pool
     45        resources on
     46     1. Make sure there is no, or at least minimal, duplication of effort
     47     1. List of the resources (all across protogeni) that can be
     48        measured/instrumented, and to discuss whether there is a single
     49        measurement infrastructure that should be general enough to
     50        run/manage them all
     51
     52 * User Feedback: '''discussion leaders needed'''
     53
     54   Over a dozen people from outside Utah have been exercising the ProtoGENI
     55   interface to create slices. This is your chance to give feedback on how
     56   well they are working: what's working well, what's not working, and what
     57   missing features are giving you the most trouble?