Transcript Slide 1

2
SEEREN
Technical Execution Plan
http://www.seeren.org
Costas Kotsokalis / Yannis Mitsos
SEEREN2 Technical Coordinator / SEEREN2 Operations Manager
Greek Research and Technology Network (GRNET)
[email protected] / [email protected]
The SEEREN2 initiative is co-funded by the European Commission under the FP6 Research Infrastructures contract no. 026748
Overview
o Technical Execution Plan: Live document
o Definition of:
o Required technical activity (based on Annex-I)
o Task assignment
o Task inter-dependencies
o Fine-grain temporal sequence of tasks
o Estimation of risks
o T+1: Define strategies to avoid them
Athens, October 13th, 2005
2
New services to be implemented
o With no particular order:
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
Network security
IP Telephony
Video Conferencing
Video Streaming
QoS Provisioning
Bandwidth on Demand
Directory Services
Identity Management, AAA
Eduroam
Network Database
MCU/GKP
Multicasting
Correlation of active & passive monitoring
Monitoring & management tools integration
Timesheet/Groupware/Wiki software? This is to help the consortium!
Athens, October 13th, 2005
3
WP2 / WP3
o Will not elaborate on WP2 &
WP3
o Have proceeded greatly after
schedule crashing
o Final network topology known
by now
Athens, October 13th, 2005
4
WP4 (1)
o A4.1: Define operational procedures
o Activity leader: Kotsokalis
o One-off task (but can be updated if/when things do change)
o Part of this discussion today
o Must take decisions
o Must be ready until the 22nd, even if in premature form
o Should provide strict activity model of everyday & uncommon tasks
o Basic tasks
o Establish use cases
o Provide formal description
o Model interactions between partners on technical issues
o FCAPS model
o Notation
o Initially can be a list of solutions to different problems or other conditions
o Eventually: UML?
Athens, October 13th, 2005
5
WP4 (2)
o A4.1 (cont’d): First must define teams
PSC
o APMs
o International connections: Edin,
Goran, Neki, Octavian, Slavko,
Tamas, Vedrin, Yannis
o National connections: Amir, Dejan,
Dorian, Kozeta, Milorad, Novica
NME
o NME
o == APMs?
o SIEs
Operator
#
Help
Desk
SIE #
o Can be defined at the beginning of
each service development phase
o Mailing list for each SIE?
o Helpdesk
Athens, October 13th, 2005
APMs
NOCs
6
WP4 (3)
o A4.2: Define acceptance tests
o
o
o
o
o
o
Activity leader: Rusu
One-off task
Input: D07
Output: D09a
Refers to network links only
Basic tasks:
o Define pragmatic methods for acceptance tests taking under consideration the
equipment available (including exact setup suggestions)
o Define metrics to be used
o Define analysis method to follow including expected input, required output,
acceptance thresholds for output variables
o What about DF?
o Must be ready for non-DF links (even as a premature draft) until the 22nd.
Athens, October 13th, 2005
7
WP4 (4)
o A4.3: Deliver equipment and
connections (Core provider)
o Contracts under way
o “Revision is the mother of all
knowledge” (ancient Greek
saying)
o …so re-view the final topology 
o First connection delivered on the
22nd
Athens, October 13th, 2005
8
WP4 (5)
o A4.4: Adjust equipment configuration
o
o
o
o
Activity leader: Mitsos
Input: D07, D09a, A4.3
Output: D09b
All NRENs that are not willing to share their edge router config should have a
tested repository installation in place.
o NetIS module can do the work though
o Basic tasks for each link:
o
o
o
o
IPv4 connectivity should be available right away
Perform acceptance tests as defined in A4.2
Initiate Network DB (NetIS module?)
Apply necessary changes (OS upgrades, routing plan changes, etc)
o Right next (even in parallel with establishing other connections):
o IPv6 connectivity
o Base QoS (let’s agree today what this means)
o Multicast
Athens, October 13th, 2005
9
WP4 (6)
o A4.5: Technical support in stable operation
o
o
o
o
o
Activity leader: Gajin
Long-standing process
Input: A4.1
Output: D12
Basic tasks:
o Helpdesk overview
o Daily monitoring of open TTs – not closing, just notifying that there are open tickets and
people should close them if issues are resolved.
o Daily monitoring of links’ performance and uncommon patterns
o Reaction to problems encountered, communication with core provider when required
o SLA check against operator data
o Usage statistics
o Periodic overall assessment of the SEEREN2 infrastructure
o This is also part of the “procedures” discussion…
o Have skype IDs for everyone by now. Publicize to the list?
Athens, October 13th, 2005
10
WP5 (1)
o A5.1: Review services and tools state of the art
o Activity leader: Maray
o One-off
o Basic tasks:
o Locate candidate software & technologies to be used
o Assess their suitability for the cause of SEEREN2 and the SEEREN2 networking
infrastructure
o Describe capabilities of each software for interaction with external services
o Standards compliance
o Message passing methods
o Message format
o Evaluate the best options and come up with conclusive suggestions on the proper
toolset
o Whenever necessary, suggest software to be developed by the consortium
o Questionnaire to extract services that users need/prefer: Tamas, Octavian, Slavko,
Yannis, Costas
o SIEs will have to do this
o Need to move on fast; Let’s try to plan this today according to current
situation
Athens, October 13th, 2005
11
WP5 (2)
o A5.2: Execute feasibility study
o
o
o
o
Activity leader: Rusu
One-off
Input: A5.1
Basic tasks:
o Provide detailed study on the risk factors related to each module in the
toolset proposed by A5.1
o Suggest architectural/implementation options for tools to be developed by
the consortium
o SIEs will have to do this
o Must follow right after A5.1
Athens, October 13th, 2005
12
WP5 (3)
o A5.3: Define architecture and deploy services and tools
o
o
o
o
o
Activity leader: Jeliazkov/ISTF
Long-standing process
Input: A5.1, A5.2
Output: D13
Basic tasks:
1.
2.
3.
4.
5.
6.
Define in full the interactions between different services deployed
Develop necessary code as suggested by input activities
Define tests for quality assurance, carry out the tests
Identify rework required in readily available software
Execute staged deployment of software (ready & custom)
Provide support for the proper operation of software modules
o 1-4: SIEs
o 5-6: NME
Athens, October 13th, 2005
13
WP5 (4)
o A5.4: Evaluate performance and acceptance of services and
tools
o
o
o
o
o
Activity leader: Gajin
Long-standing process
Input: D13
Output: D15
Basic tasks:
o Performance, correctness & completeness evaluation of deployed services
o Document the development & deployment procedures used by the project
o Identify related technical issues of importance and provide training
suggestions to WP6
o ALL technical people must work on this activity
o Documenting our work very important
Athens, October 13th, 2005
14
Notes
o This presentation will be updated today with notes & APs from
our discussions, will quickly go through it at the end of the
meeting
o Next technical meetings
o March 2006 – Kopaonik
o May 2006 – w/ TERENA06?/15-18 May
Athens, October 13th, 2005
15
2
SEEREN
Technical Execution Plan
http://www.seeren.org
Costas Kotsokalis / Yannis Mitsos
SEEREN2 Technical Coordinator / SEEREN2 Operations Manager
Greek Research and Technology Network (GRNET)
[email protected] / [email protected]
The SEEREN2 initiative is co-funded by the European Commission under the FP6 Research Infrastructures contract no. 026748