Sh Cache Microservice is a service that provides HTTP access to the HSS via diameter Sh, as well as caching some of that data to reduce round trips to the HSS.
This manual provides instructions for configuring and deploying ShCM nodes on VMware or Openstack virtual machine hosts.
It assumes you are familiar with Sh Cache Microservice and have planned your network as described in the Top Level Architecture.
For configuration of your deployment following the initial installation and day-to-day management of the Sh Cache Microservice, refer to the Sh Cache Microservice Configuration Guide.
The acronym ShCM is pronounced as shook-um, and thus we refer to "a ShCM", not "an".
Glossary
The following acronyms and abbreviations are used throughout the Sh Cache Microservice documentation.
CDS |
Configuration Data Store Database used to store configuration data for the VMs. |
CSAR |
Cloud Service ARchive File type used by the Commissioning VM. |
Deployment ID |
Uniquely identifies a deployment, which can consist of many sites, each with many groups of VMs |
HSS |
Home Subscriber System |
HTTP |
Hypertext Transfer Protocol |
OVA |
Open Virtual Appliance File type used by VMware. |
OVF |
Open Virtualization Format File type used by VMware. |
QCOW2 |
QEMU Copy on Write 2 File type used by OpenStack. |
RVT |
Rhino VoLTE TAS |
SAS |
Service Assurance Server |
SDF |
Solution Definition File Describes the deployment, for consumption by the Commissioning VM. |
Sh |
Diameter Sh protocol |
ShCM |
Sh Cache Microservice The abbreviated form ShCM is pronounced as |
Site ID |
Uniquely identifies one site within the deployment, normally a geographic site (e.g. one data center) |
TAS |
Telecom Application Server |
TSN |
TAS Storage Node TSNs provide Cassandra databases and CDS services to the other VMs. |
VM |
Virtual Machine |
YANG |
Yet Another Next Generation Schemas used for verifying YAML files. |
