added NFS costs #247
added NFS costs #247
Conversation
|
Thank you for your feedback! We’ll look into it and come back to you if we have any questions. |
PlamiIG
added
ua-review
|
@PlamiIG Thanks for taking care of it. But please hold on a while, it's still a draft. I'll ping you as soon as I'm done with the update :) |
|
@marco-porru - @PlamiIG distributed it to the author in charge: I will take care of this. |
|
@NHingerl Please review it. |
| @@ -262,7 +262,7 @@ Number of CU per Hour | |||
| </tr> | |||
| </table> | |||
|
|
|||
| **For Storage** | |||
| **For Standard Storage** | |||
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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")
|
|
||
| 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. |
There was a problem hiding this comment.
"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?
There was a problem hiding this comment.
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.
|
|
||
| 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. | ||
| 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**. |
There was a problem hiding this comment.
Do you mean the formula from the Backward Calculation section?
There was a problem hiding this comment.
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 | ||
|
|
||
| Premium storage can be enabled using Cloud Manager and will create storage using NFS technology. |
There was a problem hiding this comment.
When someone adds the Cloud Manager Module do they already start using the premium storage? What are the prerequisites?
There was a problem hiding this comment.
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?
| #### Premium Storage | ||
|
|
||
| Premium storage can be enabled using Cloud Manager and will create storage using NFS technology. | ||
| The pricing for premium storage is based on the storage metrics and is scaled up by a factor of **3** compared to standard storage. |
There was a problem hiding this comment.
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?
|
|
||
| #### Cloud-managed Redis | ||
|
|
||
| When deployed with the Cloud Manager module, Redis creates a cluster in the Kyma's cloud provider account and begins consuming new, dedicated machines. |
| @@ -304,7 +304,79 @@ Number of CU per Hour | |||
| </tr> | |||
| </table> | |||
|
|
|||
| ### Additional Costs | |||
There was a problem hiding this comment.
What does it mean? Can we write clearly what the additional costs refer to already in the headline?
There was a problem hiding this comment.
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. | ||
| 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**. | ||
|
|
||
| #### Premium Storage |
There was a problem hiding this comment.
Why is it called premium? What does it mean?
| @@ -262,7 +262,7 @@ Number of CU per Hour | |||
| </tr> | |||
| </table> | |||
|
|
|||
| **For Storage** | |||
| **For Standard Storage** | |||
There was a problem hiding this comment.
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")
| @@ -304,7 +304,79 @@ Number of CU per Hour | |||
| </tr> | |||
| </table> | |||
|
|
|||
| ### Additional Costs | |||
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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.
|
|
||
| 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. | ||
| 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**. |
There was a problem hiding this comment.
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 | ||
|
|
||
| Premium storage can be enabled using Cloud Manager and will create storage using NFS technology. |
There was a problem hiding this comment.
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?
|
|
||
| When deployed with the Cloud Manager module, Redis creates a cluster in the 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. |
There was a problem hiding this comment.
| 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?
| | P5 | 101 | 30363 | 12335 | | ||
| | P6 | 200 | 60704 | 24661 | | ||
|
|
||
| NB: **Approx. Available Size (GiB)** might vary depending on the cloud provider. |
There was a problem hiding this comment.
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.
|
|
||
| | **Tier** | **Approx. Available Size (GiB)** | **Cost expressed in Storage size** | **Cost in CU** | | ||
| |:--------: |:--------------------------------: |-----------------------------------: |---------------: | | ||
| | S1 | 1 | 182 | 74 | |
There was a problem hiding this comment.
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?
| @@ -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. | |||
|
|
|||
There was a problem hiding this comment.
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?
|
|
||
| 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. |
There was a problem hiding this comment.
First the purpose, then the instruction:
| 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)?
Introduced computation of additional costs