Presentation is loading. Please wait.

Presentation is loading. Please wait.

2 SEEREN The SEEREN2 initiative is co-funded by the European Commission under the FP6 Research Infrastructures contract no. 026748.

Similar presentations


Presentation on theme: "2 SEEREN The SEEREN2 initiative is co-funded by the European Commission under the FP6 Research Infrastructures contract no. 026748."— Presentation transcript:

1 2 SEEREN The SEEREN2 initiative is co-funded by the European Commission under the FP6 Research Infrastructures contract no Technical Execution Plan Costas Kotsokalis / Yannis Mitsos SEEREN2 Technical Coordinator / SEEREN2 Operations Manager Greek Research and Technology Network (GRNET) /

2 Athens, October 13 th, Overview oTechnical Execution Plan: Live document oDefinition of: oRequired technical activity (based on Annex-I) oTask assignment oTask inter-dependencies oFine-grain temporal sequence of tasks oEstimation of risks oT+1: Define strategies to avoid them

3 Athens, October 13 th, New services to be implemented oWith no particular order: oNetwork security oIP Telephony oVideo Conferencing oVideo Streaming oQoS Provisioning oBandwidth on Demand oDirectory Services oIdentity Management, AAA oEduroam oNetwork Database oMCU/GKP oMulticasting oCorrelation of active & passive monitoring oMonitoring & management tools integration oTimesheet/Groupware/Wiki software? This is to help the consortium!

4 Athens, October 13 th, WP2 / WP3 oWill not elaborate on WP2 & WP3 oHave proceeded greatly after schedule crashing oFinal network topology known by now

5 Athens, October 13 th, WP4 (1) oA4.1: Define operational procedures oActivity leader: Kotsokalis oOne-off task (but can be updated if/when things do change) oPart of this discussion today oMust take decisions oMust be ready until the 22 nd, even if in premature form oShould provide strict activity model of everyday & uncommon tasks oBasic tasks oEstablish use cases oProvide formal description oModel interactions between partners on technical issues oFCAPS model oNotation oInitially can be a list of solutions to different problems or other conditions oEventually: UML?

6 Athens, October 13 th, WP4 (2) oA4.1 (cont’d): First must define teams oAPMs oInternational connections: Edin, Goran, Neki, Octavian, Slavko, Tamas, Vedrin, Yannis oNational connections: Amir, Dejan, Dorian, Kozeta, Milorad, Novica oNME o== APMs? oSIEs oCan be defined at the beginning of each service development phase oMailing list for each SIE? oHelpdesk NME Help Desk Operator # SIE # APMs NOCs PSC

7 Athens, October 13 th, WP4 (3) oA4.2: Define acceptance tests oActivity leader: Rusu oOne-off task oInput: D07 oOutput: D09a oRefers to network links only oBasic tasks: oDefine pragmatic methods for acceptance tests taking under consideration the equipment available (including exact setup suggestions) oDefine metrics to be used oDefine analysis method to follow including expected input, required output, acceptance thresholds for output variables oWhat about DF? oMust be ready for non-DF links (even as a premature draft) until the 22 nd.

8 Athens, October 13 th, WP4 (4) oA4.3: Deliver equipment and connections (Core provider) oContracts under way o“Revision is the mother of all knowledge” (ancient Greek saying) o…so re-view the final topology oFirst connection delivered on the 22 nd

9 Athens, October 13 th, WP4 (5) oA4.4: Adjust equipment configuration oActivity leader: Mitsos oInput: D07, D09a, A4.3 oOutput: D09b oAll NRENs that are not willing to share their edge router config should have a tested repository installation in place. oNetIS module can do the work though oBasic tasks for each link: oIPv4 connectivity should be available right away oPerform acceptance tests as defined in A4.2 oInitiate Network DB (NetIS module?) oApply necessary changes (OS upgrades, routing plan changes, etc) oRight next (even in parallel with establishing other connections): oIPv6 connectivity oBase QoS (let’s agree today what this means) oMulticast

10 Athens, October 13 th, WP4 (6) oA4.5: Technical support in stable operation oActivity leader: Gajin oLong-standing process oInput: A4.1 oOutput: D12 oBasic tasks: oHelpdesk overview oDaily monitoring of open TTs – not closing, just notifying that there are open tickets and people should close them if issues are resolved. oDaily monitoring of links’ performance and uncommon patterns oReaction to problems encountered, communication with core provider when required oSLA check against operator data oUsage statistics oPeriodic overall assessment of the SEEREN2 infrastructure oThis is also part of the “procedures” discussion… oHave skype IDs for everyone by now. Publicize to the list?

11 Athens, October 13 th, WP5 (1) oA5.1: Review services and tools state of the art oActivity leader: Maray oOne-off oBasic tasks: oLocate candidate software & technologies to be used oAssess their suitability for the cause of SEEREN2 and the SEEREN2 networking infrastructure oDescribe capabilities of each software for interaction with external services oStandards compliance oMessage passing methods oMessage format oEvaluate the best options and come up with conclusive suggestions on the proper toolset oWhenever necessary, suggest software to be developed by the consortium oQuestionnaire to extract services that users need/prefer: Tamas, Octavian, Slavko, Yannis, Costas oSIEs will have to do this oNeed to move on fast; Let’s try to plan this today according to current situation

12 Athens, October 13 th, WP5 (2) oA5.2: Execute feasibility study oActivity leader: Rusu oOne-off oInput: A5.1 oBasic tasks: oProvide detailed study on the risk factors related to each module in the toolset proposed by A5.1 oSuggest architectural/implementation options for tools to be developed by the consortium oSIEs will have to do this oMust follow right after A5.1

13 Athens, October 13 th, WP5 (3) oA5.3: Define architecture and deploy services and tools oActivity leader: Jeliazkov/ISTF oLong-standing process oInput: A5.1, A5.2 oOutput: D13 oBasic tasks: 1.Define in full the interactions between different services deployed 2.Develop necessary code as suggested by input activities 3.Define tests for quality assurance, carry out the tests 4.Identify rework required in readily available software 5.Execute staged deployment of software (ready & custom) 6.Provide support for the proper operation of software modules o1-4: SIEs o5-6: NME

14 Athens, October 13 th, WP5 (4) oA5.4: Evaluate performance and acceptance of services and tools oActivity leader: Gajin oLong-standing process oInput: D13 oOutput: D15 oBasic tasks: oPerformance, correctness & completeness evaluation of deployed services oDocument the development & deployment procedures used by the project oIdentify related technical issues of importance and provide training suggestions to WP6 oALL technical people must work on this activity oDocumenting our work very important

15 Athens, October 13 th, Notes oThis presentation will be updated today with notes & APs from our discussions, will quickly go through it at the end of the meeting oNext technical meetings oMarch 2006 – Kopaonik oMay 2006 – w/ TERENA06?/15-18 May

16 2 SEEREN The SEEREN2 initiative is co-funded by the European Commission under the FP6 Research Infrastructures contract no Technical Execution Plan Costas Kotsokalis / Yannis Mitsos SEEREN2 Technical Coordinator / SEEREN2 Operations Manager Greek Research and Technology Network (GRNET) /


Download ppt "2 SEEREN The SEEREN2 initiative is co-funded by the European Commission under the FP6 Research Infrastructures contract no. 026748."

Similar presentations


Ads by Google