Download presentation
Presentation is loading. Please wait.
Published byGary Phelps Modified over 8 years ago
1
Enterprise Requirements: Industry Workshops and OGF Robert Cohen, Area Director, Enterprise Requirements
2
Industry Workshops OGF Industry Workshops shifted focus: –From identifying standards issues for end-users –To defining challenges and issues facing end- users that also encompass standards issues In financial services, end-users began by defining data delivery, manageability and workflow issues –But then requested OGF experts in data standards and APIs for Grid applications to join in discussions at OGF 21 –They expect to continue to: 1) draw on these experts as they develop an industry group to resolve key issues and 2) report back to OGF conferences on progress
3
Industry Workshop Plans Financial Services - workshop in NYC, 7/07 –to include 5-8 banks/brokerages, 4-6 vendors, and 3-5 OGF staff and experts; space at a bank. Semiconductors - workshop in Silicon Valley, 9/07 –to include 20-35 chip and design firms, 3-6 vendors, 3- 8 OGF staff and experts; space at AMD Pharmas - workshop in Philadelphia area, 9/07 –to include 15-30 pharmas/biotechs, 2-6 vendors, 3-8 OGF staff and experts; space at a pharma R&D lab
4
Workshops lead to Actions We expect end-users will formulate plans to address key issues of interoperability, APIs, moving data to the Grid by: –1) Setting up working groups using bank staff –2) Organizing joint efforts between banks and vendors –3) Creating joint efforts between OGF experts, bank staffers and vendors –All of these forms can be used; OGF experts are likely to be central to the efforts, including TSC
5
Reporting from Industry Workshops Written reports of OGF sessions on Gridforge Short White Papers to be prepared on Issues and Challenges in Specific Verticals Longer White Papers covering major issues and actions (i.e., data center actions at financial firms) will serve to make industry players aware of how banks, vendors and OGF are addressing key issues Reporting of Progress at OGF conferences, –to the Technology Steering Committee, –relevant standards groups and –the OGF Board
6
Summary of Industry Issues The following slides summarize the main issues that have been raised at OGF Industry Workshops over the past year There is some attempt to get end-users in different industries to consider commonalities in the issues they raised –“Cross-Industry Workshops” at OGF conferences that include EGR have provided a platform to begin to identify common problems
7
Financial Services Issues 1 Data delivery and manageability –Expanding databases are used to analyze exotic investments and credit markets –different types of financial modeling make the need for more rapid data delivery very acute –credit derivative analysis uses 30k scenarios Scaling –Banks have Grids with 100s of nodes –How can they manage everything?
8
Financial Services Issues 2 Workflow capability –Need to automate the ability to integrate things into the business workflow APIs for financial applications –Banks currently write APIs for every new application; need generalized APIs Metascheduler
9
Auto/Aero Issues 1 Application integration over the Grid and how to provide access to apps by outside suppliers Recapturing and reuse of data –Data related to process knowledge and to process data knowledge needs to be captured and reused Security –Especially when providing access to partners and suppliers
10
Auto/Aero Issues 2 Manageability –Managing middleware from several vendors is very difficult –Grids are helping workflows become collaboration vehicles and accelerating computational tasks, but heterogeneity of data sources makes integration difficult Virtual Product Development –Requires simulations to create meshes and poses a sizable challenge for users
11
Semiconductor Issues 1 Load balance license servers. Want flow control to get optimal control of license. Want to load balance the license servers that are deployed. Monitoring of the compute farms that is dynamic and tunable or customizable Charge back and metering, particularly when multiple projects share the same infrastructure.
12
Semiconductor Issues 2 Validation. Make sure there is a fine grain validation of access to resources; associate attributes with Grid identity. Also, require a validation/security mechanism that handles things consistently across flows. Need storage aware scheduling. Must have hooks in place. The direct structures and disk volumes become full, so then flow control comes into play.
13
Semiconductor Issues 3 OGF storage standard – need to define attributes about storage system that we schedule a job into. Dynamically updated information about storage.
14
Pharma Issues 1 Data access and sharing of resources –All databases need to be interoperable –Different things are described the same way, so need to build ontologies Need to interpret new models and do new kinds of analysis Problem getting software to run on Grids at pharmas. Need to talk to several different scheduling systems for jobs.
15
Pharma Issues 2 Need to have common data repository with UML level. –Common ontology. What could be standardized is some type of shared representation of what a data repository should look like.
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.