Meta tags:
description=Learn how to move your applications and data from an existing compute instance to a new compute instance in this Google Cloud guide.;

Headings (most frequently used words):

prepare, your, to, the, resources, move, new, compute, vm, requirements, workload, instance, and, migration, standard, gcloud, rest, required, storage, stay, organized, with, collections, save, categorize, content, based, on, preferences, before, you, begin, evaluate, options, existing, vms, example, of, n1, n4, clean, up, what, next, console, roles, networking, network, suse, enterprise, linux, server, operating, system, create, after, starts, products, pricing, support, engage, permissions,

Text of the page (most frequently used words):
the (577), disk (218), and (184), create (174), for (138), new (133), your (129), you (128), disks (119), vms (110), #instance (106), with (102), #compute (84), machine (82), type (69), boot (63), about (62), use (62), troubleshoot (62), using (60), from (58), that (57), hyperdisk (55), instances (50), zone (49), manage (47), snapshot (46), network (45), data (44), source (43), name (43), server (41), view (39), following (37), mig (37), cloud (36), windows (36), attached (36), performance (36), google (34), project (34), configure (33), snapshots (32), series (32), balanced (31), set (31), overview (31), current (30), zones (29), storage (29), supported (29), persistent (28), reservation (28), ssd (27), image (27), resources (26), can (26), are (25), local (25), workload (25), engine (25), start (24), project_name (23), custom (23), this (22), projects (22), change (22), linux (21), vm_name (21), images (21), sql (21), example (20), gcloud (20), move (20), configuration (20), access (20), monitor (20), stop (19), then (19), support (18), must (18), available (18), gpu (18), request (17), upgrade (17), interface (17), standard (17), types (17), generation (17), virtual (17), policies (16), any (16), uses (16), region (16), take (16), update (16), addresses (16), add (16), reservations (16), all (15), connect (15), replace (15), method (15), workloads (15), load (15), review (15), microsoft (15), networking (15), availability (15), groups (15), ssh (15), recommendations (15), system (14), migration (14), only (14), operating (14), creation (14), host (14), apply (14), created (13), include (13), attach (13), gpus (13), managed (13), time (13), applications (13), regional (13), delete (13), management (13), bulk (13), cluster (13), after (12), where (12), hdb (12), gvnic (12), multiple (12), might (12), version (12), when (12), existing (12), run (12), sole (12), best (12), need (11), copy (11), located (11), virtio (11), first (11), choose (11), non (11), options (11), install (11), resource (11), prepare (11), high (11), application (11), migrate (11), based (11), practices (11), stateful (11), https (10), perform (10), detach (10), have (10), group (10), complete (10), not (10), disaster (10), recovery (10), guest (10), metadata (10), migs (10), machines (10), logs (10), see (9), other (9), information (9), temporary (9), remove (9), googleapis (9), com (9), isn (9), device (9), driver (9), creating (9), but (9), moving (9), dns (9), make (9), drivers (9), scripts (9), default (9), roles (9), h4d (9), licenses (9), tenant (9), openshift (9), shutdown (9), hpc (9), samples (8), understand (8), license (8), issues (8), post (8), body (8), disk_name (8), place (8), option (8), regions (8), second (8), size (8), cli (8), required (8), backup (8), templates (8), startup (8), interfaces (8), bare (8), metal (8), back (8), features (8), permissions (8), authentication (8), maintenance (8), service (8), import (8), cpu (8), login (8), optimize (8), internal (8), agent (8), keys (8), flexibility (8), optimized (8), tpu (8), third (7), thumb (7), more (7), running (7), snapshot_name (7), plan (7), has (7), nvme (7), how (7), security (7), static (7), transfer (7), files (7), requirements (7), get (7), commitments (7), balancing (7), benchmark (7), enable (7), manually (7), idle (7), scale (7), deploy (7), mysql (7), zonal (7), events (6), code (6), details (6), send (6), schedules (6), central1 (6), want (6), doesn (6), nic (6), full (6), before (6), ubuntu (6), capacity (6), manager (6), different (6), highly (6), select (6), newer (6), edit (6), systems (6), sure (6), names (6), plans (6), restore (6), identity (6), console (6), usage (6), updates (6), instant (6), nested (6), across (6), mode (6), demand (6), pools (6), failover (6), extension (6), customized (6), spot (6), down (5), next (5), verify (5), devicename (5), both (5), procedure (5), step (5), such (5), snapshotted (5), rest (5), number (5), test (5), additional (5), policy (5), deployment (5), work (5), location (5), quota (5), pool (5), list (5), environment (5), bandwidth (5), monitoring (5), databases (5), accounts (5), errors (5), future (5), virtualization (5), nvidia (5), operations (5), placement (5), node (5), build (5), multi (5), modify (5), audit (5), symphony (5), email (5), between (5), enhanced (5), capabilities (5), tenancy (5), control (5), workstation (5), faq (5), flex (5), português (4), español (4), sign (4), page (4), lifecycle (4), troubleshooting (4), needed (4), createsnapshot (4), original (4), also (4), part (4), global (4), networks (4), optional (4), throughput (4), minutes (4), process (4), long (4), takes (4), pro (4), api (4), account (4), schedule (4), format (4), mount (4), file (4), used (4), specify (4), steps (4), during (4), command (4), specific (4), same (4), changes (4), one (4), idpf (4), arm (4), documentation (4), services (4), apis (4), development (4), authenticate (4), external (4), provider (4), tools (4), distributed (4), tcp (4), pmu (4), share (4), live (4), autoscaling (4), cross (4), requests (4), calendar (4), single (4), metrics (4), health (4), active (4), clusters (4), containers (4), container (4), database (4), postgresql (4), extensions (4), suspend (4), resize (4), graceful (4), locations (4), replication (4), bound (4), terms (3), architecture (3), started (3), updated (3), content (3), under (3), apache (3), read (3), what (3), were (3), attachdisk (3), machinetype (3), machine_type (3), setmachinetype (3), sizegb (3), sourcesnapshot (3), insert (3), performing (3), 100 (3), once (3), iops (3), provisioned (3), instead (3), dependent (3), upon (3), factors (3), still (3), note (3), backups (3), rules (3), public (3), large (3), either (3), vpc (3), previously (3), configured (3), later (3), section (3), hardware (3), compatible (3), while (3), contain (3), switch (3), migrating (3), net (3), distribution (3), check (3), determine (3), don (3), reserved (3), automatically (3), described (3), upgrading (3), physical (3), costs (3), predefined (3), admin (3), credentials (3), rdma (3), guides (3), infrastructure (3), observability (3), analytics (3), automatic (3), encryption (3), serial (3), configurations (3), patterns (3), higher (3), discounts (3), cuds (3), manual (3), scalable (3), resilient (3), autoscale (3), balancer (3), prevent (3), testing (3), ibm (3), spectrum (3), deploying (3), rhel (3), protect (3), certificates (3), query (3), state (3), disable (3), properties (3), increase (3), design (3), workstations (3), tpus (3), product (3), 한국어 (2), 日本語 (2), עברית (2), brasil (2), italiano (2), indonesia (2), français (2), américa (2), latina (2), deutsch (2), english (2), action (2), site (2), youtube (2), center (2), pricing (2), products (2), last (2), 2026 (2), utc (2), licensed (2), feedback (2), tips (2), known (2), expected (2), false (2), true (2), machinetypes (2), detachdisk (2), generates (2), error (2), incompatibility (2), subnet (2), subnet_name (2), network_name (2), two (2), each (2), non_boot_disk_name (2), boot_disk_name (2), new_machine_type (2), previous (2), provision (2), provisioned_throughput (2), provisioned_iops (2), disk_size (2), disk_type (2), source_disk_zone (2), source_disk_name (2), snapshotting (2), recent (2), supports (2), those (2), there (2), ubuntu1804 (2), out (2), customer (2), recommended (2), changed (2), recompile (2), entries (2), forwarding (2), moved (2), programs (2), packages (2), over (2), instructions (2), rename (2), preparing (2), root (2), rebuild (2), initramfs (2), ram (2), failure (2), prevents (2), address (2), keep (2), promote (2), queue (2), than (2), approach (2), amount (2), tib (2), recommend (2), alternatively (2), most (2), enough (2), possible (2), symlinks (2), pci (2), attr (2), kernel (2), eth0 (2), provide (2), connectivity (2), udev (2), extend (2), ensure (2), consume (2), describe (2), per (2), tier_1 (2), like (2), scsi (2), compatibility (2), aren (2), upgrades (2), own (2), however (2), enabled (2), function (2), requires (2), shielded (2), family (2), evaluate (2), able (2), these (2), iam (2), idp (2), federated (2), operation (2), advantage (2), greater (2), sdk (2), languages (2), frameworks (2), industry (2), solutions (2), hybrid (2), multicloud (2), pipelines (2), hosting (2), commitment (2), consumption (2), registration (2), sles (2), export (2), port (2), collecting (2), nodes (2), report (2), core (2), rdp (2), general (2), app (2), latency (2), analyze (2), visible (2), cores (2), committed (2), underutilized (2), insights (2), utilization (2), globally (2), web (2), autohealing (2), iis (2), shared (2), reserve (2), autoscaler (2), autoscalers (2), activity (2), kubernetes (2), directory (2), setting (2), redis (2), cloning (2), writer (2), always (2), alwayson (2), volumes (2), synchronization (2), byol (2), payg (2), byos (2), families (2), guide (2), securing (2), event (2), simulate (2), topology (2), together (2), repairs (2), repair (2), failures (2), template (2), suspended (2), stopped (2), target (2), cancel (2), limit (2), ipv6 (2), decrease (2), basic (2), consistent (2), scoped (2), appliances (2), asynchronous (2), encrypt (2), memory (2), extreme (2), organization (2), user (2), through (2), advanced (2), preemptible (2), provisioning (2), models (2), rtx (2), vws (2), constraints (2), accelerator (2), reference (2), technology (2), areas (2), close (2), subscribe, newsletter, our, decade, climate, join, cookies, privacy, tech, twitter, blog, engage, training, certification, getting, github, status, release, notes, community, forums, contact, sales, marketplace, easy, easytounderstand, solved, problem, solvedmyproblem, otherup, hard, hardtounderstand, incorrect, sample, incorrectinformationorsamplecode, missing, missingtheinformationsamplesineed, otherdown, tell, except, otherwise, noted, java, registered, trademark, oracle, its, affiliates, developers, creative, commons, attribution, learn, longer, clean, networkinterfaces, subnetwork, subnetworks, nictype, disktypes, times, containing, repeat, 290, 3600, 100gb, repeating, specifying, total, tbs, recommends, them, scenario, restored, receive, patches, reach, technical, tam, open, case, care, tasks, configuring, balancers, updating, associated, reassign, contents, modified, necessary, users, directories, recreated, least, detached, now, been, finish, starts, promoted, ephemeral, chosen, describes, sudo, dracut, force, hostonly, shutting, avoid, dependencies, initial, filesystem, includes, wider, range, modules, making, will, into, booting, properly, issue, suse, enterprise, unassign, counts, allocations, changing, subnets, larger, taken, offline, contained, even, copied, written, captured, because, capture, should, minimize, length, unavailable, incremental, blank, runs, reconfigured, stornvme, follow, applies, may, 2022, they, subsystem, dev_id, 0x0, kernels, 0000, eth, applicable, relevant, entry, ensures, provided, which, could, lead, gve, etc, transferred, vendor, consumed, few, days, completed, requesting, evaluation, was, assigned, referencing, recreate, store, lost, unless, stored, some, hypervisor, presented, adjust, prospective, provides, explore, identify, suitable, consider, whether, lower, another, several, including, respect, exact, expand, granting, folders, organizations, networkadmin, ask, administrator, grant, haven, already, verifies, selecting, installed, latest, components, init, installation, initialize, tab, begin, newest, simpler, conditions, met, c3d, benefit, price, relative, value, 5th, intel, xeon, processor, faster, speeds, improved, certain, situations, reasons, save, categorize, preferences, stay, organized, collections, home, concurrent, renewal, resizing, common, pay, viewing, output, diagnostic, sudoers, screenshots, generate, bug, blackwell, soft, lockups, bus, locks, rescue, inaccessible, dumps, panic, fstab, unresponsive, suspension, reboots, shutdowns, nics, dpdk, improve, resiliency, communication, reduce, compact, irdma, customize, threads, sustained, merge, split, renew, without, purchase, cost, savings, dynamic, overcommit, cpus, floating, reliable, udp, backends, routing, scaling, consuming, combine, cud, allow, sharing, decisions, signals, serving, predictions, organize, labels, replica, states, observe, reports, tensorflow, inference, tensorrt5, learning, monte, carlo, methods, spark, others, integrate, clustering, exchange, 2016, sharepoint, strategies, passive, inactive, setups, built, integrations, validation, deployed, transition, hammerdb, bucket, aws, ec2, pacemaker, s2d, block, netapp, hot, standby, drbd, architectures, client, private, mailjet, mailgun, sendgrid, sending, blue, green, deployments, lamp, joomla, asp, interactive, mongodb, flask, terraform, servers, mtls, random, generator, rng, accurate, protocol, ntp, append, els, restrictions, deprecate, versions, trusted, red, hat, knowledgebase, functionality, risks, controls, confidential, kek, secure, expiration, attributes, handle, notices, faulty, unmanaged, affect, preserved, turn, off, alternate, fails, repairing, maintain, click, override, selectively, applying, accelerate, outage, rebalance, reenable, proactive, redistribution, shape, distribute, define, info, accidental, deletion, spread, reset, resume, restart, referrers, uuid, recover, corrupted, duplicate, clones, alerts, vss, regionally, protection, considerations, synchronous, consistency, failback, replicate, limits, settings, help, kms, supplied, symbolic, links, practice, exapools, ptr, record, rates, tags, restrict, automate, password, require, powershell, sac, securely, apps, vpn, bastion, iap, connection, browser, connections, within, iso, imported, prerequisites, importing, exporting, bring, path, reattach, constraint, accounting, examples, slurm, team, slice, slices, adds, scenarios, deterministic, base, ready, aci, preempted, historical, alternative, similar, displays, ops, logging, gpudirect, ultra, minimum, platform, hostname, quickstarts, office, licensing, premium, strategy, gemini, accelerators, platforms, scores, purpose, discover, free, skip, main,

