Cloud4all WP103 2014-05-08

From wiki.gpii
(Redirected from Cloud4all WP103 2014-05-07)
Jump to: navigation, search

Back to meetings list

Time and date


Important Information for the Meeting

This is a meeting of WP103 within the European Project Cloud4All. However, the minutes of the meeting will be made available to the public to allow people outside Cloud4All to follow our thoughts. If, in the meeting, you want to share confidential information that should not appear in the public minutes, you need to state so in the meeting. This is in line with the Cloud4All Consortium Agreement, section 10.

Please connect to the audio using gotomeeting:

1. Please join my meeting.

2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone.

  • United States: +1 (213) 493-0618
  • Australia: +61 2 8355 1036
  • Austria: +43 (0) 7 2088 1036
  • Belgium: +32 (0) 28 08 4345
  • Canada: +1 (647) 497-9372
  • Denmark: +45 (0) 69 91 89 24
  • Finland: +358 (0) 942 41 5788
  • France: +33 (0) 170 950 586
  • Germany: +49 (0) 811 8899 6928
  • Ireland: +353 (0) 19 030 053
  • Italy: +39 0 693 38 75 53
  • Netherlands: +31 (0) 208 080 212
  • New Zealand: +64 (0) 4 974 7243
  • Norway: +47 21 04 29 76
  • Spain: +34 931 81 6713
  • Sweden: +46 (0) 852 500 182
  • Switzerland: +41 (0) 225 3311 20
  • United Kingdom: +44 20 3657 6777

Access Code: 619-028-605 Audio PIN: Shown after joining the meeting

Meeting ID: 619-028-605


andres ignacio javi kasper colin guillem


Last meeting minutes


minutes approved

CAS <-> Flow Manager integration, run-time layer

Guillem: working on integrating real motes. Next steps to integrate the CAS with the FM. Next steps? Colin: define requirements for integration (by mail) Guillem: websockets - who's starting the connection? CAS: the FM Guillem: the CAS sends all the info throuth the websocket. Colin: needs payload with context information. Guillem: mock-up client that emulates what the FM does. Or we can modify the FM to start this connection to the context. How can the FM know where to connect? Colin: part of its config file. The FM has configuration for each of the server with which it collaborates with. Guillem to start developing or start doing some technical documentation?? Colin: wiki page that describes how the comm is established, what the payload looks like. Guillem: how the fm works? Colin: start working on the documentation. Andrés: websocket or Guillem: we are talking about the websockets to send the info from the sensors to the FM. On the other hand, we have an API to create the user and the sensors, think we should stick on the API for creating this. Colin: websockets are for a particular use case. Guillem: the CAS will recieve a lot of connections from different FM, and hte CAS has to send only the context from one or the other users. All the sensible important context will be sent to the FM. It is important to send the context for a particular user. The payload will contain info about the user id. C: the FM will provide the user token. Location? G: already implemented in teh CAS. The FM should send user id + GPS location. G: not include administration until the profile management tool with advance security functionalities is implemented. Probably deprecate the user API. CC: is a library on top of Web Sockets, and that's how we'll use it :) AI: may we use other events rather than the ones from websockets? GS: yes CC and GS agree on "using" GS redis or mongo.db CC up to you

Evaluation of contexts on preferences sets

KM Context is used in several parts of the project. in several parts of the framework we need to evaluate it.the conditions and the contexts and the preferences sets. have a single component to evaluate the {working of the system maybe???}

AI does it suffice with unit testing? Colin: evaluating context -> does not mean evaluation as 'testing', but in the 'computer science' term. The user defines in the preferences set 'give me a nice high contrast view when the brightness is higher than x'. Kasper: Evaluation means the part that reads this conditions, compares to the current environment (coming from the ER and the CAS) and takes a decision. Kasper: we need to make sure that the MM teams know this and agree with this. This is not explicitly in the DoW. Andrés: they would have to do that for the non-conditional part of the preference set. The evaluation mechanism should be the same. Kasper: it's more complex to evaluate preferences with conditions than plain preferences.

K has and acceptance testing for the framework (instead of A doing fake unit testing)

next meeting

next meeting MMM and testing thursday works but next week is holiday in Madrid friday 16 at 2 pm CEST