This page explains main aspects of a pilot phase of a product or a service.
Text written with Italic blue letters explains the purpose of the field and should be deleted when this template is populated for a specific pilot.
Name: Consolidated Connection Service
Start Date: 1. 1. 2018
End Date: 30.6.2018
Pilot Description:
The Consolidated Connection Service is successor of the BoD service. It provides fully transparent Ethernet circuits over the Geant network using specific software tools for automated provisioning. Key characteristic of CCS are:
- Automated provisioning based on Network Service Interface (NSI) protocol
- Provides API (SOAP, REST) which can be used by 3rd party systems to request a connection
- Enables automated multi-domain service provisioning over NSI enabled networks worldwide
- Resources reservations
The CCS is an abstraction of network functionality and some physical entity which could be pointed as "the CCS instance" is probably the Network Service Agent (NSA) - the Geant NSI aggregator. It provides the NSI interface (the API) which different other systems can use to request circuits. Such system can be a Connection Service GUI or other more complex services like GTS application, or NSAs of foreign network domains.
The pilot deployment of the CCS will cover all eight routers/locations where GTS has any resources connected to MX routers. The pilot deployment will be managed by JRA2 T1 in cooperation with SA1.
The technology used for CCS provisioning will be for the pilot time frame supported by JRA2 T1.
Description of the pilot - what will be tested, why, how.Who leads the pilot, who participates in the pilot, who provides support,.... - list all parties involved.
Pilot Category: Service
Is this a pilot of a technology or a service. Delete what is not applicable. If it is both, then both aspects should we defined separately: objectives, means of verification, documentation etc.
Required Infrastructure:
The CCS itself requires a little in case of physical infrastructure. Considering the IP/MPLS core network as prerequisite, the only what is need is the VM with running instances of OpenNSA. The VM is now hosted on the GTS CSF0 server in the core GTS node in Prague.
| VM requirements |
|---|
Description of the infrastructure that will be used for the pilot. Explain also who runs which part of the infrastructure, who is responsible, contact details for the operations and maintenance team.
Users:
Who are the target users for this pilot, and who actually participates in the pilot as the user.
Objectives:
Explain the objectives for the pilot - what does the pilot want to test / prove. Define Critical Success Factors (CSFs) and Key Performance Indicators (KPIs)
Means of verification:
How it will be checked if the pilot has met the defined objectives. Consider also conducting a survey among pilot participants. Each objective might have their own means of verification. Since this page will be used for pilot closure, the table is created with the third column stating is the objective is verified and reached or not. This should be populated before the end of the pilot and be used for pilot success assessment.
| Objective | Means of verification | Status (objective verified?) |
|---|---|---|
Communication plan:
Explain how will the team communicate with pilot participants, e.g. regular (weekly/bi-weekly/...) meetings, mailing lists, instant-messaging channels,...
Additional documentation:
Provide (links to) any additional documentation as needed.
If this is a pilot of a technology, provide relevant links about the technology that is being tested, previous related work in and outside of GEANT project.
If this is a pilot of a service, provide links to Service template completed for this service.