|
|
|
|
|
|
|
|
|
|
«
|
November
2009
|
»
|
| Su |
Mo |
Tu |
We |
Th |
Fr |
Sa |
| 1 |
2 |
3 |
4 |
5 |
6 |
7 |
| 8 |
9 |
10 |
11 |
12 |
13 |
14 |
| 15 |
16 |
17 |
18 |
19 |
20 |
21 |
| 22 |
23 |
24 |
25 |
26 |
27 |
28 |
| 29 |
30 |
|
|
|
|
|
|
|
|
TIGRE Milestones
These are the milestones in our TIGRE contract with the state.
The Steering Committee has proposed a 12/1/2005 start date for the TIGRE project. The dates below reflect this.
| Date | Milestone |
| 2/28/2006 |
Present a project plan and scope of work in a mutually acceptable format to Department of Information Resources (DIR). Establish a common web site, shared Certificate of Authority (CA) service and minimum testbed requirements within the first quarter of the first year. This will enable TIGRE Institutions to immediately perform outreach activities by publishing lessons learned and experience papers to the community and the public at large. Select three driving applications of importance to the State that will be used to derive grid software stack requirements for construction, as well as provide a set of applications for testing, verification and assessment of success. |
| 5/30/2006 |
A prototype alpha quality portal service will be deployed within the second quarter of year 1 to facilitate requirement gathering of application and site specific resource submission characteristics amongst the varied scientific and educational communities that will be using the portal. |
| 8/31/2006 |
Within the third quarter of year 1, a site service software stack will have been defined. A distribution mechanism, possibly using packaging technologies like pacman, will be agreed upon and customized for TIGRE. Demonstrate, on a small scale, basic functionalities of TIGRE capabilities using at least one of the driving applications. |
| 11/30/2006 |
A prototype alpha-quality client tools package will be distributed to friendly users by the end of year 1. This client tools package will allow friendly users to start using site resources earlier on to identify missing components, and harden tools which will eventually be released to the wider TIGRE user community. |
| 2/28/2007 |
An alpha-quality customer management services system will be deployed in the first quarter of year 2 to enable testing and site specific customization. Demonstrate across resources from the majority of the TIGRE Institutions capabilities using all three driving applications. |
| 5/30/2007 |
In the middle of year 2, a global grid scheduler service will be deployed. This grid scheduler will enable sites to advertise resources, and TIGRE user jobs to be routed to the most appropriate site for execution. |
| 8/31/2007 |
In the third quarter of year 2, the alpha-quality packages will be upgraded with bug fixes and new feature requirements and a cool down period will be enforced. During this period only critical changes to the infrastructure will be done, allowing a stable environment to be migrated into production at the end of year 2. Also the minimum set of services needed to use and/or join TIGRE production grids will be defined. Prepare and execute a major demonstration of TIGRE software capabilities using the three driving applications and asses ease of use and success. |
| 11/30/2007 |
During the final quarter, the software hardening will be completed and the installation and support documentation will be prepared. Procedures and policies for joining TIGRE and sharing resources will be developed and documented, and posted to the TIGRE web sites. Demonstrate TIGRE at the national supercomputing conference. |
Created by
josten
Last modified
December 13, 2007 05:06 PM
|
|
|