20160318 - Meeting minutes, Friday March 18th 2016 - Task force SML/SMP

Owned by michele.foucart
Last updated: Mar 18, 2016
3 min read

 

Estimated: 15:00 to 16:00 CET.

Performed: 15:05 to 15:53 CET

Agenda

  1. Introduction
    1. Approval of previous meeting minutes
    2. Approval of the agenda
    3. Review of the actions from the previous meeting
  2. Feedback from Oasis Technical meeting - change request on SMP
  3. Integration of the SMP with OpenNCP
    1. Business analysis 0.9 (see attached file)
    2. Cache mechanism
  4. AOB
    1. Connectathon
    2. Next meeting

Location

  • AdobeConnect:

http://ec-wacs.adobeconnect.com/openncp/
Room Passcode:  markus.kalliola or michele.foucart
------------------------------------------------------------------------------------------------
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.
------------------------------------------------------------------------------------------------

Adrien FERIAL

Yves ADAM

Joao Cunha

Kostas Karkaletsis

Massimiliano Masi

YacoubouY

michele.foucart

Support documents

Meeting Notes

  1. Introduction
    1. Approval of previous meeting minutes
    2. Approval of the agenda
    3. Review of the actions from the previous meeting
  2. Feedback from Oasis Technical meeting - change request on SMP
    1. Joao and Massi attended the meeting with DIGIT. 8 change requests were submitted
      1. 7 change requests will be solved quickly
      2. 1 change regarding the requirement on digital signature is still under discussion => There is a chance that Oasis come back with a solution that does not suits eHealthDSI needs, impacting OpenNCP
        1. One of the problem arises because we are using a centralized SMP while the model is done for distributed signature
        2. If Oasis does not come with a solution, not wanting to implement the eHealthDSI use case (central SMP) => we need to take a decision, changing SMP or change trust model; other solution would be to use an extension (but not the preferred one)
        3. We are expecting a feedback from the Oasis technical committee in 4 weeks
  3. Integration of the SMP with OpenNCP
    1. Business analysis 0.9 (see attached file)
      1. Yves received feedback from Joao - First 15 points are easy to solve, for the other points, Yves will come back to Joao before distributing an updated version to the Community
    2. Cache mechanism
      1. Last meeting: SMP/SML waiting a decision for today
      2. Massimiliano Masi:
        1. research made on different cache mechanism possibilities. Merged TSL extension and SMP to achieve an implementation
        2. 4 scenariis => See OpenNCP page for the detailed analysis and tests results https://openncp.atlassian.net/wiki/pages/viewpage.action?spaceKey=ncp&title=Cache+implementation+through+ConfigurationManager+refactoring
          1. Redis
            1. Linear increase
          2. Redis + LUA
          3. Memcache
            => Redis and Memcache behave exactly the same
          4. Microcaching - very similar in performance to Redis. DB kept as it is (little change in actual config), value increases
            1. Difference is on the standard deviation: time to connect to the database
            2. Limitations of the test: use of Eclipse, the object get cached after some time. The standard deviation is expected to be higher
          5. Change proposal solution (hibernate) :
            1. the proposal needs to be better clarified, it needs metric, need to be better clarified
            2. This solution can be complex to implement too, conclusion about simplicity to implement is "subjective".
            3. Publish this solution on the same page to make a comparison
        3. Cache mechanism is part of the overall architecture, not only related to SMP/SML
        4. Need metrics, performance...
      3. In SMP/SML: discussion is how to store.
      4. Adrien confirms that in SMP/SML there is no strong requirements on cache mechanism. Cache limits the number of request. How it is implemented inside is implementation specific.
        1. We could go for a very simple solution (spring cache, simple annotation...). But does not want to interfere in the discussion.
      5. We should compare the different scenarios in term of implementation effort, time, costs... this dimension should be included in the table
      6. DG SANTE will share next week the results of the stress/load tests
        1. It is crucial to use the same approach!
  4. AOB
    1. Connectathon
      1. Tests in scope: Generate TSL, SML record and scrutiny test => same test as in Lisbon (won't test the on the fly lo-up for the metadata => Need to deploy an SMP like DIGIT did last time for Lisbon? We'll need to send a request to DIGIT
      2. Yves cannot come to the Connectathon for contract administrative reasons
    2. Next meeting
      1. Cache discussion  11am CET
      2. SMP/SML task force 3pm CET