1 / 7

WP3 Semivirtual Campus Progress Report

Petr Grygarek VSB-CZ. WP3 Semivirtual Campus Progress Report. What was done by WP3 (from last meeting in Bern) ‏. * Working with individual partners on integration of their labs into SVC * CP Usage manual screenshot guide

wallis
Télécharger la présentation

WP3 Semivirtual Campus Progress Report

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. Petr Grygarek VSB-CZ WP3Semivirtual CampusProgress Report

  2. What was done by WP3 (from last meeting in Bern)‏ * Working with individual partners on integration of their labs into SVC * CP Usage manual screenshot guide - http://edinet.cs.vsb.cz/images/9/98/EdinetCP-step-by-step-guide.pdf - describes basic operations for admins and students * User filters on PreconfigImpl reservations* Some testing tools for SVCAdmin added - buttons for immediate initiation of VPN tunnels to partners' labs - ability to view/edit other labs' device management interfaces definitions

  3. Remaining actions needed to finish SVC integration (1)(state current on March 6 as known to WP3)‏ • ALL: • Place the task to the CP • create PreconfigImpl & PreconfigDescr • insert task assignment text • advertise task on the noticeboard) • Finish the configuration cleaning system ASAP • Check the proper operation of local Shibboleth IdP • WP3 have no chance do test it centrally • Preconfigure hostnames to devices wherever possible to simplify further testing

  4. Remaining actions needed to finish SVC integration (2)(state current on March 6 as known to WP3)‏ • AT: • Place the task to the CP • Correct port numbers at Device managements configuration on CP (500x instead of 300x). • Preconfigure devices' hostnames • Finish the configuration cleaning system ASAP • IT-FI • Finish the configuration cleaning system ASAP • HSB-DE: • Place the task to the CP. • Decide how to handle Security Game WWW server accounts for Edinet users (1 account for all users ?)‏ • Decide how to organize groups of users sharing the game

  5. Remaining actions needed to finish SVC integration (3)(state current on March 6 as known to WP3)‏ • SK: • Define device managements on CP and describe the device management addresses/ports on WP3 Wiki. • Not devices are reachable at 10.3.1.1/500x. • The lab description at WP3 Wiki is somewhat messy - there are 4 routers on the picture, but only 3 routers mentioned at in the text window. • Place the task to the CP. • Finish the configuration cleaning system ASAP • CH: • Place the task to the CP. • Add the list of the device management interfaces to WP3 Wiki. • Finish the configuration cleaning system ASAP.

  6. Non-WP3 TODO and open questions (1)‏ • WP6: Instructions for organizing the whole piloting (including timing and outputs) needed • Will we have some technical testing period (who will do the testing ?) or just let the piloting students enter the SVC in “as is” state ? (consider the lack of time)‏ • Which partner will test which module(s)‏ ? • How to protect network devices from misconfiguration/damage ? • Protection not identified as a need during the SVC requirement definition phase • WP6: Bugtracking system – define overall usage guidelines • Define bug processing workflow, name the person responsible for account creation, … • VSB-CZ suggestions may be used

  7. Non-WP3 TODO and open questions (2)‏ • WP1: Are online piloting questionaries ready to collect data ? • WP2: Collect the final versions of the lab tasks and distribute them among other partners ASAP • needed for partners to decide how to incorporate other partners' tasks into currently taught subjects for the for purpose of Edinet piloting • Partners have to place final task's versions to the CP also

More Related