Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Add support vSAN space efficiency #1702

Merged
merged 5 commits into from
Jul 30, 2022
Merged

Conversation

appilon
Copy link
Contributor

@appilon appilon commented Jul 29, 2022

Copying original PR description from #1683
Please see original PR comments for full context of conversation

Description

This feature is to support configuring the compression and deduplication for vSAN. In this change, we added two new parameters vsan_dedup_enabled and vsan_compression_enabled to support the toggling of data efficiency configuration for the specified vSAN datastore. The vmware/govmomi version is also updated 0.28.0 to support the latest VMODL connection to vSphere/vSAN.

Testing Details:

We did end to end test from 6 standalone hosts based on the vSphere 7.0. A vSAN cluster could be created with deduplication and compression enabled by running .tf file which contains the following settings.

resource "vsphere_compute_cluster" "cluster" {
   name = "clustername"
   datacenter_id = data.vsphere_datacenter.datacenter.id
   vsan_enabled = true
   vsan_dedup_enabled = true
   vsan_compression_enabled = true
}

We can also create a vSAN cluster with compression only by only setting vsan_compression_enabled to true.

resource "vsphere_compute_cluster" "cluster" {
   name = "clustername"
   datacenter_id = data.vsphere_datacenter.datacenter.id
   vsan_enabled = true
   vsan_dedup_enabled = false
   vsan_compression_enabled = true
}

Acceptance tests

  • Have you added an acceptance test for the functionality being added?
  • Have you run the acceptance tests on this branch?

Output from acceptance testing:

Release Note

resource/compute_cluster: Add support for vSAN compression and deduplication (GH-1683)

References

Closes: #1669

appilon and others added 4 commits July 29, 2022 18:29
This feature is to support configuring the compression and deduplication for vSAN. In this change, we added two new parameters "vsan_dedup_enabled" and "vsan_compression_enabled" to support the toggling of data efficiency configuration for the specified vSAN datastore. The goVmomi version is also updated to support the latest VMODL connection to vSphere/vSAN.

Testing Details:

We did end to end test from 6 standalone hosts based on the vSphere 7.0. A vSAN cluster could be created with deduplication and compression-only enabled by running .tf file which contains the following settings.

```
resource "vsphere_compute_cluster" "cluster" {
   name         = "clusternemae"
   datacenter_id = data.vsphere_datacenter.datacenter.id
   vsan_enabled = true
   vsan_dedup_enabled = true
   vsan_compression_enabled = true
}
```

We can also create a vSAN cluter with compression only by set vsan_compression_enabled true only.

```
resource "vsphere_compute_cluster" "cluster" {
   name         = "clusternemae"
   datacenter_id = data.vsphere_datacenter.datacenter.id
   vsan_enabled = true
   vsan_dedup_enabled = false
   vsan_compression_enabled = true
}
```
Updates the context for `vsan_dedup_enabled` argument and addresses line breaks.

Signed-off-by: Ryan Johnson <[email protected]>
@github-actions github-actions bot added documentation Type: Documentation provider Type: Provider labels Jul 29, 2022
@appilon appilon added area/storage Area: Storage and removed documentation Type: Documentation provider Type: Provider labels Jul 29, 2022
@github-actions github-actions bot added the size/l Relative Sizing: Large label Jul 29, 2022
@appilon appilon requested a review from tenthirtyam July 29, 2022 22:43
@appilon appilon added this to the v2.3.0 milestone Jul 29, 2022
@appilon appilon changed the title feat: add support vSAN space efficiency configuration feat: add support vSAN space efficiency configuration [RE-OPEN] Jul 29, 2022
Copy link
Collaborator

@tenthirtyam tenthirtyam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved based on previous pull request.

Updates `r/vsphere_compute_cluster` documentation to include a note that you must disable vSphere HA before you enable vSAN on the cluster. Then you can enable / re-enable vSphere HA after vSAN is configured.

Signed-off-by: Ryan Johnson <[email protected]>
@github-actions github-actions bot added documentation Type: Documentation provider Type: Provider size/xl Relative Sizing: Extra-Large and removed size/l Relative Sizing: Large labels Jul 30, 2022
@tenthirtyam tenthirtyam changed the title feat: add support vSAN space efficiency configuration [RE-OPEN] feat: Add support vSAN space efficiency Jul 30, 2022
@tenthirtyam tenthirtyam self-assigned this Jul 30, 2022
@tenthirtyam tenthirtyam merged commit a3f2e67 into main Jul 30, 2022
@tenthirtyam tenthirtyam deleted the slimyang-vsan-1683 branch July 30, 2022 04:09
tenthirtyam pushed a commit that referenced this pull request Jul 30, 2022
Updates `CHANGELOG.md` to include the feature provided in #1702.
@github-actions
Copy link

I'm going to lock this pull request 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 related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/storage Area: Storage documentation Type: Documentation provider Type: Provider size/xl Relative Sizing: Extra-Large
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add support for vSAN dedupe and compression feature.
3 participants