Bug 1580434 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

at: https://cloud.google.com/compute/docs/reference/rest/v1/instanceTemplates, the disk definition parameters are described and include: `properties.disks[].initializeParams.diskType` which is used to define the disk type. if this property is omitted, google defaults to a disk type of `pd-standard`.

since we prefer to use a disk type of `pd-ssd` to keep build times down, it is necessary for us to define this property.

unfortunately all of the syntax formats accepted by gcloud for defining this property expect to find a zone identifier preceding  `pd-ssd`.

when we are defining worker pools, the definition may span multiple zones and regions, so we don't have a way to specify that we want to use ssd's while at the same time specifying a worker pool that can take advantage of multiple zones.

to work around this, it would be useful if the worker pool definition could include a zone placeholder. something like what is conveyed below:

```
  "disks": [
    {
      "type": "PERSISTENT",
      "boot": true,
      "autoDelete": true,
      "initializeParams": {
        "sourceImage": "projects/windows-cloud/global/images/family/windows-2012-r2",
        "diskSizeGb": 50,
        "diskType": "zones/{{zone-placeholder}}}/diskTypes/diskType/pd-ssd"
      }
    },
    {
      "type": "PERSISTENT",
      "autoDelete": true,
      "initializeParams": {
        "diskSizeGb": 120,
        "diskType": "zones/{{zone-placeholder}}/diskTypes/diskType/pd-ssd"
      }
    }
  ],
```
at: https://cloud.google.com/compute/docs/reference/rest/v1/instanceTemplates, the disk definition parameters are described and include: `properties.disks[].initializeParams.diskType` which is used to define the disk type. if this property is omitted, google defaults to a disk type of `pd-standard`.

since we prefer to use a disk type of `pd-ssd` to keep build times down, it is necessary for us to define this property.

unfortunately all of the syntax formats accepted by gcloud for defining this property expect to find a zone identifier preceding  `pd-ssd`.

when we are defining worker pools, the definition may span multiple zones and regions, so we don't have a way to specify that we want to use ssd's while at the same time specifying a worker pool that can take advantage of multiple zones.

to work around this, it would be useful if the worker pool definition could include a zone placeholder. something like what is conveyed below:

```
  "disks": [
    {
      "type": "PERSISTENT",
      "boot": true,
      "autoDelete": true,
      "initializeParams": {
        "sourceImage": "projects/windows-cloud/global/images/family/windows-2012-r2",
        "diskSizeGb": 50,
        "diskType": "zones/{{zone-placeholder}}/diskTypes/diskType/pd-ssd"
      }
    },
    {
      "type": "PERSISTENT",
      "autoDelete": true,
      "initializeParams": {
        "diskSizeGb": 120,
        "diskType": "zones/{{zone-placeholder}}/diskTypes/diskType/pd-ssd"
      }
    }
  ],
```
at: https://cloud.google.com/compute/docs/reference/rest/v1/instanceTemplates, the disk definition parameters are described and include: `properties.disks[].initializeParams.diskType` which is used to define the disk type. if this property is omitted, google defaults to a disk type of `pd-standard`.

since we prefer to use a disk type of `pd-ssd` to keep build times down, it is necessary for us to define this property.

unfortunately all of the syntax formats accepted by gcloud for defining this property expect to find a zone identifier preceding  `pd-ssd`.

when we are defining worker pools, the definition may span multiple zones and regions, so we don't have a way to specify that we want to use ssd's while at the same time specifying a worker pool that can take advantage of multiple zones.

to work around this, it would be useful if the worker pool definition could include a zone placeholder. something like what is conveyed below:

```
  "disks": [
    {
      "type": "PERSISTENT",
      "boot": true,
      "autoDelete": true,
      "initializeParams": {
        "sourceImage": "projects/windows-cloud/global/images/family/windows-2012-r2",
        "diskSizeGb": 50,
        "diskType": "zones/{{zone-placeholder}}/diskTypes/diskType/pd-ssd"
      }
    },
    {
      "type": "PERSISTENT",
      "autoDelete": true,
      "initializeParams": {
        "diskSizeGb": 120,
        "diskType": "zones/{{zone-placeholder}}/diskTypes/diskType/pd-ssd"
      }
    }
  ],
```

of course, the worker manager would then have to fill in the zone information when spawning the instance later.
at: https://cloud.google.com/compute/docs/reference/rest/v1/instanceTemplates, the disk definition parameters are described and include: `properties.disks[].initializeParams.diskType` which is used to define the disk type. if this property is omitted, google defaults to a disk type of `pd-standard`.

since we prefer to use a disk type of `pd-ssd` to keep build times down, it is necessary for us to define this property.

unfortunately all of the syntax formats accepted by gcloud for defining this property expect to find a zone identifier preceding  `pd-ssd`.

when we are defining worker pools, the definition may span multiple zones and regions, so we don't have a way to specify that we want to use ssd's while at the same time specifying a worker pool that can take advantage of multiple zones.

to work around this, it would be useful if the worker pool definition could include a zone placeholder. something like what is conveyed below:

```json
  "disks": [
    {
      "type": "PERSISTENT",
      "boot": true,
      "autoDelete": true,
      "initializeParams": {
        "sourceImage": "projects/windows-cloud/global/images/family/windows-2012-r2",
        "diskSizeGb": 50,
        "diskType": "zones/{{zone-placeholder}}/diskTypes/diskType/pd-ssd"
      }
    },
    {
      "type": "PERSISTENT",
      "autoDelete": true,
      "initializeParams": {
        "diskSizeGb": 120,
        "diskType": "zones/{{zone-placeholder}}/diskTypes/diskType/pd-ssd"
      }
    }
  ],
```

of course, the worker manager would then have to fill in the zone information when spawning the instance later.

Back to Bug 1580434 Comment 0