Text of the page (random words):
o prepare for moving the data in the disks attached to your current instance to a new instance on linux systems test your updated applications and scripts to make sure they work with persistent device names or symlinks instead of the disk device names if you re migrating from a vm that runs microsoft windows you must update the nvme driver on vms created before may 2022 this applies to the boot disk in your current vm and any previously created snapshots or custom images that are used to create a vm windows must be reconfigured to start using the microsoft nvme driver stornvme follow the instructions to update your boot device if your new vm doesn t support the same disk types as your current vm you might need to update your deployment scripts or instance templates to support the new machine series if your current vm uses a disk type for the boot disk that isn t supported by the new machine series and you are migrating multiple vms with the same configuration create a custom image to use when creating the new vms create a snapshot of the pd standard boot disk of your current vm create a custom image using the disk snapshot as the source if you need to move local ssd information create a blank disk large enough to backup your local ssd disks if possible use a disk type that is supported by the new vm if there are no disk types that are supported by both the current vm and the new vm then create a temporary disk using a disk type supported by the current vm attach the new disk to the current vm then format and mount the disk copy the data from the local ssd disks attached to the current vm to this temporary disk change the disk type of any disks attached to the current vm that use a disk type that isn t supported by the new vm to move the disk data to new disks create snapshots of the disks you can alternatively transfer files from one vm to the other you can take the snapshots while the vm is running but any data written to the disks after you take the snapshot is not captured because snapshots are incremental you can take a second snapshot after you stop the vm to capture all the most recent changes this approach should minimize the length of time the vm is unavailable while you switch to a new vm alternatively you can take all the disk snapshots after you stop the vm we recommend that you create a snapshot of all the disks attached to your vm even if the disk type is supported by the new machine series include any temporary disks that contain the copied local ssd data the amount of time it takes to snapshot a disk is dependent upon multiple factors such as the disk size and amount of data contained on the disk for example if you take a snapshot of a 1 tib disk that is 85 full it might take 5 minutes for the snapshot to complete but if you take a snapshot of a 100 tib disk that is 85 full it might take 11 minutes to complete we recommend you perform test snapshots of your disks before you start the migration process to understand how long snapshotting takes if you have a disk that can be taken offline you can use the following approach to move the data to a new disk while the source vm is still available detach the disk from your vm take a snapshot of the disk use the snapshot to create a new disk using a disk type that is supported by the new machine series the new disk must be either the same size or larger than the source disk prepare network resources complete the following steps to update the network configuration used by your current instance to support the new instance if you re creating a vm in a new region create a vpc network and subnets in the new region if you configured custom nic queue counts see queue allocations and changing the machine type if you want to keep the ip addresses used by the source vm promote the ip addresses to static ip addresses unassign static ip address before you stop your source vm prepare the suse enterprise linux server operating system to avoid hardware specific dependencies rebuild the initramfs initial ram filesystem this includes a wider range of drivers and modules making the operating system compatible with other instance types failure to do so will run into the known issue that prevents the vm from booting properly before shutting down the system run the following command as root to rebuild the initramfs with all drivers sudo dracut force no hostonly move your workload to the new vm after preparing your vms for migration the next step is to move your workload to the new vm if you are moving your vms from the first generation to the second generation machine series read the instructions on the edit the machine type of a vm page if you want to change the name of your existing vm review the information at rename a vm this section describes how to move your workload from a first or second generation vm to a third or newer generation vm during this procedure you create a new vm instance then move your workloads to the new vm note moving from an h3 vm to any other machine series is not supported create the new vm when moving your workloads from first or second generation vms n1 or n2 for example to third generation or later you must first create a new vm and then move your workloads if the source vm uses non boot disks with a disk type that is supported by the new machine series detach the disks from the vm stop your source vm create snapshots of all disks that are still attached to the source vm create a new compute vm instance using either a public image or a custom image that is configured to use gvnic when creating the new vm choose the following options select the machine type from the machine series that you have chosen select a supported os image or use a custom image that you created previously select a supported disk type for the boot disk for example hyperdisk balanced if you created new disks from snapshots of the original disks include those new disks specify the new vpc network if you re creating the instance in a different region if both virtio and gvnic are supported for the new instance select gvnic specify the static ip addresses if you promoted the ephemeral ip addresses of the source vm start the new vm after the instance starts now that the new instance has been created and started complete the following steps to finish the configuration of the new instance and copy over all the data from the source instance attach the disks you detached from the source vm to the new vm for any disks attached to the source vm that use a disk type not supported by the new vm create a disk from a snapshot and attach it to the new instance when creating the new disk select a disk type that is supported by the new vm and specify a size that is at least as large as the original disk if the original vm used a resource policy for any disks that were recreated for the new vm you need to add the resource policy to the new disks if you created the new vm using a public os image and not a custom image then do the following configure the necessary users drivers packages and file directories on the new instance to support your workload install your modified applications and programs on the new vm recompile the programs on the new os or architecture if required optional if you moved the contents of local ssd disks to a temporary disk and the new vm has attached local ssd storage after you format and mount the disks you can move the data from the temporary disk to the local ssd disks reassign any static ip addresses associated with the source vm to the new vm complete any additional tasks required to make your new vm highly available such as configuring load balancers and updating the forwarding rules optional update the dns entries if needed for the new vm recommended schedule disk backups for the new disks recommended if you changed the os to a different version or architecture recompile your applications if you have capacity issues when moving your workloads reach out to your technical account manager tam for other issues open a support case with cloud customer care migration example of n1 standard 8 to n4 standard 8 the following example is a migration of an n1 standard 8 vm to an n4 standard 8 vm the n1 standard 8 vm has a pd ssd boot disk running an ubuntu1804 image and a pd ssd data disk you must use the cli or rest api for this procedure note to receive security patches for ubuntu1804 upgrade to ubuntu pro there are two options available to upgrade your n1 vm to an n4 vm option 1 if your n1 vm uses the virtio network interface then you must create a new n4 vm n4 supports only the gvnic network interface and hyperdisk balanced disks you create a snapshot of your persistent disk boot and data disks create hyperdisk balanced disks from those snapshots attach the hyperdisk balanced disks and create the new n4 vm with the hyperdisk balanced disks you can also choose to create a new hyperdisk balanced boot disk using a more recent version of the ubuntu os in this scenario you can create a new hyperdisk balanced disk from the boot disk snapshot but you attach that disk as a non boot disk to the n4 vm then you can copy non system data from the restored snapshot to the new boot disk option 2 if your n1 vm uses the gvnic network interface the operating system has an nvme storage device driver doesn t have any attached local ssd disks or gpus and isn t part of a managed instance group mig then you can change the machine type from n1 to n4 but you still must change your persistent disk disk types to hyperdisk balanced disks you must first detach your persistent disk boot and data disks create snapshots of the disks create hyperdisk balanced disks using the snapshots as the source then attach the new hyperdisk balanced disks to your n4 vm after you change the machine type if your vm has attached gpus then you must detach them first the time to snapshot a disk is dependent upon multiple factors such as the total number of tbs on a disk for example if you take a snapshot of a 1 tb disk that is 85 full it might take 5 minutes for the snapshot to complete but if you take a snapshot of a 100 tb disk that is 85 full it might take 11 minutes to complete google recommends you perform test snapshots of your disks before you start the migration process to understand how long snapshotting takes gcloud option 1 create a new n4 vm with snapshotted disks stop the vm by using gcloud compute instances stop gcloud compute instances stop vm_name zone zone replace the following vm_name the name of your current n1 standard 8 vm zone the zone where the vm is located snapshot your disks use the gcloud compute snapshots create to create a snapshot of both the persistent disk boot disk and data disk attached to the vm gcloud compute snapshots create snapshot_name source disk source_disk_name source disk zone source_disk_zone replace the following snapshot_name the name of the snapshot you want to create source_disk_name the name of your source disk source_disk_zone the zone of your source disk create a new hyperdisk balanced disk for the data disk by repeating the previous step and specifying the data disk information instead of the boot disk gcloud compute disks create gcloud compute disks create disk_name project project_name type disk_type size disk_size zone zone source snapshot snapshot_name provisioned iops provisioned_iops provisioned throughput provisioned_throughput replace the following disk_name the name of the new disk you are creating from the snapshotted disk project_name the name of your project disk_type the new disk type in this example it s a hyperdisk balanced disk disk_size the size of the disk example 100gb zone the zone where the new disk is located snapshot_name the name of the snapshot source disk optional provisioned_iops the iops performance for the disk example 3600 optional provisioned_throughput the throughput performance to provision the disk example 290 repeat the previous step for each snapshotted disk create the n4 standard 8 vm and attach the hyperdisk balanced disks using the gcloud compute instances create gcloud compute instances create vm_name project project_name zone zone machine type new_machine_type boot disk device name boot_disk_name disk name non_boot_disk_name boot no network interface nic type gvnic replace the following vm_name the name of the new vm instance project_name the name of your project zone the zone where the new vm is located new_machine_type the machine type in this example it s n4 standard 8 boot_disk_name the name of the hyperdisk balanced boot disk you created from the source disk snapshot attached to the n1 standard 8 vm non_boot_disk_name the name of the hyperdisk balanced data disk you created from the source snapshot disk attached to the n1 standard 8 vm start the n4 standard 8 vm using the gcloud compute instances start gcloud compute instances start vm_name replace vm_name with name of the new vm option 2 perform an in place machine upgrade this option is only available if your n1 vm uses the gvnic network interface the operating system has an nvme storage device driver doesn t have any attached local ssd disks or gpus and isn t a part of a managed instance group mig performing this procedure with an n1 vm with a virtio network interface generates a vm incompatibility error stop the vm detach the disks from the vm create a snapshot of the boot and data disks create hyperdisk balanced boot and data disks using a disk snapshot as the source for each disk set the machine type to an n4 vm attach the hyperdisk balanced boot disk and the hyperdisk balanced data disk start the n4 vm rest option 1 create a new n4 vm with snapshotted disks stop the vm by using the instances stop method post https compute googleapis com compute v1 projects project_name zones zone instances vm_name stop replace the following project_name the project id zone the zone containing the vm vm_name the name of your current n1 standard 8 vm snapshot your disks using the disks createsnapshot method to create a snapshot of both the persistent disk boot disk and data disk attached to the instance post https compute googleapis com compute v1 projects project_name zones zone disks disk_name createsnapshot in the body of the request include the name for your new snapshotted persistent disk disk for example name snapshot_name replace the following project_name the name of your project zone the zone where your disk is located disk_name the disk you plan to snapshot snapshot_name a name for the snapshot such as hdb boot disk or hdb data disk create a hyperdisk balanced disk using the disks insert method you perform this step two times once to include the name of your hyperdisk balanced boot disk and a second time to include the name of your data disks use the sourcesnapshot for the new hyperdisk balanced boot and data disks the type of disk hyperdisk balanced and sizegb of the disk in the request body post https compute googleapis com compute v1 projects project_name zones zone disks re...