Page Operations
Browse Space
Planned Agenda
- Alex and Dorian: Status on the DDN stability and readiness for test - 10 min
- Alex: Walk through Jira setup for DDN Testing - 5 min
- Claudiu: DDN As built architecture overview - 15 min
- Claudiu: DDN User Documentation and Testing plan - 5 min
- Michael: OSSE (Ocean Observatory Simulation Experiment) Statement of Work with JPL, MIT, Rutgers - 5 min
- Emilia: Agent Contract Network Statement of Work with NCSU - 5 min
- Matthew: Overview of scope being contemplated for the Pilot period through Sept - 15 min
Notes
The Word version of the notes is here.
| ID | Ag. |
Type |
What? |
Who? |
Due Date |
| 1 | 1 | I | The DDN prototype uses UCSD's email server accessed from the cloud. This did not work because of authentication reasons. As work-around, used Gmail's SMTP server with a new account dedicated for sending email. | ||
| 2 | 1 | DD | There will be a QA version of the DDN assigned to the static URL; we use a different staging version for testing and development such that service remains least interrupted. | ||
| 3 | 1 | AI | For upcoming releases of the prototypes, state which Jira issues have been addressed in that release. This can be a saved version of a Jira generated report. Make sure that Jira versions and components are used such that this information can be extracted. | DT | |
| 4 | 1 | AI | Add the build date and an automatically incremented build number automatically during each build cycle to visible web pages and version pages of the DDN components | DT | |
| 5 | 1 | I | The current build is stable enough to hand over to QA. | ||
| 6 | 1 | D | To get out of the DDN effort for now, a handover to Bob, Roy, Keith will occur. There is a need for a presentation. The system must not have blocker and critical bugs. A defect that brings the system down is blocker A defect that never allows a significant function to be completed is critical. If such bugs can be resolved by taking the cluster out, then ship without the cluster. |
||
| 7 | 2 | D | Use of versions in Jira for DDN: DDN1 refers to the FDR prototype DDN2 refers to the current version to be completed by end of January |
||
| 8 | 2 | AI | Design the Jira use of projects, components, versions. Present proposal about Jira use in February. | Michael | Feb |
| 9 | 2 | D | Jira workflows: Developers should resolve issues but not close them. Reporter should verify resolved issues but not close them. The development manager (board) verifies that there is agreement for issue to be closed. Need to add another state in Jira and protected. |
||
| 10 | 2 | I | Alex suggests to look at Joel Spolsky's software development best practices. | ||
| 11 | 3 | I | Architecture presentation by Claudiu: ERDDAP can respond to any correct DAP request and more. In this way it is an extended compliant DAP server. |
||
| 12 | 3 | AI | Revisit and refine logical architecture domain. SOAP should be RESTful Technologies: HAproxy replaced by engineX Add RabbitMQ Other changes as discussed. |
Claudiu | Jan 30 |
| 13 | 3 | I | In the DDN, ERDDAP is still configured using datasets.xml. Upon change of registration, a message with datasets.xml is sent to an ERDDAP util, which in turn publish the file to the memcache and to the crawlers. | ||
| 14 | 4 | D | Roadmap for documentation creation: We don't need the Developers Guide right now but a development report is helpful. Priority 1 is the context sensitive user guide. |
||
| 15 | 4 | AI | Complete user documentation and related documentation as discussed for DDN | Claudiu | Jan 30 |
| 16 | 6 | AI | Agent and contract network SoW with Munindar. Emilia and Munindar have iterated. The first phase is defined in quite detail. There are some open issues regarding responsibilities. Several have UCSD as main responsibility. Matthew reviews the open issues and provides guidance to Munindar and Emilia. |
Matthew | Jan 27 |
| 17 | 5 | I | Michael gives an overview of the upcoming main pilot efforts: 1. Data Distribution Network, version 2. Effort with NOAA. Emphasis on Real-time data sources and dynamic scaling 2. Common Execution Infrastructure and Cloud Provisioning. Work with Kate Keahey. 3. Agent and Contract Network. Work with NCSU 4. OSSE. Work with NASA JPL, MIT and Rutgers 5. Semantic Framework Integration. Work with Peter Fox, based on the DDN 6. Global Traffic Management. Work with Brian Dunne (Calit2) internal |
||
| 18 | 6 | I | Emilia provides an overview of the SoW currently in development with Munindar | ||
| 19 | 7 | I | Michael provides an overview of the SoWs with JPL and MIT for the OSSE. There will be a simulator deployment in 2009 and an field deployment in 2010. | ||
| 20 | 7 | I | Michael provides an overview of the SoW with Kate. Emphasis is on getting scheduler, provisioner and resource agents represented in an infrastructure based on a messaging network, such that dynamic monitoring and scaling can be achieved. |