You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 32 Next »

Time

Session 1

Notes

 WEDNESDAY

             ITANA                                

 

THURSDAY

Advanced CAMP

 

7:30-8:30

Breakfast

 

8:30-9:00

Introductions and Goals of the Workshop
Bob

Provide set of issues to report on
per Chas examples below

9:00-10:00


CI Salad: Defining the Problem 
What needs must CyberInfrastructure for the Humanities meet? Two Mellon-funded projects, SEASR and Bamboo, are trying to determine the leading problems to be solved to support digital humanties efforts and the frameworks, tools, and services needed to solve them. This session will brief us on what has been learned up to this early point in these projects, the approach each is taking, and the relationships they'd like to develop between their efforts and others.

Chad Kainz, SEASR (Ken)

10:00-10:15

Break

 

10:15-11:30

Open Source Service Oriented Projects in Higher Ed
The Kuali projects and Fedora are open source service oriented efforts to address issues in higher education.  In this session we will compare and contrast these efforts and hear experiences of devlopers and early adopters.



Jens to ask Kuali Rice/Student
Fedora - Ken?

11:30-1:00

Lunch

 

1:00-2:15

Computing as a Service
What tools and frameworks do we develop to make research computing into a service oriented endeavor?  The OGSA and several Cloud Computing vendors are developing standards to create a grid-like architecture based on Web Services.  This session wile explore the current state of the "Cloud" and visualize a future where computing is as ubiquitous and commodified as electricity.

Leif to find cloud computing speaker.
Other vendors? Amazon, Google, MS?
Bob to look into UW CS contacts.
OGSA (Ken)


 

2:15-2:30

Break


2:30-3:45


Panel: ESBs and widely-distributed services.
Many organizations use Enterprise Service Bus products to integrate services across large organizations.  While loosely-coupled technically, these deployments tend to be single-organization and centrally-managed.  A panel of ESB experts will reflect on the applicability of technology and methods to multi-organization, decentralized, serendipitous, project-centric service environments.


Dennis Gagnon (Ken)
ISI - Ewa Deelman (Bob)

MULE, JBoss, IBM -  possibly global routing table ESB

3:45-4:00

Break

 

4:00-5:00

Discussion Groups: Data Models, Governance, Service Discovery
Groups will consider each of these in turn given the examples so far and develop a set of requirements for each.
Leif

Orchestration/Information discovery: How do you go about finding information of interest and cross linking your results? Introduce Tool from caBIG??? But where does infrastructure stop and governance begin? Or is it a design pattern instead of an infrastructure component?

Breakout room needed for this session only.

5:30-7:00

Reception

Offer an unconference: Set up blank poster boards aroudn the room with markers and have folks write their own topic(s) on the board for discussion in that area of the room.

 

 

 

 FRIDAY

 

 

7:30-8:30

Breakfast

 

8:30-9:30

Privacy and Policy Panel: Expose privacy and policy issues that loosely coupled environments create.
Leif


Blakely (Bob), Lori Crantor (Chas)

EGEE

9:30-10:30


Lightning Talks and Discussion Group Report-outs 
Do you have a practice or interesting approach to share? Or would you like to connect up with someone with a similar challenge and collaborate on a solution? This session will provide a final chance for attendees to discuss a good idea or opportunity for peer networking. Attendees will also offer short reports of the discussions on the previous day.
Ann

 

10:30-11:00

Break

 

11:00-Noon


Wrap-up and Findings
The program committee will lead a discussion session to summarize the final points from the last day and develop any conclusions and next steps.
Ann


Issues to Compare and Contrast

- vision of project
- motivation (business and technical)
- brief narrative
- initial timeline
- how they began to define requirements
        - business/operational
        - technical
- defining governance model
- describe their technology
        - architecture
        - why they made specific decisions
- status thus far
        - progress to date (real timeline)
        - problems
        - risks
                - core competencies of staff?
                        - development/operational
                - continued funding?
                - technology?
                        - development
                        - operations
                - governance?
                - etc?

  • No labels