From 72856392274e57d37a532fbfde4161389ba78869 Mon Sep 17 00:00:00 2001 From: Matthias Bernhardt <40292398+matthiasbernhardt@users.noreply.github.com> Date: Wed, 14 Jun 2023 14:04:23 +0200 Subject: [PATCH 1/2] explain usage (running vs. occupied) --- user/pages/04.Reference/03.compute/docs.en.md | 9 +++++++++ user/pages/05.Background/03.resource-limits/docs.en.md | 5 +++++ 2 files changed, 14 insertions(+) diff --git a/user/pages/04.Reference/03.compute/docs.en.md b/user/pages/04.Reference/03.compute/docs.en.md index ad8a13a1..7f421ee3 100644 --- a/user/pages/04.Reference/03.compute/docs.en.md +++ b/user/pages/04.Reference/03.compute/docs.en.md @@ -240,3 +240,12 @@ This security group can now be connected to a port of your network: ``` The security group "default" is added in this example, since this group is taking care of allowing outbound traffic. + + +### Are stopped instances counted regarding quota or ondemand billing? + +Any occupied resources are considered "used" and counted against your [quota limits](../../05.Background/03.resource-limits/docs.en.md#usage). They will also be counted against your upfront commitment or charged on demand. +When you create an instance, volume, snapshot, object, loadbalancer, floating ip, dns zone, rescources will be allocated and so they will be counted and charged, no matter if they are actually running, attached, assigned. +To save money or free quota, it is thus not sufficient to stop, detach or unassign them, you must delete them completely to free the resources so that we can reuse them. +It is part of higher level automation like kuberenetes or terraform or similar tools to recreate them if needed. + diff --git a/user/pages/05.Background/03.resource-limits/docs.en.md b/user/pages/05.Background/03.resource-limits/docs.en.md index 750be46e..ec9e9e04 100644 --- a/user/pages/05.Background/03.resource-limits/docs.en.md +++ b/user/pages/05.Background/03.resource-limits/docs.en.md @@ -39,5 +39,10 @@ Some customers prefer to commit to a certain volume paid upfront, other prefer p While quota limits apply per project and region, your upfront commitment can be applied over all regions. This comes in handy, if you have a not fully redundant, but fully automated infrastructure in one of our regions and we announce a maintenance. You can get the same quota limits in another region, build a copy of your infrastructure, switch over and tear down the now unused infrastructure in the old region. While the baseline of you setup is covered by the commitment, you only have to pay the exceeding resources on demand for the short duration where the setup is doubled. The idle buffers do not need to be paid. +### Usage +Any occupied resources are considered "used" and counted against your quota limits. They will also be counted against your upfront commitment or charged on demand. +When you create an instance, volume, snapshot, object, loadbalancer, floating ip, dns zone, rescources will be allocated and so they will be counted and charged, no matter if they are actually running, attached, assigned. +To save money or free quota, it is thus not sufficient to stop, detach or unassign them, you must delete them completely to free the resources so that we can reuse them. +It is part of higher level automation like kuberenetes or terraform or similar tools to recreate them if needed. From 8c5ff461a60036536a9da4982e22f1d9d784a684 Mon Sep 17 00:00:00 2001 From: Matthias Bernhardt <40292398+matthiasbernhardt@users.noreply.github.com> Date: Mon, 26 Jun 2023 11:41:07 +0200 Subject: [PATCH 2/2] fix typos --- user/pages/04.Reference/03.compute/docs.en.md | 4 ++-- user/pages/05.Background/03.resource-limits/docs.en.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/user/pages/04.Reference/03.compute/docs.en.md b/user/pages/04.Reference/03.compute/docs.en.md index 7f421ee3..ae586a40 100644 --- a/user/pages/04.Reference/03.compute/docs.en.md +++ b/user/pages/04.Reference/03.compute/docs.en.md @@ -245,7 +245,7 @@ The security group "default" is added in this example, since this group is takin ### Are stopped instances counted regarding quota or ondemand billing? Any occupied resources are considered "used" and counted against your [quota limits](../../05.Background/03.resource-limits/docs.en.md#usage). They will also be counted against your upfront commitment or charged on demand. -When you create an instance, volume, snapshot, object, loadbalancer, floating ip, dns zone, rescources will be allocated and so they will be counted and charged, no matter if they are actually running, attached, assigned. +When you create an instance, volume, snapshot, object, loadbalancer, floating ip, dns zone, resources will be allocated and so they will be counted and charged, no matter if they are actually running, attached, assigned. To save money or free quota, it is thus not sufficient to stop, detach or unassign them, you must delete them completely to free the resources so that we can reuse them. -It is part of higher level automation like kuberenetes or terraform or similar tools to recreate them if needed. +It is part of higher level automation like kubernetes or terraform or similar tools to recreate them if needed. diff --git a/user/pages/05.Background/03.resource-limits/docs.en.md b/user/pages/05.Background/03.resource-limits/docs.en.md index ec9e9e04..f18cedde 100644 --- a/user/pages/05.Background/03.resource-limits/docs.en.md +++ b/user/pages/05.Background/03.resource-limits/docs.en.md @@ -42,7 +42,7 @@ While quota limits apply per project and region, your upfront commitment can be ### Usage Any occupied resources are considered "used" and counted against your quota limits. They will also be counted against your upfront commitment or charged on demand. -When you create an instance, volume, snapshot, object, loadbalancer, floating ip, dns zone, rescources will be allocated and so they will be counted and charged, no matter if they are actually running, attached, assigned. +When you create an instance, volume, snapshot, object, loadbalancer, floating ip, dns zone, resources will be allocated and so they will be counted and charged, no matter if they are actually running, attached, assigned. To save money or free quota, it is thus not sufficient to stop, detach or unassign them, you must delete them completely to free the resources so that we can reuse them. -It is part of higher level automation like kuberenetes or terraform or similar tools to recreate them if needed. +It is part of higher level automation like kubernetes or terraform or similar tools to recreate them if needed.