1 / 11

Middleware renovation – Plans for validation and migration 16 th april 201 3

Middleware renovation – Plans for validation and migration 16 th april 201 3. Wojciech Sliwinski BE-CO-IN for the Middleware team: Felix Ehm, Kris Kostro, Joel Lauener, Radoslaw Orecki, Ilia Yastrebov , [ Andrzej Dworak ] Special thanks to : Vito Baggiolini and Pierre Charrue.

sybil
Download Presentation

Middleware renovation – Plans for validation and migration 16 th april 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 renovation– Plans for validationand migration16thapril 2013 Wojciech SliwinskiBE-CO-IN for the Middleware team: • Felix Ehm, Kris Kostro, Joel Lauener, • Radoslaw Orecki, Ilia Yastrebov, [Andrzej Dworak] • Special thanks to: Vito Baggiolini and Pierre Charrue

  2. Agenda • MW Upgrade milestones in 2013 • Risk assessment and mitigation • Conclusions Wojciech Sliwinski, Middleware Renovation: Plans for Validation and Migration

  3. MW Upgrade Milestones in 2013 July’13 October’13 Winter’14 Spring’14 August’14 Wojciech Sliwinski, Middleware Renovation: Plans for Validation and Migration

  4. Riskassessment and mitigation Wojciech Sliwinski, Middleware Renovation: Plans for Validation and Migration

  5. Risk: Wrong product developed(wrong requirements) Mitigation: Early and continuous involvement ofclients & experts • We involved clients and experts since 2010 • Requirements review with all major clients • Technical discussions with eqp.experts • Iterative development involving the Reviewteam • Design meetings (API and internals) since January 2013 • Alpha versions will be available for feedback and validation severalmonths before the final release • Feedback is continuously integrated in development (= iterative) Wojciech Sliwinski, Middleware Renovation: Plans for Validation and Migration

  6. Risk: Product is (too) late Mitigation: Careful planning and follow-up Fall-back to less ambitious goals • Planning prepared and followedby the MW team • Taking into account needs and priorities of other CO projects and clients • Regular follow-up • In CO internally by TECcoordinator • In informal meetings with the MW experts (as doneso far) • Fall-back to less ambitious goals • Plan priorities of functionality • Drop (postpone) work with lower priority Wojciech Sliwinski, Middleware Renovation: Plans for Validation and Migration

  7. Risk: Product has bugs orincompatibilities Mitigation: Early, continuous testing (unit, functional & integrationtests) • Unit tests to asses quality inside the MW project • Requireddev. phase in the MW team • Functionality tests in CO Testbed • Functionality of CMW only • Integration tests to check interoperability • Integration with FESA in CO Testbed • Integration with FGC in FGC Lab Wojciech Sliwinski, Middleware Renovation: Plans for Validation and Migration

  8. Risk: Bugs affect operations Mitigation: Gradual Migration (1) • No BIG-BANGmigration but gradual • Backward compatible (connection-wise)newRDA3client library • New RDA3clients can talk to old RDA2servers • FESA3 willexist with both: old RDA2and new RDA3 OldJAPC New JAPC Old RDA2client New RDA3client Old RDA2 server Old RDA2 server New RDA3 server FESA2 FESA3 FESA3 Wojciech Sliwinski, Middleware Renovation: Plans for Validation and Migration

  9. Risk: Bugs affect operations Mitigation: Gradual Migration (2) • Deploy firston systems controlled by the MW team • E.g. Proxies, Gateways • Gainexperience and confidence • Start deploymentwith less critical systems first Wojciech Sliwinski, Middleware Renovation: Plans for Validation and Migration

  10. Risk: Bugs affect operations Mitigation: Fast deployment of bugfixes • If (inspite of all) something goes wrong in operations • Fast reaction from the MW team • In CO, we will study the need and mechanisms to quickly upgrade also servers Wojciech Sliwinski, Middleware Renovation: Plans for Validation and Migration

  11. Conclusions • LS1  the uniqueopportunity for major upgrade! • MW librarieswill bethoroughly tested, especially in CO Testbed • Staying with old MW meanshiddenlong-term risk, difficult to estimate • We have the requiredknow-how and momentumto push the changes • Your action is required • Contact the MW team for related questions Wojciech Sliwinski, Middleware Renovation: Plans for Validation and Migration

More Related