1 / 8

Middleware PLANS for LS1 20 th March 201 3

Middleware PLANS for LS1 20 th March 201 3. Wojciech S liwi n ski BE-CO-IN for the Middleware team. Changes in MW Architecture in LS1. User written. Middleware. Configuration Server. Central services. VB, Excel, LabView. Java Control Programs. C++ Programs. Administration

milla
Télécharger la présentation

Middleware PLANS for LS1 20 th March 201 3

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Middleware PLANSfor LS120th March 2013 WojciechSliwinskiBE-CO-IN for the Middleware team

  2. Changes in MW Architecture in LS1 User written Middleware Configuration Server Central services VB, Excel, LabView Java Control Programs C++ Programs Administration console Passerelle C++ Clients RDA Client API (C++/Java) Device/Property Model Configuration Database CCDB Directory Service RBAC A1 Service Directory Service RBAC A1 Service Log/Tracing Service CMW Infrastructure CORBA-IIOP Proxy Server RDA Server API (C++/Java) Device/Property Model Virtual Devices (Java) FESA Server FGC Server PS-GM Server PVSS Gateway More Servers Servers DIP GW AlarmMon Physical Devices (BI, BT, COLL, PC, RF, …) Wojciech Sliwinski, BE-CO TC: Middleware Progress Report and Plans

  3. Middleware Upgrade in LS1 • Why to upgrade ? • Replace CORBA-basedcommunicationlibrary • Becamelegacy, not activelysupported maintenanceissue • Major technicallimitations, e.g. blockingcommunication • Outstanding OP issues • No protectionagainst’slow/bad’clientapplications • Poorscalabilitywhenmanyclientssubscribed • Missing support for priorityclients (e.g. SIS, PM, InCA) • + others … • Upgrade Plan(tentative) • Convention: RDA2 (OLD)  RDA3 (NEW) • Integration of RDA3 with JAPC (summer’13) • Integration of RDA3 with FESA3, FGC & PVSS (autumn’13) • Validation & testing of MW with Eqp. groups (winter’13/14) • Operational deployment in 2014 (e.g. FESA3 classes)

  4. LS1: Changes in RDA • New major version: RDA3 (summer’13) • Public API NOT backward compatible • New protocol, new architecture, new design • Same device/property model & Get/Set/Subscribe calls • Announcement via accsoft-java-announcelist • Note: FESA2.10 stays with RDA2, FESA3 willuse RDA3 (end of 2013) • RequiredActions for RDA Users • For Java: Use new version of JAPC • 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.) • NOTpossible to perform Get/Set/Subscribe on RDA3 servers

  5. LS1: Changes in JAPC • New major JAPC version  upgrade for RDA3 (summer’13) • Public API backward compatible • Possible API extensions, but always compatible • Announcement via accsoft-java-announce list • Extensions requested by other projects (InCA/LSA, JMON) • Public API backward compatible • RequiredActions for JAPC Users • Update JAPC jars (via CommonBuild) • Re-release your product (via CommonBuild) • New JAPC will support communication with RDA2 & RDA3 servers • Consequences if NO Action  staying with old JAPC & RDA2 • NOT possible to communicate with new RDA3 servers (FESA3, FGC, etc.) • NOTpossible to perform Get/Set/Subscribe on RDA3 servers

  6. LS1: Changes in RBAC • Rename of RBAC Java projects (summer’13) • NOT backward compatible change • Change of package names  different imports • Old projects deprecated: • accsoft-security-rba rbac-client • accsoft-security-rba-util  rbac-util • accsoft-security-rba-util-gui  rbac-util-gui • + clean-up of deprecated API (methods) • Announcement via accsoft-java-announcelist • RequiredActions for RBAC Users • Update product names in product.xml • Update RBAC jars (via CommonBuild) • Update imports in user code • Re-release your product (via CommonBuild) • Consequences if NO Action • End-of-life for old RBAC Java projectsFebruary’14 • Afterthatdate, oldprojectsREMOVED from PCROPSrepository

  7. Middleware Team • Wojtek Sliwinski (Lead) 100% – Directory, RDA, Proxy, RBAC • Felix Ehm 30% – JMS, Log/Tracing, Feedback/Metrics • Joel Lauener 90% – CMW Admin, Directory, RDA, GM, DIP Gw. • Kris Kostro20% – DIP Gateways, RDA3 • Wojtek Buczak 30% – JAPC Core • Ilia Yastrebov100% – RDA, RBAC, Passerelle, Proxy, Log • Radoslaw Orecki 100% – Directory, RDA, Proxy • Support: cmw-support@cern.ch, rbac-support@cern.ch • Docs: http://wikis/display/MW

  8. Conclusions • LS1  the uniqueopportunity for major upgrade! • Involved MW libraries thoroughly tested in CO Testbed • Your action is required • Contact CMW support for related questions

More Related