Get documents about "TR-2005-024 NEESgrid Release 3.4 Project Plan
Shared by: yaofenjin
-
Stats
- views:
- 9
- posted:
- 8/24/2011
- language:
- Turkish
- pages:
- 12
Document Sample
TR-2005-024
NEESgrid Release 3.4
Project Plan
Shannon Whitmore1
1
NEES Cyberinfrastructure Center, SDSC
Last Modified: 2005-06-22 Version: 1.0
Acknowledgment: This work was supported by the George E. Brown, Jr. Network for Earthquake Engineering Simulation (NEES) Program
of the National Science Foundation under Award Number CMS-0000000. Visit http://it.nees.org/ for more information.
NEESgrid Release 3.4 Project Plan 2 of 12
Table of Contents
Revision History ............................................................................................................................................3
About This Document ....................................................................................................................................3
1. Introduction ............................................................................................................................................4
1.1 Project Scope and Objectives ........................................................................................................4
1.2 Deliverables ...................................................................................................................................4
1.3 Schedule Summary .........................................................................................................................4
1.4 Supporting Materials ......................................................................................................................5
1.5 Risks and Mitigation Strategies .....................................................................................................5
2 Project Organization...............................................................................................................................6
2.1 Internal Structure...........................................................................................................................6
2.2 External Interfaces .........................................................................................................................7
2.3 Responsibilities ..............................................................................................................................8
3 Project Resources, Schedule, and Control .............................................................................................9
3.1 Software/Hardware Resources .......................................................................................................9
3.2 Schedule, Tracking and Control ..................................................................................................10
List of Figures
Figure 1: NEESit Organizational Structure ...................................................................................................6
Figure 2: External Collaborators....................................................................................................................8
List of Tables
Table 1: Release 3.4 Deliverables..................................................................................................................4
Table 2: Release 3.4 Schedule Overview.......................................................................................................4
Table 3: Release 3.4 Supporting Documentation...........................................................................................5
Table 4: 3.4 Risks/Mitigation Strategies........................................................................................................5
Table 5: NEESit Staff Roles for 3.4...............................................................................................................7
Table 6: External Collaborators/Responsibilities ..........................................................................................8
Table 7: 3.4 Software Responsibilities ..........................................................................................................9
Table 8: 3.4 Documentation Responsibilities ................................................................................................9
Table 9: Compute Resources .......................................................................................................................11
Table 10: Test Equipment ............................................................................................................................12
Shannon Whitmore Web it.nees.org
TR-2005-024 Updated: 2005-06-22 Email it-support@nees.org
NEESgrid Release 3.4 Project Plan 3 of 12
Revision History
Date Version Description Authors
5/19/2005 0.1 Initial document creation Shannon Whitmore
6/6/2005 0.2 Modified to reflect fogbugz case numbers. Shannon Whitmore
Removed NEEScentral from this project plan.
6/22/2005 1.0 Updated TR document number Shannon Whitmore
About This Document
The purpose of this project plan is to assist NEESit project management with the 3.4 release of NEESgrid
software and services. This plan communicates the scope, resources, deliverables, and timeline for the 3.4
release.
This document consists of the following sections:
1. Section 1 provides on overview of the 3.4 software development effort and specifies the scope,
schedule summary, list of deliverables, and list of supporting documentation to reference for the
3.4 release.
2. Section 2 presents the organizational structure of the software development team, including
NEESit staff and all collaborators contributing to the 3.4 release. This section also details the
functional areas associated with each organization.
3. Section 3 lists the hardware and software dependencies needed for the release and gives
information on how NEESit will track the schedule.
Shannon Whitmore Web it.nees.org
TR-2005-024 Updated: 2005-06-22 Email it-support@nees.org
NEESgrid Release 3.4 Project Plan 4 of 12
1. Introduction
1.1 Project Scope and Objectives
The primary objective of the 3.4 patch is to fix major defects found in the NEESpop and flexTPS software
distributions. The 1.1 release of NEEScentral will occur after the 3.4 release and will be documented in
its own project plan.
1.2 Deliverables
The deliverables for the 3.4 release are updates to the NEESpop and flexTPS software distributions.
Although no new documentation will be written for the 3.4 release, the content of a few existing
documents will be modified. All software and documentation will be made available via the NEESit web
site.
A complete list of all deliverables for the 3.4 release is shown in Table 1.
Table 1: Release 3.4 Deliverables
Deliverable Location
NEESpop Software Distribution ftp://ftp.nees.org/pub/site-software/3.4/neespop/neesgrid-3.4-neespop.bin
flexTPS Software Distribution ftp://ftp.nees.org/pub/site-software/3.4/flextps/neesgrid-3.4-flextps.tgz
NEESpop Installation and http://it.nees.org/software (Actual location TBD)
Configuration Manual
RDV User’s Manual http://it.nees.org/documentation/library/telepresence/000232.php
flexTPS User’s Manual http://it.nees.org/documentation/library/telepresence/000219.php
1.3 Schedule Summary
Release 3.4 will be made available to the NEES community on June 30, 2005. Refer to Table 2 for the
schedule and key milestones associated with the 3.4 software development process.
Table 2: Release 3.4 Schedule Overview
Date Key Milestones
April 1 – June 3 Bug fixes and minor new implementation efforts
June 3 Code freeze
June 8 Release 3.4 beta available for internal testing
June 8 – June 18 Execute tests/fix regressions
June 17 CVS freeze
Shannon Whitmore Web it.nees.org
TR-2005-024 Updated: 2005-06-22 Email it-support@nees.org
NEESgrid Release 3.4 Project Plan 5 of 12
June 22 Release 3.4 production candidate deployed
June 23 – June 27 Final testing – system and acceptance
June 30 Final release packaged/deployed
1.4 Supporting Materials
The procedures specified in the NEESit Software Development Process document (TR-2005-001) and
NEESit Software Configuration Management Plan (TR-2005-002) will be used for the 3.4 release. Refer
to Table 3 for a list of all required documentation produced for this release.
Table 3: Release 3.4 Supporting Documentation
Title Report # Due Date Author Organization
NEESgrid 3.4 Quality Assurance
QA-2005-006A 6/10/05 Shannon Whitmore NEESit
Plan
NEESgrid 3.4 Quality Assurance
QA-2005-006B 7/15/05 Shannon Whitmore NEESit
Report
1.5 Risks and Mitigation Strategies
The risks associated with the 3.4 release and corresponding mitigation strategies are shown in Table 4.
Table 4: 3.4 Risks/Mitigation Strategies
Risk Description Likelihood Severity Mitigation Strategy
The 3.4 software will be of lower Low High • Full tests will be executed against all
quality then the 3.3 release released software
• Software patches will be released for all
high priority defects found in the system
after the 3.4 release.
The 3.4 software will not be released on Low Low • A new release date will be announced.
time • Any sites needing the 3.4 software will be
assisted on a case by case basis
Shannon Whitmore Web it.nees.org
TR-2005-024 Updated: 2005-06-22 Email it-support@nees.org
NEESgrid Release 3.4 Project Plan 6 of 12
2 Project Organization
This section lists the performing organizations in the project and describes their responsibilities.
2.1 Internal Structure
The organizational chart for NEESit staff is shown in Figure 1 and the primary role of each staff member
contributing to the 3.4 release is shown in Table 5.
Principal Investigator/Director
Anke Kamrath
Asst Director of Operations Program Coordinator
Lelli Van Den Einde Tess Lacuesta
Dev & Deployment Mgr Sr. Data Architect User Services Mgr
Shannon Whitmore Tim Warnock Wei Deng
Sr. Developer SDSC Data Team User Support Engr
Paul Hubbard Vladimir Veytser Susan Rappoport
QA Engineer Data Developer Sr. Writer/Web Design
Jinghong Gao Dan Frysinger Daniel Rehn
Developer Undergrad Assistant
Larry Miller Jared Bell
Builds & Pack Engr
Mike Packard
Figure 1: NEESit Organizational Structure
Shannon Whitmore Web it.nees.org
TR-2005-024 Updated: 2005-06-22 Email it-support@nees.org
NEESgrid Release 3.4 Project Plan 7 of 12
Table 5: NEESit Staff Roles for 3.4
Name Role
Operations Manager & Assistant Director
Lelli Van Den Einde
Tester
Release 3.4 Project Manager
Shannon Whitmore Configuration Manager
Tester
Release 3.4 Assistant Manager
User Services Manager
Wei Deng
Authentication Lead
Tester
Data Architect
Tim Warnock Data Developer
Tester
Telepresence/DAQ Lead
Paul Hubbard Telepresence/DAQ Developer
Tester
Senior Developer
Larry Miller
Tester
Jinghong Gao Tester (part time)
Builds and Packaging
Mike Packard Configuration Management
Tester
Documentation Lead
Daniel Rehn Portals and We b Developer
Tester
Developer
Vladimir Veytser
Tester
Developer
Dan Frysinger
Tester
Susan Rappoport Not available – on leave
Jared Bell Tester
2.2 External Interfaces
Under the direction of NEESinc, NEESit will manage the software development efforts of all external
collaborators. There are numerous distributed organizations who are contributing to NEESit’s production
software releases, as shown in Figure 2. Not all of these organizations are contributing to the 3.4 release.
Table 6 gives the list of PI’s, staff, and researchers associated with each organization and the functional
area each organization will contribute to for the 3.4 release.
Shannon Whitmore Web it.nees.org
TR-2005-024 Updated: 2005-06-22 Email it-support@nees.org
NEESgrid Release 3.4 Project Plan 8 of 12
NSF
NEESinc
NEESit
Subcontractors Equipment Sites
Oregon University University Mississippi University University System
State of of State of Texas of Buffalo Integration
University Michigan California Austin SUNY Team
Berkeley
Stanford Michigan NCSA Quanser Creare
Figure 2: External Collaborators
Table 6: External Collaborators/Responsibilities
Organization Name Responsibility
University of Michigan (UMICH) Tom Finholt (PI) CHEF and Data
Chuck Severance Turbine
Terry Weymouth
Beth Kirschner
Jim Eng
Swapnaa Jayaraman
University of Texas at Austin (UTA) Christopher Stanton flexTPS
University of Buffalo, SUNY Jason Hanley RDV
(SUNY)
2.3 Responsibilities
Deliverables for the 3.4 software release have been divided into 2 areas: software development (Table 7),
and documentation (Table 8). Refer to the tables below for specific details on the deliverables for the
release and the personnel who are responsible for each area.
Shannon Whitmore Web it.nees.org
TR-2005-024 Updated: 2005-06-22 Email it-support@nees.org
NEESgrid Release 3.4 Project Plan 9 of 12
Table 7: 3.4 Software Responsibilities
Deliverable Functional Area Description Contributors
NEESpop System RHEL4 migration: Fogbugz Mike Packard (NEESit)
548, 1358 Wei Deng (NEESit)
Collaboration Bug fixes, including the Wei Deng (NEESit)
following fogbugz case Beth Kirschner (UMICH)
numbers: 618, 708, 815, Jim Eng (UMICH)
881, 910, 1190, 1421, 1171,
and 1232.
Enhancement:
Automate account creation on
the NEESpop: fogbugz 1014.
Installation and Fix PHP issue: Fogbugz 1363 Wei Deng (NEESit)
Configuration Mike Packard (NEESit)
RDV Non-MIME channels broken Jason Hanley (SUNY)
in latest RDV. Fogbugz 1418
flexTPS Telepresence Christopher Stanton (UTA)
Table 8: 3.4 Documentation Responsibilities
Deliverable Category Description Contributors
NEESpop Installation and Fogbugz cases 1367, 1509 Mike Packard (NEESit)
Installation and Configuration Wei Deng (NEESit)
Configuration Daniel Rehn (NEESit)
Instructions
RDV Users Telepresence Fogbugz 1378, 1246, 1336, and Jason Hanley (NEESit)
Manual 1510. Shannon Whitmore (NEESit)
Daniel Rehn (NEESit)
flexTPS Users Telepresence Fogbugz 1492 Christopher Stanton
Manual Daniel Rehn
it.nees.org Web Site Fogbugz 1140 and 1428. Daniel Rehn
updates
3 Project Resources, Schedule, and Control
3.1 Software/Hardware Resources
As per the NEESit Configuration Management Plan (TR-2005-002), computing systems are configured to
support three development phases: development (dev), staging (stage), and production (prod).
Development systems are used by programmers to prototype, implement, and test their code while staging
systems are more tightly controlled to ensure integrity. Production systems are deployed with software
Shannon Whitmore Web it.nees.org
TR-2005-024 Updated: 2005-06-22 Email it-support@nees.org
NEESgrid Release 3.4 Project Plan 10 of 12
released to the community. Error! Not a valid bookmark self-reference. lists all compute resources
available for the 3.4 development effort where each resource is mapped to one or more of phases.
Software integration testing requires access to systems that simulate the equipment found at the
equipment sites. Table 10 shows the 3 systems available to NEESit staff for these end-to-end test efforts.
3.2 Schedule, Tracking and Control
The project schedule and software functionality will be tracked by the NEESit project management using
Fogbugz. For information on tracking quality, refer to the NEESgrid 3.4 Quality Assurance Plan (QA-
2005-006A). Details on release management and functionality tracking may also be found in NEESit
Software Configuration Management Plan (TR-2005-002).
Shannon Whitmore Web it.nees.org
TR-2005-024 Updated: 2005-06-22 Email it-support@nees.org
NEESgrid Release 3.4 Project Plan 11 of 12
Table 9: Compute Resources
Hostname Phase Location Hardware Software Description
neesdev POP SDSC Dell 1750, 2 VMWare NEESpop development system
Dev machine processors with private network. Software
neesdev0 room 2 RHEL 3 w/latest “builds” performed on neesdev0
neesdev1 patch and deployments on neesdev1-3.
neesdev2 1 RH 9
neesdev3 Security policy not strongly
Various neespop enforced -- developers allowed to
deployments have sudo privileges
Libraries for We will use one of these machines
building the to test the upgrade from NEESpop
distribution 3.3 to 3.4 on RHEL 3.
available on
neesdev0
seismos POP SDSC Dell 1850 RHEL 3 w/patches NEESpop 3.4 staging system.
Stage machine
room
creep POP SDSC Dell 1850 VMWare NEESpop 3.4 staging system.
Stage machine
creepvm1 room RHEL 4 w/patches
creepvm2
creepvm3
creepvm4
neespop POP SDSC Dell 1750 2 RHEL 3 w/patches NEESpop 3.4 production will be
Prod machine processors deployed here
room Libraries for
building the
distribution
available here.
dev-central Central SDSC TBD RHEL 3 w/patches NEEScentral development system
Dev machine LAMP
room SRB
gridauth
NEES CA
stage-central Central SDSC Dell 1850 RHEL 3 w/patches NEEScentral staging system
Stage machine LAMP
room SRB
gridauth
NEES CA
central1 Central SDSC Dell 1850 dual RHEL 3 w/patches NEEScentral 1.0 production
central2 Prod machine processor LAMP systems
room SRB
gridauth
NEES CA
neestpm flexTPS LJPC 109 Dell 1800 RHEL 3 w/patches High bandwidth telepresence
Dev Power H server developing and staging system
Shannon Whitmore Web it.nees.org
TR-2005-024 Updated: 2005-06-22 Email it-support@nees.org
NEESgrid Release 3.4 Project Plan 12 of 12
Stage flextps
Prod
neessim Dev SDSC Dell 1750, 1 RHEL 3 w/patches Simulation machine
Stage machine processor
Prod room OpenSees
neespop 3.2
neesdaq DAQ LJPC 109 Dell ?? Windows XP Connected to miniMOST-1
Dev Controlling X10 devices
Stage LabView 7.0
Prod Tortoise CVS
N/A DAQ LJPC 109 IBM Thinkpad Connected to miniMOST-2
Dev T42 Laptop
Stage 1.7GHz
Prod 512MB mem
shaketable DAQ SDSC 1 processor, Windows XP Connected to Quanser shaketable
Stage B02 Pentium 2 MATLAB 7
Prod LabView 6 & 7
Tortoise CVS
Table 10: Test Equipment
Name Location Hardware
miniMOST-1 LJPC 109 1 actuator
3 sensors (LVDT, strain, displacement)
miniMOST-2 LJPC 109 2 actuators
3 sensors (LVDT, strain, displacement)
shaketable SDSC Quanser shaketable with 2 sensors
B02
Shannon Whitmore Web it.nees.org
TR-2005-024 Updated: 2005-06-22 Email it-support@nees.org
