20160303 - Meeting minutes, Thursday, March 03rd, 2016 - OpenNCP Technical Committee Meeting
OpenNCP Technical Committee Meeting
Feb 18, 2016
Estimated - 13:00 to 14:00 CET
Performed - to CET
AGENDA
Connectathon
Relaxation topics:
Decision on how to implement and to deal with message signature (https://openncp.atlassian.net/wiki/display/ncp/Open+discussion)
National connector specifications: National Connector Specifications
Cache mechanism
Caching mechanism for the configuration manager
Performance hooks
JIRA Issues review
AOB
LOCATION
Adobe Connect
Room Passcode: @markus.kalliola or @Licinio Kustra Mano
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If you have never attended an Adobe Connect meeting before:
Test your connection: http://ec-wacs.adobeconnect.com/common/help/en/support/meeting_test.htm
Get a quick overview: http://www.adobe.com/products/adobeconnect.html
Adobe, the Adobe logo, Acrobat and Adobe Connect are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
PARTICIPANTS
Today's Meeting Participants:
@Heiko Zimmermann
@João Pedro Cunha Gonçalves
@Massimiliano Masi
@Stéphane Spahni
@TE
@S
@Kostas Karkaletsis
@michele.foucart
MEETING NOTES
Connectathon
Portugal
Austria
EC
Update will follow!
Relaxation topics:
Decision on how to implement and to deal with message signature (https://openncp.atlassian.net/wiki/display/ncp/Open+discussion)
Decision was taken during technical committee of 18/02 to implement digital signature
Discussion regarding the comment published by Natasha on the discussion page
Objective of implementation is to have "integrity"
What are the next steps?
@...: are we using the framework for ssl communication?
- @... will send the link to acces tool signature
Task list, analysis
Issue to be created in JIRA
Next steps, activities, to be discussed during Task force security on Mar 8, 2016
National connector specifications: National Connector Specifications
Feedback received on the page during the security task force
Next steps:
Send the mail to the OpenNCP community for consultation - wait for comment from @...
Then we can start the implementation
@... will create an issue in JIRA and organize it in Epic
Cache mechanism
See Cache implementation through ConfigurationManager refactoring
@...: the use of the tool might expose to network? Proposed to use a simpler solution?
@...: we discussed on multiple instances...since apparently there is no need of database...Massi analysed the different cache mechanisms. After testing, they all behave the same. Implemented and created 5 singleton instances...REDIS and REM cache installed on VM. 2 scenariis were analyzed.
Values cached: all info stored in TSL
@...: Frequency: one a year
Questioning the need of distributed cache...Alternative could be to keep the data local & invalidate? => New version every...max time by node = 10 sec
Discussions on
publicString getProperty(String name) {scheduled.time.between.failed.logs.handling.minutes
João Cunha: I think it works like this (I remember now): if that property is not found, a default value of 60 is use. João Cunha: but needs confirmation
What we could do is to look at epsos properties & check whether they need to be synchronized with others
@...: Micro caching - see comment on page: https://openncp.atlassian.net/wiki/pages/viewpage.action?spaceKey=ncp&title=Open+discussion
@...: How would we load properties?
we would not resolve the performance issue
Next steps:
Look on all the properties that we need => With @... and @...
@... will share the list
Whether to go via distributed cache or REDIS
Continue the page, keeping @... in the loop of the discussions
Mar 4, 2016 SMP/SML 3pm
JIRA Issues review - No time to go through the issues, this will be discussed during the next Technical Committee meeting
AOB
@...: Topic to be put at the agenda of the next meeting: Usage of a toolkit on real time monitoring
Next Technical Committee meeting proposed date Mar 21, 2016 1pm
Update received from IHE regarding MS registrations to the Connectathon:
Portugal, Austria, Cyprus, Denmark, in addition to DG SANTE.
This is a great news since this is confirming our participation (min of 4 being reached).