This page contains service description outlining how and where service should be used, targeted users, service delivery model and service elements and topology. RESPONSIBLE: Information provided in this page is initially populated by the development team (during the transition phase), and revised based on the need or in a yearly service check by Consolidated Connection Service Service Manager, with exception of CBA which remains the responsibility of business development team. |
Service description
Consolidated Connection Service (CCS) 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.
Users
User of the CCS can be anyone (or anything - in case of other system like GTS) who (which) needs a connection between two defined termination points.
Possible currently known users are:
- Geant Testbed Service (GTS): uses the CCS for Ethernet virtual circuits
- Connection Service GUI: successor of the current BoD service portal - can be used by network operations to automatize circuit provisioning (currently done manually for Geant plus), or can be used by users directly
- Other network's NSAs (member NRENs, or partner networks around the world) which needs a connection trough Geant core for their users
Average number of circuits requested by GTS per one month is approximately 400.
Contacts
All operations, business development and stakeholders contacts
| Service Manager | Deputy Service Manager | L1 support | L2 support | L3 support |
|---|---|---|---|---|
Service delivery model
Add explanation about organisation of service delivery
Service Elements
Service Elements, with brief description and links to products, resource instances and software stack of the service, indicating the software components types - if they are internally (in-house) developed, OSS or commercial off-the-shelf software. Service elements can be grouped in two following categories:
Technology infrastructure
Add list and description of products and resources used to deliver main functionalities of the service. Add service technical architecture - i.e. its good to have a conceptual architectural diagram and topology diagram.
Supporting infrastructure
Add list and descriptions of products and resources used to deliver supporting services such as specialized monitoring and measuring systems, configuration management system, issue/ticket reporting system, etc.)
Cost Benefit Analysis
Provide URL to last valid CBA