Skip to content

Is mounting pre-existing persistent disks lost in google-batch vs google-cls-v2? #333

Description

@carbocation

Previously we could build zonal disks and mount them using google-cls-v2. The README says that we can do this with google-batch as well. However, the code doesn't seem to support this?

The README says:

Mounting an existing peristent disk
To have the google-batch provider mount a persistent disk that you have pre-created and populated, use the --mount command line flag and the url of the source disk:

--mount RESOURCES="https://www.googleapis.com/compute/v1/projects/your-project/zones/your_disk_zone/disks/your-disk"

But other than the disks built at launch time, it seems that only GCS-based mounts actually get attached, not persistent disk mounts? This seems to be in contrast to the old google-cls-v2 provider. Not sure I'm reading the code correctly but it seems like there is a mismatch between what the README says and what the google-batch provider offers?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions