일 | 월 | 화 | 수 | 목 | 금 | 토 |
---|---|---|---|---|---|---|
1 | ||||||
2 | 3 | 4 | 5 | 6 | 7 | 8 |
9 | 10 | 11 | 12 | 13 | 14 | 15 |
16 | 17 | 18 | 19 | 20 | 21 | 22 |
23 | 24 | 25 | 26 | 27 | 28 |
- influxdb 설치
- grafana dashboard
- CentOS7
- c3 second
- python popen
- python subprocess
- c3 초
- linux시간으로 변경
- c3 축 가리기
- snmp
- semanage
- 정규식 컴파일
- gcc regex
- regex_search
- centos pyhon 설치
- 1697
- c3 축 없애기
- 정규식 활용
- python os
- telegraf
- c3 step graph
- snmp test
- selinux port 등록
- c++ 정규식
- gcc 업데이트
- 백준
- subporcess path
- InfluxDB
- 정규식 문자열 출력
- g++ 업데이트
- Today
- Total
리셋 되지 말자
[Terraform] NCP - Terraform을 활용한 네이버 클라우드 플랫폼 인프라 구성하기 본문
데모 출처
blog.naver.com/n_cloudplatform/221500682259
[이렇게 사용하세요!] Terraform을 활용한 네이버 클라우드 플랫폼 인프라 구성하기
안녕하세요,네이버 클라우드 플랫폼입니다.Terraform Provider로 네이버 클라우드 플랫폼이 정식 등록...
blog.naver.com
위의 블로그의 Terraform 예제를 업데이트된 Terraform 버젼에서 수행하는 것을 목표로 함. (뭘 하는건지 위 사이트 살펴본 뒤에 아래로 넘어가는걸 추천) - 요약 하자면 두개의 서버를 하나의 로드밸런스로 묶은 인프라를 테라폼으로 생성하는것.
버전이 바뀌면서 새로운 문법이나 변수명을 사용해야해서 테스트 진행했음.
테라폼 버전
$ terraform version
Terraform v0.14.8
Your version of Terraform is out of date! The latest version
is 0.14.9. You can update by downloading from https://www.terraform.io/downloads.html
쓴이의 현재 terraform 버전. 그세 또 새로운 버전 나왔네 ㅋㅋ
설치 및 key 등록
not-to-be-reset.tistory.com/369?category=922790
[NCP] Terraform으로 서버 생성하기
NCP를 사용하는 이유 AWS는 프리티어 기간이 끝났다. => 유료다 NCP는 아직 프리티어 기간이다 => 무료다 사전 준비 사항 1. 당연히 NCP에 가입된 아이디가 있어야 한다. 2. Terraform 0.13 이상 버전 설치 -
not-to-be-reset.tistory.com
위 게시물을 참고하여 진행하시면 됩니다.
테라폼 파일 작성
$ ls
main.tf outputs.tf user-data.sh variables.tf versions.tf
위 파일들을 작성
- main.tf
$ cat main.tf
provider "ncloud" {
access_key = var.access_key
secret_key = var.secret_key
region = var.region
}
# keypair create
#resource "ncloud_login_key" "loginkey"{
# key_name = "webinar"
#}
data "template_file" "user_data" {
template = templatefile("user-data.sh", {})
}
#server create
resource "ncloud_server" "server" {
count = "2"
#name = "tf-vm-${count.index+1}"
name = format("tf-vm-%s", count.index+1)
server_image_product_code = var.server_image_product_code
server_product_code = var.server_product_code
login_key_name = "kkj-ncp"
access_control_group_configuration_no_list = ["203098"]
zone = var.ncloud_zones[count.index]
user_data = data.template_file.user_data.rendered
}
# LB create
resource "ncloud_load_balancer" "lb" {
name = "my_lb"
# 라운드 로빈 방식 사용
algorithm_type = "RR"
description = "my_lb_description"
rule_list {
protocol_type = "HTTP"
load_balancer_port = 80
server_port = 80
l7_health_check_path = "/"
}
server_instance_no_list = [ncloud_server.server.*.id[0], ncloud_server.server.*.id[1]]
internet_line_type = "PUBLC"
network_usage_type = "PBLIP"
region = "KR"
}
1. 새로운 키페어를 생생하려면 위의 #keypair create 항목의 주석을 해제하고, #server create의 login_key_name에 새롭게 생성할 키페어의 이름을 넣어주면 된다.
그게 아니고 쓴이처럼 기존의 키페어를 사용하려면 주석처리를 하고, NCP에서 미리 생성한 키페어의 이름을 넣어주면 된다.
키페어 생성은 NCP console에서 직접 해주면 된다. (구글링 해주세욜)
2. 위의 #server create 항목에서, access_control_group_configuration_no_list에 있는 "203098"은 아래 그림에서 처럼 직접 확인해야 한다. 즉, 미리 ACG가 생성되어 있어야 함
기본으로 생성되어 있는 ACG였는데, ICMP 규칙이 빠져있어서 추가해주었다. ICMP가 없으면 Load Balancer가 헬스체크를 하지 못해서 생성되지 않더라...
- outputs.tf
$ cat outputs.tf
output "server_name_list" {
value = join(",", ncloud_server.server.*.name)
}
그저 어떤 이름을 가진 서버가 생성되었는지 출력해주는 tf 파일. plan 및 apply 명령어 최 하단에 출력됨.
- user-data.sh
$ cat user-data.sh
#!bin/bash
yum install -y httpd
apachectl start
echo "NCP SERVER-$HOSTNAME" > /var/www/html/index.html
생성될 서버에 접속하면, 어떤 서버에 접속한건지 확인할 수 있도록 작성되는 스크립트 파일이다.
(httpd 설치, httpd 시작, index.html을 "NCP SERVER-서버의 호스트 네임"으로 대체)
- variables.tf
$ cat variables.tf
variable "access_key" { # export TF_VAR_access_key=...
}
variable "secret_key" { # export TF_VAR_secret_key=...
}
variable "ncloud_zones" {
default = ["KR-1", "KR-2"]
}
variable "region" {
default = "KR"
}
variable "server_name" {
default = "terraform-test"
}
variable "server_image_product_code" {
default = "SPSW0LINUX000046"
}
variable "server_product_code" {
default = "SPSVRSSD00000002" #SPSVRSTAND000056
}
사용한 server image는 centos-7.3-64이고 서버 스펙은 [Compact] 2vCPU, 2GB Mem [g1] 이다.
- versions.tf
$ cat versions.tf
terraform {
required_version = ">= 0.13"
required_providers {
ncloud = {
source = "navercloudplatform/ncloud"
}
}
}
테라폼 init
$ terraform init
Initializing the backend...
Initializing provider plugins...
- Finding latest version of hashicorp/template...
- Finding latest version of navercloudplatform/ncloud...
- Installing hashicorp/template v2.2.0...
- Installed hashicorp/template v2.2.0 (signed by HashiCorp)
- Installing navercloudplatform/ncloud v2.0.5...
- Installed navercloudplatform/ncloud v2.0.5 (self-signed, key ID 9DCE24305722E9C9)
Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html
Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.
Terraform has been successfully initialized!
You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.
If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
테라폼 plan
$ terraform plan
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
+ create
Terraform will perform the following actions:
# ncloud_load_balancer.lb will be created
+ resource "ncloud_load_balancer" "lb" {
+ algorithm_type = "RR"
+ certificate_name = (known after apply)
+ connection_timeout = (known after apply)
+ description = "my_lb_description"
+ domain_name = (known after apply)
+ id = (known after apply)
+ instance_no = (known after apply)
+ instance_operation = (known after apply)
+ instance_status = (known after apply)
+ instance_status_name = (known after apply)
+ internet_line_type = "PUBLC"
+ is_http_keep_alive = (known after apply)
+ load_balanced_server_instance_list = (known after apply)
+ name = "my_lb"
+ network_usage_type = "PBLIP"
+ region = "KR"
+ server_instance_no_list = (known after apply)
+ virtual_ip = (known after apply)
+ rule_list {
+ l7_health_check_path = "/"
+ load_balancer_port = 80
+ protocol_type = "HTTP"
+ proxy_protocol_use_yn = "N"
+ server_port = 80
}
}
# ncloud_server.server[0] will be created
+ resource "ncloud_server" "server" {
+ access_control_group_configuration_no_list = [
+ "203098",
]
+ base_block_storage_disk_detail_type = (known after apply)
+ base_block_storage_disk_type = (known after apply)
+ base_block_storage_size = (known after apply)
+ cpu_count = (known after apply)
+ description = (known after apply)
+ id = (known after apply)
+ init_script_no = (known after apply)
+ instance_no = (known after apply)
+ internet_line_type = (known after apply)
+ is_encrypted_base_block_storage_volume = (known after apply)
+ is_fee_charging_monitoring = (known after apply)
+ is_protect_server_termination = (known after apply)
+ login_key_name = "kkj-ncp"
+ memory_size = (known after apply)
+ name = "tf-vm-1"
+ placement_group_no = (known after apply)
+ platform_type = (known after apply)
+ port_forwarding_external_port = (known after apply)
+ port_forwarding_internal_port = (known after apply)
+ port_forwarding_public_ip = (known after apply)
+ private_ip = (known after apply)
+ public_ip = (known after apply)
+ region = (known after apply)
+ server_image_name = (known after apply)
+ server_image_product_code = "SPSW0LINUX000046"
+ server_product_code = "SPSVRSSD00000002"
+ subnet_no = (known after apply)
+ user_data = <<-EOT
#!bin/bash
yum install -y httpd
apachectl start
echo "NCP SERVER-$HOSTNAME" > /var/www/html/index.html
EOT
+ vpc_no = (known after apply)
+ zone = "KR-1"
+ network_interface {
+ network_interface_no = (known after apply)
+ order = (known after apply)
+ private_ip = (known after apply)
+ subnet_no = (known after apply)
}
}
# ncloud_server.server[1] will be created
+ resource "ncloud_server" "server" {
+ access_control_group_configuration_no_list = [
+ "203098",
]
+ base_block_storage_disk_detail_type = (known after apply)
+ base_block_storage_disk_type = (known after apply)
+ base_block_storage_size = (known after apply)
+ cpu_count = (known after apply)
+ description = (known after apply)
+ id = (known after apply)
+ init_script_no = (known after apply)
+ instance_no = (known after apply)
+ internet_line_type = (known after apply)
+ is_encrypted_base_block_storage_volume = (known after apply)
+ is_fee_charging_monitoring = (known after apply)
+ is_protect_server_termination = (known after apply)
+ login_key_name = "kkj-ncp"
+ memory_size = (known after apply)
+ name = "tf-vm-2"
+ placement_group_no = (known after apply)
+ platform_type = (known after apply)
+ port_forwarding_external_port = (known after apply)
+ port_forwarding_internal_port = (known after apply)
+ port_forwarding_public_ip = (known after apply)
+ private_ip = (known after apply)
+ public_ip = (known after apply)
+ region = (known after apply)
+ server_image_name = (known after apply)
+ server_image_product_code = "SPSW0LINUX000046"
+ server_product_code = "SPSVRSSD00000002"
+ subnet_no = (known after apply)
+ user_data = <<-EOT
#!bin/bash
yum install -y httpd
apachectl start
echo "NCP SERVER-$HOSTNAME" > /var/www/html/index.html
EOT
+ vpc_no = (known after apply)
+ zone = "KR-2"
+ network_interface {
+ network_interface_no = (known after apply)
+ order = (known after apply)
+ private_ip = (known after apply)
+ subnet_no = (known after apply)
}
}
Plan: 3 to add, 0 to change, 0 to destroy.
Changes to Outputs:
+ server_name_list = "tf-vm-1,tf-vm-2"
------------------------------------------------------------------------
Note: You didn't specify an "-out" parameter to save this plan, so Terraform
can't guarantee that exactly these actions will be performed if
"terraform apply" is subsequently run.
3 to add : 3개가 추가된다고 뜨면 됨(2개의 서버, 1개의 로드밸런서)
테라폼 apply
$ terraform apply
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
+ create
Terraform will perform the following actions:
# ncloud_load_balancer.lb will be created
+ resource "ncloud_load_balancer" "lb" {
+ algorithm_type = "RR"
+ certificate_name = (known after apply)
+ connection_timeout = (known after apply)
+ description = "my_lb_description"
+ domain_name = (known after apply)
+ id = (known after apply)
+ instance_no = (known after apply)
+ instance_operation = (known after apply)
+ instance_status = (known after apply)
+ instance_status_name = (known after apply)
+ internet_line_type = "PUBLC"
+ is_http_keep_alive = (known after apply)
+ load_balanced_server_instance_list = (known after apply)
+ name = "my_lb"
+ network_usage_type = "PBLIP"
+ region = "KR"
+ server_instance_no_list = (known after apply)
+ virtual_ip = (known after apply)
+ rule_list {
+ l7_health_check_path = "/"
+ load_balancer_port = 80
+ protocol_type = "HTTP"
+ proxy_protocol_use_yn = "N"
+ server_port = 80
}
}
# ncloud_server.server[0] will be created
+ resource "ncloud_server" "server" {
+ access_control_group_configuration_no_list = [
+ "203098",
]
+ base_block_storage_disk_detail_type = (known after apply)
+ base_block_storage_disk_type = (known after apply)
+ base_block_storage_size = (known after apply)
+ cpu_count = (known after apply)
+ description = (known after apply)
+ id = (known after apply)
+ init_script_no = (known after apply)
+ instance_no = (known after apply)
+ internet_line_type = (known after apply)
+ is_encrypted_base_block_storage_volume = (known after apply)
+ is_fee_charging_monitoring = (known after apply)
+ is_protect_server_termination = (known after apply)
+ login_key_name = "kkj-ncp"
+ memory_size = (known after apply)
+ name = "tf-vm-1"
+ placement_group_no = (known after apply)
+ platform_type = (known after apply)
+ port_forwarding_external_port = (known after apply)
+ port_forwarding_internal_port = (known after apply)
+ port_forwarding_public_ip = (known after apply)
+ private_ip = (known after apply)
+ public_ip = (known after apply)
+ region = (known after apply)
+ server_image_name = (known after apply)
+ server_image_product_code = "SPSW0LINUX000046"
+ server_product_code = "SPSVRSSD00000002"
+ subnet_no = (known after apply)
+ user_data = <<-EOT
#!bin/bash
yum install -y httpd
apachectl start
echo "NCP SERVER-$HOSTNAME" > /var/www/html/index.html
EOT
+ vpc_no = (known after apply)
+ zone = "KR-1"
+ network_interface {
+ network_interface_no = (known after apply)
+ order = (known after apply)
+ private_ip = (known after apply)
+ subnet_no = (known after apply)
}
}
# ncloud_server.server[1] will be created
+ resource "ncloud_server" "server" {
+ access_control_group_configuration_no_list = [
+ "203098",
]
+ base_block_storage_disk_detail_type = (known after apply)
+ base_block_storage_disk_type = (known after apply)
+ base_block_storage_size = (known after apply)
+ cpu_count = (known after apply)
+ description = (known after apply)
+ id = (known after apply)
+ init_script_no = (known after apply)
+ instance_no = (known after apply)
+ internet_line_type = (known after apply)
+ is_encrypted_base_block_storage_volume = (known after apply)
+ is_fee_charging_monitoring = (known after apply)
+ is_protect_server_termination = (known after apply)
+ login_key_name = "kkj-ncp"
+ memory_size = (known after apply)
+ name = "tf-vm-2"
+ placement_group_no = (known after apply)
+ platform_type = (known after apply)
+ port_forwarding_external_port = (known after apply)
+ port_forwarding_internal_port = (known after apply)
+ port_forwarding_public_ip = (known after apply)
+ private_ip = (known after apply)
+ public_ip = (known after apply)
+ region = (known after apply)
+ server_image_name = (known after apply)
+ server_image_product_code = "SPSW0LINUX000046"
+ server_product_code = "SPSVRSSD00000002"
+ subnet_no = (known after apply)
+ user_data = <<-EOT
#!bin/bash
yum install -y httpd
apachectl start
echo "NCP SERVER-$HOSTNAME" > /var/www/html/index.html
EOT
+ vpc_no = (known after apply)
+ zone = "KR-2"
+ network_interface {
+ network_interface_no = (known after apply)
+ order = (known after apply)
+ private_ip = (known after apply)
+ subnet_no = (known after apply)
}
}
Plan: 3 to add, 0 to change, 0 to destroy.
Changes to Outputs:
+ server_name_list = "tf-vm-1,tf-vm-2"
Do you want to perform these actions?
Terraform will perform the actions described above.
Only 'yes' will be accepted to approve.
Enter a value: yes
ncloud_server.server[1]: Creating...
ncloud_server.server[0]: Creating...
ncloud_server.server[1]: Still creating... [10s elapsed]
ncloud_server.server[0]: Still creating... [10s elapsed]
ncloud_server.server[0]: Still creating... [20s elapsed]
ncloud_server.server[1]: Still creating... [20s elapsed]
ncloud_server.server[0]: Still creating... [30s elapsed]
ncloud_server.server[1]: Still creating... [30s elapsed]
ncloud_server.server[0]: Still creating... [40s elapsed]
ncloud_server.server[1]: Still creating... [40s elapsed]
ncloud_server.server[0]: Still creating... [50s elapsed]
ncloud_server.server[1]: Still creating... [50s elapsed]
ncloud_server.server[1]: Still creating... [1m0s elapsed]
ncloud_server.server[0]: Still creating... [1m0s elapsed]
ncloud_server.server[1]: Still creating... [1m10s elapsed]
ncloud_server.server[0]: Still creating... [1m10s elapsed]
ncloud_server.server[1]: Still creating... [1m20s elapsed]
ncloud_server.server[0]: Still creating... [1m20s elapsed]
ncloud_server.server[1]: Still creating... [1m30s elapsed]
ncloud_server.server[0]: Still creating... [1m30s elapsed]
ncloud_server.server[0]: Still creating... [1m40s elapsed]
ncloud_server.server[1]: Still creating... [1m40s elapsed]
ncloud_server.server[1]: Still creating... [1m50s elapsed]
ncloud_server.server[0]: Still creating... [1m50s elapsed]
ncloud_server.server[1]: Still creating... [2m0s elapsed]
ncloud_server.server[0]: Still creating... [2m0s elapsed]
ncloud_server.server[0]: Still creating... [2m10s elapsed]
ncloud_server.server[1]: Still creating... [2m10s elapsed]
ncloud_server.server[0]: Still creating... [2m20s elapsed]
ncloud_server.server[1]: Still creating... [2m20s elapsed]
ncloud_server.server[0]: Still creating... [2m30s elapsed]
ncloud_server.server[1]: Still creating... [2m30s elapsed]
ncloud_server.server[1]: Still creating... [2m40s elapsed]
ncloud_server.server[0]: Still creating... [2m40s elapsed]
ncloud_server.server[1]: Still creating... [2m50s elapsed]
ncloud_server.server[0]: Still creating... [2m50s elapsed]
ncloud_server.server[1]: Still creating... [3m0s elapsed]
ncloud_server.server[0]: Still creating... [3m0s elapsed]
ncloud_server.server[0]: Still creating... [3m10s elapsed]
ncloud_server.server[1]: Still creating... [3m10s elapsed]
ncloud_server.server[1]: Still creating... [3m20s elapsed]
ncloud_server.server[0]: Still creating... [3m20s elapsed]
ncloud_server.server[1]: Still creating... [3m30s elapsed]
ncloud_server.server[0]: Still creating... [3m30s elapsed]
ncloud_server.server[0]: Still creating... [3m40s elapsed]
ncloud_server.server[1]: Still creating... [3m40s elapsed]
ncloud_server.server[1]: Still creating... [3m50s elapsed]
ncloud_server.server[0]: Still creating... [3m50s elapsed]
ncloud_server.server[1]: Creation complete after 3m54s [id=6313549]
ncloud_server.server[0]: Still creating... [4m0s elapsed]
ncloud_server.server[0]: Creation complete after 4m5s [id=6313547]
ncloud_load_balancer.lb: Creating...
ncloud_load_balancer.lb: Still creating... [10s elapsed]
ncloud_load_balancer.lb: Still creating... [20s elapsed]
ncloud_load_balancer.lb: Still creating... [30s elapsed]
ncloud_load_balancer.lb: Creation complete after 36s [id=6313560]
Apply complete! Resources: 3 added, 0 changed, 0 destroyed.
Outputs:
server_name_list = "tf-vm-1,tf-vm-2"
결과 확인
- server 생성 확인
2개의 centos 서버가 생성된 것을 확인할 수 있다.
- Load Balancer 생성 확인
로드 밸런서의 접속 정보에 있는 도메인 주소로 접속해보면, 접속할 때마다 두 대의 server에 번갈아 가면서 접속되는것을 확인할 수 있다.
이는 user-data.sh 에서 설정해준 "NCP SERVER-$HOSTNAME"이 출력되는 것이다.
테라폼 detroy
$ terraform destroy
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
- destroy
Terraform will perform the following actions:
# ncloud_load_balancer.lb will be destroyed
- resource "ncloud_load_balancer" "lb" {
- algorithm_type = "RR" -> null
- connection_timeout = 60 -> null
- description = "my_lb_description" -> null
- domain_name = "slb-6313560.ncloudslb.com" -> null
- id = "6313560" -> null
- instance_operation = "NULL" -> null
- instance_status = "USED" -> null
- instance_status_name = "used" -> null
- internet_line_type = "PUBLC" -> null
- is_http_keep_alive = false -> null
- load_balanced_server_instance_list = [
- "6313549",
- "6313547",
] -> null
- name = "my_lb" -> null
- network_usage_type = "PBLIP" -> null
- region = "KR" -> null
- server_instance_no_list = [
- "6313547",
- "6313549",
] -> null
- virtual_ip = "211.249.55.148,211.249.55.95" -> null
- rule_list {
- l7_health_check_path = "/" -> null
- load_balancer_port = 80 -> null
- protocol_type = "HTTP" -> null
- proxy_protocol_use_yn = "N" -> null
- server_port = 80 -> null
}
}
# ncloud_server.server[0] will be destroyed
- resource "ncloud_server" "server" {
- access_control_group_configuration_no_list = [
- "203098",
] -> null
- base_block_storage_disk_detail_type = "SSD" -> null
- base_block_storage_disk_type = "NET" -> null
- base_block_storage_size = 53687091200 -> null
- cpu_count = 2 -> null
- id = "6313547" -> null
- instance_no = "6313547" -> null
- internet_line_type = "PUBLC" -> null
- is_fee_charging_monitoring = false -> null
- is_protect_server_termination = false -> null
- login_key_name = "kkj-ncp" -> null
- memory_size = 2147483648 -> null
- name = "tf-vm-1" -> null
- platform_type = "LNX64" -> null
- port_forwarding_public_ip = "220.230.116.195" -> null
- private_ip = "10.33.133.158" -> null
- server_image_name = "centos-7.3-64" -> null
- server_image_product_code = "SPSW0LINUX000046" -> null
- server_product_code = "SPSVRSSD00000002" -> null
- user_data = <<-EOT
#!bin/bash
yum install -y httpd
apachectl start
echo "NCP SERVER-$HOSTNAME" > /var/www/html/index.html
EOT -> null
- zone = "KR-1" -> null
}
# ncloud_server.server[1] will be destroyed
- resource "ncloud_server" "server" {
- access_control_group_configuration_no_list = [
- "203098",
] -> null
- base_block_storage_disk_detail_type = "SSD" -> null
- base_block_storage_disk_type = "NET" -> null
- base_block_storage_size = 53687091200 -> null
- cpu_count = 2 -> null
- id = "6313549" -> null
- instance_no = "6313549" -> null
- internet_line_type = "PUBLC" -> null
- is_fee_charging_monitoring = false -> null
- is_protect_server_termination = false -> null
- login_key_name = "kkj-ncp" -> null
- memory_size = 2147483648 -> null
- name = "tf-vm-2" -> null
- platform_type = "LNX64" -> null
- port_forwarding_public_ip = "101.101.167.158" -> null
- private_ip = "10.41.7.147" -> null
- server_image_name = "centos-7.3-64" -> null
- server_image_product_code = "SPSW0LINUX000046" -> null
- server_product_code = "SPSVRSSD00000002" -> null
- user_data = <<-EOT
#!bin/bash
yum install -y httpd
apachectl start
echo "NCP SERVER-$HOSTNAME" > /var/www/html/index.html
EOT -> null
- zone = "KR-2" -> null
}
Plan: 0 to add, 0 to change, 3 to destroy.
Changes to Outputs:
- server_name_list = "tf-vm-1,tf-vm-2" -> null
Do you really want to destroy all resources?
Terraform will destroy all your managed infrastructure, as shown above.
There is no undo. Only 'yes' will be accepted to confirm.
Enter a value: yes
ncloud_load_balancer.lb: Destroying... [id=6313560]
ncloud_load_balancer.lb: Destruction complete after 3s
ncloud_server.server[0]: Destroying... [id=6313547]
ncloud_server.server[1]: Destroying... [id=6313549]
ncloud_server.server[1]: Still destroying... [id=6313549, 10s elapsed]
ncloud_server.server[0]: Still destroying... [id=6313547, 10s elapsed]
ncloud_server.server[1]: Still destroying... [id=6313549, 20s elapsed]
ncloud_server.server[0]: Still destroying... [id=6313547, 20s elapsed]
ncloud_server.server[0]: Destruction complete after 22s
ncloud_server.server[1]: Destruction complete after 28s
Destroy complete! Resources: 3 destroyed.
요금이 많이 나가지 않도록 테스트 진행 후에는 반드시 다 제거해 줍시다.
잘 삭제되었는지 NCP 콘솔에서도 확인 필수!
고생하셨습니다~
'Infra' 카테고리의 다른 글
[Terraform] AWS - EC2 Keypair RDS 생성 테스트 (0) | 2021.06.07 |
---|---|
[Ansible] Ubuntu Ansible 설치 (0) | 2021.04.07 |
[Terraform] NCP - server(VM 스펙) 정보 출력 (0) | 2021.03.18 |
[Terraform] NCP - server(VM 스펙) 정보 출력 (1) | 2021.03.18 |
[Terraform] NCP - Terraform 이미지 정보 (0) | 2021.03.18 |