20 likes | 125 Views
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)
E N D
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
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