Based on the use-cases and requirements outlined in deliverable D2.1, this document presents the initial overall architecture of the SONATA system. Its aim is to propose an architecture that is able to cover all use-cases and requirements and allows for a flexible implementation with reasonable technical complexity and performance. To this end, it takes state-of-the-art system architectures of NFV MANO systems and state-of-the-art architectures of high performance distributed systems into account.
The overall contributions of D2.2 can be summarized as follows:
- A detailed description of the overall architecture of the SONATA system comprising the various components and their relations. That is, the SONATA service programming and orchestration framework consists of the SONATA software development toolkit (SDK), the SONATA service platform, and different catalogues storing artefacts that can be produced, used, and managed by the SONATA system.
- A general information model describing the most important reference points.
- A detailed specification of the catalogues and repositories used by the service platform as well as the SDK to store, retrieve, and exchange information and data.
- An initial specification of the service development kit, its functions, and components, including a detailed description on how the SDK is integrated with the service platform and how it supports the development, deployment, and operation of network services is provided.
- A description of the high-level workflow and life-cycle management of networks services in the service platform.
- A description of the core components of the service platform including the gatekeeper, an infrastructure abstraction, and the MANO framework.
- The specification of DevOps operations including slicing support as well as recursive installations of the service platform itself.
The architecture deliverable is used as a reference point to kick-o and coordinate the SONATA development. Thus, the overall architecture makes sure that all the different components are integrated efficiently. However, since SONATA is following a modern agile development process, we do not consider the presented architecture as the final results, but expect the architecture to change over time based on findings throughout the project. Besides, many decisions that are directly related to implementation details are left to the development teams of work packages WP3 and WP4.