Compute: Add support for FLEX_START and RESERVATION_BOUND provisioning model (FIXED)#16838
Compute: Add support for FLEX_START and RESERVATION_BOUND provisioning model (FIXED)#16838MihajloLinic wants to merge 10 commits intoGoogleCloudPlatform:mainfrom
Conversation
|
Googlers: For automatic test runs see go/terraform-auto-test-runs. @trodge, a repository maintainer, has been assigned to review your changes. If you have not received review feedback within 2 business days, please leave a comment on this PR asking them to take a look. You can help make sure that review is quick by doing a self-review and by running impacted tests locally. |
|
The tests were messed up because of RECORDING mode, do note im not exactly certain about changes in FutureReservations.yaml because I don't know what is planned for it in the end |
|
@trodge This PR has been waiting for review for 3 weekdays. Please take a look! Use the label |
|
@GoogleCloudPlatform/terraform-team @trodge This PR has been waiting for review for 1 week. Please take a look! Use the label |
|
Any updates? Not critical since we are serving our custom terraform provider im just asking |
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
Breaking Change(s) DetectedThe following breaking change(s) were detected within your pull request.
If you believe this detection to be incorrect please raise the concern with your reviewer. |
Tests analyticsTotal tests: 1414 Click here to see the affected service packages
Action takenFound 7 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
|
🟢 Tests passed during RECORDING mode: 🟢 No issues found for passed tests after REPLAYING rerun. 🔴 Tests failed during RECORDING mode: 🔴 Errors occurred during RECORDING mode. Please fix them to complete your PR. |
trodge
left a comment
There was a problem hiding this comment.
Tests that are beta only should have provider = google-beta in each resource config.
|
Added google-beta to failing tests |
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
Breaking Change(s) DetectedThe following breaking change(s) were detected within your pull request.
If you believe this detection to be incorrect please raise the concern with your reviewer. |
Tests analyticsTotal tests: 1416 Click here to see the affected service packages
Action takenFound 5 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
|
🔴 Tests failed during RECORDING mode: 🔴 Errors occurred during RECORDING mode. Please fix them to complete your PR. |
|
@trodge This PR has been waiting for review for 3 weekdays. Please take a look! Use the label |
|
@GoogleCloudPlatform/terraform-team @trodge This PR has been waiting for review for 1 week. Please take a look! Use the label |
Fixed version of PR: #16750
Error was during testing not accounting for recording mode
This PR adds support for the
FLEX_STARTandRESERVATION_BOUNDprovisioning models togoogle_compute_instance,google_compute_instance_template, andgoogle_compute_region_instance_template.FLEX_STARTis a VM scheduling option in Google Cloud Compute Engine (part of the Dynamic Workload Scheduler) that allows flexible start times for VM instances, enabling cost optimization by letting Google schedule VM creation within a 24-hour time window. It is specifically designed for accelerator-optimized workloads (GPUs/TPUs).RESERVATION_BOUNDis a VM scheduling option that binds an instance to a specific reservation. When set, the instance will only consume capacity from the targeted reservation (configured viareservation_affinity). This is used with Calendar Reservations (Future Reservations) in the Dynamic Workload Scheduler, where GPU/TPU capacity is pre-booked for a specific time window and delivered as a standard reservation that instances can then target.Changes
FLEX_STARTandRESERVATION_BOUNDas valid values forprovisioning_modelin the scheduling block of instances and instance templates. Updated field descriptions and validation logic.FLEX_STARTandRESERVATION_BOUNDare correctly handled during resource conversion.FLEX_START(with its required companion fields likeinstance_termination_actionandmax_run_duration) andRESERVATION_BOUND(with its companionreservation_affinityblock).TestAccComputeInstance_flexStart,TestAccComputeInstanceTemplate_flexStart,TestAccComputeRegionInstanceTemplate_flexStartTestAccComputeInstance_reservationBound,TestAccComputeInstanceTemplate_reservationBound,TestAccComputeRegionInstanceTemplate_reservationBound