Meta tags:
Headings (most frequently used words):
console, gcloud, rest, and, multiple, machine, types, add, with, preferences, mig, instance, flexibility, create, terraform, to, additional, overrides, stay, organized, collections, save, categorize, content, based, on, your, before, you, begin, an, existing, example, for, yaml, file, configure, what, next, products, pricing, support, resources, engage,
Text of the page (most frequently used words):
the (585), #instance (253), create (172), and (164), for (153), you (149), mig (144), #machine (124), vms (124), with (89), that (82), types (78), name (77), want (77), add (75), use (71), click (68), region (64), troubleshoot (62), disk (61), about (60), selection (57), template (55), compute (50), configure (49), disks (48), flexibility (47), manage (46), type (46), set (46), cloud (45), view (45), multiple (42), using (42), google (41), groups (39), server (39), your (37), following (36), rank (35), instances (35), shape (33), windows (33), number (32), configuration (31), images (31), selections (31), section (31), select (31), overview (31), zone (30), performance (30), any (28), regional (28), projects (27), reservation (27), preference (26), can (26), engine (26), distribution (26), boot (25), image (25), then (25), gcloud (24), instance_group_name (24), existing (24), field (24), from (24), zones (24), target (22), hyperdisk (22), cpu (21), regions (21), managed (21), delete (21), default (21), single (21), sql (21), policy (20), monitor (20), resources (19), global (19), access (19), network (19), standard (18), specify (18), list (18), project_id (18), update (18), done (18), console (18), gpu (18), preferences (17), apply (17), resource (17), availability (17), linux (17), see (16), this (16), page (16), policies (16), platform (16), machine_type (16), request (16), storage (16), autoscaling (16), reservations (16), machinetypes (15), value (15), replace (15), new (15), each (15), balanced (15), target_size (15), virtual (15), snapshots (15), ssh (15), recommendations (15), migs (14), workload (14), creation (14), host (14), load (14), custom (14), connect (14), file (13), order (13), project (13), where (13), after (13), enter (13), best (13), management (13), bulk (13), microsoft (13), cluster (13), cli (12), higher (12), image_name (12), image_project (12), instance_selection (12), true (12), override (12), opens (12), service (12), one (12), url (12), instance_template_id (12), instance_template_url (12), terraform (12), group (12), install (12), based (12), sole (12), persistent (12), are (11), remove (11), overrides (11), make (11), flex (11), zonal (11), authentication (11), application (11), practices (11), workloads (11), stateful (11), support (10), other (10), change (10), command (10), minimum (10), machine_type_2 (10), machine_type_1 (10), properties (10), complete (10), adding (10), repeat (10), redistribution (10), back (10), location (10), identity (10), local (10), time (10), metadata (10), machines (10), attached (10), migrate (10), logs (10), terms (9), samples (9), instanceselections (9), mincpuplatform (9), initializeparams (9), sourceimage (9), representing (9), lower (9), means (9), source (9), patch (9), not (9), rest (9), which (9), modify (9), any_single_zone (9), none (9), mode (9), selected (9), login (9), choose (9), licenses (9), tenant (9), openshift (9), shutdown (9), start (9), hpc (9), license (8), yaml (8), rank_2 (8), machine_type_4 (8), machine_type_3 (8), instance_selection_2 (8), rank_1 (8), instance_selection_1 (8), method (8), window (8), available (8), specific (8), how (8), spot (8), import (8), optimize (8), internal (8), disaster (8), recovery (8), high (8), agent (8), guest (8), keys (8), h4d (8), dns (8), optimized (8), tpu (8), thumb (7), down (7), information (7), need (7), more (7), devicename (7), data (7), example (7), flag (7), device (7), located (7), https (7), beta (7), when (7), attach (7), specified (7), checkbox (7), maintain (7), provider (7), follows (7), don (7), run (7), environment (7), networking (7), commitments (7), startup (7), balancing (7), benchmark (7), enable (7), manually (7), idle (7), addresses (7), scale (7), deploy (7), mysql (7), maintenance (7), templates (7), snapshot (7), backup (7), events (6), code (6), all (6), send (6), first (6), debian (6), ssd (6), flags (6), device_name (6), googleapis (6), com (6), instancegroupmanagers (6), instanceflexibilitypolicy (6), must (6), regioninstancegroupmanagers (6), step (6), already (6), contain (6), either (6), values (6), instancetemplates (6), post (6), machine_types (6), instance_selections (6), igm (6), google_compute_region_instance_group_manager (6), size (6), dialog (6), drop (6), disable (6), before (6), creating (6), development (6), options (6), external (6), credentials (6), errors (6), usage (6), security (6), migration (6), updates (6), instant (6), files (6), nested (6), gpus (6), across (6), applications (6), demand (6), pools (6), failover (6), extension (6), transfer (6), customized (6), sign (5), understand (5), details (5), min_cpu_platform (5), have (5), additional (5), resize (5), supported (5), distributionpolicy (5), basic (5), created (5), monitoring (5), databases (5), accounts (5), future (5), drivers (5), virtualization (5), nvidia (5), operations (5), placement (5), node (5), highly (5), build (5), multi (5), capacity (5), schedules (5), audit (5), symphony (5), email (5), scripts (5), manager (5), between (5), operating (5), systems (5), enhanced (5), capabilities (5), stop (5), tenancy (5), restore (5), control (5), workstation (5), faq (5), português (4), español (4), device_name_2 (4), min_cpu_platform_2 (4), device_name_1 (4), min_cpu_platform_1 (4), always (4), also (4), save (4), follow (4), prompts (4), among (4), steps (4), edit (4), pre (4), general (4), shapes (4), version (4), haven (4), settings (4), sure (4), allow (4), however (4), furthermore (4), include (4), services (4), apis (4), authenticate (4), idp (4), federated (4), user (4), account (4), running (4), plan (4), tools (4), distributed (4), issues (4), ubuntu (4), bandwidth (4), tcp (4), pmu (4), get (4), share (4), upgrade (4), live (4), cross (4), requests (4), calendar (4), metrics (4), health (4), active (4), clusters (4), containers (4), container (4), database (4), uses (4), postgresql (4), extensions (4), work (4), suspend (4), graceful (4), locations (4), plans (4), replication (4), review (4), bound (4), content (3), apache (3), json (3), filename (3), file_name (3), will (3), expand (3), targetsize (3), instancetemplate (3), targetshape (3), updatepolicy (3), instanceredistributiontype (3), insert (3), learn (3), commands (3), max_unavailable_fixed (3), max_surge_fixed (3), minimal_action (3), opportunistic (3), instance_redistribution_type (3), update_policy (3), family (3), instance_flexibility_policy (3), google_compute_instance_template (3), instance_template (3), distribution_policy_target_shape (3), central1 (3), base_instance_name (3), specifies (3), repair (3), leave (3), fields (3), their (3), needed (3), scroll (3), downs (3), test (3), documentation (3), api (3), automatically (3), guides (3), infrastructure (3), observability (3), analytics (3), automatic (3), troubleshooting (3), encryption (3), pro (3), serial (3), configurations (3), patterns (3), discounts (3), cuds (3), manual (3), scalable (3), resilient (3), autoscale (3), balancer (3), prevent (3), testing (3), ibm (3), spectrum (3), perform (3), deploying (3), during (3), prepare (3), deployment (3), rhel (3), protect (3), certificates (3), query (3), state (3), increase (3), schedule (3), lifecycle (3), design (3), non (3), pool (3), move (3), workstations (3), series (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), site (2), youtube (2), center (2), started (2), system (2), pricing (2), products (2), last (2), updated (2), 2026 (2), utc (2), licensed (2), under (2), feedback (2), next (2), intel (2), ice (2), lake (2), updating (2), overwrite (2), included (2), important (2), property (2), instead (2), feature (2), subject (2), offerings (2), features (2), might (2), limited (2), launch (2), stage (2), descriptions (2), preview (2), ways (2), has (2), resizing (2), yes (2), disk_type (2), disk_size_gb (2), source_image (2), auto_delete (2), shell (2), initialize (2), reduce (2), verify (2), sdk (2), languages (2), frameworks (2), costs (2), industry (2), solutions (2), hybrid (2), multicloud (2), pipelines (2), hosting (2), quota (2), commitment (2), consumption (2), full (2), registration (2), sles (2), export (2), port (2), collecting (2), nodes (2), report (2), arm (2), core (2), rdp (2), app (2), latency (2), analyze (2), visible (2), cores (2), committed (2), generation (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), place (2), directory (2), setting (2), redis (2), cloning (2), writer (2), alwayson (2), volumes (2), synchronization (2), switch (2), byol (2), payg (2), byos (2), changes (2), families (2), guide (2), securing (2), event (2), simulate (2), topology (2), together (2), repairs (2), check (2), failures (2), suspended (2), stopped (2), physical (2), cancel (2), once (2), limit (2), interfaces (2), ipv6 (2), static (2), decrease (2), consistent (2), scoped (2), copy (2), appliances (2), asynchronous (2), throughput (2), encrypt (2), names (2), format (2), mount (2), memory (2), extreme (2), organization (2), through (2), advanced (2), rdma (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, third, decade, climate, action, join, cookies, privacy, tech, twitter, blog, engage, training, certification, architecture, 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, what, false, disktype, those, continue, required, certain, instancelifecyclepolicy, forceupdateonrepair, force_update_on_repair, instance_lifecycle_policy, second, force, optionally, definitions, nothing, else, still, choice, verifies, selecting, provide, error, returned, confirm, signed, auth, installed, previously, latest, components, note, init, installation, tab, checking, helps, chances, encountering, instructions, begin, know, works, editing, creates, selects, listed, assign, ranks, lists, indicate, document, describes, lets, categorize, stay, organized, collections, home, concurrent, operation, renewal, nvme, common, pay, viewing, output, diagnostic, sudoers, screenshots, generate, bug, blackwell, soft, lockups, bus, locks, rescue, inaccessible, dumps, kernel, panic, fstab, unresponsive, suspension, reboots, shutdowns, connectivity, tips, nics, dpdk, improve, resiliency, communication, compact, idpf, interface, irdma, driver, nic, customize, threads, per, sustained, merge, split, extend, renew, without, purchase, cost, savings, dynamic, overcommit, cpus, floating, reliable, udp, backends, routing, scaling, consuming, consume, combine, cud, sharing, decisions, signals, serving, predictions, organize, labels, replica, states, observe, reports, tensorflow, inference, tensorrt5, learning, monte, carlo, methods, spark, forwarding, others, integrate, clustering, exchange, 2016, sharepoint, strategies, passive, inactive, setups, built, integrations, validation, were, deployed, transition, hammerdb, bucket, aws, ec2, pacemaker, s2d, block, netapp, hot, standby, drbd, architectures, client, private, address, mailjet, mailgun, sendgrid, sending, blue, green, deployments, lamp, joomla, asp, net, interactive, mongodb, flask, servers, over, mtls, random, generator, virtio, rng, accurate, protocol, ntp, append, els, restrictions, packages, deprecate, versions, trusted, red, hat, knowledgebase, functionality, risks, vpc, controls, confidential, kek, secure, expiration, shielded, attributes, predefined, handle, notices, process, faulty, unmanaged, affect, preserved, turn, off, alternate, fails, repairing, upgrades, selectively, applying, accelerate, out, outage, rebalance, reenable, proactive, distribute, define, info, accidental, deletion, spread, rename, reset, resume, restart, referrers, uuid, recover, corrupted, duplicate, clones, alerts, backups, vss, regionally, different, protection, considerations, synchronous, consistency, failback, replicate, provisioned, iops, limits, evaluate, help, kms, customer, supplied, symbolic, links, practice, ram, exapools, ptr, record, failure, rates, tags, restrict, automate, password, require, powershell, sac, securely, apps, root, vpn, bastion, iap, connection, only, browser, connections, networks, within, iso, imported, prerequisites, importing, exporting, bring, own, path, detach, reattach, constraint, accounting, provision, examples, slurm, reserved, team, slice, slices, adds, scenarios, deterministic, base, requirements, ready, aci, configured, preempted, historical, alternative, similar, displays, ops, logging, subnet, public, gpudirect, enabled, ultra, hostname, quickstarts, iam, roles, permissions, office, licensing, premium, strategy, gemini, bare, metal, accelerators, platforms, scores, purpose, discover, free, skip, main,
Text of the page (random words):
le tenant vms manual live migration about manual live migration manually live migrate vms share sole tenant node groups next generation dynamic resource management cost savings get discounts for committed usage about commitments and committed use discounts cuds resource based cuds purchase resource based commitments without attached reservations with attached reservations for os licenses manage resource based commitments renew commitments automatically extend commitment terms merge and split commitments upgrade commitments share resource based cuds across projects get discounts for sustained usage disk performance optimize hyperdisk performance optimize persistent disk performance optimize local ssd performance workload performance set the number of threads per core customize the number of visible cpu cores analyze the cpu performance using the pmu pmu overview enable the pmu in vms manage the pmu in vms network performance network bandwidth use google virtual nic use irdma network driver use idpf network interface configure a vm with higher bandwidth reduce latency by using compact placement policies optimize tcp network communication optimize tcp network performance optimize tcp network resiliency benchmark higher bandwidth vms optimize app latency with load balancing use dpdk to improve network performance network performance and gpu vms networking and gpu machines use higher network bandwidth patterns for using multiple host nics troubleshoot general tips troubleshoot connectivity troubleshoot rdp troubleshoot ssh troubleshoot os login troubleshoot vms troubleshoot vm operations troubleshoot vm creation troubleshoot resource availability errors troubleshoot bulk api vm creation troubleshoot vm reboots and shutdowns troubleshoot vm suspension troubleshoot vm updates troubleshoot unresponsive vms troubleshoot vm startup troubleshoot fstab errors troubleshoot kernel panic collecting core dumps rescue an inaccessible vm troubleshoot cpu bus locks troubleshoot cpu soft lockups troubleshoot vm configurations troubleshoot arm vms troubleshoot gpu vms troubleshoot nvidia gpu errors generate a nvidia bug report for blackwell gpus troubleshoot nested virtualization troubleshoot using vm screenshots troubleshoot sole tenant nodes troubleshoot vm performance issues troubleshoot sudoers files troubleshoot windows vms troubleshoot windows vms collecting diagnostic information troubleshoot using the serial console troubleshoot using the serial console viewing serial port output troubleshoot instance groups troubleshoot managed instance groups migs troubleshoot os management troubleshoot licenses troubleshoot image import and export troubleshooting sles pay as you go registration troubleshooting ubuntu pro registration troubleshoot metadata server troubleshoot metadata server troubleshoot networking issues troubleshoot common networking issues troubleshoot network drivers troubleshoot vm performance issues troubleshoot storage troubleshoot disk creation troubleshoot full disks and disk resizing troubleshoot disk encryption troubleshoot nvme disks troubleshoot instant snapshots troubleshoot standard snapshots troubleshoot reservations and commitments troubleshoot reservation creation troubleshoot reservation consumption troubleshooting reservation monitoring troubleshoot reservation updates troubleshoot future reservation creation and updates troubleshoot automatic commitment renewal troubleshoot quota errors troubleshoot concurrent operation quota errors troubleshoot workload authentication troubleshoot default service accounts troubleshoot workload to workload authentication ai and ml application development application hosting compute data analytics and pipelines databases distributed hybrid and multicloud industry solutions migration networking observability and monitoring security storage access and resources management costs and usage management infrastructure as code sdk languages frameworks and tools home documentation compute compute engine guides send feedback add instance flexibility stay organized with collections save and categorize content based on your preferences this document describes how to add instance flexibility that lets you set multiple machine types in a mig you can add instance flexibility when creating a mig or by editing an existing mig to add the flexibility configure an instance flexibility policy in the mig the policy overrides the machine type specified in the instance template each time the mig creates a virtual machine vm instance it automatically selects one of the machine types you ve listed in the policy based on resource availability you can also assign ranks to the lists of machine types to indicate your preference to know how instance flexibility works in a mig see about instance flexibility before you begin verify that you choose machine types that are supported in the region where your mig is located to see the machine types in a region see available regions and zones if you want to create spot vms in a mig then view the availability of resources before you add vms to the mig checking the availability of resources helps reduce your chances of encountering resource availability errors for instructions see view resource availability of spot vms if you haven t already set up authentication authentication verifies your identity for access to google cloud services and apis to run code or samples from a local development environment you can authenticate to compute engine by selecting one of the following options select the tab for how you plan to use the samples on this page console when you use the google cloud console to access google cloud services and apis you don t need to set up authentication gcloud install the google cloud cli after installation initialize the google cloud cli by running the following command gcloud init if you re using an external identity provider idp you must first sign in to the gcloud cli with your federated identity note if you installed the gcloud cli previously make sure you have the latest version by running gcloud components update set a default region and zone terraform to use the terraform samples on this page in a local development environment install and initialize the gcloud cli and then set up application default credentials with your user credentials install the google cloud cli if you re using an external identity provider idp you must first sign in to the gcloud cli with your federated identity if you re using a local shell then create local authentication credentials for your user account gcloud auth application default login you don t need to do this if you re using cloud shell if an authentication error is returned and you are using an external identity provider idp confirm that you have signed in to the gcloud cli with your federated identity for more information see set up authentication for a local development environment rest to use the rest api samples on this page in a local development environment you use the credentials you provide to the gcloud cli install the google cloud cli if you re using an external identity provider idp you must first sign in to the gcloud cli with your federated identity for more information see authenticate for using rest in the google cloud authentication documentation create a mig with instance flexibility before creating a mig you must first create an instance template if you don t already have one you can then create a mig with instance flexibility to override the machine type specified in the instance template create a mig with instance flexibility in one of the following ways use multiple machine types use multiple machine types and preferences create a mig with multiple machine types console in the google cloud console go to the instance groups page go to instance groups click create instance group in the name field enter a name for the mig in the instance template list select the instance template that you want to use for the mig before you can specify the number of instances and add instance selections you need to do the following go to the location section on the page and set a location as follows select multiple zones in the regions and the zones drop downs select a region and the zones in which you want to create the vms in the mig if you selected a regional instance template then the region of that template is selected by default in the target distribution shape field select balanced any or any single zone if you select balanced or any single zone then in the dialog that opens click disable instance redistribution if you select any then make sure that the allow instance redistribution checkbox is not selected go to the autoscaling section on the page and delete the autoscaling configuration as follows in the autoscaling mode drop down click delete autoscaling configuration in the dialog that opens click delete scroll back to the number of instances field in the number of instances field specify the number of vms that you want in the group in the instance selections section click add selections the instance selections window opens click add instance selection in the new instance selection section do the following in the name field enter a name for the instance selection in the machine types section click add machine type select a machine type that you want to add in the instance selection and then click done repeat this step for each machine type that you want to add to the instance selection after you complete adding the machine types click done in the instance selections window click done leave the other fields in their default settings or modify as needed click create gcloud to create a regional mig with multiple machine types use the instance groups managed create command as follows gcloud compute instance groups managed create instance_group_name region region size target_size template instance_template_url target distribution shape shape instance redistribution type none instance selection machine types machine_type machine_type zonal migs don t support instance flexibility however if you want to create a mig in a single zone set the target distribution shape to any single zone furthermore if you want a specific zone use the any single zone distribution shape and include the zones zone flag replace the following instance_group_name the name of the mig region the region where you want to create the mig target_size the number of vms you want the mig to create and maintain instance_template_url the url of the instance template that you want to use to create instances in the mig the url can contain either the id or name of the instance template specify one of the following values for a regional instance template projects project_id regions region instancetemplates instance_template_id for a global instance template instance_template_id shape the target distribution shape the value can be balanced any or any single zone machine_type the machine types that you want to configure in the mig for example n1 standard 16 n2 standard 16 e2 standard 16 terraform if you haven t already created an instance template which specifies the vm properties that you want for each vm in your mig create an instance template to create a regional mig with multiple machine types use the google_compute_region_instance_group_manager resource resource google_compute_region_instance_group_manager default name flex igm base_instance_name tf test flex igm region us central1 target_size 3 distribution_policy_target_shape any_single_zone version instance_template google_compute_instance_template default id instance_flexibility_policy instance_selections name default instance selection machine_types n1 standard 16 n2 standard 16 e2 standard 16 update_policy instance_redistribution_type none type opportunistic minimal_action replace max_surge_fixed 0 max_unavailable_fixed 6 to learn how to apply or remove a terraform configuration see basic terraform commands rest to create a regional mig with multiple machine types make a post request to the regioninstancegroupmanagers insert method post https compute googleapis com compute v1 projects project_id regions region instancegroupmanagers name instance_group_name targetsize target_size instancetemplate instance_template_url distributionpolicy targetshape shape updatepolicy instanceredistributiontype none instanceflexibilitypolicy instanceselections instance_selection machinetypes machine_type_1 machine_type_2 zonal migs don t support instance flexibility however if you want to create a mig in a single zone set the target distribution shape to any_single_zone furthermore if you want a specific zone use the any_single_zone distribution shape and include the distributionpolicy zones zone field in the request replace the following project_id your project id region the region where you want to create the mig instance_group_name the name of the mig target_size the number of vms you want the mig to create and maintain instance_template_url the url of the instance template that you want to use to create instances in the mig the url can contain either the id or name of the instance template specify one of the following values for a regional instance template projects project_id regions region instancetemplates instance_template_id for a global instance template instance_template_id shape the target distribution shape the value can be balanced any or any_single_zone instance_selection the name for the list of machine types machine_type the machine types that you want to configure in the mig for example n1 standard 16 n2 standard 16 e2 standard 16 create a mig with multiple machine types and preferences console in the google cloud console go to the instance groups page go to instance groups click create instance group in the name field enter a name for the mig in the instance template list select the instance template that you want to use for the mig before you can specify the number of instances and add instance selections you need to do the following go to the location section on the page and set a location as follows select multiple zones in the regions and the zones drop downs select a region and the zones in which you want to create the vms in the mig if you selected a regional instance template then the region of that template is selected by default in the target distribution shape field select balanced any or any single zone if you select balanced or any single zone then in the dialog that opens click disable instance redistribution if you select any then make sure that the allow instance redistribution checkbox is not selected go to the autoscaling section on the page and delete the autoscaling configuration as follows in the autoscaling mode drop down click delete autoscaling configuration in the dialog that opens click delete scroll back to the number of instances field in the number of instances field specify the number of vms that you want in the group in the instance selections secti...
|
