🌱 Scripts for creating N VMs and constructing VM timelines #1322
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This patch introduces two scripts:
* hack/create-vm.sh
* hack/vm-timeline.sh
The first script may be used to generate N VMs as members of a VM
group. The script emits the YAML to create the VMs and the group. For example,
the following command would emit YAML to create two VMs and a group:
$ hack/create-vm.sh -n 2
apiVersion: vmoperator.vmware.com/v1alpha5
kind: VirtualMachine
metadata:
name: my-vm-drc75v9
namespace: default
spec:
className: best-effort-small
imageName: vmi-0a0044d7c690bcbea
storageClass: wcplocal-storage-profile
groupName: my-vm-group-mnyci9f
---
apiVersion: vmoperator.vmware.com/v1alpha5
kind: VirtualMachine
metadata:
name: my-vm-7vtp106
namespace: default
spec:
className: best-effort-small
imageName: vmi-0a0044d7c690bcbea
storageClass: wcplocal-storage-profile
groupName: my-vm-group-mnyci9f
---
apiVersion: vmoperator.vmware.com/v1alpha5
kind: VirtualMachineGroup
metadata:
name: my-vm-group-mnyci9f
namespace: default
spec:
bootOrder:
- members:
- name: my-vm-drc75v9
- name: my-vm-7vtp106
The second script parses the YAML of a deployed VM and constructs
a timeline based on the VM's creation timestamp and conditions. For example,
take the following VM YAML:
apiVersion: vmoperator.vmware.com/v1alpha5
kind: VirtualMachine
metadata:
creationTimestamp: "2025-11-14T23:58:31Z"
name: my-vm-rchb56v
namespace: wcpbench-vm-ns1
resourceVersion: "2027273"
uid: e06d7a16-fc34-4bfc-85cf-dd5df17f2bb4
spec:
biosUUID: f12c13d0-a087-46b1-9fad-cb384468556d
className: best-effort-small
groupName: my-vm-group-1eiirpq
hardware:
ideControllers:
- busNumber: 0
- busNumber: 1
image:
kind: VirtualMachineImage
name: vmi-e65f20bb4354ec918
imageName: vmi-e65f20bb4354ec918
instanceUUID: a15a2e3c-5d11-49ab-9598-4e4333cad673
network:
interfaces:
- name: eth0
network:
apiVersion: crd.nsx.vmware.com/v1alpha1
kind: SubnetSet
name: ""
powerOffMode: TrySoft
powerState: PoweredOn
promoteDisksMode: Online
restartMode: TrySoft
storageClass: wcp-policy
suspendMode: TrySoft
status:
biosUUID: f12c13d0-a087-46b1-9fad-cb384468556d
changeBlockTracking: false
class:
apiVersion: vmoperator.vmware.com/v1alpha5
kind: VirtualMachineClass
name: best-effort-small
conditions:
- lastTransitionTime: "2025-11-14T23:59:16Z"
message: ""
reason: "True"
status: "True"
type: GroupLinked
- lastTransitionTime: "2025-11-15T00:03:23Z"
message: ""
reason: GuestCustomizationRunning
status: "False"
type: GuestCustomization
- lastTransitionTime: "2025-11-15T00:03:23Z"
message: 'Backup version: 1763165001729'
reason: "True"
status: "True"
type: VirtualMachineBackupUpToDate
- lastTransitionTime: "2025-11-15T00:02:41Z"
message: ""
reason: "True"
status: "True"
type: VirtualMachineClassConfigurationSynced
- lastTransitionTime: "2025-11-14T23:58:31Z"
message: ""
reason: "True"
status: "True"
type: VirtualMachineClassReady
- lastTransitionTime: "2025-11-15T00:02:36Z"
message: ""
reason: "True"
status: "True"
type: VirtualMachineConditionPlacementReady
- lastTransitionTime: "2025-11-15T00:02:41Z"
message: ""
reason: "True"
status: "True"
type: VirtualMachineCreated
- lastTransitionTime: "2025-11-15T00:03:32Z"
message: Pending guest customization
reason: DiskPromotionPending
status: "False"
type: VirtualMachineDiskPromotionSynced
- lastTransitionTime: "2025-11-13T10:21:26Z"
message: ""
reason: "True"
status: "True"
type: VirtualMachineImageReady
- lastTransitionTime: "2025-11-14T23:58:33Z"
message: ""
reason: "True"
status: "True"
type: VirtualMachineNetworkReady
- lastTransitionTime: "2025-11-15T00:03:23Z"
message: ""
reason: PoweredOn
status: "True"
type: VirtualMachinePowerStateSynced
- lastTransitionTime: "2025-11-15T00:02:41Z"
message: ""
reason: "True"
status: "True"
type: VirtualMachineReconcileReady
- lastTransitionTime: "2025-11-14T23:58:31Z"
message: ""
reason: "True"
status: "True"
type: VirtualMachineStorageReady
- lastTransitionTime: "2025-11-15T00:03:23Z"
message: ""
reason: "True"
status: "True"
type: VirtualMachineTools
guest:
guestFullName: Ubuntu Linux (64-bit)
guestID: ubuntu64Guest
hardware:
controllers:
- busNumber: 0
deviceKey: 200
type: IDE
- busNumber: 1
deviceKey: 201
type: IDE
- busNumber: 0
deviceKey: 1000
devices:
- type: Disk
unitNumber: 0
type: SCSI
cpu:
total: 2
memory:
total: 4096M
hardwareVersion: 22
instanceUUID: a15a2e3c-5d11-49ab-9598-4e4333cad673
network:
config:
dns:
hostName: my-vm-rchb56v
nameservers:
- 192.19.189.30
- 192.19.189.10
interfaces:
- ip:
addresses:
- 172.30.0.195/27
gateway4: 172.30.0.193
name: eth0
nodeName: vcfpperf133.lvn.broadcom.net
powerState: PoweredOn
storage:
requested:
disks: 20Gi
total: "21585987556"
usage:
disks: "9252634624"
other: "111151076"
uniqueID: vm-3612
volumes:
- attached: true
diskUUID: 6000C291-16a9-1764-24bf-27cc4a11b1d1
limit: 20Gi
name: disk-96c3cc82
requested: 20Gi
type: Classic
used: "9252634624"
zone: mgmt-zone
The script vm-timeline.sh would produce the following report from the above
YAML:
================================================================================
VM Timeline for my-vm-rchb56v
================================================================================
Creation Time: 2025-11-14T23:58:31Z
--------------------------------------------------------------------------------
Timeline of Events
--------------------------------------------------------------------------------
T+0s (2025-11-14T23:58:31Z)
Event: VM Created (metadata.creationTimestamp)
Duration from creation: 0s
Duration from previous: —
Conditions set:
• VirtualMachineClassReady: True
• VirtualMachineStorageReady: True
T+2s (2025-11-14T23:58:33Z)
Event: NetworkReady
Duration from creation: 2s
Duration from previous: 2s
Conditions set:
• VirtualMachineNetworkReady: True
T+45s (2025-11-14T23:59:16Z)
Event: GroupLinked
Duration from creation: 45s
Duration from previous: 43s
Conditions set:
• GroupLinked: True
T+4m 5s (2025-11-15T00:02:36Z)
Event: PlacementReady
Duration from creation: 4m 5s
Duration from previous: 3m 20s
Conditions set:
• VirtualMachineConditionPlacementReady: True
T+4m 10s (2025-11-15T00:02:41Z)
Event: ClassConfigurationSynced & Created & ReconcileReady
Duration from creation: 4m 10s
Duration from previous: 5s
Conditions set:
• VirtualMachineClassConfigurationSynced: True
• VirtualMachineCreated: True
• VirtualMachineReconcileReady: True
T+4m 52s (2025-11-15T00:03:23Z)
Event: GuestCustomization & BackupUpToDate & PowerStateSynced & Tools
Duration from creation: 4m 52s
Duration from previous: 42s
Conditions set:
• GuestCustomization: False (GuestCustomizationRunning)
• VirtualMachineBackupUpToDate: True
Message: Backup version: 1763165001729
• VirtualMachinePowerStateSynced: True (PoweredOn)
• VirtualMachineTools: True
T+5m 1s (2025-11-15T00:03:32Z)
Event: DiskPromotionSynced
Duration from creation: 5m 1s
Duration from previous: 9s
Conditions set:
• VirtualMachineDiskPromotionSynced: False (DiskPromotionPending)
Message: Pending guest customization
--------------------------------------------------------------------------------
Summary
--------------------------------------------------------------------------------
Total elapsed time: 5m 1s
Current power state: PoweredOn
Conditions not ready: GuestCustomization,VirtualMachineDiskPromotionSynced
================================================================================
akutz
force-pushed
the
feature/create-vm-script
branch
from
978063f to
6950b46
Compare
github-actions
bot
added
size/XL
akutz
changed the title
Minimum allowed line rate is |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch defines a script for creating N VMs in a group.
What does this PR do, and why is it needed?
This patch introduces two scripts:
The first script may be used to generate N VMs as members of a VM group. The script emits the YAML to create the VMs and the group. For example, the following command would emit YAML to create two VMs and a group:
The above command would emit YAML similar to the following:
The second script parses the YAML of a deployed VM and constructs
a timeline based on the VM's creation timestamp and conditions. For example,
take the following VM YAML:
The script vm-timeline.sh would produce the following report from the above YAML:
Which issue(s) is/are addressed by this PR? (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes
NAAre there any special notes for your reviewer:
Please add a release note if necessary: