Meta tags:
Headings (most frequently used words):
and, instance, flexibility, how, overrides, machine, mig, selects, types, example, for, about, in, migs, stay, organized, with, collections, save, categorize, content, based, on, your, preferences, works, reservations, spot, vms, vm, repairs, autoscaling, use, cases, limitations, what, next, mincpuplatform, disks, work, zones, improve, obtainability, optimize, costs, maximize, performance, seamless, transition, to, latest, products, pricing, support, resources, engage, type, minimum, cpu, platform, disk,
Text of the page (most frequently used words):
the (241), and (145), #instance (143), vms (130), create (126), for (123), machine (121), mig (120), with (107), about (72), types (67), you (66), troubleshoot (62), disks (54), disk (53), using (51), #flexibility (49), that (48), configure (48), manage (46), use (46), performance (43), can (43), type (43), view (42), server (39), your (33), reservation (33), windows (33), cloud (31), selection (31), overview (31), set (30), from (30), compute (29), reservations (28), google (27), cpu (25), configuration (25), when (25), based (25), availability (25), images (25), engine (23), resources (22), zones (22), hyperdisk (22), different (21), sql (21), this (20), instances (20), monitor (20), standard (19), gpu (19), workload (19), image (19), network (19), multiple (18), resource (18), boot (18), all (17), machines (17), specify (17), apply (17), regional (17), rank (17), selects (17), then (17), groups (17), access (17), linux (17), see (16), more (16), policies (16), load (16), migs (16), available (16), spot (16), creation (16), template (16), preference (15), properties (15), best (15), custom (15), virtual (15), snapshots (15), ssh (15), recommendations (15), across (14), host (14), connect (14), information (13), add (13), override (13), distribution (13), delete (13), how (13), storage (13), management (13), bulk (13), microsoft (13), cluster (13), choose (12), stateful (12), following (12), target (12), shape (12), single (12), zone (12), platform (12), ranks (12), application (12), sole (12), persistent (12), autoscaling (11), example (11), updates (11), any (11), capacity (11), overrides (11), within (11), high (11), time (11), uses (11), managed (11), practices (11), workloads (11), higher (10), machinetypes (10), mincpuplatform (10), start (10), specific (10), cost (10), minimum (10), run (10), service (10), metadata (10), attached (10), migrate (10), logs (10), support (9), balancing (9), selections (9), existing (9), enable (9), select (9), generation (9), optimize (9), keys (9), licenses (9), tenant (9), openshift (9), shutdown (9), hpc (9), are (8), license (8), local (8), ssd (8), automatically (8), templates (8), zonal (8), region (8), remove (8), group (8), list (8), scale (8), import (8), login (8), internal (8), install (8), disaster (8), recovery (8), agent (8), update (8), guest (8), h4d (8), dns (8), optimized (8), tpu (8), thumb (7), has (7), same (7), also (7), policy (7), first (7), lowest (7), most (7), follows (7), configured (7), default (7), change (7), projects (7), work (7), applications (7), demand (7), networking (7), commitments (7), startup (7), benchmark (7), manually (7), idle (7), addresses (7), request (7), deploy (7), back (7), mysql (7), maintenance (7), snapshot (7), backup (7), terms (6), events (6), send (6), similar (6), hardware (6), size (6), families (6), have (6), mix (6), which (6), number (6), field (6), repairs (6), limitations (6), automatic (6), don (6), flex (6), creating (6), latest (6), share (6), preferred (6), each (6), location (6), prioritizes (6), autoscaler (6), creates (6), errors (6), balanced (6), instanceselections (6), true (6), debian (6), control (6), usage (6), security (6), migration (6), data (6), instant (6), files (6), nested (6), gpus (6), mode (6), pools (6), failover (6), extension (6), new (6), transfer (6), customized (6), architecture (5), code (5), samples (5), understand (5), details (5), prevent (5), ensure (5), vcpu (5), not (5), those (5), resize (5), requests (5), lower (5), family (5), compatible (5), preemption (5), order (5), improve (5), get (5), repair (5), want (5), global (5), arm (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), modify (5), schedules (5), audit (5), symphony (5), options (5), email (5), scripts (5), manager (5), between (5), operating (5), systems (5), enhanced (5), capabilities (5), stop (5), tenancy (5), restore (5), regions (5), workstation (5), faq (5), português (4), español (4), down (4), need (4), its (4), highest (4), performing (4), utilization (4), per (4), mixing (4), must (4), only (4), fails (4), assign (4), these (4), require (4), configurations (4), sizes (4), possible (4), chances (4), preferences (4), helps (4), infrastructure (4), lets (4), might (4), increase (4), works (4), scales (4), out (4), non (4), section (4), instanceflexibilitypolicy (4), devicename (4), architectures (4), series (4), platforms (4), setting (4), tools (4), distributed (4), authentication (4), issues (4), ubuntu (4), console (4), bandwidth (4), tcp (4), pmu (4), upgrade (4), live (4), cross (4), calendar (4), metrics (4), health (4), active (4), clusters (4), containers (4), container (4), database (4), postgresql (4), extensions (4), suspend (4), graceful (4), locations (4), plans (4), replication (4), review (4), bound (4), other (3), content (3), under (3), apache (3), over (3), help (3), count (3), limited (3), because (3), another (3), skylake (3), attach (3), through (3), include (3), once (3), will (3), provision (3), older (3), always (3), while (3), define (3), core (3), limit (3), selecting (3), maximize (3), settings (3), obtaining (3), where (3), costs (3), rates (3), basic (3), obtainability (3), document (3), specified (3), current (3), considers (3), unused (3), selected (3), autodelete (3), initializeparams (3), sourceimage (3), disksizegb (3), disktype (3), intel (3), x86 (3), additional (3), created (3), general (3), changes (3), guides (3), observability (3), analytics (3), troubleshooting (3), encryption (3), pro (3), serial (3), patterns (3), discounts (3), cuds (3), manual (3), scalable (3), resilient (3), autoscale (3), balancer (3), project (3), testing (3), ibm (3), spectrum (3), perform (3), deploying (3), plan (3), during (3), prepare (3), deployment (3), rhel (3), environment (3), protect (3), certificates (3), query (3), state (3), disable (3), account (3), schedule (3), lifecycle (3), design (3), pool (3), move (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), sign (2), third (2), action (2), site (2), youtube (2), center (2), started (2), system (2), pricing (2), products (2), last (2), updated (2), 2026 (2), utc (2), otherwise (2), licensed (2), feedback (2), next (2), deletion (2), effective (2), however (2), newer (2), generations (2), typically (2), counts (2), one (2), allow (2), configuring (2), without (2), operation (2), error (2), overriding (2), even (2), doesn (2), features (2), instead (2), ensures (2), ensuring (2), requested (2), total (2), fallback (2), containing (2), second (2), serve (2), transition (2), specifying (2), offer (2), achieve (2), such (2), obtain (2), needs (2), minimize (2), their (2), disruption (2), rate (2), allows (2), them (2), equal (2), cases (2), behavior (2), checks (2), deleting (2), ranked (2), repairing (2), stockout (2), attempts (2), unavailable (2), enabled (2), instructions (2), reduce (2), least (2), matches (2), any_single_zone (2), diskencryptionkey (2), machinetype (2), know (2), selectively (2), note (2), defined (2), corresponding (2), pre (2), ready (2), operate (2), requirements (2), documentation (2), sdk (2), languages (2), frameworks (2), industry (2), solutions (2), hybrid (2), multicloud (2), pipelines (2), hosting (2), development (2), quota (2), commitment (2), consumption (2), full (2), registration (2), sles (2), export (2), port (2), collecting (2), nodes (2), report (2), api (2), rdp (2), app (2), latency (2), analyze (2), visible (2), cores (2), committed (2), underutilized (2), insights (2), globally (2), web (2), autohealing (2), iis (2), external (2), shared (2), reserve (2), autoscalers (2), activity (2), kubernetes (2), provider (2), place (2), running (2), directory (2), services (2), redis (2), cloning (2), writer (2), alwayson (2), name (2), file (2), volumes (2), authenticate (2), method (2), synchronization (2), switch (2), byol (2), payg (2), byos (2), guide (2), securing (2), event (2), simulate (2), topology (2), together (2), check (2), failures (2), suspended (2), stopped (2), physical (2), cancel (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), credentials (2), organization (2), user (2), advanced (2), rdma (2), preemptible (2), provisioning (2), models (2), rtx (2), vws (2), constraints (2), accelerator (2), apis (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, noted, page, java, registered, trademark, oracle, affiliates, developers, creative, commons, attribution, learn, what, addition, smaller, faster, unique, cannot, broadwell, ssds, variants, lssd, overridden, suspending, stopping, two, canary, updating, searches, find, enough, met, maximizing, newest, prioritize, adoption, seamless, additionally, equivalent, ranking, provisions, combination, meet, criteria, given, increases, they, according, ratio, optimal, preemptions, recommends, many, result, further, chance, choosing, search, setup, gives, letting, sections, describe, some, effectively, attempt, frequently, happen, regardless, finally, recommendation, among, prioritized, preserve, manner, autoscaled, happens, recreating, including, occurs, recreate, original, enabling, recreated, reliability, before, encountering, observed, complete, steps, recommended, any_reservation, affinity, property, balance, evenly, depending, impact, varies, followed, ice, lake, consider, merges, diagram, shows, c4a, separate, technologies, appropriate, required, gains, but, alternatively, supported, creations, fail, level, provides, especially, feature, subject, offerings, launch, stage, descriptions, preview, like, listed, assured, unless, value, means, c2d, c3d, instanceselection, compares, depicted, identical, whereas, specifies, describes, rather, than, being, particularly, large, save, categorize, stay, organized, collections, home, concurrent, renewal, nvme, resizing, 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, resiliency, communication, compact, idpf, interface, irdma, driver, nic, customize, threads, sustained, merge, split, extend, renew, purchase, savings, dynamic, overcommit, cpus, floating, reliable, udp, backends, routing, https, 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, test, hammerdb, bucket, aws, ec2, pacemaker, s2d, block, netapp, hot, standby, drbd, client, private, address, mailjet, mailgun, sendgrid, sending, blue, green, deployments, lamp, joomla, asp, net, interactive, mongodb, flask, terraform, servers, mtls, random, generator, virtio, rng, accurate, protocol, ntp, append, els, after, restrictions, packages, deprecate, versions, trusted, red, hat, knowledgebase, functionality, risks, command, vpc, controls, confidential, kek, secure, expiration, shielded, attributes, predefined, handle, notices, process, faulty, unmanaged, affect, preserved, turn, off, alternate, maintain, click, upgrades, applying, accelerate, outage, rebalance, reenable, proactive, redistribution, distribute, info, accidental, spread, edit, rename, reset, resume, restart, referrers, source, uuid, recover, corrupted, duplicate, clones, alerts, backups, vss, regionally, protection, considerations, synchronous, consistency, failback, replicate, make, provisioned, iops, limits, evaluate, kms, customer, supplied, symbolic, links, practice, device, ram, exapools, verify, identity, ptr, record, failure, tags, restrict, automate, password, powershell, sac, securely, apps, root, vpn, bastion, iap, connection, browser, connections, networks, iso, imported, prerequisites, importing, exporting, bring, own, path, detach, reattach, constraint, accounting, examples, slurm, reserved, team, slice, slices, adds, scenarios, deterministic, base, aci, preempted, historical, alternative, displays, ops, logging, subnet, public, gpudirect, ultra, hostname, quickstarts, iam, roles, permissions, office, licensing, premium, strategy, gemini, bare, metal, accelerators, scores, purpose, discover, free, skip, main,
Text of the page (random words):
ces management costs and usage management infrastructure as code sdk languages frameworks and tools home documentation compute compute engine guides send feedback about instance flexibility in migs stay organized with collections save and categorize content based on your preferences instance flexibility in managed instance groups migs lets you specify multiple machine types for the virtual machine vm instances in the group rather than being limited to a single machine type if a machine type is unavailable the mig can automatically select another compatible type from your list based on the current resource availability this flexibility helps to improve resource obtainability particularly for applications that can operate on different machine types and that require large scale capacity or hardware with high demand this document describes how instance flexibility works in a mig and its limitations to know how to configure a mig to use instance flexibility see add instance flexibility instance flexibility a mig creates all its vms based on the instance template that you select the instance template specifies the machine type to use for each vm with instance flexibility you can list all the machine types that are compatible with your application the following image compares a mig that uses a single machine type with a mig that uses instance flexibility as depicted in the image a mig with a single machine type creates identical vms based on an instance template whereas a mig with instance flexibility can create vms with different machine types and sizes how instance flexibility works by default a mig creates all vms using a single machine type from the instance template you can set multiple machine types in a mig by configuring an instance selection instanceselections in the instance flexibility policy instanceflexibilitypolicy note the instanceselections machinetypes field overrides the machinetype field in your instance template if you want to use the machine type defined in your instance template you must list that machine type in the instanceselections machinetypes field you can also specify machine types that run on different cpu platforms and those with different architectures x86 and arm architecture to use machine types with different requirements for minimum cpu platform or disks use the instance flexibility policy to override corresponding properties from the instance template for more information see how mincpuplatform and disks overrides work example for machine type overrides if your workload can operate on a number of different machine types you can configure a list of all machine types compatible with your application in a single instanceselection as follows instanceflexibilitypolicy instanceselections instance selection 1 machinetypes c2 standard 8 c2d standard 8 c3 standard 8 c3d standard 8 the machine types within an instance selection have equal preference if you want a mig to choose machine types in a specific order you can configure multiple instance selections each with a list of machine types and a rank to define preference a lower value of rank means higher preference the mig attempts to create its vms using machine types with a higher preference if these preferred machine types are not available the mig uses a machine type with a lower preference instanceflexibilitypolicy instanceselections most preferred rank 1 machinetypes c3 standard 8 c2 standard 8 least preferred rank 2 machinetypes n2 standard 16 n1 standard 16 your application needs to be ready to run on any of the listed machine types as the availability of hardware changes over time and specific hardware is not assured unless you use reservations instance selections can also override the instance properties like mincpuplatform and disks for more information see the following section about how instance selection overrides work how mincpuplatform and disks overrides work preview minimum cpu platform and disk overrides this feature is subject to the pre ga offerings terms in the general service terms section of the service specific terms pre ga features are available as is and might have limited support for more information see the launch stage descriptions in an instance selection you can specify additional instance properties such as minimum cpu platform mincpuplatform and disks disks to override those defined in the instance template when a mig selects a machine type from an instance selection the mig creates a vm by using the instance properties specified in that instance selection if you don t specify any of these properties for an instance selection the mig will use the corresponding properties from the template for that selection overriding these properties at the instance selection level provides more control and flexibility especially when using different hardware in a mig note if you specify instance properties that are not supported for the machine types in an instance selection then instance creations using those machine types fail override minimum cpu platform when mixing machine types that run on different cpu platforms you can specify a minimum cpu platform for instances created from the machine types within a selection this override lets you mix different machine types but selectively apply minimum cpu platforms alternatively you can configure the instance selection to automatically select a cpu platform by setting the mincpuplatform field to automatic this automatic selection overrides the instance template s minimum cpu platform setting and allows the mig to use any compatible cpu platform for the selected machine types for example you can mix machine types from n1 and n2 machine series in a selection while ensuring that n1 machines run on intel skylake to achieve performance gains override disks when mixing machine types that have different architectures you can specify a custom disk configuration to override the boot disk or additional disks specified in the instance properties or to attach a specific storage this override lets you mix machine types that have different architectures or those that don t share disk technologies and specify the appropriate boot images or disks required for each machine type for example you can mix c4 x86 architecture and c4a arm architecture machine types as x86 and arm machines require different boot images you can use separate instance selections to override the boot disk for each architecture when you specify the disks for an instance selection the mig merges the disks in the instance template and in the instance selection by their devicename keys the following diagram shows an example to know about the limitations when using instance selection overrides see the limitations section in this document example for minimum cpu platform and disk overrides consider an instance template with the following configuration disks autodelete true devicename boot boot true diskencryptionkey initializeparams sourceimage projects debian cloud global images family debian 12 disksizegb 10 disktype pd balanced machinetype n2 standard 2 the following example of an instance flexibility policy overrides the template configuration by specifying a minimum cpu platform and disk configuration instanceflexibilitypolicy instanceselections first preference rank 1 machinetypes n4 standard 4 disks autodelete true devicename boot boot true diskencryptionkey initializeparams sourceimage projects debian cloud global images family debian 12 disksizegb 10 disktype hyperdisk balanced second preference rank 2 machinetypes n2 standard 4 mincpuplatform intel ice lake disks autodelete true devicename boot boot true initializeparams sourceimage projects debian cloud global images family debian 12 disksizegb 10 disktype pd ssd third preference rank 3 machinetypes n1 standard 4 mincpuplatform intel skylake how a mig selects machine types when you configure multiple machine types the mig selects a machine type based on current resource availability and prioritizes unused reservations if you ve configured ranks the mig first considers your preference order within a ranked instance selection the mig then checks resource availability followed by reservations the zones in the mig s region might also impact the machine type selection because resource availability varies across zones for more information see the following section about how a mig selects zones how a mig selects zones you can configure instance flexibility in a regional mig that has a balanced any or any_single_zone target distribution shape instance flexibility doesn t support even target distribution shape with instance flexibility when a regional mig creates a vm the mig selects a zone depending on the selected target distribution shape as follows balanced the mig selects a zone with available resources that can balance the vm distribution across zones as evenly as possible within a selected zone the mig prioritizes machine types based on ranks if configured and available reservations any the mig selects a zone with available resources and reservations if ranks are configured then the mig prioritizes the zone in which a machine type based on ranks is available any_single_zone the mig selects a zone which has the most machine types based on the ranks if configured and where the mig can create most vms out of unused reservations for more information about how a target distribution shape works see regional mig target distribution shape instance flexibility and reservations you can use instance flexibility with reservations based on the reservation affinity property you set in the instance template a mig uses reservations as follows any_reservation recommended for instance flexibility when using any reservation the mig selects the machine type with unused reservation first if you want to change the order in which the mig selects machine types you can configure multiple instance selections and specify your preference using ranks the mig then first follows the ranks and then considers available reservations for the machine types within a rank specific when using a specific reservation the mig selects the machine type that matches the reservation properties if your instance selections don t include the machine type that matches the specific reservation properties then instance creation fails for more information about reservations see about reservations instance flexibility and spot vms if your mig with instance flexibility uses spot vms then the mig automatically selects a machine type with the lowest observed preemption rate to help ensure the least disruption for your workload if you want to override this behavior then complete the following steps view resource availability before you create a mig with spot vms you can view resource availability in the region or zone where you want to create your mig this action helps reduce your chances of encountering resource availability errors for instructions see view the availability of spot vms configure multiple instance selections you can specify the machine type and zones in which to create spot vms by using ranks the mig then first follows your preference order and then considers the reliability of spot vms within an instance selection for instructions see create a mig with multiple machine types and preferences for more information about using spot vms in a mig see spot vms in a managed instance group instance flexibility and vm repairs by default if a vm in a mig fails the mig repairs the vm by recreating it using the same configuration including the machine type if you configure instance flexibility and enable updates on repair then you can improve the chances to obtain resources if a stockout occurs when a mig attempts to recreate a vm if the original machine type of the vm is unavailable then you will get a stockout error with updates on repair enabled the mig then uses your specified instance selections and current availability to choose another machine type for the vm creation enabling updates on repair also helps to ensure that the recreated vm uses the latest instance flexibility configuration for more information about repairs see about repairing vms for high availability instance flexibility and autoscaling when you configure autoscaling in a mig that has multiple machine types the following happens when an autoscaler scales out a mig the mig creates vms by selecting machine types in the same manner as in a non autoscaled mig for more information see the how a mig selects machine types in this document when an autoscaler scales in a mig the mig selects the vms to delete as follows the mig first prioritizes deleting vms that best preserve the target distribution shape if you configured ranks then among the prioritized vms the mig prioritizes deleting vms that use lower ranked machine types finally the mig checks the autoscaler recommendation to select the vms to delete autoscaling works effectively when your mig has machine types of similar performance for example machines with the same vcpu count otherwise when the mig scales out or scales in the autoscaler might attempt to add or remove the highest performing machine type more frequently this behavior can happen regardless of the rank that you configured for that machine type for more information about autoscaling see autoscaling groups of instances use cases the following sections describe some use cases of instance flexibility in migs improve obtainability you can configure mig instance flexibility to improve resource obtainability machine types the basic setup is to configure multiple machine types within a single rank this single rank gives them equal preference letting the mig select any of them based on resource availability however if you have preferences then you can assign different ranks to specify a preference order for the machine types location you can further increase the chance of obtaining the resources by choosing all zones when creating your mig and using the any target distribution shape the any shape allows the mig to search for capacity across all zones spot vms and preemption when you use spot vms to maximize the chances of obtaining the vms and to minimize their preemptions google recommends that you include as many compatible machine types as possible within the same rank this configuration lets mig choose machine types with the lowest preemption rates to minimize disruption for your workload if you configure machine types with different ranks then mig prioritizes machine types based on rank instead of preemption rates which might result in selecting a machine type with a higher preemption rate optimize costs a mig can automatically provision the most cost effective instances for your infrastructure when you configure the instance flexibility settings of your mig as follows machine types select the machine types that offer the preferred cost performance ratio for your workload you don t need to specify all the available sizes of each machin...
|
