1 / 2

Optimizing Software Development Outside the TN: A Collaborative Approach

This initiative proposes shifting software development outside the TN to reduce operational risks and enhance security. With numerous devices in the TN being outdated and unpatched, this model allows for testing simulated devices using japc-ext-mock, ensuring a safer and more efficient development environment. We recommend establishing a dedicated DEV network that connects office desktop machines and exposes necessary databases and servers while keeping final validation within the TN. Join the discussion to explore these ideas further, led by Vito Baggiolini and other experts.

evers
Télécharger la présentation

Optimizing Software Development Outside the TN: A Collaborative Approach

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. Idea: Move Development out of TN • Idea: • Develop outside the TN • Validate in the TN • Reason: • Risk for operations (erroneous testing with operational devices) • Security issues (not all machines are patched, thus vulnerable) • Not necessary (for people who don’t need direct device access) • For testing, devices can/should be simulated with japc-ext-mock • Most development “lab” FECs are already on the GPN • Possible approach: • Create a “DEV network” with all the office desk-top machines • Expose DBs, JMS, middle-tier servers (e.g. LSA) to DEV network • Expose devices through proxies (read-only, no set()) • Final validation of software still in the TN • To be further discussed - please participate! Vito Baggiolini

  2. Agenda • General BE/CO upgrade strategy for LS1 (Vito, 10') • Changes to the development tools and infrastructure • Development tools (Niall, 15') • Development platforms (VPC, cs-ccr-devX) (Luigi 10’) • Ideas for Development outside the TN (Vito 5’) • Linux platforms (consoles, back-end and front-end) (Vito, 5’) • Changes to widely used software libraries • Brief introduction (Katarina, 5') • CMW and JAPC (Wojtek, 20') • LSA/InCA (Greg, 10') • Controls Configuration DirService (Zere, 10') • SDDS (Chris, 10') Vito Baggiolini

More Related