Basic deployment scenarios for TrueSight Orchestration in containers
In a deployment model for TrueSight Orchestration in containers, pre-installed images for the repository, the configuration distribution peer (CDP), and an internal Apache Derby database where content is pre-installed are available in Docker containers.
You must have Docker entities such as Docker Engine, Docker Swarm, and Docker Registry set up in your environment. When you deploy these images on containers, with a few steps, your basic TrueSight Orchestration platform environment is set up and ready for use.
You can start with deploying images on a single host in a test environment for any testing or proof-of-concept deployments. For development or production environments, you can use a combination of containerized platform and other TrueSight Orchestration components on servers (physical or virtual).
The following figure depicts a basic deployment scenario, with at least three hosts, in a Docker Swarm, with an embedded Remedy Single Sign-On, and Development Studio installed outside the container world.
|Docker Swarm||Containerized platform must be installed in a Docker swarm mode. In a swarm mode, Docker provides cluster management, orchestration, and support for service failover scenarios amongst many other features. In a swarm mode, you create a cluster of hosts, on which containers are deployed with component images.|
Docker uses a registry as a repository to store images. BMC recommends that you push the images provided in the installation bundle in a registry before starting the deployments. Storing images to a central registry ensures that the images are ready to be pulled on any host, making the installation process less cumbersome.
If you already have a Docker registry set up in your environment, you can choose to push the TrueSight Orchestration images to your trusted registry. You can also choose to create a local registry while deploying containerized TrueSight Orchestration Platform. Docker Engine must be running on any host that you want to designate as a registry.
|Database node||Containerized platform deployments must start with deploying the database image. The database image contains all content (includes all adapters and modules). Content is installed, but not configured or enabled. You must configure and enable content based on your requirements. In this release, all adapters and modules that typically get installed when you choose the Custom feature set installation path. For runbooks (BSM Solutions), you can still choose to install them after your containerized platform environment is functional.|
TrueSight Orchestration is providing a pre-installed image of the repository that you can deploy in one of the hosts in your swarm. After successfully deploying the repository image, you access the repository using the Repository Manager web application similar to a classic deployment. All content is preloaded in the repository and can be accessible from the Repository Manager.
In a basic deployment, embedded Remedy Single Sign-On is deployed with the repository image. The embedded instance of RSSO is used as an external Remedy SSO for the CDP. Default user, groups, and tenants are available in RSSO.
|CDP node||A single CDP image is provided. Basic failover scenarios such as service stopped is taken care of by the swarm. You do not need a High Availability CDP or an Activity Peer in containerized platform.|
In this release, containerized platform can be installed only on linux-based operating systems such RHEL and CentOS. If you need to use windows-based adapters in your environment, you can add a Lightweight Activity Peer to your grid to host the adapters.
LAP is not available on containers and must exist as an independent server in your network.
|Development Studio||Development Studio can be installed on Windows hosts only. For a basic deployment, you must install it on a server outside containerized platform deployment.|