I currently have a Google Compute Engine VM located in Zone us-central1-a. I want to purchase a Committed Use Discount for this VM, but when I visit the signup page, there is no option for us-central1-a, the closest being us-central1.
Will it be necessary for me to move the instance to us-central1 using the information here, or will the purchase of a commitment in us-central1 automatically apply to a VM located in us-central1-a?
Since I plan to make a 3-year commitment, I don't want to make a mistake because I have heard stories about the lack of support from GCP.
us-central1 is the region. us-central1-a is a zone within that region. Committed use discounts are per region.
Committed use discounts work on most Compute Engine machine types,
including predefined and custom machine types. Committed use discounts
are simple and flexible, and require no upfront costs. Discounts apply
to the aggregate number of vCPUs, memory, GPUs, and local SSDs within
a region, so they are not affected by changes to your instance's
machine setup.
Committed use discounts
Google Cloud Video: Committed Use Discounts
Related
I create a blog on GCP using ghost cms with a bitnami server. I recently found commitment discounts.
I know bitanmi provides a commitment discount on that. But my website is 15 months old maybe for that reason a commitment discount is not added to my bills and my bill amount is very high forme. So that's the reason I try to set up my own commitment discount for my blog.
I config my blog comes to the default configuration. My machine type is g1-small and uses 10 GB storage.
Fill in the information on the commitment page. Them click to purchase button, I face an error.
Creating commitment "commitment-1" failed. Error: invalid value for type Long
Guide me on how to solve it.
Unfortunately you won't be able to use Committed Discounts.
You've mention that you are using g1-small
My machine type is g1-small and uses 10 GB storage
In the Restrictions part you will find:
Committed use discounts do not apply to preemptible VM instances, N1 shared-core machine types, or extended memory.
g1-small is a shared-core machine type. You can confirm it in this docs or in the GCP UI like below (view from Compute Engine)
In Commitment types you can find information on what resources can be committed. On the bottom of this part you also can find information that g1-small cannot be committed.
You can't purchase commitments for f1-micro, or g1-small machine types or for the sole-tenant premium charge.
Regarding storage, only Local SSD disk can be committed and those are 375 GB as per About local SSDs documentation.
Each local SSD is 375 GB in size, but you can attach a maximum of 24 local SSD partitions for 9 TB per instance.
To sum up
With your current setup you are not able to use Committed Discounts. You would need to use different machine type.
In GCP, it is not notified when a virtual machine of with resources higher than the free tier limit is created. An error message of following pattern arises in the notification. So, what is the maximum allowed resourced for Google cloud platform virtual machine?
Create VM instance "instance-2" and its boot disk "instance-2"
Quota 'C2_CPUS' exceeded. Limit: 0.0 in region asia-south1.
As written in the documentation:
Compute Engine
1 non-preemptible e2-micro VM instance per month in one of the following US regions:.
Oregon: us-west1
Iowa: us-central1
South Carolina: us-east1
30 GB-months HDD.
5 GB-month snapshot storage in the following regions:.
Oregon: us-west1
Iowa: us-central1
South Carolina: us-east1
Taiwan: asia-east1
Belgium: europe-west1
1 GB network egress from North America to all region destinations (excluding China and Australia) per month
Your Free Tier e2-micro instance limit is by time, not by instance. Each month, eligible use of all of your e2-micro instances is free until you have used a number of hours equal to the total hours in the current month. Usage calculations are combined across the supported regions.
Google Cloud Free Tier does not include external IP addresses.
Compute Engine offers discounts for sustained use of virtual machines. Your Free Tier use doesn't factor into sustained use.
GPUs and TPUs are not included in the Free Tier offer. You are always charged for GPUs and TPUs that you add to VM instances.
NB: This is subject to changes, check the link for up-to-date information.
Step-by-Step guide to create a free instance:
Create instance
Now go create the instance at https://console.cloud.google.com/compute/instancesAdd
region: us-east1 or one of the region indicated in the documentation.
Select General Purpose -> N2 -> e2-micro. You will see "Your first 744 hours of e2-micro instance usage are free this month"
Select Boot disk -> public image -> ubuntu -> 20.04LS -> boot disk type: Standard persistent disk (HDD) -> size 30gb (or as per documentation)
Allow http and https traffic (or don't check the boxes, if you don't intend to use port 80 and 443)
Click on Create
You can check "view billing report" to make sure you did it right.
You can found more information at the documentation Google Cloud Free Tier:
The Google Cloud Free Tier has two parts:
A 3-month(previously 12) free trial with $300 credit to use with any Google Cloud services.
Always Free, which provides limited access to many common Google Cloud resources, free of charge.
At the section 12-month, $300 free trial you can find Program coverage details:
Your free trial credit applies to all Google Cloud resources, with the
following exceptions:
You can't have more than 8 cores (or virtual CPUs) running at the same time.
You can't add GPUs to your VM instances.
You can't request a quota increase. For an overview of Compute Engine quotas, see Resource quotas.
You can't create VM instances that are based on Windows Server images.
You must upgrade your account to perform any of the actions in the preceding list.
In addition, have a look at the End of the free trial:
The free trial ends when you use all of your credit, or after 12
months, whichever happens first. At that time, the following
conditions apply:
You must upgrade to a paid account to continue using Google Cloud.
All resources you created during the trial are stopped.
Any data you stored in Compute Engine is lost.
Your account enters a 30-day grace period, during which you can recover resources and data you stored in any Google Cloud services
during the trial period.
You might receive a message stating that your account has been canceled, which only indicates that your account has been suspended to
prevent charges.
and at the Recovering data:
Caution: There is no automated way to recover data that you used on VM instances you created with Compute Engine. You must manually
export any data that you want to keep from your Compute Engine VM
instances before the trial period ends.
I do recommend you to upgrade your account before free trial ends.
After the free trial period ends you just have to register a credit card to continue to use their services if/when you accrue charges from them. If you set it up right it might charge you .02 cents every now and then. I just set up my first one with wordpress and at first I would get charged .02cents/month but once I updated the software and the config it rarely charges me. p.s. I started getting hack attempts pretty quickly.
I'm new at GCP and I confess that don't undestand all of the billings.
I'm being charged twice for my instance as you can see in the following image
First for my Instance Core, okay, but later for a Instance Ram, I had made my research and discovered that this can charge me when I use custom RAM on my instance
In this following print, it says me how to find out if I'm using more vCPUs than the pre-defined options
As you can see I'm only using 1 reserved vCPU
That is the pre-defined options of n1-standard-1
Is this charge correct? If so, is there a way to prevent it using n1-standard-1? How?
I am following up regarding your concern about how your instances are being charged. You can verify pricing for Predefined vCPUs and memory. This is the actual price of the service and is more reliable compared to the Pricing Calculator which only gives you an estimate.
The VM instances charge pricing is in this link. It shows the cost for N1’s machine standard predefined machine types. The vCPUs and memory from each of the machine types are billed by their individual predefined vCPU and memory prices.
I suggest that you check the complete pricing matrix for all of our services so you'll have an idea of how much the actual charges will be for your projects and you can choose different instance types or memory from pre-defined n1-standard-1.
If you are interested in discounts, this document explain 3 type of discounts: Sustained use discounts, Committed use discounts, Discounts for preemptible VM instances
Also the Google Cloud Free Tier gives you free resources to learn about Google Cloud services by trying them on your own.
I purchased a VM with a committed use discount from GCP and it's active but now I would think that this VM would be added to my VM instances list but it's not.
My two old VM's are still running but I don't see my VM that should be connected to my committed use discount purchase.
Does anybody know how to proceed to setup a VM with my purchase?
Thanks,
Claudio
Committed use discounts are automatically applied to the project they were purchased under, and are only applied to the number of cores that were specified when the commitment was purchased.
So for example, if the commitment was made for 4 cores for 24 hours and 8 were used, the discount will be applied to the 4 cores.
It is also specific to a region. If you purchase a committed usage discount for us-east1 it won't apply to a VM in us-central1 for instance.
You can find more detailed information and some examples on this article here .
Is it possible to use Google Container Engine with Google Cloud free tier?
(I mean the "Always Free" usage limit, not the $300 free credit)
The docs for GKE says:
The basic cluster is free but each node is charged at standard Compute
Engine pricing
But the Compute Engine also have a free instance. Is it possible to use them together?
Unfortuniately, this is no longer a correct answer, as GKE no longer (as of December 2020 if not earlier) supports f1-micro instances for node pools as they do not have sufficient memory (as alluded to in my original answer below where enabling stackdrier would make the cluster unstable). Therefore, it is not possible to run a GKE cluster fully within the free tier.
Previously, this was possible. See explanation below.
Yes, you can use GKE with the free tier. GKE only charges for the underlying compute engine resources, which are directly billed by compute engine. (Note that after June 6, 2020, the free tier only includes one free GKE zonal cluster -- not an unlimited number of clusters).
GKE will likely require you to run 3 free f1-micro instances concurrently to get the cluster to a minimum size, but as long as the cluster is in one of the free regions and the total usage in a month is under the total number of hours per month it will still be free (that is, you can run 3 f1-micros for a bit under 250 hours and still be in the free tier). Make sure to shut off your instances when you are not using them. See more at https://cloud.google.com/free/docs/gcp-free-tier#always-free-usage-limits (especially the notes about the limit being time rather than instance count).
You may also want to ensure that the persistant disks are not kept around while the cluster isn't running, as the free tier only allows 3 10GB disks over the course of the month.
If you happen to run over the usage, you will only be charged for the usage beyond the free tier.
Of course, this all assumes that f1-micro instances are suitable to your use case. They are quite limited, and once GKE is on them, they have almost nothing remaining in terms of RAM: https://cloud.google.com/kubernetes-engine/docs/concepts/cluster-architecture#memory_cpu
Finally, it has been my experience that setting up the stackdriver support when you create the cluster if you only have micro instances can cause the cluster to struggle greatly -- the stackdriver monitoring alone (or with even minimal other applications) start to cause the nodes to be throttled and time out.
For now It's not possible to create kubernates cluster with one f1-micro. It requires minimum 3 f1-micro instances:
ERROR: (gcloud.container.clusters.create) ResponseError: code=400,
message=Clusters of f1-micro instances must contain at least 3 nodes.
Please make the cluster larger or use a different machine type
This is how I made mine. I created a cluster named 'free-cluster' which runs 2 nodes. These nodes are in 'us-west1-a' as the 'free' tier only allows for the us-east, us-west and us-central zones only. also the VM instance-type should only use 'f1-micro' as that is the freebie they give. the rest are paid.
As is pointed out, GCP does force us to create 3 nodes and no option to state this in the dashboard. But after that you can just go to the nodes and "cordon" and "drain" them so they will not consume the free compute fast. You can leave just one node for the free-tier... this however makes less sense as you will not take advantage of load balancing, self-healing and other features as to why we use kubernetes clusters to begin with. for me I am good testing on 2 nodes as I only need to pay for that 1 cheap monthly f1-micro for my hobby and learning. make sure to go to Google Compute Engine in the dashboard and open the 'Instance groups' in the sidebar, you will find the VM instances in that cluster which you can just delete by selecting and clicking the "Delete Instance" button.
There is no way to get a free GKE cluster on GCP, but you can get a very cheap one by following the instructions at https://github.com/Neutrollized/free-tier-gke.
Using a combination of GKE's free management tier and a low cost machine type, the cost estimate is less than $5 per month: .
More details on what is available as part of the free tier can be found here: https://cloud.google.com/free.
tl;dr
gcloud container clusters create cheap-cluster \
--zone us-west1-a \
--node-locations us-west1-a \
--machine-type=e2-small \
--max-nodes=1 \
--num-nodes=1
As I understand, Google allows 1 f1-micro instance to be used for free even after the 12 month free period.