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

Allow to specify space-allocation option when using ontap_san backend #136

Closed

Conversation

stang
Copy link
Contributor

@stang stang commented Jun 24, 2018

Further details in: #135

In term of implementation, the storage_drivers/ontap/api/azgo library was already supporting the option, so I just passed it down at the ontap_san driver level.

It also recognize the trident.netapp.io/spaceAllocate PVC's annotation in order to allow to modify that setting on a case per case basis.

@stang stang force-pushed the feature/add-space-allocation-support branch 4 times, most recently from 09da0a5 to e25e70a Compare June 26, 2018 08:50
@stang stang changed the title WIP: Allow to specify space-allocation option when using ontap_san backend Allow to specify space-allocation option when using ontap_san backend Jun 26, 2018
Signed-off-by: Stephane Tang <hi@stang.sh>
Signed-off-by: Stephane Tang <hi@stang.sh>
@stang stang force-pushed the feature/add-space-allocation-support branch from e25e70a to 88fad86 Compare June 26, 2018 09:38
  When not enabled, any LUN that belong to a volume that is perceived as full
  by the ONTAP will be put offline and lead to unexpected behavior on the guest
  OS.
  OTOH, having this option enabled is the preferred option for systems that are
  compatible with it, while most of the major OS we can find in the containers
  world are compatible.

Signed-off-by: Stephane Tang <hi@stang.sh>
@phoebegoh
Copy link

Would be great to see this merged! /gentlebump

@psingh59
Copy link

We are in desperate need of this feature...any chance it can be done in next release??

@korenaren
Copy link
Contributor

Close with commits: bb66f59, a031b74, 5bd7f0b, 1527b78

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants