Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make minCpuPlatform a variable to enable launching Cascade Lake instances on Google Compute Platform #66

Open
christopheredsall opened this issue Oct 20, 2019 · 6 comments
Assignees
Labels
bug Something isn't working

Comments

@christopheredsall
Copy link
Contributor

I haven't yet been able to successfully launch a "Cascade Lake" instance. The result coming back from GCP is

[provisioner@mgmt ~]$ sudo tail -f /var/log/slurm/elastic.log 
2019-10-20 21:54:28,338 startnode  INFO     Starting c2-standard-4-0001 in citc-test-ce europe-west4-c
2019-10-20 21:54:30,947 startnode  ERROR     problem launching instance: <HttpError 400 when requesting https://compute.googleapis.com/compute/v1/projects/citc-test-ce/zones/europe-west4-c/instances?alt=json returned "The selected machine type 'c2-standard-4' has a required CPU platform of 'cascadelake'. The minimum CPU platform must match this, but was 'skylake'.">
@christopheredsall christopheredsall transferred this issue from clusterinthecloud/terraform Oct 20, 2019
@christopheredsall christopheredsall self-assigned this Oct 20, 2019
@christopheredsall christopheredsall added the bug Something isn't working label Oct 20, 2019
@christopheredsall
Copy link
Contributor Author

Google documentation

Specifying a Minimum CPU Platform for VM Instances

@christopheredsall
Copy link
Contributor Author

@christopheredsall christopheredsall changed the title Extra arguments needed to launch Cascade Lake instances on Google Compute Platform Make minCpuPlatform a variable to enable launching Cascade Lake instances on Google Compute Platform Oct 20, 2019
@christopheredsall
Copy link
Contributor Author

As a quick YOLO test changing the hard coded value

--- /opt/cloud_sdk/lib/python3.6/site-packages/citc_cloud.py.orig	2019-10-20 22:18:43.864878497 +0000
+++ /opt/cloud_sdk/lib/python3.6/site-packages/citc_cloud.py	2019-10-20 22:19:12.751080593 +0000
@@ -102,7 +102,7 @@
                 ]
             }
         ],
-        'minCpuPlatform': 'Intel Skylake',
+        'minCpuPlatform': 'Intel Cascade Lake',
         'metadata': {
             'items': [{
                 'key': 'startup-script',

works, the node provisions and boots:

2019-10-20 22:20:06,577 startnode  INFO     Starting c2-standard-4-0001 in citc-test-ce europe-west4-c
2019-10-20 22:20:09,602 startnode  INFO     c2-standard-4-0001:  No VNIC attachment yet. Waiting...
2019-10-20 22:20:15,237 startnode  INFO       Private IP 10.1.0.3
2019-10-20 22:20:15,246 startnode  INFO      Started c2-standard-4-0001

@christopheredsall
Copy link
Contributor Author

Another approach that works is to just remove that attribute:

--- /opt/cloud_sdk/lib64/python3.6/site-packages/citc_cloud.py.orig	2019-10-21 13:45:37.285506506 +0000
+++ /opt/cloud_sdk/lib64/python3.6/site-packages/citc_cloud.py	2019-10-21 15:11:17.601853276 +0000
@@ -102,7 +102,6 @@
                 ]
             }
         ],
-        'minCpuPlatform': 'Intel Skylake',
         'metadata': {
             'items': [{
                 'key': 'startup-script',

@christopheredsall
Copy link
Contributor Author

What would be the downsides to not specifying minCpuPlatform?

@geoffnewell
Copy link
Collaborator

Extend citc_gcp.py: create_node_config() to cater for Slurm Features to allow for specifying minCPUPlatform in the SBatch Slurm job config. For example:

#! /bin/bash

#SBATCH --job-name=test
#SBATCH --nodes=1
#SBATCH --ntasks-per-node=2
#SBATCH --cpus-per-task=1
#SBATCH --time=10:00
#SBATCH --constraint="minCPUPlatform=Intel Cascade Lake"

srun -l hostname

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants