-
Notifications
You must be signed in to change notification settings - Fork 10
Meeting 2020 06 22
-
Review of actions
- From the previous meeting:
- (2020-05-25) ACTION: Piotr will add develop branch which will include work in progess branches (rfc-10)
- the branch is there but not yet merged as Piotr ask for clarification for what to do with potential conflicts
- Older:
- (2020-05-11) ACTION: Andy will reverse the merge and do rebase on RFC-1
- From the previous meeting:
-
Status of the existing RFC list
-
The current goal:
- goal RFC-8 and RFC 12
-
update on current WIP
- RFC-12 Publisher-Subscriber protocol
- RFC-13 Publisher-Subscriber protocol implementation with ZMQ
- RFC-8 Device server
- RFC-1 Tango Controls
- RFC-14 Logging Service
- RFC-10 Request-Reply
-
new RFC-s proposition
- no new RFCs
-
-
AoB:
- vacation period
-
Next meeting:
Participants: Vincent Hardion (MAX-IV), Lorenzo Pivetta (Elettra), Reynald Bourtembourg (ESRF), Piotr Goryl (S2Innovation)
-
Review of actions
-
From the previous meeting:
- (2020-05-25) ACTION: Piotr will add develop branch which will include work in progess branches (rfc-10)
- the branch is there but not yet merged as Piotr ask for clarification for what to do with potential conflicts,
-
Older:
- (2020-05-11) ACTION: Reynald will reverse the merge and do rebase on RFC-1
-
-
Status of the existing RFC list
-
The current goal:
- RFC-10
-
update on current WIP
-
RFC-13 - Publisher-Subscriber protocol implementation with ZMQ
-
RFC-8 Device server - merged into 'draft' branch. Gratulations!
-
RFC-1 Tango Controls - no news
-
RFC-10 Request-Reply - Vincent has sent a PR with a list of features to specify. Piotr will merge it into the branch.
Below are the topics from the PR and volunteers:
- Reconnection - Piotr
- Version compatibility
-
Message - Vincent SHOULD include:
- client process idendification i.e pid
- source (cache or device)
- note about request source traceing. It may be moved to the black box section
-
Exception
-
Timeout
-
Synchronous request
-
Asynchronous request TODO understand the PUSH_BACK model. CORBA or more generic?
-
Cache - Lorenzo
- Here just mention. It should be written as RFC-16
-
Serialisation - Lorenzo
- Say only it is up to a Device Server and that it allows different modes of serialisations.
- Maybe put group requests for attributes should be in this section
-
-
new RFC-s proposisitons:
- Group requests
-
-
AoB:
-
Architecture overview:
- It should go to RFC-1,
- It should be graphics showing Tango architecture
- component-connector view,
- modules view, not necessery formal (like UML)
-
vacation period - next meeting will be chaired by Michał.
-
-
Next meeting: 06.07.2020