1 Introduction
This document provides information to operate and maintain Oracle Communications Cloud Native Core, Cloud Native Environment (CNE) clusters.
1.1 Overview
CNE is an essential infrastructure code that provisions, configures, and manages cloud native environments.
1.2 References
Refer to the following documents for more information about CNE:
- Oracle Communications Cloud Native Core, Cloud Native Environment Installation, Upgrade, and Fault Recovery Guide
- Oracle Communications Cloud Native Core, Cloud Native Environment Network Impact Report
1.3 Key Terms
The following table lists the terminologies used in this document.
Table 1-1 Key Terms
Term | Definition |
---|---|
Host | A host is a computer that is loaded with an Operating System (OS) and is accessible over a network. This includes physical or virtual machines. Though host and node have different meanings, they can often be confused. Therefore, in this document, the host refers to the role of the physical computer in the CNE solution, and Host OS refers to the operating system running on the physical computer. |
Node | In general use, a "node" is any system or device connected to a network. A "node" is usually a networking endpoint. In this document, a "node" refers to a service within the CNE, such as "Kubernetes Controller Node", which provides the Kubernetes etcd data and serves as a management entity for the cluster. |
Computer or Machine | A computer is a machine or device that performs processes, calculations, and operations based on instructions provided by a software or hardware program. Machine and computer are equivalent and interchangeable. Therefore, a virtual machine or physical machine is equivalent to a virtual computer or physical computer. |
Server | A server is a physical computer. Servers are rack-mounted servers (RMS). |
Rack Mount Server (RMS) | RMS denotes a profile for a specific computer designed to support a server function. An RMS is mounted directly into a frame and is individually powered and networked. |
Management Host | The Management Host is a physical machine in the RMS frame that contains a special configuration to support hardware installation and configuration of other components within a frame. For CNE, there is one machine, RMS1, with dedicated connectivity to out of band (OOB) interfaces on the Top of Rack switches. The OOB interfaces provide the connectivity required to initialize ToR switches. When referring to a machine as a Management Host, the context is related to its OOB connections that are unique to the RMS1 configuration. |
Bastion Host | The Bastion Host is a node that hosts general orchestration support for the site. The Bastion Node runs as a virtual machine on a Kubernetes Master Host. It is used to host the automation environment and run the install automation. The install automation provisions and configures all other hosts, nodes, and switches within the frame. After the installation process is completed, the Bastion Host continues to serve as the customer gateway to cluster operations and control. |
Installer Bootstrap Host | As an early step in the site installation process, one of the hosts is minimally provisioned to act as an Installer Bootstrap Host. The Installer Bootstrap Host has a very short lifetime since its job is to provision a Bastion Host. The Bastion Host performs the remainder of the OCCNE installation. The Installer Bootstrap Host is also known as the Bootstrap Host. Later in the installation process, this Bootstrap Host (RMS1) is reprovisioned as a Kubernetes Master Host. |
K8s Controller Node | Some nodes in the system such as RMS 1, 2, and 3 are dedicated to providing container management. These nodes are responsible for managing all of the containerized workloads that run on the Kubernetes Worker Nodes. |
K8s Worker Node | Some nodes in the system such as the blade servers within the enclosure, are dedicated to hosting containerized software and providing the 5G application services. |
Container | An encapsulated software service. All 5G applications and Operations, Administration, Maintenance (OAM) functions are delivered as containerized software. The purpose of the OCCNE is to host containerized software providing 5G Network Functions (NFs) and services. |
Cluster | A collection of hosts and nodes dedicated to providing a cloud native runtime environment for containerized services and applications. The cluster is comprised of the collection of Master and Worker Nodes and is managed by Kubernetes. |
Virtualized CNE | A Virtualized CNE is a cloud native environment that is deployed on VMs instead of Bare Metal servers. |