search

reTHINK-project / core-framework

The main goal of WP3 is to provide the reTHINK core framework comprised by the runtime environment where Hyperties are executed and the messaging nodes used to support messages exchange between Hyperties.
Apache License 2.0
1 stars 0 forks source link

D3.5 QoS Control Specification #177

Closed pchainho closed 7 years ago

pchainho commented 8 years ago

see https://github.com/reTHINK-project/dev-runtime-core/issues/105

emmelmann-fokus commented 8 years ago

This relates to the TURN service and not to the LHCP. Kay is implementing it for DT and Ewa leads for Orange. We did not have any stacks in the QoS-related runtime core part.

pchainho commented 8 years ago

I understand the LHCP is one component of reTHINK QoS Control and now we have to specify how to fully integrate it in the Core Framework

EwaJan commented 8 years ago

Simon is working on integration of TURN-based solution and will provide soon a description along with isolated piece of code.

emmelmann-fokus commented 8 years ago

@EwaJan @sbecot Perfect. Let's sync next week then on how to structure the corresponding section in the deliverable. Any preferred time / date for a short call?

emmelmann-fokus commented 8 years ago

Syncing with @sbecot , there is currently no interaction with the runtime; so there is ongoing discussion if this section should be skipped in this deliverable and included -- once available -- in the QoS-focused deliverable.

pchainho commented 8 years ago

I'll propose a meeting to clarify this

emmelmann-fokus commented 8 years ago

@pchainho please initiate a doodle poll for a call.

pchainho commented 8 years ago

Here is the doodle link:

http://doodle.com/poll/bu92a6kg7wvhzb8m

kay-haensge commented 8 years ago

Hi all, I will be on vacation for the next two weeks. However, as heard from Steffen, there is a proposal to re-arrange/move that section towards the next phase. A short notice that this is still under consideration and will be evaluated in further progress of the project seems valid for the current deliverable. I would consider that as a feasible progress.

Otherwise, I am back on 19th September and can contribute to this. Hence, until the end of the month, we might have some time to iterate on a contribution for that

Do you have other opinions how to proceed?

I leave the decision(s) up to you and will contribute as soon I am back.

Sorry and Best Regards,

Kay

emmelmann-fokus commented 8 years ago

From @pchainho message in https://github.com/reTHINK-project/dev-runtime-core/issues/105 I assume that we will provide our contributions in the location given therein, i.e., https://github.com/reTHINK-project/specs/blob/master/qos/readme.md .

Per last telco focusing on the QoS contributions, @pchainho will take what we will provide there, and integrate that in D3.5 (i.e. he takes the editorial lead for the QoS section in the Word document to be delivered to the EU).

emmelmann-fokus commented 7 years ago

To proceed here, we need to agree and close on https://github.com/reTHINK-project/specs/issues/16

@Endebert and I feel that the library-based approach is doable; but we need all partner to agree that we proceed this way.

emmelmann-fokus commented 7 years ago

Closing. All contributions are available, see:

https://github.com/reTHINK-project/specs/issues/16 https://github.com/reTHINK-project/specs/blob/master/dynamic-view/qos/readme.md https://github.com/reTHINK-project/specs/blob/master/qos/readme.md