DC3Schedule: notes-LSST-DC3-updated-08.14.txt

File notes-LSST-DC3-updated-08.14.txt, 9.0 KB (added by cbeldica, 11 years ago)
Line 
1Jacek:
2======
3No changes, I've been on vacation since Aug 2nd.
4The only DC3 related thing I've done since the last update was providing some text for the fault tolerance doc.
5
6Steve:
7======
8Re: #95 Implement configurable on-the-fly event processing - extended the deadlien by 1 week
9I've been on vacation for the last couple of days.   I'm working on a solution for a potential problem Ray and
10I discussed late last Friday.  The current implementation handles the problem, but I've come up with a better
11(and much faster) way have handling things that I need to implement.   Depending on how fast I can do this,
12the week slip might be shortened up.
13
14Re: #121 "implement an orchestration layer" --  not started, need to talk to Ray
15
16David:
17======
18Re: #34 convert to new package build mechanism (remove dependency on pacman) 85% - working with Ray on this; most of the external packages now build on
1964-bit and 32-bit without pacman.
20
21
22Bill:
23=====
2443 - 60% complete
25
26    * Installed buildbot and published at dev.lsstcorp.org/build/
27    * Configured initial test of tools installation
28
2944 - no change - waiting for V&V software (Russ & David?)
30122 - no change - need guidance (same as Steve P)
31208 - 50%
32    * Progress on most sections of outline & document
33    * new expected finish date: xxxxxxx
34
35
36KT:
37===
38#73 (removing CORAL): Ticket #332, 98% (some bugs remain)
39#76 (image archive): [this is the same as #146]
40#83 (expanded match algorithms): [this is the same as #129-#131]
41#115 (fault tolerance plan): 50% [additional work added]
42#116 (fault tolerance editing): waiting on #115
43#146 (image retrieval): requirements gathered, 20%
44
45
46Ray:
47====
48Ray Plante
49Progress as of 12 Aug.
50
51Note:  My progress on DC3 has been significantly hampered these last two weeks due to PDR preparation.  See non-DC3 activities below.
52
53DC3 Tasks:
54Task 32:  update software dist. server
55   Status:  underway, behind schedule
56   Activity:  I completed the changes to eups distrib for use with our
57       server.  David and I are now putting packages into place.  The
58       majority of packages have been deployed and build fine on
59       CentOS/Red Hat platforms, both 32-bit and 64-bit.  Some package
60       version issues are being sorted out now.
61   Time to Complete: I estimate I need 2 more days to get to the point of
62       having other people download packages.
63
64Task 35:  enable support for 64-bit Linux
65   Status:  underway, behind schedule
66   Activity:  64-bit CentOS has been my primary development platform for
67       task 32.  There are no major problems related to this task; but
68       it's completion is tied to task 32.
69
70Task 85:  policy/data property integration
71   Status:  not started
72   Notes:  recent discussion regarding metadata may have an impact on this
73       task; discussion is underway in various WG telecons.
74
75Task 115:  fault tolerance plan
76   Status:  completed
77Task 116:  fault tolerance plan editing
78   Status:  transfered to KT
79
80Task 120, 121: Orchestration Layer
81   Status:  not started
82
83Other non-DC3 activity:
84   o  worked with B. Baker on reviewing and editing the Security Plan
85        Document.
86   o  worked with C. Cribbs and C. Beldica on update to Infrastructure
87        costing.  We restructured the document to allow for our more
88        detailed understanding of the architecture.  We concentrated on
89        updating the numbers for the Base Facility.  I worked on
90        translating requirements from the FRS, storage estimates,
91        computing estimates, and the community data access white paper
92        into input data for costing.
93   o  moderated middleware telecons
94
95
96
97
98DC3 Milestones for Roberta Allsman  12 August 2008
99===================================================
100
1016   SW Quality Assurance
102______________________________________________________________
1037   .. Software Quality Assurance: Planning
104______________________________________________________________
1058   .... Develop Framework of LSST DM Software Development Process
106______________________________________________________________
1079   ...... Software Quality Assurance (SQA) Plan
108           Draft: Framework is 90% complete
109           Draft: Content is 30% complete
110           Review and Rewrite:
111           PL and CCB Approval:
112           % Complete: 30%
113______________________________________________________________
11410  ...... Verification and Validation (V&V) Plan
115                                    (Excludes APP & MW Unit Test Plans)
116           Draft: Plan framework is 90% complete
117           Draft: Content is 30% complete 
118           Review and Rewrite:
119           PL and CCB Approval:
120           % Complete:30%
121______________________________________________________________
12211  ...... Configuration Management  (CM) Plan
123           Draft: Plan framework is 90% complete
124           Draft: Content is 60% complete
125           Review then Rewrite:
126           PL and CCB Approval:
127           % Complete: 60%
128______________________________________________________________
12912  .... V&V: Tracking Requirements to Tested Product Release
130______________________________________________________________
13113  ...... Std: develop standard labelling scheme for products and their
132           provenance
133           Draft: Policy is 90% complete
134           Review and Rewrite:
135           PL and CCB approval:
136           % Complete: 90%
137______________________________________________________________
13814  ...... V&V: define procedure whereby the initial requirements are traced
139           to the validated product
140           Draft: 0%
141           Review and Rewrite:
142           PL and CCB approval:
143           % Complete: 0%
144______________________________________________________________
14515  .... Develop DC3 specialization of those SQA plans
146           DC3 SQA Draft: 0%
147           DC3 V&V Draft: 0%      depends on completion of Robustness diagrams
148                                        and MW & App Unit Test Plans
149           DC3 CM Draft: 0%
150           % Complete: 0% 
151______________________________________________________________
15216  .... Evaluation of commercial or open-source testing tools
153           DELETE THIS ENTRY  it's covered by 19.1 and 20.1
154______________________________________________________________
15517  .... Decision on testing tool
156           DELETE THIS ENTRY  it's covered by 19.2 and 20.2
157______________________________________________________________
15818  .. V&V: Acquire SQA support tools
159______________________________________________________________
16019  .... Configurable tool to perform Lsst software standards checking
161           C++ LSST benchmark test suite packaged (done)
162______________________________________________________________
16319.1  ...... benchmark  ***  being done by Russ Laher IPAC ***
164           C++: Programming Research benchmarked using industry standard RuleSet
165           C++: Abraxis preparing for benchmark: LSST RuleSet being implemented
166           C++: Parasoft solicted for benchmarking
167           python: no options identified
168           % Complete: ???
169______________________________________________________________
17019.2  ...... acquire for widespread use
171           % Complete: 0%
172______________________________________________________________
17320  .... coverage analysis tool
174______________________________________________________________
17520.1  ...... benchmark
176           C++: gcov (open source) 
177           C++: ggcov (open source)
178           python: no option identified
179           % Complete: 0%   
180______________________________________________________________
18120.2  ...... acquire for widespread use
182           % Complete: 0%
183______________________________________________________________
18421  .. V&V: Increased Validation Testing
185______________________________________________________________
18622  .... Std: specify testing requirements for each phase of Prod development
187______________________________________________________________
18824  ...... unit test: black box, white box, performance tests
189           % Complete: 0%
190______________________________________________________________
19125  ...... integration tests: black box, white box, performance, regression
192           % Complete: 0%
193______________________________________________________________
19426  ...... system tests: function, performance, interface, resource, security,
195           portability, reliability, maintainability, safety
196           % Complete: 0%
197______________________________________________________________
19827  ...... acceptance tests: capability and constraint tests
199           % Complete: 0%
200______________________________________________________________
20128  .... Std: specify the pass/fail metrics for each test type
202         (eg compliance levels)
203           % Complete: 0%
204______________________________________________________________
20529  .... V&V: Refine workflow process to incorporate additional V & V testing.
206           % Complete: 0%
207______________________________________________________________
208