Skip to content

Commit

Permalink
Update from SAP DITA CMS (squashed):
Browse files Browse the repository at this point in the history 
commit ca22655201028047919664f6a554377877eb2cea
Author: REDACTED
Date:   Wed May 15 15:57:42 2024 +0000

    Update from SAP DITA CMS 2024-05-15 15:57:42
    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Output: loio2080d0faf9d84ce6aa14caa4caa32935
    Language: en-US
    Builddable map: 0fcfe38e11674227bb0a8d014337319b.ditamap

commit b714c0b5fe54b4894c342802935569357f927928
Author: REDACTED
Date:   Wed May 15 15:36:36 2024 +0000

    Update from SAP DITA CMS 2024-05-15 15:36:36
    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Output: loio2080d0faf9d84ce6aa14caa4caa32935
    Language: en-US
    Builddable map: 0fcfe38e11674227bb0a8d014337319b.ditamap

commit c7ccc4ad6ed097c2df55ab97d260c1cdcfdd498d
Author: REDACTED
Date:   Wed May 15 12:43:31 2024 +0000

    Update from SAP DITA CMS 2024-05-15 12:43:31
    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Output: loio2080d0faf9d84ce6aa14caa4caa32935
    Language: en-US
    Builddable map: 0fcfe38e11674227bb0a8d014337319b.ditamap

##################################################
[Remaining squash message was removed before commit...]
  • Loading branch information
@ditaccms-bot
ditaccms-bot committed May 15, 2024
1 parent 282d934 commit b4a4e75
Show file tree
Hide file tree
Showing 75 changed files with 4,090 additions and 2,462 deletions.
4 changes: 2 additions & 2 deletions docs/10-concepts/basic-platform-concepts-73beb06.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -188,9 +188,9 @@ For more information, see [Entitlements and Quotas](entitlements-and-quotas-00aa

## User and Member Management

On SAP BTP, member management happens at all levels from global account to environment, while user management is done for business applications.
On SAP BTP, member management takes place at all levels from global account to environment, while user management is relevant for business applications.

**User accounts** enable users to log on to SAP BTP and access subaccounts and use services according to the permissions given to them. We distinguish between two types of users:
**User accounts** enable users to log on to SAP BTP, access subaccounts, and to use services according to the permissions granted to them. We distinguish between two types of users:

![Platform and Business Users](images/user-accounts_27c8463.png)

Expand Down
2 changes: 1 addition & 1 deletion docs/10-concepts/commercial-information-b7f5a93.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@

### Description

SAP BTP ABAP environment is SAP’s Platform-as-a-Service offering to create innovative ABAP applications and extensions in the cloud. It provides the modern ABAP RESTful Application Programming Model, leveraging SAP HANA, SAP Fiori, and a cloud-optimized ABAP language with a clear set of released standard APIs. Developers can utilize a development toolset that enables tight integration with Git-enabled lifecycle management.
SAP BTP ABAP environment is SAP’s Platform-as-a-Service offering to create innovative ABAP applications and extensions in the cloud. It provides the modern ABAP RESTful Application Programming Model, leveraging SAP HANA Cloud, SAP Fiori, and a cloud-optimized ABAP language with a clear set of released standard APIs. Developers can utilize a development toolset that enables tight integration with Git-enabled lifecycle management.



Expand Down
373 changes: 373 additions & 0 deletions docs/10-concepts/commercial-information-for-kyma-runtime-c33bb11.md
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,373 @@
<!-- loioc33bb114a86e474a95db29cfd53f15e6 -->

# Commercial Information for Kyma Runtime



<a name="loioc33bb114a86e474a95db29cfd53f15e6__section_rkn_4pz_5zb"/>

## Service Description

SAP BTP, Kyma runtime is a fully managed Kubernetes runtime based on the open-source project "Kyma". This cloud-native solution allows the developers to extend SAP solutions with serverless Functions and combine them with containerized microservices. The offered functionality ensures smooth consumption of SAP and non-SAP applications, running workloads in a highly scalable environment, and building event- and API-based extensions.



<a name="loioc33bb114a86e474a95db29cfd53f15e6__section_gwp_yyy_5zb"/>

## Service Plans



### Service Overview

![](images/Service_Plans_Kyma_3b88103.png)



### SAP BTP Cockpit Service Plan Descriptions

**SAP BTP Cockpit Service Plan Descriptions**


<table>
<tr>
<th valign="top">

Name

</th>
<th valign="top">

Service Plan \(Discovery Center\)

</th>
<th valign="top">

Description

</th>
</tr>
<tr>
<td valign="top">

free

</td>
<td valign="top">

Free

</td>
<td valign="top">

Subscribe to the 30-day free plan provided on Amazon Web Services. This plan uses Kyma on a limited size cluster \(4CPU - 16GB RAM\). The upgrade to the paid plan is not yet supported. Only best-effort support is available for free tier service plans and these are not subject to SLAs. The services you plan to use must be available in the same region as the subaccount for the Kyma runtime.

</td>
</tr>
<tr>
<td valign="top">

aws

</td>
<td valign="top">

Standard

</td>
<td valign="top">

Select Amazon Web Services as the cloud provider where your Kyma cluster is deployed.

</td>
</tr>
<tr>
<td valign="top">

gcp

</td>
<td valign="top">

Standard

</td>
<td valign="top">

Select Google Cloud as the cloud provider where your Kyma cluster is deployed.

</td>
</tr>
<tr>
<td valign="top">

azure

</td>
<td valign="top">

Standard

</td>
<td valign="top">

Select Microsoft Azure as the cloud provider where your Kyma cluster is deployed.

</td>
</tr>
</table>



<a name="loioc33bb114a86e474a95db29cfd53f15e6__section_x43_x1z_5zb"/>

## Metrics

The usage metric for the Cloud Service is a Capacity Unit \(CU\) per month.


<table>
<tr>
<th valign="top">

Metric

</th>
<th valign="top">

Definition

</th>
</tr>
<tr>
<td valign="top">

Capacity Unit

</td>
<td valign="top">

Number of units consumed by the usage of the services as outlined in the solution-specific product supplement.

For SAP BTP, Kyma runtime, there are two capacity units: one to measure the workload, the second to measure the storage.

</td>
</tr>
</table>



<a name="loioc33bb114a86e474a95db29cfd53f15e6__section_o4b_bsz_5zb"/>

## Backward Calculation



### Formula

The relationship between consumed workload/storage and the respective CU is straightforward.

However, cost per monthly bill may vary because it depends on the size of the nodes that were used. There is no fixed formula because of Kyma's flexible scaling.



### Underlying Metrics

In the following tables, “CU” stands for “Capacity Unit”.

**For CPU**


<table>
<tr>
<th valign="top">

Amount of CPU/CPU Nodes

</th>
<th valign="top">

Number of CU per Hour

</th>
</tr>
<tr>
<td valign="top">

2

</td>
<td valign="top">

0.48055555555555557 x 0.75

</td>
</tr>
<tr>
<td valign="top">

4

</td>
<td valign="top">

0.48055555555555557

</td>
</tr>
<tr>
<td valign="top">

8

</td>
<td valign="top">

0.48055555555555557 x 2

</td>
</tr>
<tr>
<td valign="top">

16

</td>
<td valign="top">

0.48055555555555557 x 4

</td>
</tr>
<tr>
<td valign="top">

32

</td>
<td valign="top">

0.48055555555555557 x 8

</td>
</tr>
<tr>
<td valign="top">

...

</td>
<td valign="top">

...

</td>
</tr>
</table>

**For Storage**


<table>
<tr>
<th valign="top">

Amount of Storage

</th>
<th valign="top">

Number of CU per Hour

</th>
</tr>
<tr>
<td valign="top">

1GB

</td>
<td valign="top">

0.00056423611

</td>
</tr>
<tr>
<td valign="top">

32GB

</td>
<td valign="top">

0.01805555552 \(0.00056423611 x 32\)

</td>
</tr>
</table>



### Examples

- Your bill for Nodes shows 1800 capacity units charged for 4vCPU Nodes in a month.

This means that you were running roughly 1800 / 0.4806 = 3745.32 hours worth of 4vCPU nodes. Given that a month has 720 hours, this means you were running 3745.32/720 = 5.2 Nodes cluster for a full month.

Due to Kyma’s automatic scaling, 5.2 does not mean actual size. It means that during some hours in the month, the cluster size was 4 nodes. At other times, there was more load, so the cluster autoscaled to 5 or 6 nodes, based on your configurations. So your average cluster size for the full month was 5.2 Nodes.

- Your bill for storage shows 200 capacity units charged for storage \(32GB block\) for the month.

This means that you used 200 / 0.0181 = 11049.72 hours of 32GB storage blocks. Given that a month has 720 hours, this means that you have used 11049.72/720 = 15,34 blocks of 32GB over the month. So, you used 15.34 \* 32 = 491GB of storage continuously during the month.

This implies that as you started using Kyma, you deployed more applications that used storage of various sizes, such as 4GB or 8GB.

Note that storage is provided in blocks of 32GB, so if you used 33 GB, you would be charged for 2 \* 32GB, that is 64 GB.




<a name="loioc33bb114a86e474a95db29cfd53f15e6__section_dnb_hsz_5zb"/>

## Calculator

Find the Kyma price calculator on [https://kyma-project.github.io/price-calculator/](https://kyma-project.github.io/price-calculator/) and use it to estimate the costs for your SAP BTP, Kyma runtime.

1. Choose the **size of virtual machine** \(VM\).

2. Choose the **minimum of VMs** you need.

3. Estimate the **hours per month** you expect to run them.

4. Optionally, add more Nodes and more storage to the calculation.


Note that the result is an estimate, and the monthly bill may vary depending on the actual hours and size of the Kyma cluster \(workload and storage\) that was running in a month.



<a name="loioc33bb114a86e474a95db29cfd53f15e6__section_egv_qcn_1bc"/>

## Supplemental Terms And Conditions

For additional information, please refer to the [SAP Business Technology Platform Service Description Guide](https://www.sap.com/about/trust-center/agreements/cloud/cloud-services.html?sort=latest_desc&search=SAP%20Business%20Technology%20Platform%20Service%20Description%20Guide&tag=language:english), section “SAP BUSINESS TECHNOLOGY PLATFORM, KYMA RUNTIME”.



<a name="loioc33bb114a86e474a95db29cfd53f15e6__section_bl4_4tz_5zb"/>

## Glossary

[Commercial Information Glossary](https://help.sap.com/docs/help/5d771150f8f547c6bc604c7d674cf30d/7014f9db099148f1897c1bda5db21f39.html?locale=en-US)



<a name="loioc33bb114a86e474a95db29cfd53f15e6__section_ypn_rtz_5zb"/>

## Service Specifics

As soon as you instantiate a Kyma cluster, the basic costs for the empty cluster incurs.

Cost may then vary depending on the actual workloads and storage you consume per month.

Loading

0 comments on commit b4a4e75

Please sign in to comment.