Migrating the INTO-CPS Application to the Cloud Mikkel Bayard Rasmussen Casper Thule Peter Gorm Larsen Hugo Daniel Macedo DIGIT Aarhus University Centre for Digitalisation, Big Data and Data Analytics AU AARHUS UNIVERSITY DEPARTMENT OF ENGINEERING October 7, 2019
Agenda Introduction The INTO-CPS Project The INTO-CPS Tool Chain The INTO-CPS Application The INTO-CPS Cloud Application Adding Multi-User Support and Cloud Based Co-simulation Technologies of the Cloud-based INTO-CPS Application Architecture of the Cloud Version of the INTO-CPS Application Conclusion Discussion Future Work: Migrating Missing Desktop Application Features
Outline Introduction The INTO-CPS Project The INTO-CPS Tool Chain The INTO-CPS Application The INTO-CPS Cloud Application Adding Multi-User Support and Cloud Based Co-simulation Technologies of the Cloud-based INTO-CPS Application Architecture of the Cloud Version of the INTO-CPS Application Conclusion Discussion Future Work: Migrating Missing Desktop Application Features
INtegrated TOol chain for model-based design of CPSs • EU Cordis webpage
The INTO-CPS Tool Chain
The INTO-CPS Application The INTO-CPS Projects The INTO-CPS Interface The INTO-CPS Outputs DSEs FMUs Resources SysML Model- Models Checking Test-Data- userMetric- Generation Scripts Traceability Multi- Models .project.json README.md
The INTO-CPS Technologies INTO-CPS Application Third Party Development Application frame .... Angular CSS HTML DSE TypeScript JavaScript Gulp ElectronJS Git JavaScript COE NodeJS Chromium Desktop
Drawback: Frustrated Users Troublesome installs � Practice shows that the integration of the diverse tools in the INTO-CPS tool chain forces the installation of several software packages, and multiple versions of some. . . Unexpected performances �� Moreover, as specifications vary, variations in performance are often observed.
Outline Introduction The INTO-CPS Project The INTO-CPS Tool Chain The INTO-CPS Application The INTO-CPS Cloud Application Adding Multi-User Support and Cloud Based Co-simulation Technologies of the Cloud-based INTO-CPS Application Architecture of the Cloud Version of the INTO-CPS Application Conclusion Discussion Future Work: Migrating Missing Desktop Application Features
The INTO-CPS Cloud Application
R.E. Architecture diagram of the INTO-CPS Application codebase Init System Utils Proj Menu Main Bottom Browser DownloadManager FMUBuilder Handler Preview COE Process IntoCpsApp Fetch Settings Traceability DSE view MM view COE view Service view New Traceability COE Config DSE Config MM Component Overview Component Rename Traceability COE Simulation MM Config Config Component COE Service FMU
Cloud issues: Adding Multi-User Support and Cloud Based Co-simulation Configure Save CoSim CoSim Request New Logout Password Simulate Stop Get available Upload Login projects project View Results Actor Configure Save Signup Select Project MM MM
Technologies of the Cloud-based INTO-CPS Application INTO-CPS Application Third Party Development Cloud: AWS (IaaS) Backend Firebase .... Docker TypeScript Docker NodeJS Docker- DSE Compose Docker Frontend Angular Git Docker TypeScript Docker NodeJS COE Docker NGINX Browser Docker
Frontend Micro-service Frontend Server Communication Management Context Component Menu Component Status Component Component Component Display List projects COE status User Authentication Json content List selected Modify Json COE Log User Settings project context Project Management Communication Start simulation import / export / delete COE Console Service (git) REST Simulation Project Modification Trace Daemon Log visualization Compoenent REST Backend
Backend Micro-service Frontend REST REST Server Database SVN Authentication Git Handler DSE Handler COE Handler Storage Handler Handler Project Clone / Pull Push Project Settings Management Create Project Get Project Data Upload Project Download File Update / Create File Upload File Download Project
COEs Container and Pooling FROM openjdk :11 − o r a c l e COPY coe . j a r coe . j a r COPY coe . sh coe . sh RUN yum i n s t a l l net − t o o l s − y RUN mkdir − p / data #!/ bin / sh ADD . / data # My f i r s t s c r i p t RUN chmod +x ./ coe . sh echo ” H e l l o Coe ! ” RUN l s echo $ ( l s ) CMD [ ” ./ coe . sh ” ] myIP=$ ( i f c o n f i g eth0 | grep ’ i n e t ’ | awk ’ { p r i n t $2 } ’ ) EXPOSE 8082 echo $myIP myPATH=’ / data / ’ cd $myPATH coes=’ coes / ’ mkdir − p $coes$myIP Dockerfile cd $coes$myIP $ ( j a v a − j a r . . / . . / . . / coe . j a r ) coe.sh
Outline Introduction The INTO-CPS Project The INTO-CPS Tool Chain The INTO-CPS Application The INTO-CPS Cloud Application Adding Multi-User Support and Cloud Based Co-simulation Technologies of the Cloud-based INTO-CPS Application Architecture of the Cloud Version of the INTO-CPS Application Conclusion Discussion Future Work: Migrating Missing Desktop Application Features
Discussion • Software development was carried out over 80 days including: the migration of existing components: • project management UI • co-simulation launching and visualization UI • Developed from scratch the many cloud specific components absent in the desktop version: • authentication • encrypted web connection • shared COEs pool • Code available at the INTO-CPS Association github • https://github.com/INTO-CPS-Association/into-cps- application-cloud
Future Work: Migrating Missing Desktop Application Features • Logging • Download Manager • Single File Upload • DSE & Traceability & Test Case Generation • Git
Recommend
More recommend