From df45eab5fd585cf1ea69a42344b15cbf910e2c56 Mon Sep 17 00:00:00 2001
From: SheryarButt <m.sheryarbutt@gmail.com>
Date: Mon, 20 May 2024 23:56:54 +0500
Subject: [PATCH] Custom Pricing Model (for Opencost by MTO)

---
 .../crds-api-reference/integration-config.md  | 24 ++++++++++++++++++
 content/installation/openshift.md             | 25 +++++++++++++++++++
 2 files changed, 49 insertions(+)

diff --git a/content/crds-api-reference/integration-config.md b/content/crds-api-reference/integration-config.md
index 356aa611..0fd72300 100644
--- a/content/crds-api-reference/integration-config.md
+++ b/content/crds-api-reference/integration-config.md
@@ -564,3 +564,27 @@ path "identity/group/id/*" {
   capabilities = ["create", "read", "update", "patch", "delete", "list"]
 }
 ```
+
+### Custom Pricing Model
+
+You can modify IntegrationConfig to customise the default pricing model. Here is what you need at `IntegrationConfig.Spec.components`:
+
+```yaml
+components:
+    console: true # should be enabled
+    showback: true # should be enabled
+    # add below and override any default value
+    # you can also remove the ones you do not need
+    customPricingModel:
+        CPU: "0.031611"
+        spotCPU: "0.006655"
+        RAM: "0.004237"
+        spotRAM: "0.000892"
+        GPU: "0.95"
+        storage: "0.00005479452"
+        zoneNetworkEgress: "0.01"
+        regionNetworkEgress: "0.01"
+        internetNetworkEgress: "0.12"
+```
+
+After modifying your default IntegrationConfig in `multi-tenant-operator` namespace, a configmap named `opencost-custom-pricing` will be updated. You will be able to see updated pricing info in `mto-console`.
diff --git a/content/installation/openshift.md b/content/installation/openshift.md
index a671157d..b94fa894 100644
--- a/content/installation/openshift.md
+++ b/content/installation/openshift.md
@@ -8,6 +8,8 @@ This document contains instructions on installing, uninstalling and configuring
 
 1. [Enabling Console](#enabling-console)
 
+1. [License configuration](#license-configuration)
+
 1. [Uninstall](#uninstall-via-operatorhub-ui)
 
 ## Requirements
@@ -139,6 +141,29 @@ spec:
 
 * Now the `InstallPlan` will be approved, and MTO console components will be installed.
 
+## License Configuration
+
+We offer a free license with installation and you can create max 2 [Tenants](../tutorials/tenant/create-tenant.md) with it.
+
+We offer a paid license as well. You need to have a configmap `license` created in MTO's namespace (multi-tenant-operator). To get this configmap, you can contact [`sales@stakater.com`](mailto:sales@stakater.com). It would look like this:
+
+```yaml
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: license
+  namespace: multi-tenant-operator
+data:
+  payload.json: |
+    {
+        "metaData": {
+            "tier" : "paid",
+            "company": "<company name here>"
+        }
+    }
+  signature.base64.txt: <base64 signature here.>
+```
+
 ## Uninstall via OperatorHub UI
 
 You can uninstall MTO by following these steps: