Update image and spec managed by tb (fix #958) #1111
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -60,64 +60,81 @@ AZURE,azure-uaecentral,Canonical:UbuntuServer:18.04-LTS:18.04.202106220,Ubuntu 1 | |
| AZURE,azure-norwaywest,Canonical:UbuntuServer:18.04-LTS:18.04.202106220,Ubuntu 18.04 | ||
| AZURE,azure-francesouth,Canonical:UbuntuServer:18.04-LTS:18.04.202106220,Ubuntu 18.04 | ||
| AZURE,azure-australiacentral2,Canonical:UbuntuServer:18.04-LTS:18.04.202106220,Ubuntu 18.04 | ||
| GCP,gcp-asia-east1,https://www.googleapis.com/compute/v1/projects/gce-uefi-images/global/images/ubuntu-1804-bionic-v20200317,Ubuntu 18.04 | ||
| GCP,gcp-europe-west3,https://www.googleapis.com/compute/v1/projects/gce-uefi-images/global/images/ubuntu-1804-bionic-v20200317,Ubuntu 18.04 | ||
| GCP,gcp-asia-east2,https://www.googleapis.com/compute/v1/projects/gce-uefi-images/global/images/ubuntu-1804-bionic-v20200317,Ubuntu 18.04 | ||
| GCP,gcp-asia-northeast1,https://www.googleapis.com/compute/v1/projects/gce-uefi-images/global/images/ubuntu-1804-bionic-v20200317,Ubuntu 18.04 | ||
| GCP,gcp-asia-northeast2,https://www.googleapis.com/compute/v1/projects/gce-uefi-images/global/images/ubuntu-1804-bionic-v20200317,Ubuntu 18.04 | ||
| GCP,gcp-asia-northeast3,https://www.googleapis.com/compute/v1/projects/gce-uefi-images/global/images/ubuntu-1804-bionic-v20200317,Ubuntu 18.04 | ||
| GCP,gcp-us-west4,https://www.googleapis.com/compute/v1/projects/gce-uefi-images/global/images/ubuntu-1804-bionic-v20200317,Ubuntu 18.04 | ||
| GCP,gcp-asia-southeast1,https://www.googleapis.com/compute/v1/projects/gce-uefi-images/global/images/ubuntu-1804-bionic-v20200317,Ubuntu 18.04 | ||
| GCP,gcp-australia-southeast1,https://www.googleapis.com/compute/v1/projects/gce-uefi-images/global/images/ubuntu-1804-bionic-v20200317,Ubuntu 18.04 | ||
| GCP,gcp-europe-north1,https://www.googleapis.com/compute/v1/projects/gce-uefi-images/global/images/ubuntu-1804-bionic-v20200317,Ubuntu 18.04 | ||
| GCP,gcp-europe-west1,https://www.googleapis.com/compute/v1/projects/gce-uefi-images/global/images/ubuntu-1804-bionic-v20200317,Ubuntu 18.04 | ||
| GCP,gcp-europe-west2,https://www.googleapis.com/compute/v1/projects/gce-uefi-images/global/images/ubuntu-1804-bionic-v20200317,Ubuntu 18.04 | ||
| GCP,gcp-europe-west4,https://www.googleapis.com/compute/v1/projects/gce-uefi-images/global/images/ubuntu-1804-bionic-v20200317,Ubuntu 18.04 | ||
| GCP,gcp-europe-west6,https://www.googleapis.com/compute/v1/projects/gce-uefi-images/global/images/ubuntu-1804-bionic-v20200317,Ubuntu 18.04 | ||
| GCP,gcp-northamerica-northeast1,https://www.googleapis.com/compute/v1/projects/gce-uefi-images/global/images/ubuntu-1804-bionic-v20200317,Ubuntu 18.04 | ||
| GCP,gcp-southamerica-east1,https://www.googleapis.com/compute/v1/projects/gce-uefi-images/global/images/ubuntu-1804-bionic-v20200317,Ubuntu 18.04 | ||
| GCP,gcp-us-central1,https://www.googleapis.com/compute/v1/projects/gce-uefi-images/global/images/ubuntu-1804-bionic-v20200317,Ubuntu 18.04 | ||
| GCP,gcp-us-east1,https://www.googleapis.com/compute/v1/projects/gce-uefi-images/global/images/ubuntu-1804-bionic-v20200317,Ubuntu 18.04 | ||
| GCP,gcp-us-east4,https://www.googleapis.com/compute/v1/projects/gce-uefi-images/global/images/ubuntu-1804-bionic-v20200317,Ubuntu 18.04 | ||
| GCP,gcp-us-west1,https://www.googleapis.com/compute/v1/projects/gce-uefi-images/global/images/ubuntu-1804-bionic-v20200317,Ubuntu 18.04 | ||
| GCP,gcp-us-west2,https://www.googleapis.com/compute/v1/projects/gce-uefi-images/global/images/ubuntu-1804-bionic-v20200317,Ubuntu 18.04 | ||
| GCP,gcp-us-west3,https://www.googleapis.com/compute/v1/projects/gce-uefi-images/global/images/ubuntu-1804-bionic-v20200317,Ubuntu 18.04 | ||
| GCP,gcp-asia-south1,https://www.googleapis.com/compute/v1/projects/gce-uefi-images/global/images/ubuntu-1804-bionic-v20200317,Ubuntu 18.04 | ||
| GCP,gcp-asia-southeast2,https://www.googleapis.com/compute/v1/projects/gce-uefi-images/global/images/ubuntu-1804-bionic-v20200317,Ubuntu 18.04 | ||
| GCP,gcp-europe-central2,https://www.googleapis.com/compute/v1/projects/gce-uefi-images/global/images/ubuntu-1804-bionic-v20200317,Ubuntu 18.04 | ||
| ALIBABA,alibaba-ap-northeast-1,ubuntu_18_04_x64_20G_alibase_20220322.vhd,Ubuntu 18.04 | ||
|
There was a problem hiding this comment.
There was a problem hiding this comment. @jihoon-seo 알리바바는 리전에 따라서 제공하는 Image가 다르네요. (최신 버전에 대한 적용 시점과 예전 버전 삭제 시점이 다른 듯합니다.) |
||
| ALIBABA,alibaba-ap-south-1,ubuntu_18_04_x64_20G_alibase_20220322.vhd,Ubuntu 18.04 | ||
| ALIBABA,alibaba-ap-southeast-1,ubuntu_18_04_x64_20G_alibase_20220428.vhd,Ubuntu 18.04 | ||
| ALIBABA,alibaba-ap-southeast-2,ubuntu_18_04_x64_20G_alibase_20220322.vhd,Ubuntu 18.04 | ||
| ALIBABA,alibaba-ap-southeast-3,ubuntu_18_04_x64_20G_alibase_20220322.vhd,Ubuntu 18.04 | ||
| ALIBABA,alibaba-ap-southeast-5,ubuntu_18_04_x64_20G_alibase_20220322.vhd,Ubuntu 18.04 | ||
| ALIBABA,alibaba-us-west-1,ubuntu_18_04_x64_20G_alibase_20220322.vhd,Ubuntu 18.04 | ||
| ALIBABA,alibaba-us-east-1,ubuntu_18_04_x64_20G_alibase_20220322.vhd,Ubuntu 18.04 | ||
| ALIBABA,alibaba-eu-central-1,ubuntu_18_04_x64_20G_alibase_20220322.vhd,Ubuntu 18.04 | ||
| ALIBABA,alibaba-eu-west-1,ubuntu_18_04_x64_20G_alibase_20220322.vhd,Ubuntu 18.04 | ||
| ALIBABA,alibaba-me-east-1,ubuntu_18_04_x64_20G_alibase_20220322.vhd,Ubuntu 18.04 | ||
| ALIBABA,alibaba-cn-hongkong,ubuntu_18_04_x64_20G_alibase_20220428.vhd,Ubuntu 18.04 | ||
| ALIBABA,alibaba-cn-shanghai,ubuntu_18_04_x64_20G_alibase_20220322.vhd,Ubuntu 18.04 | ||
| ALIBABA,alibaba-cn-beijing,ubuntu_18_04_x64_20G_alibase_20220322.vhd,Ubuntu 18.04 | ||
| ALIBABA,alibaba-cn-qingdao,ubuntu_18_04_x64_20G_alibase_20220428.vhd,Ubuntu 18.04 | ||
| ALIBABA,alibaba-cn-zhangjiakou,ubuntu_18_04_x64_20G_alibase_20220322.vhd,Ubuntu 18.04 | ||
| ALIBABA,alibaba-cn-huhehaote,ubuntu_18_04_x64_20G_alibase_20220322.vhd,Ubuntu 18.04 | ||
| ALIBABA,alibaba-cn-hangzhou,ubuntu_18_04_x64_20G_alibase_20220428.vhd,Ubuntu 18.04 | ||
| ALIBABA,alibaba-cn-shenz,ubuntu_18_04_x64_20G_alibase_20220322.vhd,Ubuntu 18.04 | ||
| ALIBABA,alibaba-cn-heyuan,ubuntu_18_04_x64_20G_alibase_20220322.vhd,Ubuntu 18.04 | ||
| ALIBABA,alibaba-cn-chengdu,ubuntu_18_04_x64_20G_alibase_20220428.vhd,Ubuntu 18.04 | ||
| ALIBABA,alibaba-cn-wulanchabu,ubuntu_18_04_x64_20G_alibase_20220428.vhd,Ubuntu 18.04 | ||
| ALIBABA,alibaba-cn-guangzhou,ubuntu_18_04_x64_20G_alibase_20220322.vhd,Ubuntu 18.04 | ||
| CLOUDIT,cloudit-region01,ee441331-0872-49c3-886c-1873a6e32e09,CentOS-7 | ||
| TENCENT,tencent-ap-singapore,img-pi0ii46r,Ubuntu 18.04 | ||
| TENCENT,tencent-ap-jakarta,img-pi0ii46r,Ubuntu 18.04 | ||
| TENCENT,tencent-ap-seoul,img-pi0ii46r,Ubuntu 18.04 | ||
| TENCENT,tencent-ap-tokyo,img-pi0ii46r,Ubuntu 18.04 | ||
| TENCENT,tencent-ap-mumbai,img-pi0ii46r,Ubuntu 18.04 | ||
| TENCENT,tencent-ap-bangkok,img-pi0ii46r,Ubuntu 18.04 | ||
| TENCENT,tencent-na-toronto,img-pi0ii46r,Ubuntu 18.04 | ||
| TENCENT,tencent-na-siliconvalley,img-pi0ii46r,Ubuntu 18.04 | ||
| TENCENT,tencent-na-ashburn,img-pi0ii46r,Ubuntu 18.04 | ||
| TENCENT,tencent-eu-frankfurt,img-pi0ii46r,Ubuntu 18.04 | ||
| TENCENT,tencent-eu-moscow,img-pi0ii46r,Ubuntu 18.04 | ||
| TENCENT,tencent-ap-guangzhou,img-pi0ii46r,Ubuntu 18.04 | ||
| TENCENT,tencent-ap-shanghai,img-pi0ii46r,Ubuntu 18.04 | ||
| TENCENT,tencent-ap-nanjing,img-pi0ii46r,Ubuntu 18.04 | ||
| TENCENT,tencent-ap-beijing,img-pi0ii46r,Ubuntu 18.04 | ||
| TENCENT,tencent-ap-chengdu,img-pi0ii46r,Ubuntu 18.04 | ||
| TENCENT,tencent-ap-chongqing,img-pi0ii46r,Ubuntu 18.04 | ||
| TENCENT,tencent-ap-hongkong,img-pi0ii46r,Ubuntu 18.04 | ||
| CLOUDTWIN,cloudtwin-region01,ubuntu18.04-sshd-systemd,Ubuntu 18.04 | ||
| NCP,ncp-korea1,SPSW0LINUX000130,Ubuntu 18.04 | ||
| NCP,ncp-us-western,SPSW0LINUX000130,Ubuntu 18.04 | ||
| NCP,ncp-germany,SPSW0LINUX000130,Ubuntu 18.04 | ||
| NCP,ncp-singapore,SPSW0LINUX000130,Ubuntu 18.04 | ||
| NCP,ncp-japan,SPSW0LINUX000130,Ubuntu 18.04 | ||
| MOCK,mock-seoul,mock-vmimage-01,Ubuntu 18.04 | ||
| OPENSTACK,openstack-region01,ubuntu-18.04,Ubuntu 18.04 | ||
| MOCK,testcloud01-seoul,mock-vmimage-01,Ubuntu 18.04 | ||
| MOCK,testcloud02-canada,mock-vmimage-01,Ubuntu 18.04 | ||
| MOCK,testcloud03-frankfurt,mock-vmimage-01,Ubuntu 18.04 | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
이거는 어떨까요 😊
https://www.googleapis.com/compute/v1/projects/ubuntu-os-cloud/global/images/ubuntu-minimal-1804-bionic-v20220511
(검색 페이지: https://console.cloud.google.com/compute/images?hl=ko&pageState=(%22images%22:(%22f%22:%22%255B%257B_22k_22_3A_22_22_2C_22t_22_3A10_2C_22v_22_3A_22_5C_22ubuntu-minimal-1804_5C_22_22%257D%255D%22)))
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jihoon-seo 혹시 어떤 차이가 있는지 아시나요~? 변경하면 일단 몇 개 테스트해봐야할 것 같습니다. (spider에서도 특정 이미지로만 ssh 키 사용자 생성, 접속 여부 확인 등을 진행하고 계셔서)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
son@son:~/go/src/github.com/cloud-barista/cb-tumblebug/src/testclient/scripts/misc$ gcloud compute images list | grep ubuntu
ubuntu-1804-bionic-v20220505 ubuntu-os-cloud ubuntu-1804-lts READY
ubuntu-pro-1604-xenial-v20211213 ubuntu-os-pro-cloud ubuntu-pro-1604-lts READY
ubuntu-pro-1804-bionic-v20220510 ubuntu-os-pro-cloud ubuntu-pro-1804-lts READY
ubuntu-pro-2004-focal-v20220426 ubuntu-os-pro-cloud ubuntu-pro-2004-lts READY
ubuntu-pro-2204-jammy-v20220506 ubuntu-os-pro-cloud ubuntu-pro-2204-lts READY
ubuntu-pro-fips-1804-bionic-v20220411a ubuntu-os-pro-cloud ubuntu-pro-fips-1804-lts READY
ubuntu-pro-fips-2004-focal-v20220411b ubuntu-os-pro-cloud ubuntu-pro-fips-2004-lts READY
ubuntu-2004-focal-v20220419 ubuntu-os-cloud ubuntu-2004-lts READY
ubuntu-2110-impish-v20220505 ubuntu-os-cloud ubuntu-2110 READY
ubuntu-2204-jammy-v20220506 ubuntu-os-cloud ubuntu-2204-lts READY
ubuntu-minimal-1804-bionic-v20220511 ubuntu-os-cloud ubuntu-minimal-1804-lts READY
ubuntu-minimal-2004-focal-v20220419a ubuntu-os-cloud ubuntu-minimal-2004-lts READY
ubuntu-minimal-2110-impish-v20220505 ubuntu-os-cloud ubuntu-minimal-2110 READY
ubuntu-minimal-2204-jammy-v20220506a ubuntu-os-cloud ubuntu-minimal-2204-lts READY
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
훔.. 알리바바와 같이 예전 버전의 image가 deprecate 되어 사용 불가하게 되는 경우도 방지하고
가급적 최신 버전의 이미지를 사용하는 취지였는데
말씀하신 대로 이미지 버전별로 ssh 키 사용자 생성, 접속 가능 여부 등의 이슈도 있네요.. 🤔
UEFI 여부 관련해서는.. non-UEFI 가 좀 더 compatible 할 것 같기는 한데
어차피 Google이 이미지도 관리하고 GCP services도 관리하니까
UEFI 이미지도 별 문제 없을 것 같기는 합니다 😊
→ 가끔 이런 에러가 발생하기도 하나 보네요 (시간 지나서 다시 확인해 보니 문제가 없어졌다고 함)
https://serverfault.com/questions/911926/gcp-invalid-resource-usage-uefi-feature-is-not-available-for-this-project
→ 인스턴스의 UEFI 여부와 boot disk의 UEFI 여부가 안 맞으면 에러가 발생한다고 합니다.
https://stackoverflow.com/questions/62036923/error-uefi-setting-must-be-the-same-for-the-instance-and-the-boot-disk-while-e
이런 측면을 보면 non-UEFI 가 좀 더 나을 것 같기도 하구요..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
golang 코드를 통해 ssh 를 하면 [ERROR: ssh: must specify HostKeyCallback] 오류 발생
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
그렇다면 원래 제안하신 대로 하는 것이 좋겠네용.. ㅎㅎㅎ
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
uefi-images 우분투는 deprecated 된 이미지들이네요;
변경이 필요해 보입니다.