Managing & Metering

See how to deal with deployed and running projects. Get access to the dashboard and logs.

Introduction

Once a project is built and deployed to a k5-project, there is several information that can be accessed. There are two possibilities to access the deployed projects.

  • via the Solution Hub (read more)
  • via the Solution Envoy (read more)

Manage Projects via Solution Hub

Within the Solution Hub all projects deployed by Financial Services Workbench are shown. Besides that, the user has access to all deployments within a k5-project.

Manage Projects via Solution Envoy

Users can access the Solution Envoy's dashboard via the DNS name of the Solution Envoy. A Solution Envoy is the agent that is capable of showing deployed projects built with the Solution Designer.

The Solution Envoy is installed in a so called Tethered Namespace. This special setup allows the main namespace (e.g. cpd) to control it in terms of re-using permissions and several infrastructure components like Helm. Setting up a new namespace is described here.

A detailed description of the available information is provided here. In addition you can use the OpenShift Developer perspective to access additional information about the deployed projects.

Metering

To ensure the correct metering in the sense of complying to the license, it is currently necessary to install the CPD Control Plane on each cluster. The IBM Financial Services Workbench components Solution Hub and Solution Designer must be installed in the same namespace as the CPD Control Plane.

The metering information and key figures can be seen in the Platform Management (Monitoring) of the CPD Control Plane. You can find the URL for the CPD Control Plane with the following command (e.g. for namespace zen): 

oc get route zen-cpd -n zen

In the section Services> you will see Financial Services Workbench> in addition to the IBM Cloud Pak for Data Control Plane. You can click on the Financial Services Workbench service to see the detailed metering data about all regarding namespaces and pods. It can be filtered by Pod statuses and Namespaces (tethered namespaces as well).