View on GitHub



« Back

1. Introduction

Table of Contents

1.1 Overview

The Reference Model (RM) specifies a virtualisation technology agnostic (VM-based and container-based) cloud infrastructure abstraction and acts as a “catalogue” of the exposed infrastructure capabilities, resources, and interfaces required by the workloads. This document has been developed by Cloud iNfrastructure Telco Taskforce (CNTT). For more information about CNTT, its activities and deliverables, see Cloud iNfrastructure Telco Taskforce.

The document starts from the abstract and as it progresses it increasingly gets into more details. It follows the traditional design process where you start from core principles, progress to abstract concepts and models, then finish with operational considerations, such as security and lifecycle management.

1.2 Scope

This Reference Model document focuses on identifying the abstractions, and associated concepts, that are needed to represent the cloud infrastructure. Figure 1-1 below highlights its scope in more details.


Figure 1-1: Scope of Reference Model

This document specifies:

1.3 Principles

The Reference Model specifications conform to the overall principles defined in Cloud iNfrastructure Telco Taskforce.

1.4 Definitions/Terminology

To help guide the reader, the Reference Model Glossary provides an introduction to the main terms used within this document and throughout the project in general. These definitions are, with a few exceptions, based on the ETSI GR NFV 003 [1] definitions. In a few cases, they have been modified to avoid deployment technology dependencies only when it seems necessary to avoid confusion.

1.5 Conventions

“The key words “must”, “must not”, “required”, “shall”, “shall not”, “should”, “should not”, “recommended”, “may”, and “optional” in this document are to be interpreted as described in RFC2119 [2].”