feat: Enhance vCenter integration with resource pool and folder support

- Added methods to ResourceService for fetching resource pools and updated existing methods to include datacenter filtering.
- Modified CreateVirtualMachine to accept folder and resource pool parameters from product data.
- Updated various jobs to synchronize resource pools and include them in the provisioning process.
- Introduced new ModuleResourcePool model and migration for resource pool management.
- Enhanced existing models (ModuleDatastore, ModuleNetwork, Os) to include relationships with vCenter and resource pools.
- Added netmask field to IpPool and updated related logic for IP reservation.
- Improved error handling and logging in VM creation and IP reservation processes.
- Updated API routes to include sync functionality for vCenter.
This commit is contained in:
baodev0
2026-07-21 21:37:28 +07:00
parent 2d43e95855
commit 5d3ed57b32
33 changed files with 708 additions and 152 deletions
@@ -95,9 +95,9 @@ class VirtualMachineService
'source' => $template,
'placement' => [
'datacenter' => $datacenter->datacenter_id,
'folder' => $providerSettings->defaultFolder(),
'folder' => $product_data['folder'] ?? $providerSettings->defaultFolder(),
'host' => $host->host_id,
'resource_pool' => $providerSettings->defaultResourcePool(),
'resource_pool' => $product_data['resource_pool'] ?? $providerSettings->defaultResourcePool(),
'datastore' => $datastoreId,
],
'power_on' => false,
@@ -159,6 +159,12 @@ class VirtualMachineService
return ['error' => false, 'data' => $vmId];
}
Log::error('VM clone failed on vCenter', [
'status' => $response->status(),
'request' => $body,
'response' => $responseData ?? $response->body(),
]);
return ['error' => true, 'data' => $responseData['value'] ?? $response->body()];
} catch (Exception $e) {
Log::error('Exception when creating VM', ['message' => $e->getMessage()]);