Page Operations
Browse Space
Planned Agenda
1. Release of DDN V1 Prototype: Status from Development and architecture teams. Decisions about remaining issues and release.
2. Status user and architecture documentation for DDN
3. Use of Jira issue tracking and reporting
4. Hardening of the OOI Collaboration Tool Infrastructure
5. Work breakdown for pilot period
6. Planning of tasks for Feb performance period.
7. Visualization Pipeline Demo
Notes
Word version of the notes is here
| ID | Ag. |
Type |
What? |
Who? |
Due Date |
| 1 | 1 | I | The prototype is now released and available on production and for testing on the staging environment. Regapp.ooici.net is the production environment Regappstage.ooici.net is the staging environment |
||
| 2 | I | There is potential for performance improvement by adding dispatchers to the endpoints of the job queues that can dispatch to execution processes and throttle based on load. Currently there is one endpoint per machine and one job processor. | |||
| 3 | 2 | I | Philipp Weber gives a demo of the Visualization Pipeline. The pipeline is based on a DAP Client. Uses OpenSceneGraph through COLLADA and OssimPlanet. Provides a viewer application. Source data is model output from SoCal bight (JPL provided): ocean current vectors: 48 time steps, one per hour. The calculation for particle traceing is done on the model output: does an integration of streamlines over the vecor field. It has to interpolate space and time grid. The move the particle through several grid planes. The vision for CI is to set up the pipeline with style-sheets once and data and geometry is updated continuously. |
||
| 4 | 2 | AI | Follow-up work with Phil: do the domain models for the as built architecture in the same way as the DDN was documented | AT | |
| 5 | 3 | I | Matthew presents the list of 13 efforts as identified today. They can be grouped within an architecture of effort dependencies. Efforts are either infrastructure, application or community deployment focused. The Data Distribution Network is no effort in itself but realized an integration activity and outcome. It is the driving force and story behind all of the efforts |
||
| 6 | 4 | I | Status of defects in current DDN prototype. There are no blockers. There is one critical defect: All settings can be changed independent of permission level of user. The user gets an error message but changes are saved. This is a non-issue currently but need be reviewed with Roy and Rich once the prototype gets wider community exposure. |
||
| 7 | 4 | D | Language for defects: A blocker: the system fails to run after the bug. Scope affects all users other than individual A critical: the user's intent cannot be completed (don't use the word crash here). A major: the user workflow is interrupted but workaround exists and intent can be completed with inconvenience |
||
| 8 | 4 | AI | Add bug and comment page to prototype web interface. User feedback with bugs and feature requests should be reported through a feedback page. No exposure to Jira for end users. |
DT | |
| 9 | 4 | AI | On the prototype login page, state that this is a prototype and not meant to be around for long term. State use at your own risk | DT | |
| 10 | 4 | I | The cost of the DDN in the current architecture is about $40 per day. It is 13 virtual servers. | ||
| 11 | 4 | AI | Discuss with Roy and Rich about their expectation of extent of operational hours and exposure of the prototype | ||
| 12 | 4 | D | Prototype is in a condition to be released. Decision is to release it at this point. No direct work on this prototype anymore. | ||
| 13 | 4 | D | Usage reporting will be done with Intermapper once the hardening project is done. | ||
| 14 | 6 | D | Collaboration Tool hardening discussion will occur tomorrow. Starts at 10am with Tom, Alex, Dorian, Matt. Tom starts with what early steps have been performed in terms of server/application assessment. Michael joins at 11am. | ||
| 15 | 7 | D | February Planning meeting will define the objectives and deliverables for this months and individual focus. Deferred to tomorrow at 1pm |