diff --git a/backend_service_custom_metrics/backing_file.tf b/backend_service_custom_metrics/backing_file.tf new file mode 100644 index 00000000..c60b1199 --- /dev/null +++ b/backend_service_custom_metrics/backing_file.tf @@ -0,0 +1,15 @@ +# This file has some scaffolding to make sure that names are unique and that +# a region and zone are selected when you try to create your Terraform resources. + +locals { + name_suffix = "${random_pet.suffix.id}" +} + +resource "random_pet" "suffix" { + length = 2 +} + +provider "google" { + region = "us-central1" + zone = "us-central1-c" +} diff --git a/backend_service_custom_metrics/main.tf b/backend_service_custom_metrics/main.tf new file mode 100644 index 00000000..6e1f8134 --- /dev/null +++ b/backend_service_custom_metrics/main.tf @@ -0,0 +1,50 @@ +resource "google_compute_network" "default" { + name = "network-${local.name_suffix}" +} + +// Zonal NEG with GCE_VM_IP_PORT +resource "google_compute_network_endpoint_group" "default" { + name = "network-endpoint-${local.name_suffix}" + network = google_compute_network.default.id + default_port = "90" + zone = "us-central1-a" + network_endpoint_type = "GCE_VM_IP_PORT" +} + +resource "google_compute_backend_service" "default" { + name = "backend-service-${local.name_suffix}" + health_checks = [google_compute_health_check.default.id] + + # WEIGHTED_ROUND_ROBIN and CUSTOM_METRICS require EXTERNAL_MANAGED. + load_balancing_scheme = "EXTERNAL_MANAGED" + locality_lb_policy = "WEIGHTED_ROUND_ROBIN" + custom_metrics { + name = "orca.application_utilization" + # At least one metric should be not dry_run. + dry_run = false + } + backend { + group = google_compute_network_endpoint_group.default.id + balancing_mode = "CUSTOM_METRICS" + custom_metrics { + name = "orca.cpu_utilization" + max_utilization = 0.9 + dry_run = true + } + custom_metrics { + name = "orca.named_metrics.foo" + # At least one metric should be not dry_run. + dry_run = false + } + } +} + +resource "google_compute_health_check" "default" { + name = "health-check-${local.name_suffix}" + timeout_sec = 1 + check_interval_sec = 1 + + tcp_health_check { + port = "80" + } +} diff --git a/backend_service_custom_metrics/motd b/backend_service_custom_metrics/motd new file mode 100644 index 00000000..45a906e8 --- /dev/null +++ b/backend_service_custom_metrics/motd @@ -0,0 +1,7 @@ +=== + +These examples use real resources that will be billed to the +Google Cloud Platform project you use - so make sure that you +run "terraform destroy" before quitting! + +=== diff --git a/backend_service_custom_metrics/tutorial.md b/backend_service_custom_metrics/tutorial.md new file mode 100644 index 00000000..edbd381a --- /dev/null +++ b/backend_service_custom_metrics/tutorial.md @@ -0,0 +1,79 @@ +# Backend Service Custom Metrics - Terraform + +## Setup + + + +Welcome to Terraform in Google Cloud Shell! We need you to let us know what project you'd like to use with Terraform. + + + +Terraform provisions real GCP resources, so anything you create in this session will be billed against this project. + +## Terraforming! + +Let's use {{project-id}} with Terraform! Click the Cloud Shell icon below to copy the command +to your shell, and then run it from the shell by pressing Enter/Return. Terraform will pick up +the project name from the environment variable. + +```bash +export GOOGLE_CLOUD_PROJECT={{project-id}} +``` + +After that, let's get Terraform started. Run the following to pull in the providers. + +```bash +terraform init +``` + +With the providers downloaded and a project set, you're ready to use Terraform. Go ahead! + +```bash +terraform apply +``` + +Terraform will show you what it plans to do, and prompt you to accept. Type "yes" to accept the plan. + +```bash +yes +``` + + +## Post-Apply + +### Editing your config + +Now you've provisioned your resources in GCP! If you run a "plan", you should see no changes needed. + +```bash +terraform plan +``` + +So let's make a change! Try editing a number, or appending a value to the name in the editor. Then, +run a 'plan' again. + +```bash +terraform plan +``` + +Afterwards you can run an apply, which implicitly does a plan and shows you the intended changes +at the 'yes' prompt. + +```bash +terraform apply +``` + +```bash +yes +``` + +## Cleanup + +Run the following to remove the resources Terraform provisioned: + +```bash +terraform destroy +``` +```bash +yes +``` diff --git a/region_backend_service_ilb_custom_metrics/backing_file.tf b/region_backend_service_ilb_custom_metrics/backing_file.tf new file mode 100644 index 00000000..c60b1199 --- /dev/null +++ b/region_backend_service_ilb_custom_metrics/backing_file.tf @@ -0,0 +1,15 @@ +# This file has some scaffolding to make sure that names are unique and that +# a region and zone are selected when you try to create your Terraform resources. + +locals { + name_suffix = "${random_pet.suffix.id}" +} + +resource "random_pet" "suffix" { + length = 2 +} + +provider "google" { + region = "us-central1" + zone = "us-central1-c" +} diff --git a/region_backend_service_ilb_custom_metrics/main.tf b/region_backend_service_ilb_custom_metrics/main.tf new file mode 100644 index 00000000..7b16b239 --- /dev/null +++ b/region_backend_service_ilb_custom_metrics/main.tf @@ -0,0 +1,46 @@ +resource "google_compute_network" "default" { + name = "network-${local.name_suffix}" +} + +// Zonal NEG with GCE_VM_IP_PORT +resource "google_compute_network_endpoint_group" "default" { + name = "network-endpoint-${local.name_suffix}" + network = google_compute_network.default.id + default_port = "90" + zone = "us-central1-a" + network_endpoint_type = "GCE_VM_IP_PORT" +} + +resource "google_compute_region_backend_service" "default" { + region = "us-central1" + name = "region-service-${local.name_suffix}" + health_checks = [google_compute_health_check.health_check.id] + load_balancing_scheme = "INTERNAL_MANAGED" + locality_lb_policy = "WEIGHTED_ROUND_ROBIN" + custom_metrics { + name = "orca.application_utilization" + # At least one metric should be not dry_run. + dry_run = false + } + backend { + group = google_compute_network_endpoint_group.default.id + balancing_mode = "CUSTOM_METRICS" + custom_metrics { + name = "orca.cpu_utilization" + max_utilization = 0.9 + dry_run = true + } + custom_metrics { + name = "orca.named_metrics.foo" + # At least one metric should be not dry_run. + dry_run = false + } + } +} + +resource "google_compute_health_check" "health_check" { + name = "rbs-health-check-${local.name_suffix}" + http_health_check { + port = 80 + } +} diff --git a/region_backend_service_ilb_custom_metrics/motd b/region_backend_service_ilb_custom_metrics/motd new file mode 100644 index 00000000..45a906e8 --- /dev/null +++ b/region_backend_service_ilb_custom_metrics/motd @@ -0,0 +1,7 @@ +=== + +These examples use real resources that will be billed to the +Google Cloud Platform project you use - so make sure that you +run "terraform destroy" before quitting! + +=== diff --git a/region_backend_service_ilb_custom_metrics/tutorial.md b/region_backend_service_ilb_custom_metrics/tutorial.md new file mode 100644 index 00000000..2422cb00 --- /dev/null +++ b/region_backend_service_ilb_custom_metrics/tutorial.md @@ -0,0 +1,79 @@ +# Region Backend Service Ilb Custom Metrics - Terraform + +## Setup + + + +Welcome to Terraform in Google Cloud Shell! We need you to let us know what project you'd like to use with Terraform. + + + +Terraform provisions real GCP resources, so anything you create in this session will be billed against this project. + +## Terraforming! + +Let's use {{project-id}} with Terraform! Click the Cloud Shell icon below to copy the command +to your shell, and then run it from the shell by pressing Enter/Return. Terraform will pick up +the project name from the environment variable. + +```bash +export GOOGLE_CLOUD_PROJECT={{project-id}} +``` + +After that, let's get Terraform started. Run the following to pull in the providers. + +```bash +terraform init +``` + +With the providers downloaded and a project set, you're ready to use Terraform. Go ahead! + +```bash +terraform apply +``` + +Terraform will show you what it plans to do, and prompt you to accept. Type "yes" to accept the plan. + +```bash +yes +``` + + +## Post-Apply + +### Editing your config + +Now you've provisioned your resources in GCP! If you run a "plan", you should see no changes needed. + +```bash +terraform plan +``` + +So let's make a change! Try editing a number, or appending a value to the name in the editor. Then, +run a 'plan' again. + +```bash +terraform plan +``` + +Afterwards you can run an apply, which implicitly does a plan and shows you the intended changes +at the 'yes' prompt. + +```bash +terraform apply +``` + +```bash +yes +``` + +## Cleanup + +Run the following to remove the resources Terraform provisioned: + +```bash +terraform destroy +``` +```bash +yes +```