1 Introduction
This Library Overview presents the information available for Cloud Execution Environment (CEE).
1.1 Product Numbers
The product numbers and delivery information is provided in Table 1.
|
Product Name |
Product Number |
Library |
|---|---|---|
|
CEE 6.6 |
AZE 102 01/5 R8A |
EN/LZN 792 0001/8 R8A |
1.2 Library Distribution and Access
CPI libraries are distributed as follows:
- Online libraries on the Ericsson eBusiness portal – requires access privileges
- Online libraries on CPI Store on the Ericsson intranet
- Online libraries on CAL Store on the Ericsson intranet
1.3 Library Access
For information on how to access the library, refer to How to Get Started with Active Library Explorer.
1.4 Library Structure
The library consists of documents grouped into the following main folders:
- Safety and Environment
- Library Overview
- Product Overview
- Planning
- Installation
- Initial Configuration
- Operation and Maintenance
- Emergency
- Interface
1.5 Document Types
The documents are grouped into the following three types:
- Descriptive documents contain descriptions of the product on different levels.
- Operational documents give instructions on how to operate or maintain the product.
- Reference documents contain more information to which a user needs to refer.
1.6 Related Information
Trademark information, typographic conventions, definition, and explanation of acronyms and terminology used in this library, refer to the following documents:
2 Cloud Execution Environment Library
This section describes the library contents for CEE.
2.1 Safety and Environment
Documents included in this area are listed in Table 2. These documents are intended for personnel who work with Ericsson products.
|
Title |
Description |
Type |
|---|---|---|
|
Information important for health and safety in the workplace and in the external environment. |
Descriptive, Operative | |
|
Information important for product safety. |
Descriptive, Operative |
2.2 Library Overview
Documents included in this area are listed in Table 3. These documents are intended for all personnel involved in work related to any aspect of the product.
|
Title |
Description |
Type |
|---|---|---|
|
This document lists the changes compared to the previous official library. |
Reference | |
|
Overview of the library. |
Reference | |
|
Explanations of all terms, abbreviations, and acronyms that occur in the library. |
Reference | |
|
Trademark information used in the library. |
Reference | |
|
Typographic conventions used in the library. |
Reference | |
|
Introduction to the use of Active Library Explorer to read Ericsson CPI. |
Reference |
2.3 Product Overview
Documents included in this area are listed in Table 4. These documents are intended as an introduction for all personnel who want to learn more about the product.
|
Title |
Description |
Type |
|---|---|---|
|
This document is a technical description of the product. |
Descriptive | |
|
This document describes the architecture of EMC ScaleIO 2.0 introduced in CEE 6. |
Descriptive | |
|
This document describes the backup and restore options available in CEE. |
Descriptive | |
|
This document describes the CEE management system Atlas. For detailed information about using the Atlas Dashboard, refer to Atlas Dashboard Administrator User Guide and Atlas Dashboard End User Guide. |
Descriptive | |
|
This document contains notices and license documentation related to the Free and Open Source Software (FOSS) that is included in CEE. |
Descriptive | |
|
This document contains the 3PP license packages used by Mirantis OpenStack v9. |
Descriptive |
2.4 Planning
Documents included in this area are listed in Table 5. These documents are intended for personnel responsible for planning, implementation, and product handling.
|
Title |
Description |
Type |
|---|---|---|
|
This document describes the changes made in the CEE 6 release, compared to CEE 16A IRP releases, and the impact on the overall network of the operator, including affected products and functions. |
Descriptive | |
|
This document describes the generic hardware requirements and characteristics and dimensioning of CEE. This document is valid for multi-server configuration. |
Descriptive | |
|
This document describes CEE hardware requirements and characteristics and dimensioning of CEE. This document is valid for single server deployment. |
Descriptive | |
|
This document contains the list of test cases described in Customer Acceptance Test Specification and summarizes the results of the customer acceptance test. |
Operative | |
|
This document provides cases to execute a customer acceptance test of the functionality of CEE 16A. |
Operative |
2.5 Installation
Documents included in this area are listed in Table 6. These documents are intended for personnel performing hardware installation, software installation, and configuration.
|
Title |
Description |
Type |
|---|---|---|
|
Common CEE Installation Documents | ||
|
This document describes the complete procedure for deploying a CEE region. |
Operative | |
|
This document describes the preparation of the installation laptop that is used for the CEE software installation process. |
Operative | |
|
This document describes procedures for installing the software in a CEE region. This document is valid for single server deployment. |
Operative | |
|
This document describes procedures for installing the software in a CEE region. This document is valid for multi-server deployment. |
Operative | |
|
HDS Installation | ||
|
This document describes the creation of CEE region on a Hyperscale Datacenter System (HDS) Virtualized Performance Optimized Datacenter (vPOD), including CEE software installation. |
Operative | |
|
Dell Installation | ||
|
This document describes procedures for installing Dell PowerEdge R630 for CEE. |
Operative | |
|
This document describes procedures for configuring Dell PowerEdge R630 server for CEE. |
Operative | |
|
This document describes procedures for configuring BIOS settings for a newly inserted Dell PowerEdge R630 server in CEE. |
Operative | |
|
This document describes procedures for installing Extreme X670V Switches to be used as Traffic and Storage Switches. |
Operative | |
|
This document describes procedures for installing Extreme X770 Switches to be used as Traffic and Storage Switches. |
Operative | |
|
This document describes procedures for installing Extreme X460 Switches to be used as Control Switches. |
Operative | |
|
Atlas Installation | ||
|
This document describes procedures for installing Atlas. Atlas is a cloud management tool, based on the OpenStack Dashboard, and delivered as a part of CEE. |
Operative | |
2.6 Initial Configuration
Documents included in this area are listed in Table 7. These documents are intended for personnel performing software installation and initial configuration.
|
Title |
Description |
Type |
|---|---|---|
|
This document describes the configuration file changes to be made when installing CEE. |
Operative, Descriptive | |
|
This document describes the different Fuel plugins available for CEE, and the mandatory Fuel plugins for a supported CEE configuration. |
Operative, Descriptive |
2.7 Operation and Maintenance
Documents within this area are listed in the subsections below. These documents are intended as an introduction for personnel involved in any operation and maintenance activity.
|
Title |
Description |
Type |
|---|---|---|
|
This document provides an overview of the available interfaces in CEE, and instructions on how to connect to these. The document covers the interfaces from both a CEE user and CEE administrator point of view. |
Descriptive, Operative |
2.7.1 Fault Management
Documents included in this area are listed in Table 9. These documents are intended for personnel performing fault handling, alarm handling, and troubleshooting.
|
Title |
Description |
Type |
|---|---|---|
|
This document provides step-by-step instructions required during data collecting activities. |
Descriptive, Operative |
2.7.1.1 Alarms
Documents included in this area are listed in Table 10. These documents are intended for personnel performing alarm handling.
|
Title |
Description |
Type |
|
This document contains the list of CEE alarms. |
Descriptive | |
|
The alarm is issued by the Managed Object (MO) Node when the periodic algorithm detects that the bandwidth requirement for the virtual machines (VMs) running on the node exceeds the available bandwidth. |
Operative, Descriptive | |
|
The alarm is issued by the MO BGP_Neighbor when the control connection with the BGP neighbor is down. |
Operative, Descriptive | |
|
This alert is issued when an alert happens in Centralized Storage Array during running of CEE. |
Operative, Descriptive | |
|
This alarm is issued when the periodic supervision algorithm detects that one of the three Cloud Infrastructure Controllers (CICs) has failed the availability test three consecutive times, and, after that, remains unavailable for more than five minutes. |
Operative, Descriptive | |
|
This alert is issued in the following situations: |
Operative, Descriptive | |
|
The alert is issued when during a periodic check the Continuous Monitoring High Availability (CM-HA) memory consumption reaches a certain threshold and CM-HA is restarted. |
Operative, Descriptive | |
|
This alert is issued for a region by the MO CtrlDomain when the periodic uptime measurements show that the uptime for all three CICs has decreased, which means that all CICs have been simultaneously unavailable. |
Operative, Descriptive | |
|
This alarm is issued by the MO ComputeHost when the periodic supervision algorithm detects that the Compute Host has failed the availability test three consecutive times, and, after that, remains unavailable for more than five minutes. |
Operative, Descriptive | |
|
This alert is issued in the following situations:
|
Operative, Descriptive | |
|
The alarm is issued by the MO DPN when the connection between the controller node of the Cloud SDN Controller (CSC) and the OpenFlow switch is lost. |
Operative, Descriptive | |
|
This alarm is issued when a process fails. This alarm is generated when the memory content of the failed process is saved in a core dump. When the Linux kernel fails, the dump is called a crash dump. |
Operative, Descriptive | |
|
The alarm is issued by the MO DstDPN when the data path connectivity between the Data Plane Nodes (DPNs) is lost. |
Operative, Descriptive | |
|
Distributed storage alarms are issued for ScaleIO alarm events by the MO DistributedStorage. |
Operative, Descriptive | |
|
This alarm is issued when the connection to the affected network is lost on both Ethernet ports. |
Operative, Descriptive | |
|
This alarm is issued when a network port on a server blade loses connectivity with the related network. The alarm remains active as long as the connectivity is missing. It is possible that the underlying fault requires site visit. |
Operative, Descriptive | |
|
This alarm is issued by the MO EthernetPort when the connectivity is lost on an Ethernet switch in the "Top of Rack" switch. |
Operative, Descriptive | |
|
This alarm is issued by the MO CtrlDomain when the Certification Authority (CA) certificate is about to expire. |
Operative, Descriptive | |
|
This alarm is issued by the MO Fan when malfunction occurs in one or more cooling fans in the "Top of Rack" switch. |
Operative, Descriptive | |
|
The alarm is issued by the MO Node when the periodic supervision algorithm detects that the compute host has failed the availability test three consecutive times, and fence_compute_before_evacuation was set to true (meaning that the compute will be fenced down), but fencing was not successful. |
Operative, Descriptive | |
|
This alarm is issued when the periodic supervision algorithm detects that the Fuel host has failed the availability test three consecutive times, and, following that, remains unavailable for at least five minutes. |
Operative, Descriptive | |
|
The alert is issued in the following situations:
|
Operative, Descriptive | |
|
This alarm is issued by the MO ServerBlade when the load on the CPU is high. |
Operative, Descriptive | |
|
This alarm is issued by the MO ServerBlade when the local disk utilization is high. |
Operative, Descriptive | |
|
This alarm is issued by the MO ServerBlade when the memory utilization is high and exceeds a set threshold level. |
Operative, Descriptive | |
|
This alarm is issued by the MO Node. CSC generates the alarm when it detects that a sub-module of CSC has failed in any of the vCICs. |
Operative, Descriptive | |
|
This alarm is issued by the Managed Object (MO) License when the Network License Server (NeLS) is not available. |
Operative, Descriptive | |
|
This alarm is issued when NTP Authentication Failure occurs. NTP service on Controller is not able to communicate with one of the upstream NTP servers according to authentication failure. |
Operative, Descriptive | |
|
This alarm is issued when NTP Stratum Level Failure occurs. That is, NTP stratum level on any of the CICs are lower or equal to any of the stratum levels on the upstream NTP servers. |
Operative, Descriptive | |
|
This alarm is issued when NTP Upstream Server Failure occurs. Upstream failure means that NTP client on CIC hosts cannot reach one of the upstream servers in the NTP server list. |
Operative, Descriptive | |
|
This alarm is issued by the MO PowerSupply when one or more power supplies fail in the "Top of Rack" switch. |
Operative, Descriptive | |
|
The alarm is issued when the distributed storage component is not accessible. |
Operative, Descriptive | |
|
This alarm is issued if a service operating at a vCIC or Compute node is stopped permanently. |
Operative, Descriptive | |
|
This alert is issued when a service operating at a host is stopped. |
Operative, Descriptive | |
|
This alarm is issued when one or more disks within the SW RAID array are unavailable |
Operative, Descriptive | |
|
This alarm is issued for a VM in the following situations: |
Operative, Descriptive | |
|
This alarm is issued for a VM when the evacuation of the VM starts. The evacuation is triggered, and the alarm is issued, for all VMs that are hosted on the compute host that fails the periodical availability test three consecutive times. |
Operative, Descriptive | |
|
This alert is issued when the VMs are restarted after a virtual Switch (vSwitch) failure in CEE. The alarm is issued by the MO Instance VM. |
Operative, Descriptive |
2.7.2 Configuration Management
Documents included in this area are listed in Table 11. These documents are intended for personnel performing configuration and fine-tuning. They are also intended for personnel performing provisioning.
|
Title |
Description |
Type |
|---|---|---|
|
This document describes the Ericsson Atlas Dashboard modifications, compared to the OpenStack Dashboard (Horizon). It also adds examples on features not described in the community user guide. |
Operative, Descriptive | |
|
This document is a user guide for OpenStack end users. |
Operative, Descriptive | |
|
This document describes the Ericsson Atlas Dashboard modifications, compared to the OpenStack Dashboard (Horizon). It also adds examples on features not described in the community user guide. |
Operative, Descriptive | |
|
This document is a user guide for OpenStack administrators. |
Operative, Descriptive | |
|
This document describes procedures for enabling multiple CEE regions in Atlas. |
Operative | |
|
This document describes procedures for disabling Atlas in a single server CEE installation. |
Operative, Descriptive | |
|
This document is a user guide for the Dell EMC2 ScaleIO storage solution. |
Operative, Descriptive | |
|
This document describes procedures for configuring the Watchmen Fault Management in CEE. |
Operative, Descriptive | |
|
This document describes procedures configuring or reconfiguring settings in a running CEE. |
Operative, Descriptive | |
|
This document describes how to activate the feature Swift store on ScaleIO and move the location of the Swift store from the local disks to the distributed storage (EMC ScaleIO). |
Operative | |
|
This document describes how to expand the existing Swift store on ScaleIO. |
Operative | |
|
This document describes procedures for disabling/enabling vFuel on a Single Server environment. |
Operative, Descriptive |
2.7.3 Security Management
Documents included in this area are listed in Table 12. These documents are intended for personnel performing security tasks, including supervision and user administration. They are also intended for personnel performing hardening of the product.
|
Title |
Description |
Type |
|---|---|---|
|
This document describes Security Management for the supported security services in CEE. |
Operative, Descriptive | |
|
This document contains general information about the hardening processes, and helps to understand the purpose of product hardening. The document gives an overview of the hardening activities that are performed during the product development, and defines hardening activities that need to be performed during and after the installation. |
Operative, Descriptive | |
|
This document describes procedures for hardening that must be performed to make CEE secure during its whole life cycle. |
Operative, Descriptive | |
|
This document describes the CEE Identity and Access Management (IdAM) tool, that is used to manage identities and credentials for Cloud Infrastructure Administrators, and to provide authentication and access control services for user accesses. |
Operative, Descriptive | |
|
This document provides the connectivity and network description of the Data Center Firewall (DC-FW) to the CEE Network architecture. In the current system, FW is not part of the CEE region, therefore this user guide gives a high-level overview about the external hardware FW solution. |
Operative, Descriptive | |
|
This document describes Security Management for the Dell EMC ScaleIO storage solution. |
Operative, Descriptive |
2.7.4 Hardware Management
Documents included in this area are listed in Table 13. These documents are intended for personnel performing preventive maintenance of the hardware and for personnel involved in troubleshooting.
|
Title |
Description |
Type |
|---|---|---|
|
This document describes procedures for replacing the Extreme switch. The document is valid for both X670V and X770 switches. |
Operative | |
|
This document describes procedures for replacing the Extreme X460 control switch. |
Operative | |
|
This document describes procedures for expanding CEE with one or more compute hosts. |
Operative | |
|
This document describes how to remove one or more compute hosts from the CEE region. |
Operative | |
|
This document describes procedures for replacing a blade in CEE. |
Operative |
2.7.5 Software Management
Documents included in this area are listed in Table 14. These documents are intended for personnel performing preventive maintenance of the software and for personnel involved in troubleshooting. They are also intended for personnel performing backup and restoration.
|
Title |
Description |
Type |
|---|---|---|
|
This document describes how to manage the Atlas software. |
Descriptive, Operative | |
|
This document describes procedures for updating and upgrading the software in an existing CEE Atlas Server. |
Operative | |
|
This document describes procedures for backing up the configuration of Atlas for CEE. For more information about the Atlas command used for the backup procedure, refer to Atlas Software Management Guide. |
Descriptive, Operative | |
|
This document describes procedures for restoring the configuration of Atlas for CEE. |
Descriptive, Operative | |
|
This document describes the generic flow of the update procedure in the CEE region. |
Operative | |
|
This document is used for performing a software update and rollback between CEE 6.5 (R7B) and CEE 6.6 (R8A), or CEE 6.5.1 (R7C) and CEE 6.6 (R8A). |
Operative | |
|
This document provides instructions on how to gracefully shut down and restore the CEE region. |
Operative | |
|
This document describes procedures for backing up CIC domain configuration data for vCIC recovery. |
Descriptive, Operative | |
|
This document describes procedures for restoring CIC domain configuration. |
Descriptive, Operative | |
|
This document describes the disaster recovery procedure. The purpose of this procedure is to create a backup of the CEE infrastructure for recovery purposes following a man-made or natural disaster (vis maior), such as hurricane, flood or similar. |
Operative | |
|
This document describes procedures for upgrading the firmware for the Extreme switch. |
Operative | |
|
This document describes the manual Fuel synchronization procedure and the change to cold-stand-by vFuel. |
Operative |
2.7.6 Health Check
Documents included in this area are listed in Table 15. These documents are intended for personnel performing installation, preventive maintenance of the software, and provisioning tasks. They are also intended for personnel involved in troubleshooting.
|
Title |
Description |
Type |
|---|---|---|
|
This document is to help support engineers check that CEE operates in a fault-free state, and to detect issues that can affect normal operation. |
Descriptive |
2.8 Emergency
Documents included in this area are listed in Table 16. These documents are intended for personnel authorized to perform an emergency recovery.
|
Title |
Description |
Type |
|---|---|---|
|
This document provides a systematic approach for resolving a system emergency experienced in CEE. |
Descriptive |
2.9 Interface
Documents included in this area are shown are listed in Table 17. These documents are intended for personnel needing to understand the logical entity, including interfaces and protocols.
|
Title |
Description |
Type |
|---|---|---|
|
This document is a complete reference of the Application Programming Interface (API) operations and extensions of OpenStack. |
Descriptive, Reference | |
|
This document describes the OpenStack command-line clients. |
Descriptive, Reference | |
|
Descriptive, Operative | ||
|
This document describes the deployment procedure for unmanaged ScaleIO. |
Descriptive, Operative | |
|
This document describes how to use specific CLI commands in CEE. |
Descriptive, Operative | |
|
This document is an introduction to the API of the OpenStack Dashboard-based cloud management component Atlas in CEE. |
Descriptive, Reference | |
|
This document describes the OpenStack Heat service and contains the Heat Orchestration Template (HOT) guide. |
Descriptive, Reference | |
|
This document describes the Atlas Open Virtualization Format Translator (OVFT) API used in CEE. |
Descriptive | |
|
This document describes a mechanism for translation of OVF descriptors into HOT templates. |
Descriptive | |
|
This document describes the syntax descriptions and examples of the commands used for managing Atlas by using the CLI. |
Descriptive, Operative | |
|
This document describes the structure and content of the In-Service Performance (ISP) Log File in CEE. |
Descriptive | |
|
This document describes the Fault Management (FM) northbound API used in CEE. |
Descriptive | |
|
This document describes the northbound interfaces of CEE used for Performance Management (PM). |
Descriptive | |
|
This document describes the factory default key performance indicators (KPIs) available at the northbound interfaces of CEE used for performance management. |
Descriptive | |
|
This document describes the Northbound Interface of the Log Aggregator that is part of CEE. |
Descriptive | |
|
This document describes the interface between the external Security Information and Event Management (SIEM) systems and the Log Collector in Atlas. |
Descriptive | |
|
This document is an introduction to using the API of the OpenStack component "Identity" (Keystone) in CEE. |
Descriptive | |
|
This document describes the API operations and extensions of OpenStack Identity. |
Descriptive, Reference | |
|
This document is an introduction to using the API of the OpenStack component "Compute" in CEE. |
Descriptive | |
|
This document describes the API operations and extensions of OpenStack Compute. |
Descriptive, Reference | |
|
OpenStack Networking API in CEE in Dell Multi-Server Deployment |
This document describes how the API for networking is used in CEE in Dell Multi-server deployment. The API is based on the OpenStack component "Networking" (Neutron). |
Descriptive |
|
This document describes how the API for networking is used in CEE in Single Server deployment. The API is based on the OpenStack component "Networking" (Neutron). |
Descriptive | |
|
This document describes how the API for networking is used in CEE in BSP deployment. The API is based on the OpenStack component "Networking" (Neutron). |
Descriptive | |
|
This document describes how the API for networking is used in CEE with SDN. The API is based on the OpenStack component "Networking" (Neutron). |
Descriptive | |
|
This document describes how the API for networking is used in CEE in HDS deployment. The API is based on the OpenStack component "Networking" (Neutron). |
Descriptive | |
|
This document describes the API operations of OpenStack Networking. |
Descriptive, Reference | |
|
This document is an introduction to using the API of the OpenStack component "Object Storage" in CEE. |
Descriptive | |
|
This document is an introduction to using the API of the OpenStack component "Block Storage" in CEE. |
Descriptive | |
|
This document is an introduction to using the API of the OpenStack component "Image Service" in CEE. |
Descriptive | |
|
This document is an introduction to using the API of the OpenStack component "Telemetry" in CEE. |
Descriptive |

Contents