Bringup workflow does not allow disabling vLCM based MGMT domain

vmware / terraform-provider-vcf

Terraform Provider for VMware Cloud Foundation

https://registry.terraform.io/providers/vmware/vcf/

Mozilla Public License 2.0

23 stars 10 forks source link

Bringup workflow does not allow disabling vLCM based MGMT domain #151

Closed pradeep17j closed 5 months ago

pradeep17j commented 7 months ago

Code of Conduct

[X] I have read and agree to the project's Code of Conduct.
[X] Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
[X] Do not leave "+1" or other comments that do not add relevant information or questions.
[X] If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

The bringup workflow does not allow disabling vLCM based MGMT domain. Since VCF 5.0 , vLCM is default . If we need to do a VUM based bringup, we need the control to disable vLCM

The schema does not accept clusterImage=False configuration

Use Case(s)

To bringup VUM based MGMT domains

Potential Configuration

VUM based MGMT domain

References

No response

spacegospod commented 7 months ago

@pradeep17j the cluster_image_id input is optional. Can you share your configuration? If I am not mistaken not providing a value for the image ID should result in a VUM-managed cluster on the management domain

pradeep17j commented 7 months ago

@stoyanzhelyazkov ,

To have control of VUM/vLCM based mgmt domain in bringup, the changes are required in resource_vcf_instance. It will have to accept a bool parameter named clusterImageEnabled. I assume , For this the vcf-sdk-go needs to be built with 5.1 swagger.json or the auto generated code in vcf-sdk-go will have to be manually edited to accept the new param in models/sddc_cluster_spec.go .

I guess the cluster_image_id you are mentioning will be applicable for day2 operations when adding a new cluster to WLD

A sample portion of bringup.json with 5.1 looks like below

 "clusterSpec": {
"clusterName": "SDDC-Cluster1",
"clusterEvcMode": "",
"clusterImageEnabled": false,
"resourcePoolSpecs": [
  {

github-actions[bot] commented 4 months ago

I'm going to lock this issue because it has been closed for 30 days. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.