|Ribbon Documentation Center|
The features for this initial release present DSC SWe instances (VMs) inside an OpenStack cloud environment. The DSC SWe (on OpenStack) builds on the existing DSC SWe using the same architecture, operating system, and application feature-sets while augmenting Operation Administration and Management (OAM) components for cloud deployments.
The minimum supported OpenStack version is Red Hat Newton. Refer to https://releases.openstack.org/ for the official OpenStack release list.
Consider the following for this document:
The SS7 Signaling Database (SDA) and Diameter Database (DB) are not supported for this release.
All system configuration activities for this platform are executed using the Web User Interface (UI) with the exception of the following:
These tasks are executed using a text-based user interface (referred to in this document as Menu UI).
For information about the Web UI and the Menu UI, see the Web UI and Menu UI Guide.
System provisioning can be performed using the Web UI, TL1, SNMP, XML, and REST API.
This section provides you with a high-level operational flow that describes the key tasks for installing and configuring the DSC SWe (on OpenStack).
Download the following files from Salesforce: Software Packages: dsc_swe_18_0_0_nb<date>.qcow2 TAR Archive file: dsc_swe_18_0_0_nb<date>_HOT.tgz (contains Heat template *.yaml files)
Task Description Creating an IP Plan on OpenStack Pre-installation Requirements Review this section to make sure that you have met all the requirements for installing, configuring, provisioning, and maintaining the DSC SWe (on OpenStack). Downloading Installation Files Installation Procedures Execute the installation procedures in the same order as they are listed on this page. Configuring and Initializing the DSC SWe (on OpenStack) Execute the procedures in this section to install, license, configure, and initialize the DSC SWe (on OpenStack).
Download the following files from Salesforce:
TAR Archive file:
dsc_swe_18_0_0_nb<date>_HOT.tgz (contains Heat template *.yaml files)