...
By Component:
- Commissioning:
- Get the unit tests done
- Probably introduce some unit ''integration tests'' with instantiation, CSITs
- Redefine the API's needed. Exact GET's needed + checks to introduce, What do we actually need?
- Pushing of control loop component definitions to participants? Flow of how you get from a commissioned control loop definition to an instantiated control loop.
- Â Monitoring:
- Monitoring and supervision functionality interchanged. Needs to be updated in the wiki.
- Need to finalize the statistics data for participants and Control loop elements. Also need to decide, if we require to implement association between statistics classes and parent.
- GUI for monitoring?
...
- Follow up on contract testing, also with CPS project test approach
- Stick with the Wiki for documentation and convert to RST later, keep the wiki page up to date. Wiki page should be updated and kept aligned before design start, as component functionality can be agreed among all.
Responsibility: All to do - Set up CSIT tests for the control loop work. Also get some help from experienced people in CSIT.
Responsibility: To be decided - Explain the concepts of Control Loops/Participants/Control Loop Elements in a good way with good diagrams and better documentation, also the TOSCA service template and node templates.
Responsibility: Liam Fallon - Put up a howto on the Wiki on how to run the demo.
Responsibility: Liam Fallon - Training on the Policy Framework and its principles.
Responsibility: To be decided - Get the Jenkins verify jobs running in Nordix
Responsibility: Liam Fallon - Create subtasks on JIRAs with Definitions of Done etc
Responsibility: (Sirisha Manchikanti to champion) - Checklist for Code Reviews
Responsibility: (Sirisha Manchikanti to champion) - Wiki page for new joiners, already is a lot of info out there but it's scattered. We should have a landing page for ourselves.
Responsibility: Saul Gill to document your learnings on a Wiki page