Docstoc

D7-FEDERICA-Project-Plan-template

Document Sample
D7-FEDERICA-Project-Plan-template Powered By Docstoc
					Project Plan for the usage of the FEDERICA infrastructure
(9th March, Version 0.2) A technical project plan has to be detailed and agreed to access to the FEDERICA infrastructure. This document contains information how to structure this project plan. The project plan has to include management information, a description of the planned work and a description of the required and available resources. These information form the basis for the FEDERICA User Policy Board (UPB) to assess the feasibility of the access to FEDERICA.

1
     

Required Informations
Name of the Project. Participating institutions (name, location) with participating persons (name, phone, e-mail), including the head of the project. Planned starting time and planned length of time of the project. Short project description (1-2 pages of text). Description of the usage scenario of FEDERICA (1 page text) with a slice topology map. Required resources from FEDERICA. This information has the goal to specify the configuration of the slice (or the slices) in terms of the resources which FEDERICA can provide: V-Nodes as a computing resource capable of executing a system image and which can be connected to one or more circuits Virtual IP router functionality provided by the network elements Point to point circuits between the V-Nodes or the network equipment Access points and bandwidth.

The possible requirements (not exhaustive) to the network properties and to the service elements in FEDERICA are listed in the below requirement table.   Required connectivity to third parties (outside of FEDERICA), e.g. other test environments. However, such connectivity to third parties is in the responsibility of the user, who has to provide a plan to establish such connectivity. Available resources of the project partners.

68cf937d-4072-48b0-ae07-8b7c7e353b89.doc 1

RI 213107 – Project FEDERICA

FEDERICA-Project-Plan

2

Requirements table

This table should be seen as a support to formulate the requirements with respect to FEDERICA. Maybe FEDERICA can not fulfill all requirements. Not all rows must be completed!

FEDERICA-service-related requirements
(For each required FEDERICA service use an extra table) CATEGORY Research on network layers / Transparency Time of usage PARAMETER Layer 2 Layer 3 Layer 4+ Short (hours) Mid (days) Long (months) Off-line On-line Provisioned Scheduled On-demand No Semi Full Off-line reports Interactive debug Number and size of the network slices R/A of the network slices Internal risks External threats DESCRIPTION Research on what layer? Typical time of usage? Experiments on the background or live? Expected service response time? Control on the service? Monitoring of the elements and/or traffic? Typical number and size of network slices? Expected number of nines? Importance of security level? REQUIREMENT [choice]

[value]

Type of usage Response / Provisioning time Level of control

[choice] [choice]

[choice]

Level of monitoring / measurement Scalability

[choice]

[value]

Reliability / Availability Security/ Authentication

[value] [Y/N]

Network-related requirements (Network slices)
CATEGORY Traffic matrix / Connection topology Bandwidth QoS level Delay Jitter Loss rate Fairness PARAMETER Point-to-point Point-to-multi point Multi point-to-multi point High cap./Narrowband Best Effort Quality of Service DESCRIPTION Typical usage? REQUIREMENT [choice]

Typical bandwidth? Level of QoS? Expected delay? Expected jitter? Expected loss? Expected fairness?

[value] [choice] [value] [value] [value] [value]

68cf937d-4072-48b0-ae07-8b7c7e353b89.doc

2

RI 213107 – Project FEDERICA

FEDERICA-Project-Plan

Type of IP network Network management Traffic management Accounting Cost

Close network Open network Fault Performance Topology Bandwidth CAC Policing

Require public IP addresses? Importance of network management? Importance of traffic management? Importance? Importance?

[choice] [Y/N]

[Y/N]

[Y/N] [Y/N]

Application-related requirements (Virtual Machines/software packages)
CATEGORY Processing power Memory Storage resources Operating Systems DESCRIPTION Typical processing power? Typical memory? Typical storage? Are you interested in a particular Operating System? REQUIREMENT [value] [value] [value] [Y/N]

3

Slice Topology Map

(a topology example to be included)

68cf937d-4072-48b0-ae07-8b7c7e353b89.doc

3


				
DOCUMENT INFO