1. Middleware – ls1 progress and planning BE-CO Tc, 30th september 2013
Wojciech Sliwinski for the Middleware team:
Wojciech Buczak, Joel Lauener,
Radoslaw Orecki, Wojciech Sliwinski, Ilia Yastrebov

2. Announced MW Milestones in 2013
Completed by ?
RDA3 Java (client/server) (alpha)
June’13
RDA3 C++ server (alpha)
July’13
RDA3 integration with: FESA, FGC, PVSS
July-Oct’13
RDA3 C++/Java (client/server) validated
September’13
New JAPC release with RDA3 Java
New FESA3.2 release with RDA3
December’13
Today
RDA3 C++
Integration with FESA, FGC, PVSS
RDA3 validated
New JAPC
New FESA3.2
Tests with eqp.
End LS1
July’13
July-Oct’13
September’13
December’13
Winter’13/14
August’14

3. Changes in the Planning
RDA3 C++ Client
Postponed to Nov’13 (was Sep’13)
Less critical than server side
Must be ready for FESA3 v (Dec’13)
RBAC Java Client – refactoring & API changes
Postponed to Jan’14 (was Oct’13)
RDA3 work much more critical
Does not impact re-commissioning of PS complex early 2014

4. Status & Progress RDA3 Java: Beta release cmw-rda3 v. 0.3.0
Fully working client & server
Deployed in CO Testbed
Dependencies:
cmw-directory-client, cmw-data, cmw-util,
zeromq, accsoft-commons-util, commons-logging
TODO: RBAC integration
RDA3 C++: Beta release cmw-rda3 v
Fully working server, stable public API
cmw-directory-client, cmw-data, cmw-log, cmw-util
zeromq, boost
TODO: RBAC integration, Client C++ API
RDA3 integration with JAPC (japc-ext-cmwrda3)
Fully working for Get, Set & Subscribe
TODO: ParameterGroup, Clean-up of ArrayCalls, Testing

5. Integration with Server Frameworks
RDA3 demos: 6th Aug. & 19th Sep.
Client/server communication: JAPC  RDA3 C++ server
Most important functionality, e.g.: subscription tree, scheduler
FESA3
Work in progress (since Sep.)
Close collaboration between the projects
Few issues have to be addressed (not blocking)
FGC
PVSS
Not started yet
Several discussions were organised
PostMortem

6. Plans until end-2013 Major milestones
October: Validation & testing of RDA3 & JAPC
e.g. WorkingSet start subscriptions time (InCA case)
October (end): Validation of RDA3 based transport for DTM renovation
November (start): RDA3 Java client/server PRO release
November (start): JAPC (japc-ext-cmwrda3) PRO release
November (mid): RDA3 C++ client/server v release
Continue integration with Server Frameworks
FESA & FGC should be completed by November
No dependencies on other projects
Dedicated vertical tests of the new MW
Eqp. groups & InCA/LSA
Good candidates : FGC & PowM1553 FESA3 class (TE/EPC)
Several hundreds instances (PS complex & LHC)

7. What can go wrong in the new MW ?
Performance and/or stability issues, bugs …
Should be minimized by integration & scalability testing
Several use cases planned: WorkingSet, slow-clients, high-freq. subscriptions
Early integration in CO Testbed, CI
Interoperability between RDA2 & RDA3
JAPC connects with RDA2 & RDA3 servers
Tested on several physical servers in CO Testbed
Additional diagnostics will be introduced
Missing subscription updates, dropped requests, …
RDA3 will provide more diagnostics (comparing to RDA2)
Async transport should handle better bursts & overflows
Plan B: Postpone RDA3 release to early 2014
Skip Injectors start-up & prepare properly for LHC start-up (summer’14)
Integration with next major FESA3 release v
Incremental migration of selected systems
FESA3 will provide a ROLLBACK mechanism to RDA2

8. Conclusions Good overall development progress
However, postponed delivery of RDA3 C++ client
Working software released & deployed in CO Testbed
Major Server Frameworks work on integration with RDA3
No BING-BANG migration but gradual
FESA3 v will provide RDA3 with option to go back to RDA2
Validation & scalability tests will be organized
Based on several critical use cases