Meta tags:
description=Learn to create future reservation requests in calendar mode to reserve H4D HPC VMs, GPU VMs, or TPUs for AI, ML, or HPC workloads.;

Headings (most frequently used words):

create, future, request, console, gcloud, rest, reservation, in, calendar, mode, and, required, vms, stay, organized, with, collections, save, categorize, content, based, on, your, preferences, before, you, begin, what, next, roles, view, resource, availability, for, gpu, h4d, or, tpus, products, pricing, support, resources, engage, permissions,

Text of the page (most frequently used words):
the (275), create (163), and (159), vms (158), for (147), you (96), with (89), #reservation (74), gpu (63), about (62), troubleshoot (62), h4d (57), view (56), compute (55), request (51), use (51), specify (49), instance (49), manage (47), reserve (47), machine (47), time (45), resources (44), future (44), your (43), that (43), using (43), disk (43), cloud (40), tpu (40), google (39), server (39), following (35), disks (35), windows (33), mig (33), set (32), configure (32), calendar (31), mode (31), capacity (31), performance (31), overview (31), reservations (30), type (30), projects (30), engine (29), availability (27), number (25), zone (25), from (25), must (24), can (24), zones (24), start (23), tpus (22), want (22), region (22), access (22), hyperdisk (21), sql (21), project (20), monitor (20), images (20), this (19), share (19), network (19), one (18), available (17), types (17), instances (17), image (17), linux (17), policies (16), value (16), include (16), based (16), configuration (16), recommendations (16), when (15), gcloud (15), select (15), custom (15), apply (15), virtual (15), snapshots (15), groups (15), ssh (15), host (15), delete (14), then (14), name (14), workloads (14), workload (14), creation (14), load (14), connect (14), see (13), high (13), between (13), management (13), bulk (13), microsoft (13), cluster (13), add (12), digit (12), hpc (12), storage (12), sole (12), persistent (12), best (12), regional (12), other (11), details (11), 256 (11), these (11), reserved (11), existing (11), console (11), resource (11), practices (11), stateful (11), are (10), requests (10), format (10), duration (10), version (10), requested (10), values (10), fields (10), install (10), metadata (10), migs (10), machines (10), attached (10), migrate (10), logs (10), status (9), more (9), consume (9), end (9), seconds (9), replace (9), field (9), chips (9), modify (9), within (9), local (9), click (9), options (9), choose (9), flexibility (9), optimized (9), gpus (9), regions (9), run (9), update (9), cpu (9), application (9), licenses (9), managed (9), tenant (9), multiple (9), openshift (9), shutdown (9), samples (8), license (8), tpu_version (8), number_of_chips (8), machine_type (8), number_of_vms (8), two (8), only (8), organization (8), default (8), list (8), count (8), hours (8), location (8), central1 (8), offset (8), permissions (8), authentication (8), service (8), import (8), login (8), optimize (8), internal (8), disaster (8), recovery (8), agent (8), guest (8), boot (8), keys (8), dns (8), thumb (7), information (7), example (7), period (7), endtime (7), than (7), shared (7), where (7), days (7), advice (7), get (7), required (7), cli (7), demand (7), networking (7), commitments (7), startup (7), balancing (7), benchmark (7), enable (7), manually (7), idle (7), addresses (7), scale (7), deploy (7), back (7), mysql (7), zonal (7), remove (7), maintenance (7), templates (7), snapshot (7), backup (7), events (6), code (6), 2026 (6), send (6), auto (6), created (6), which (6), rfc (6), 3339 (6), end_time (6), start_time (6), after (6), share_type (6), automatically (6), reservation_name (6), future_reservation_name (6), project_id (6), starttime (6), review (6), flags (6), how (6), date (6), properties (6), max_duration (6), min_duration (6), formatted (6), to_start_time (6), from_start_time (6), roles (6), identity (6), errors (6), usage (6), security (6), migration (6), data (6), updates (6), instant (6), files (6), nested (6), across (6), applications (6), multi (6), group (6), pools (6), failover (6), extension (6), change (6), new (6), transfer (6), customized (6), spot (6), understand (5), page (5), 1024 (5), 512 (5), 128 (5), confirmed (5), post (5), https (5), rest (5), separated (5), deployment (5), supported (5), output (5), latest (5), environment (5), plan (5), team (5), account (5), single (5), monitoring (5), databases (5), accounts (5), drivers (5), virtualization (5), nvidia (5), operations (5), placement (5), node (5), highly (5), build (5), schedules (5), audit (5), symphony (5), email (5), scripts (5), manager (5), operating (5), systems (5), enhanced (5), capabilities (5), stop (5), tenancy (5), restore (5), control (5), workstation (5), faq (5), flex (5), português (4), español (4), sign (4), support (4), all (4), down (4), need (4), utc (4), otherwise (4), jobs (4), ultra (4), next (4), timestamp (4), equal (4), lower (4), sharesettings (4), settings (4), important (4), provision (4), googleapis (4), com (4), futurereservations (4), true (4), submitted (4), vmfamily (4), acceleratorcount (4), machinetype (4), dense (4), submit (4), make (4), method (4), specific (4), setting (4), chip (4), command (4), section (4), reserving (4), reference (4), configurations (4), minimum (4), maximum (4), earliest (4), spec (4), 00z (4), standard (4), hour (4), minutes (4), yyyy (4), dates (4), highgpu (4), check (4), calendarmode (4), range (4), services (4), apis (4), development (4), authenticate (4), external (4), provider (4), running (4), quota (4), creating (4), tools (4), distributed (4), issues (4), ubuntu (4), bandwidth (4), tcp (4), pmu (4), ssd (4), upgrade (4), live (4), autoscaling (4), cross (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), resize (4), graceful (4), locations (4), plans (4), replication (4), bound (4), terms (3), training (3), contact (3), sales (3), content (3), apache (3), inference (3), methods (3), mega (3), consumer_project_id_2 (3), consumer_project_id_1 (3), sharetype (3), specific_projects (3), submission (3), 100 (3), don (3), creates (3), accelerator (3), flag (3), require (3), total (3), complete (3), steps (3), tab (3), contains (3), free (3), family (3), not (3), similar (3), day (3), v5p (3), v6e (3), tpu7x (3), limitations (3), predefined (3), user (3), documentation (3), api (3), credentials (3), have (3), guides (3), infrastructure (3), observability (3), analytics (3), automatic (3), troubleshooting (3), encryption (3), pro (3), serial (3), patterns (3), higher (3), discounts (3), cuds (3), manual (3), scalable (3), resilient (3), autoscale (3), balancer (3), prevent (3), policy (3), testing (3), ibm (3), spectrum (3), perform (3), deploying (3), during (3), prepare (3), rhel (3), protect (3), certificates (3), query (3), state (3), disable (3), schedule (3), lifecycle (3), design (3), size (3), non (3), pool (3), move (3), workstations (3), series (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), licensed (2), under (2), feedback (2), instead (2), ids (2), allow (2), projectmap (2), projectid (2), whether (2), autodeleteautocreatedreservations (2), planningstatus (2), reservationmode (2), reservationname (2), specificreservationrequired (2), timewindow (2), totalcount (2), deploymenttype (2), body (2), planning (2), enter (2), search (2), exact (2), least (2), follows (2), recommendationsperspec (2), recommendationid (2), recommendationtype (2), future_reservation (2), otherlocations (2), recommended (2), recommendation (2), possible (2), no_capacity (2), temporarily (2), window (2), not_supported (2), 10t00 (2), 07t00 (2), amount (2), followed (2), pacific (2), pst (2), coordinated (2), universal (2), colons (2), year (2), month (2), hyphens (2), timestamps (2), megagpu (2), ultragpu (2), futureresourcesspecs (2), targetresources (2), timerangespec (2), starttimenotearlierthan (2), starttimenotlaterthan (2), minduration (2), maxduration (2), instancecount (2), four (2), min (2), max (2), document (2), advance (2), instructions (2), approves (2), skip (2), note (2), might (2), role (2), iam (2), idp (2), first (2), federated (2), verify (2), fails (2), requirements (2), model (2), sdk (2), languages (2), frameworks (2), costs (2), industry (2), solutions (2), hybrid (2), multicloud (2), pipelines (2), hosting (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), general (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), autoscaler (2), autoscalers (2), activity (2), kubernetes (2), place (2), directory (2), redis (2), cloning (2), writer (2), always (2), alwayson (2), file (2), volumes (2), synchronization (2), global (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), repair (2), failures (2), template (2), suspended (2), stopped (2), target (2), distribution (2), physical (2), cancel (2), once (2), limit (2), interfaces (2), ipv6 (2), static (2), decrease (2), increase (2), basic (2), consistent (2), scoped (2), copy (2), appliances (2), asynchronous (2), throughput (2), encrypt (2), names (2), mount (2), memory (2), extreme (2), balanced (2), through (2), advanced (2), rdma (2), slice (2), preemptible (2), provisioning (2), models (2), rtx (2), vws (2), constraints (2), technology (2), areas (2), close (2), subscribe, newsletter, our, third, decade, climate, action, join, cookies, privacy, tech, twitter, blog, engage, certification, architecture, getting, github, release, notes, community, forums, marketplace, easy, easytounderstand, solved, problem, solvedmyproblem, otherup, hard, hardtounderstand, incorrect, sample, incorrectinformationorsamplecode, missing, missingtheinformationsamplesineed, otherdown, tell, except, noted, java, registered, trademark, oracle, its, affiliates, developers, creative, commons, attribution, online, vertex, what, aggregatereservation, reservedresources, specificskuproperties, instanceproperties, well, insert, comma, follow, prompts, table, contain, long, optional, needs, needed, lists, directly, doing, appears, pane, selected, hardware, add_box, a21a2fa0, 72c7, 4105, 8179, 88de5409890b, 400, 86400s, vm_family_cloud_tpu_pod_slice_ct5p, vm_family_cloud_tpu_lite_pod_slice_ct6e, vm_family_cloud_tpu_pod_slice_tpu7x, beta, aggregateresources, specificskuresources, 0d3f005d, f952, 4fce, 96f2, 6af25e1591eb, respectively, three, 1d2h3m4s, 24h, greater, 120, successfully, minute, step, while, likely, approve, supply, also, able, let, expand, ask, administrator, grant, granting, folders, organizations, futurereservationuser, haven, already, verifies, selecting, provide, installed, previously, sure, components, init, installation, initialize, will, encounter, allowed, sufficient, isn, eligible, feature, case, before, begin, longer, become, specified, delivery, any, same, learn, short, term, increases, computing, simulation, fine, tuning, pre, explains, obtain, save, categorize, preferences, stay, organized, collections, home, concurrent, operation, renewal, nvme, resizing, common, pay, viewing, 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, reduce, 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, combine, cud, sharing, decisions, signals, serving, predictions, organize, labels, replica, states, observe, reports, tensorflow, tensorrt5, learning, monte, carlo, spark, forwarding, others, integrate, clustering, exchange, 2016, sharepoint, strategies, passive, inactive, setups, built, integrations, validation, were, deployed, transition, test, 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, terraform, 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, handle, notices, process, faulty, unmanaged, affect, preserved, turn, off, alternate, repairing, maintain, upgrades, override, selectively, applying, accelerate, out, outage, rebalance, reenable, proactive, redistribution, shape, distribute, define, info, accidental, deletion, spread, edit, rename, reset, resume, restart, referrers, source, 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, device, ram, attach, additional, exapools, ptr, record, failure, rates, 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, slices, adds, scenarios, deterministic, base, ready, aci, configured, preempted, historical, alternative, displays, ops, logging, subnet, public, has, gpudirect, enabled, platform, hostname, quickstarts, office, licensing, premium, strategy, gemini, bare, metal, accelerators, platforms, scores, purpose, discover, main,

