1 Overview of STAP Deployment

Learn about Oracle Communications Solution Test Automation Platform (STAP) deployment.

Note:

STAP is a cloud native application.
Topics in this document:

Overview of STAP Deployment

Oracle Communications Solution Test Automation Platform (STAP) supports a Kubernetes-orchestrated containerized microservice architecture to facilitate continuous integration, continuous delivery, and DevOps practices. This allows you to harness the benefits of the cloud with STAP's services.

STAP cloud-native offers these key features:
  • Kubernetes orchestrates container images (Docker, CRI-O), providing production support for STAP deployment.
  • Helm charts simplify installation and management.
  • Images and scripts facilitate development and testing.
  • A containerized microservice architecture includes the following three essential services:
    • STAP Test Data Service (TDS)
    • STAP Test Execution Service (TES)
    • STAP UI

STAP Deployment Architecture

Figure 1-1 describes a high-level conceptual architecture for STAP deployment in a single OCI region. You use this architectural blueprint as a starting point to leverage the benefits of OCI. Your specific deployment topology will depend on multiple factors specific to the operator's requirements, and may differ from this architecture.

In this conceptual reference architecture, STAP is deployed on the Oracle Cloud Infrastructure Kubernetes Engine (OKE). The STAP Cloud Native Toolkit (CNTK) contains artifacts to deploy all three microservices: TDS, TES, and the STAP UI. The OKE Persistent Volumes (PVs) use NFS-based persistence for shared storage. Images shipped in the CNTK are used alongside the shipped helm charts to deploy each individual microservice. TDS, TES, and the UI microservices communicate with each other using Kubernetes services and are exposed to the operator via the STAP UI.

STAP supports Basic and OAuth Authentication. For OAuth, STAP supports Oracle Cloud Identity Service.

Figure 1-1 STAP Deployment Architecture


Description of Figure 1-1 follows
Description of "Figure 1-1 STAP Deployment Architecture"

This figure shows three microservice deployments: TDS, TES, and UI.

  • The TDS microservice manages the data used in STAP, storing test case data, test results, and other critical testing information. It uses an embedded database to persist all data.
  • The TES microservice is stateless and executes all test cases.
  • The UI microservice offers a web-based interface for interacting with the STAP application.

Each microservice communicates using Kubernetes services, which can be encrypted with TLS.