130 likes | 346 Views
Middleware status & Plans for Injector startup in 2014 5 th december 201 3 CO3 meeting. Wojciech Sliwinski for the BE-CO Middleware team: Wojciech Buczak, Joel Lauener Radoslaw Orecki, Ilia Yastrebov , Vitaliy Rapp (GSI). User written. Changes in MW Architecture in LS1.
E N D
Middleware status & Plansfor Injectorstartup in 20145thdecember 2013CO3 meeting Wojciech Sliwinski for the BE-CO Middleware team: • Wojciech Buczak, Joel Lauener • Radoslaw Orecki, Ilia Yastrebov, • Vitaliy Rapp (GSI)
User written Changes in MW Architecture in LS1 Middleware Central services Java Control Programs Upgrade in LS1 VB, Excel, LabView C++ Programs Administration console JAPC API Passerelle C++ Clients RDA3Client API (C++/Java) Device/Property Model Directory Service Directory Service RBAC A1 Service RBAC Service Configuration Database CCDB CMW Infrastructure ZeroMQ RDA3Server API (C++/Java) Device/Property Model CMW integr. CMW int. CMW int. CMW int. CMW int. CMW int. Servers Virtual Devices (Java) FESA3 Server FGC Server PS-GM Server WinCCOA Server More Servers Physical Devices (BI, BT, CRYO, COLL, QPS, PC, RF, VAC, …) Wojciech Sliwinski, Middleware Plans for LS1 and Outlook for LS2
Announced MW Milestones in April 2013 July’13 July-Oct’13 September’13 December’13 Winter’13/14 August’14 Today End-of-Life for RDA2: LS2
Status of the core MW libraries • RDA3 Java: cmw-rda3 v. 0.5.0 • Stable & validated public API • Fullyworkingclient & server • TODO:RBACintegration & RDA2 compatibility • RDA3 C++: cmw-rda3 v. 0.5.0 • Stable & validated public API • Fullyworkingclient& server • TODO:RBACintegration & RDA2 compatibility • JAPC • Full compatibility with RDA2 & RDA3 • TODO:clean-up of ArrayCalls & ParameterGroups
RDA3 integration with Frameworks • FESA3 • Supports GET & SET operations • RDA3 integrationsuspendedtill Spring’14 • New major FESA3 version with RDA3 in June’14 • FGC • Work in progress(since Sep.) • To be completed by February’14 • Waiting for RBAC integration • WinCC-OA (aka. PVSS) & LabVIEW • Work in progress(sinceNov.), prototypeclient & server • Plans: LabVIEW by January’14 & WinCC-OA client by March’14 • WinCC-OA server: not scheduledyet • Waiting for RBAC integration & RDA2 compatibility • PostMortemclient • Just completedfirst version based on RDA3 • Next: validation with the mainusers • Waiting for RBAC integration & RDA2 compatibility
MW Milestones in 2014 Feb’14 Feb’14 March’14 April’14 May’14 RDA2 remainsoperationaltill LS2
Conclusions • Working softwarereleased & delivered to users • All Frameworkswork on integrationwith RDA3 • No BING-BANG migration but gradualintroduction of RDA3 • RDA2 remainsoperationaltill LS2 • FESA3 v. 2.0.0 willprovide RDA3 with option to go backto RDA2 • Validation & scalabilitytestswill be organized • Based on severalcriticalusecases
Additionalslides …. Wojciech Sliwinski, Middleware Plans for LS1 and Outlook for LS2
LS1: Changes in JAPC • New major JAPC version upgrade for RDA3 (September’13) • Public API backward compatible • Possible API extensions, but always compatible • Announcement via accsoft-java-announce list • RequiredActions for JAPC Users • Update JAPC jars (via CommonBuild) • Re-release your product (via CommonBuild) • New JAPC will support communication with RDA2 & RDA3 servers Wojciech Sliwinski, Middleware Plans for LS1 and Outlook for LS2
LS1: Changes in RDA • New major version: RDA3 (June’13 – alpha version) • Public API NOT backward compatible • New protocol, new architecture, new design • Same Device/Property model & Get/Set/Subscribe calls • Announcementvia cmw-news & accsoft-java-announcelists • RequiredActions for RDA Users • For Java: Use new version of JAPC (API unchanged) • For Java: New JAPC will support communication with RDA2 & RDA3 servers • For C++: Upgrade user code to new RDA3 API • For C++: RDA3 will support communication with RDA2 & RDA3 servers • Consequences if NO Action staying with old RDA2 • NOT possible to communicate with new RDA3 servers (FESA3, FGC, etc.) Wojciech Sliwinski, Middleware Plans for LS1 and Outlook for LS2
MW Upgrade strategy in LS1 and towards LS2 • No BIG-BANG migration but gradual • Backward compatible (connection-wise)newRDA3 client library • New RDA3 clients can communicatewith RDA2 & RDA3 servers • FESA3 willexist with both: old RDA2 (FESA3.1) and new RDA3 (FESA3.2) Client appswillmigrateduring LS1 Only for justified, exceptionalcases OldJAPC New JAPC RDA2 RDA3 Gateway Old RDA2client New RDA3client Old RDA2 server Old RDA2 server FEC developersshouldmigrate to FESA3.2 ASAP New RDA3 server FESA2.10 FESA3.1 FESA3.2 Wojciech Sliwinski, Middleware Plans for LS1 and Outlook for LS2
Controls Middleware (CMW) Renovation in LS1 Linux/Windows Linux/Windows C++/Java process C++/Java process CMW client API CMW client API CORBA ZeroMQ TCP/IP TCP/IP CORBA ZeroMQ CMW server API CMW server API C++/Java process C++/Java process RT Linux/LynxOS RT Linux New communication library ZeroMQ replaces CORBA Complete rewrite of the CMW library Today: Beta release PRO release in Q1 2014 Will be open-source: LGPL External interest: GSI & LBNL
Current MW Architecture User written Middleware Java Control Programs Central services VB, Excel, LabView C++ Programs Administration console JAPC API Passerelle C++ Clients RDA Client API (C++/Java) Device/Property Model Directory Service Directory Service RBAC A1 Service RBAC Service Configuration Database CCDB CMW Infrastructure CORBA-IIOP RDA Server API (C++/Java) Device/Property Model CMW integr. CMW int. CMW int. CMW int. CMW int. CMW int. Servers Virtual Devices (Java) FESA Server FGC Server PS-GM Server PVSS Gateway More Servers Physical Devices (BI, BT, CRYO, COLL, QPS, PC, RF, VAC, …) Wojciech Sliwinski, Middleware Plans for LS1 and Outlook for LS2