Text of the page (random words):
ompute advice calendar mode chip count number_of_chips tpu version tpu_version region region start time range from from_start_time to to_start_time duration range min min_duration max max_duration replace the following number_of_vms the number of vms to reserve the value must be at least 1 and no greater than 80 for gpu vms or 256 for h4d vms machine_type the gpu or h4d machine type to reserve specify one of the following values for a4 machine types specify a4 highgpu 8g for a3 ultra machine types specify a3 ultragpu 8g for a3 mega machine types specify a3 megagpu 8g for a3 high machine types with 8 gpus specify a3 highgpu 8g for h4d hpc machine types see h4d machine types number_of_chips the number of tpu chips to reserve the value must be 1 4 8 16 32 64 128 256 512 or 1024 tpu_version the tpu version to reserve specify one of the following values for tpu7x tpu7x for tpu v6e v6e for tpu v5p v5p region the region where to reserve gpu vms h4d vms or tpus to check which regions and zones are supported see limitations from_start_time and to_start_time the earliest and latest dates that you want to reserve capacity on format these dates as rfc 3339 timestamps yyyy mm dd t hh mm ss offset replace the following yyyy mm dd a date formatted as a four digit year two digit month and a two digit day separated by hyphens hh mm ss a time formatted as a two digit hour using a 24 hour time two digit minutes and two digit seconds separated by colons offset the time zone formatted as an offset of coordinated universal time utc for example to use the pacific standard time pst specify 08 00 to use no offset specify z min_duration and max_duration the minimum and maximum amount of time that you want to reserve resources for you must format these values as the number of days hours minutes or seconds followed by d h m and s respectively for example specify 24h for 24 hours or 1d2h3m4s for one day two hours three minutes and four seconds the output is similar to the following recommendationsperspec spec endtime 2026 02 10t00 00 00z location zones us central1 a otherlocations zones us central1 b details recommendation in this zone is possible status recommended zones us central1 c details temporarily no free capacity in this zone in the requested time window status no_capacity zones us central1 f details this machine family is not supported in this zone status not_supported recommendationid 0d3f005d f952 4fce 96f2 6af25e1591eb recommendationtype future_reservation starttime 2026 02 07t00 00 00z if your requested resources are available then the output contains the starttime endtime and location fields these fields specify the earliest start time the latest end time and the zones when resources are available rest to view gpu vm h4d vm or tpu future availability in a region make a get request to the advice calendarmode method based on the resources that you want to view include the following fields in the request body to view gpu vm or h4d vm availability include the instancecount and machinetype fields post https compute googleapis com compute v1 projects project_id regions region advice calendarmode futureresourcesspecs spec targetresources specificskuresources instancecount number_of_vms machinetype machine_type timerangespec starttimenotearlierthan from_start_time starttimenotlaterthan to_start_time minduration min_duration maxduration max_duration to view tpu availability include the acceleratorcount and vmfamily fields post https compute googleapis com compute beta projects project_id regions region advice calendarmode futureresourcesspecs spec targetresources aggregateresources acceleratorcount number_of_chips vmfamily tpu_version timerangespec starttimenotearlierthan from_start_time starttimenotlaterthan to_start_time minduration min_duration maxduration max_duration replace the following project_id the id of the project where you want to reserve resources region the region where you want to reserve gpu vms h4d vms or tpus to check the regions and zones that are supported see limitations number_of_vms the number of gpu or h4d vms to reserve for gpu vms the value must be between 1 and 80 for h4d vms the value must be between 1 and 256 machine_type the gpu or h4d machine type to reserve specify one of the following values for a4 machine types specify a4 highgpu 8g for a3 ultra machine types specify a3 ultragpu 8g for a3 mega machine types specify a3 megagpu 8g for a3 high machine types with 8 gpus specify a3 highgpu 8g for h4d hpc machine types see h4d machine types number_of_chips the number of tpu chips to reserve the value must be 1 4 8 16 32 64 128 256 512 or 1024 tpu_version the tpu version to reserve specify one of the following values for tpu7x vm_family_cloud_tpu_pod_slice_tpu7x for tpu v6e vm_family_cloud_tpu_lite_pod_slice_ct6e for tpu v5p vm_family_cloud_tpu_pod_slice_ct5p from_start_time and to_start_time the earliest and latest dates that you want to reserve capacity on format these dates as rfc 3339 timestamps yyyy mm dd t hh mm ss offset replace the following yyyy mm dd a date formatted as a 4 digit year 2 digit month and a 2 digit day separated by hyphens hh mm ss a time formatted as a 2 digit hour using a 24 hour time 2 digit minutes and 2 digit seconds separated by colons offset the time zone formatted as an offset of coordinated universal time utc for example to use the pacific standard time pst specify 08 00 to use no offset specify z min_duration and max_duration the minimum and maximum amount of time in seconds that you want to reserve resources for you must format these values as the number of seconds followed by s for example specify 86400s for 86 400 seconds 24 hours the output is similar to the following recommendations recommendationsperspec spec recommendationid a21a2fa0 72c7 4105 8179 88de5409890b recommendationtype future_reservation starttime 2026 02 07t00 00 00z endtime 2026 02 10t00 00 00z otherlocations zones us central1 b status recommended details recommendation in this zone is possible zones us central1 c status no_capacity details temporarily no free capacity in this zone in the requested time window zones us central1 f status not_supported details this machine family is not supported in this zone location zones us central1 a if your requested resources are available then the output contains the starttime endtime and location fields these fields specify the earliest start time the latest end time and the zones when resources are available create a request for gpu vms h4d vms or tpus when you create a future reservation request in calendar mode you must specify a reservation period as follows start time based on the resources that you want to reserve you must specify a start time that is at least one of the following values from when you create and submit a request for gpu and h4d vms 87 hours 3 days and 15 hours for tpus 6 hours duration you can reserve resources for a minimum of 24 hours and a maximum of 90 days to create a request by using an existing gpu or h4d vm as reference use the google cloud console otherwise select one of the following options console in the google cloud console go to the reservations page go to reservations click the future reservations tab click add_box create future reservation the create a future reservation page appears and the hardware configuration pane is selected in the configurations section specify the properties of the gpu vms h4d vms or tpus that you want to reserve by doing one of the following to specify gpu vm h4d vm or tpu properties directly complete the following steps select specify machine type click the gpus tpus or compute optimized tab and then select a supported gpu machine type h4d machine type or tpu version to specify gpu or h4d vm properties by using an existing vm as reference select use existing vm and then select the vm in the search for capacity section complete the following steps in the region and zone lists select the region and zone where you want to reserve resources in the total capacity needed field when reserving gpu or h4d vms or number of chips list when reserving tpus specify the number of gpu vms h4d vms or tpu chips to reserve you can specify the following values for gpu vms a value between 1 and 80 for h4d vms a value between 1 and 256 for tpu chips a value of 1 4 8 16 32 64 128 256 512 or 1024 in the start time list select the start time for your request optional in the choose your start date flexibility list select how exact your start date needs to be in the reservation duration field specify for how long you want to reserve resources click search for capacity then in the available capacity table select one of the available options that contain the type number and reservation period of the gpu vms h4d vms or tpus to reserve click next in the share type section select the projects to share your requested capacity with to use the reserved capacity only within your project select local to share the reserved capacity with other projects select shared click add add projects and then follow the prompts to select the projects important you can only specify the share type and shared projects when you create a request you can t modify these settings after submission click next in the future reservation name field enter a name for the request in the reservation name field enter the name of the reservation that compute engine automatically creates to provision your requested capacity click create gcloud to create a future reservation request in calendar mode and submit it for review use the gcloud compute future reservations create command based on the resources that you want to reserve include the following flags to reserve gpu or h4d vms include the total count machine type and deployment type dense flags gcloud compute future reservations create future_reservation_name auto delete auto created reservations total count number_of_vms machine type machine_type deployment type dense planning status submitted require specific reservation reservation mode calendar reservation name reservation_name share setting share_type start time start_time end time end_time zone zone to reserve tpus include the chip count and tpu version flags gcloud compute future reservations create future_reservation_name auto delete auto created reservations chip count number_of_chips tpu version tpu_version planning status submitted require specific reservation reservation mode calendar reservation name reservation_name share setting share_type start time start_time end time end_time zone zone replace the following future_reservation_name the name of the request number_of_vms the number of gpu or h4d vms to reserve for gpu vms the value must be between 1 and 80 for h4d vms the value must be between 1 and 256 specify a number of vms that is equal or lower than the number of vms that you confirmed as available machine_type the gpu or h4d machine type to reserve number_of_chips the number of tpu chips to reserve specify a value equal to or lower than the number of chips that you confirmed as available the value must be one of the following 1 4 8 16 32 64 128 256 512 or 1024 tpu_version the tpu version to reserve reservation_name the name of the reservation that compute engine automatically creates to provision your requested capacity share_type whether other projects in your organization can consume the reserved capacity specify one of the following values to use capacity only within your project local to share capacity with other projects projects if you specify projects then you must include the share with flag set to a comma separated list of project ids for example project 1 project 2 you can specify up to 100 projects within your organization don t include your project id in this list you can consume the reserved capacity by default important you can only specify the share type and shared projects when you create a request you can t modify these settings after submission start_time the start time of the request which you must format as an rfc 3339 timestamp end_time the end time of your reservation period which you must format as an rfc 3339 timestamp if you want to specify a duration in seconds for your reservation period instead of an end time then replace the end time flag with the duration flag zone the zone where you want to reserve resources rest to create a future reservation request in calendar mode and submit it for review make a post request to the futurereservations insert method based on the resources that you want to reserve include the following fields in the request body to reserve gpu or h4d vms include the totalcount and machinetype fields as well as the deploymenttype field set to dense post https compute googleapis com compute v1 projects project_id zones zone futurereservations name future_reservation_name autodeleteautocreatedreservations true deploymenttype dense planningstatus submitted reservationmode calendar reservationname reservation_name sharesettings sharetype share_type specificreservationrequired true specificskuproperties totalcount number_of_vms instanceproperties machinetype machine_type timewindow starttime start_time endtime end_time to reserve tpus include the acceleratorcount and vmfamily fields post https compute googleapis com compute v1 projects project_id zones zone futurereservations name future_reservation_name autodeleteautocreatedreservations true planningstatus submitted reservationmode calendar reservationname reservation_name sharesettings sharetype share_type specificreservationrequired true aggregatereservation reservedresources accelerator acceleratorcount number_of_chips vmfamily tpu_version timewindow starttime start_time endtime end_time replace the following project_id the id of the project where you want to create the request zone the zone where you want to reserve resources future_reservation_name the name of the request reservation_name the name of the reservation that compute engine automatically creates to provision your requested capacity share_type whether other projects in your organization can consume the reserved capacity specify one of the following values to use capacity only within your project local to share capacity with other projects specific_projects if you specify specific_projects then in the sharesettings field you must include the projectmap field to specify the projects to share the capacity with you can specify up to 100 projects within your organization don t specify your project id you can consume the reserved capacity by default important you can only specify the share type and shared projects when you create a request you can t modify these settings after submission for example to share the requested capacity with two other projects include the following sharesettings sharetype specific_projects projectmap consumer_project_id_1 projectid consumer_project_id_1 consumer_project_id_2 projectid consumer_project_id_2 replace consumer_project_id_1 and consumer_project_id_2 wit...