{"id":5904,"date":"2019-06-12T16:24:52","date_gmt":"2019-06-12T09:24:52","guid":{"rendered":"http:\/\/gcloudvn.wam.vn\/tiet-kiem-chi-phi-bang-cach-thiet-lap-lich-tu-dong-bat-tat-may-chu-compute-engine\/"},"modified":"2023-05-15T13:58:30","modified_gmt":"2023-05-15T06:58:30","slug":"tiet-kiem-chi-phi-bang-cach-thiet-lap-lich-tu-dong-bat-tat-may-chu-compute-engine","status":"publish","type":"post","link":"https:\/\/gcloudvn.com\/en\/kienthuc\/google-cloud-platform\/tiet-kiem-chi-phi-bang-cach-thiet-lap-lich-tu-dong-bat-tat-may-chu-compute-engine\/","title":{"rendered":"Save costs by setting up a schedule to automatically turn on\/off the Compute Engine server"},"content":{"rendered":"

A key feature of virtual servers (VMs) in the cloud is that you only pay for the resources you use. On Google Cloud Platform<\/span>\u00a0(GCP), <\/span>Compute Engine<\/span><\/span><\/a> VMs are billed every second. The service system usually operates 24\/7; However, there are still some cases where VMs, like for service development or testing environments, are usually only used during business hours. It's pointless to keep running these types of servers all night or on weekends, so you can turn off the service to save money. But manually stopping and starting large clusters of VMs on a daily basis can easily lead to mistakes and be difficult to control throughout the organization.<\/span><\/p>\n

Cloud Scheduler, helps schedule the above jobs GCP<\/a>, provides a simple solution to automatically stop or start VMs. With Cloud Scheduler deployment with Cloud Pub\/Sub to enable Cloud Functions on a schedule, you can also enable or disable<\/span> VM clusters are marked via labels <\/span>(created in Compute Engine).<\/span><\/p>\n

In the image below you can see the schedules (examples) to stop all VMs labeled \u201cdev\u201d at 5pm and restart at 9am, while those labeled \u201cprod\u201d ' is not affected.<\/span><\/p>\n

\"Save<\/p>\n

Using this setup allows great flexibility, you can assign different schedules to different VM clusters by creating multiple Cloud Schedulers.<\/span><\/p>\n

At the same time, it helps you have more control over Compute Engine VMs, because functions on GCP all use service accounts. <\/span>\u0111\u1ec3 d\u1eebng ho\u1eb7c kh\u1edfi \u0111\u1ed9ng c\u00e1c m\u00e1y ch\u1ee7 VM Compute Engine. S\u1eed d\u1ee5ng Cloud Identity and Access Management (IAM)<\/span>, you can follow the principle of least rights<\/span>\u00a0and limit the permissions to the most necessary for this service account.<\/span><\/p>\n

When scheduling a system shutdown, VMs will execute shutdown scripts <\/span>to ensure they are functioning properly. Any attached drives that disable auto-erase<\/span>\u00a0will still retain the data and may be available as soon as the VM reboots. Last but not least, if someone needs to deploy or test VMs unexpectedly, you can simply remove the label from that VM temporarily or simply restart the VM if it has been disabled.<\/span><\/p>\n

To see an example of a deployment design, you can see more about Scheduling compute instances with Cloud Scheduler.<\/span><\/p>\n

To learn more about what you can do with Cloud Scheduler, see Reliable task scheduling on Compute Engine with Cloud Scheduler.<\/span><\/p>\n

If your business needs advice on information related to Google Cloud services. <\/span>\u00a0Contact now:<\/span><\/p>\n