100 likes | 175 Views
Petr Grygarek VSB-CZ. WP3 Semivirtual Campus Progress Report. Purpose of the WP. Design and implement SVC software infrastructure Investigate existing partners' remote access solutions and remote lab usage patterns Summarize implemented capabilities
E N D
Petr Grygarek VSB-CZ WP3Semivirtual CampusProgress Report
Purpose of the WP Design and implement SVC software infrastructure • Investigate existing partners' remote access solutions and remote lab usage patterns • Summarize implemented capabilities • Estimate expected workload of the system in real usage • needed to select proper HW/SW technologies with appropriate power • Design of SVC infrastructure architecture • Implementation of designed SVC software infrastructure • Internal testing, piloting (with WP6) + SVC maintenance
Working Progress (1) • Investigation of Partners’ Lab • overall organization and usage pattern • number of users and devices • device management types • Creation of summary report • http://edinet.cs.vsb.cz/index.php/Current_Partners%27_Remote_Labs_Status • Definition of SVC implementation goals • includes existing usage patterns of partners’ lab • definition of user roles and use cases • realistic requirements which corresponds to available time and resources • possibility of further extensions in scope of another projects taken into account • Design of SVC infrastructure architecture
Working Progress (2) • Estimation of expected workload • Selection of implementation platform • http://edinet.cs.vsb.cz/index.php/Implementation_Platform • Installation of Edinet WP3 MediaWiki for internal WP3 coordination • http://edinet.cs.vsb.cz • user Edinet, password SemiCampuS • Read-Only for non-WP3 users
Outcomes (1) • Detailed architecture proposals of • Technique of remote access • Technique to interconnect multiple partner’s labs • http://edinet.cs.vsb.cz/index.php/Remote_Access_and_Lab_Interconnection • Reservation system • http://edinet.cs.vsb.cz/index.php/Reservation_System • Includes specification of Task Descriptions • Authentication, Authorization and Accounting Infrastructu`re • http://edinet.cs.vsb.cz/index.php/Authentication%2C_Authorization_and_Accounting • Technical support for evaluation of students • http://edinet.cs.vsb.cz/index.php/Evaluation_of_Students • Specification of compliance of SVC with Pedagogical Principles
Outcomes (2) • Technical decisions • Decision of implementation platform with regard to estimated workload • opensource technologies (OpenVPN, PHP, Apache, MySQL, …) • http://edinet.cs.vsb.cz/index.php/Implementation_Platform • Placement of Task Documents • currently under discussion • Structure of Common Portal user GUI • under development • Assessment of Distributed System Technical Issues • Correct handling of timezones, system security etc. • http://edinet.cs.vsb.cz/index.php/Distributed_System_Technical_Issues
Resource Situation – VSB-CZ(does not include people working in other WPs) • 2 MSc. diploma work students • SVC implementation programming • 3 PhD students (out of their thesis topics) • SVC architecture design • investigation of technical issues of utilized lab interconnection and remote access technologies • 3 teachers • SVC architecture design • management and coordination
Resource Situation – other partners(34 WD/partner + UBE-CH) • Will be discussed ASAP • UBE-CH • AAA infrastructure implementation • IT-FI • Graphical GUI design - CSS styles of portal Web pages ? • HSB-DE – will be discussed • FHJ-AT – will be discussed • Creation of intelligent bug report forwarding system which qualifies and processes critical error records from system logs of individual SVC componenents (relation to WP6) ? • TUKE-SK - will be discussed • Subtasks to assign • Monitoring of SVC functionality (Nagios, Zabbix, …) • TUKE-SK ? • Hosting of Common Portal (dedication of 1 PC on UPS is needed, possibly an instance of virtual machine) • We need is ASAP for internal testing; it may continue to operate during piloting • VSB-CZ needs SSH root access • some ports will have to be opened in hosting institution firewall • TUKE-SK ?
Open Questions • Assignment of some developer works to other partners • WD of UBE-CH in WP3 ? • Handling of lab documents on SVC Web • Do we want to permit editing of lab documents by multiple partners ? • It requires a system of user permissions and usage of storage format which allows easy editing • HTML/Wiki is OK, not PDF (requires to make accessible both resulting document and it’s source code) • Decision will be made together with WP2 • In Jyvaskyla it was appointed that it is out of scope of Edinet project to develop our own full-featured web-based document management system • but there is still an option to some existing opensource Web content management system
Next Steps • Designate 1-2 persons from technical partners to familiarize with SVC architecture and collect comments (if any) before start of implementation work • Architecture Definition Board mentioned in original WP3 plan • Installation of CVS system (Subversion) • Start of programming of Common Portal • Start of programming of authorization extensions of VPN OpenVPN gateways • checking of validity of previous reservations during access attempt • Start of AAA implementation (UBE-CH) • related to implementation of local user databases and including maintenance Web GUI