160 likes | 264 Vues
CISL Resource Information System. High Level Kickoff Meeting 10 January 2006. Notes. As a stakeholder, what do you need from/in the accounting resource “database” to perform your task/job/function? Database Redesign is the action which needs to be taken
E N D
CISL Resource Information System High Level Kickoff Meeting 10 January 2006
Notes • As a stakeholder, what do you need from/in the accounting resource “database” to perform your task/job/function? • Database Redesign is the action which needs to be taken Need a name for the database itself: • Resource Information System (RIS) • Resource Information Repository (RIR) • Resource Control Facility (RCF) • ….some clever acronym….
Agenda • Project Need • Goals • Business Scope • High Level Requirements • Project Organization • Timeline • Stakeholders Requirements
The Need: Old Paradigm • Computers did not change frequently • Computing resources were at one location • compute, storage, analyze • NCAR was an Island
The Need: New Paradigm • Approx. 3-year cycle on computer changes • 2004-2005: • blackforest, lightning, bluevista • frost, coral, pegasus • 2006 • ICESS • Computing resources may be at multiple locations • Teragrid Partner ? • Support of new/other applications (Enact, Remedy, Directory Services?, etc) • Leverage finite staff for database support/use • Account: compute cycles, bytes archived, byte moved(?), byte residence on SAN, use of data/viz facility
Goals • Design a flexible database to support new resource-use paradigm • Division-wide acceptance • Easy access • Internal, incoming dataflow to DB • Internal, outgoing dataflow to stakeholders • Verifiable • Follow industry standard best practices • Warehouse? • method to deal with old data • new data storage
That’s HUGE How do we do this?
NCAR Business • NCAR provides computing resources for the scientific community • Atmospheric and related sciences • Community could grow (NSF 625, Geosciences, etc.) • NCAR must ensure access for all members
CISL Business • Allocate resources • facilities, communities, laboratories, divisions, PIs, groups, projects, users, etc. • Monitor Usage • for example, utilization, MSS archive size • Report Usage (multiple consumers) • Usage statistics by Lab, PI, Group, User, NSF Program, CSL PI, Univ PI, etc. • Regulate Resources • Fair-share access • “Hold” over-users • Support Operations • Account provision • Security (OTP)
Core Project Team • Project Manager: Lana Stillwell • Technical Development Team: AISG
SDLC (Team Tasks) • Define high level goals (Charter) • Discover and Document Requirements • Risk Analysis • Development Costs • Stakeholder Costs (careful: initially hidden) • Review and Approve • Architect and Design • Implement • Stages? • Beta?
Timeline Factors • Allocations Cycle • NCAR January 2006 • CSL March 2006 • Univ April and October • ICESS Delivery and Deployment • Winter 2006-2007
Timeline • Target Beta Version • Define Beta Version • October 2006 • parallel execution/comparison with existing database? • Regular Updates to Stakeholders from Core Project Team