Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added NFS costs #247

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

added NFS costs #247

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
fae0313
added NFS costs
marco-porru Dec 3, 2024
2cb91a3
added NFS storage and redis.
marco-porru Dec 3, 2024
f063d96
Merge branch 'main' into patch-4
marco-porru Dec 19, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
78 changes: 75 additions & 3 deletions docs/10-concepts/service-plans-and-metering-for-kyma-runtime-c33bb11.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -262,7 +262,7 @@ Number of CU per Hour
</tr>
</table>

**For Storage**
**For Standard Storage**
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The word "Standard" here can be misleading... We already use the word to describe the Service Plan. Maybe "Basic" instead? or leave this just as it was and add "Premium" as a differentiation?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In general, isn't it still the same "kind" of storage - just priced differently? It's not that for premium, the hardware is gold-plated? :D
So basically, what concretely is it that makes premium storage "premium" and doesn't allow putting it into the same category (just with 3x higher price) as the existing "For Storage" (vs "For CPU")



<table>
Expand Down Expand Up @@ -304,7 +304,79 @@ Number of CU per Hour
</tr>
</table>

### Additional Costs
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does it mean? Can we write clearly what the additional costs refer to already in the headline?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I second that.

Also, this introduces the "Additional Costs" as something different from the "Underlying Metrics"; as it's another headline on the same level. But aren't the "premium costs" still a kind of underlying metric? Just a special one, for a limited group of users (who probably can opt in to use that service and incur the cost).


Certain features of Cloud Manager may initiate additional hardware resources in the cloud provider account. These features could potentially incur extra costs based on the resources you implement.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Certain features" sounds vague. Do we know which features? Can we be more specific here?

May they initiate additional hardware resources? or is that certain?
These features could potentially incur extra costs based on the resources you implement or is that certain?
How do the users know that the potential extra costs are applicable to them?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is Cloud Manager? We can't assume that readers of this document have any idea about this specific module, or in fact about Kyma modules in general. We should start with a sentence that these "Additional Costs" are specific to users of the Cloud Manager module (if I don't misunderstand the situation). These aren't generic "additional costs", they have a clearly defined scope and target group.

I concur with Gosia that the whole paragraph is extremely vague.

All additional costs are calculated using a baseline formula, which is a combination of the two metrics used to compute other Kyma costs: **CPU** and **Storage**.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you mean the formula from the Backward Calculation section?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This paragraph talks about CPU and storage, but the table below only mentions (premium) storage and never again talks about CPU. So what is there to say about CPU in the context of "additional cost"?
And if "premium" CPU is identical to normal CPU and doesn't deserve mentioning again, why not put "premium" storage next to its "basic" sibling instead of opening a whole new section?


#### Premium Storage
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is it called premium? What does it mean?


Premium storage can be enabled using Cloud Manager and will create storage using NFS technology.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When someone adds the Cloud Manager Module do they already start using the premium storage? What are the prerequisites?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I concur, it's unclear if this is automatic or manual, and whether it is avoidable for Cloud Manager users.

Could this sentence be rephrased to:
"If you use the Cloud Manager module, you automatically get premium storage with NFS technology." or something similar.

Also, what is "NFS"? It seems to be important (otherwise you could just drop the last three words), but it's explained nowhere. Is normal storage created with some other technology? If yes, why does the difference matter?

The pricing for premium storage is based on the storage metrics and is scaled up by a factor of **3** compared to standard storage.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In line 310 you wrote that the additional costs are calculated using the basic formula. So actually is the formula the same as for the standard storage or not?


<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.00169271 ( = 3 * 0.00056423611)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

here, you use multiplication mark *, but in line 350, you use x. Why?


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

32GB

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

0.05416667 \(0.00169271 x 32\)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

here, you use multiplication mark x, but in line 338, you use *. Why?


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

#### Cloud-managed Redis
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
#### Cloud-managed Redis
#### Cloud-Managed Redis

Headlines must be title case


When deployed with the Cloud Manager module, Redis creates a cluster in the Kyma's cloud provider account and begins consuming new, dedicated machines.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you mean by deployed here?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Is there a way to deploy Redis without Cloud Manager? And conversely, can you deploy Cloud Manager without Redis?
  • Can we rephrase passive voice to active voice? Who deploys what?
  • Also, no "the" with Kyma.
Suggested change
When deployed with the Cloud Manager module, Redis creates a cluster in the Kyma's cloud provider account and begins consuming new, dedicated machines.
When deployed with the Cloud Manager module, Redis creates a cluster in Kyma's cloud provider account and begins consuming new, dedicated machines.

Generally, a cache is defined by its size, measured in GiB, which is then used to determine metering and billing using storage metrics as the basis.
As the price is standardized across all available cloud providers, Redis is offered in several different tiers that are essentially equivalent across all cloud providers. This applies to both the standard and the premium plans.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
As the price is standardized across all available cloud providers, Redis is offered in several different tiers that are essentially equivalent across all cloud providers. This applies to both the standard and the premium plans.
Because the price is standardized across all available cloud providers, Redis is offered in several different tiers that are essentially equivalent across all cloud providers. This applies to both, the basic and the premium plans.

Wait, what do you mean with "plans". Are we introducing a whole new Kyma service plan?
"Free", "Standard", and now "Premium"? 😮 Does the diagram need an update?

image


| **Tier** | **Approx. Available Size (GiB)** | **Cost expressed in Storage size** | **Cost in CU** |
|:--------: |:--------------------------------: |-----------------------------------: |---------------: |
| S1 | 1 | 182 | 74 |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which units belong to these naked numbers?
CPU is counted in nodes, storage in GB, and I assume cost would be Euros? But we don't and shouldn't state any actual prices in this doc. So what exactly do the last two columns mean?

| S2 | 3 | 364 | 148 |
| S3 | 6 | 953 | 387 |
| S4 | 12 | 1915 | 778 |
| S5 | 24 | 3793 | 1541 |
| S6 | 48 | 7591 | 3084 |
| S7 | 101 | 15180 | 6167 |
| S8 | 202 | 30353 | 12331 |
| P1 | 5 | 1903 | 773 |
| P2 | 12 | 3828 | 1555 |
| P3 | 24 | 7586 | 3082 |
| P4 | 48 | 15180 | 6167 |
| P5 | 101 | 30363 | 12335 |
| P6 | 200 | 60704 | 24661 |

NB: **Approx. Available Size (GiB)** might vary depending on the cloud provider.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this means nota bene: We never use latin abbreviations in documentation.
Use "Note", or just format it as normal sentence without any intro phrase.


### Examples

Expand Down Expand Up @@ -335,9 +407,9 @@ Find the Kyma price calculator on [https://kyma-project.github.io/price-calculat

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

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we dropping the steps to estimate the hours per month and the optional addition of more nodes? Did the functionality and UI of the Kyma cost calculator change?

Are the new two steps replacements for the old steps?
Are the new two steps valid for all readers, or just for Cloud Manager/Redis customers?

3. Estimate the **hours per month** you expect to run them.
3. Optionally, add more storage and additional capabilities to the calculation.

4. Optionally, add more Nodes and more storage to the calculation.
4. You can also change the **Conversion rate from Capacity Units to €** to estimate the eventual discount applicable with your contract.
Copy link
Contributor

@NHingerl NHingerl Dec 19, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First the purpose, then the instruction:

Suggested change
4. You can also change the **Conversion rate from Capacity Units to €** to estimate the eventual discount applicable with your contract.
4. To estimate the eventual discount applicable with your contract, you can also change the **Conversion rate from Capacity Units to €**.

Is the purpose "To estimate the eventual discount applicable with your contract" only applicable to this step? Or isn't this the purpose of the whole step instruction (and, basically, of the Kyma cost calculator)?



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.
Expand Down
Loading