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

provider/vsphere: Add support for memory reservation #6036

Merged
merged 1 commit into from
Apr 25, 2016

Conversation

tkak
Copy link
Contributor

@tkak tkak commented Apr 6, 2016

This PR adds memory reservation support for vsphere_virtual_machine resource. I'd like to submit again, #4138.

@stack72
Copy link
Contributor

stack72 commented Apr 14, 2016

Hi @tkak

this PR looks good - please can you rebase it against master so we can get this merged?

Paul

@chrislovecnm
Copy link
Contributor

@phinze amigo ... might we get a merge ... pretty please??

@stack72 you run the test cases locally???

@stack72
Copy link
Contributor

stack72 commented Apr 15, 2016

Hi @chrislovecnm

This PR needs rebased so that we can merge it

I asked @tkak just yesterday

Paul

@chrislovecnm
Copy link
Contributor

@stack72 thanks missed that :)

@jen20
Copy link
Contributor

jen20 commented Apr 20, 2016

Hi @tkak and @chrislovecnm - I've just looked over this now - even if the conflicts are resolved during merge there is a problem with the vendored version of the SDK for vSphere that is preventing compilation.

@tkak tkak force-pushed the f-vsphere-memory-reservation branch 2 times, most recently from 38300a7 to 6ebfcce Compare April 22, 2016 09:57
@tkak
Copy link
Contributor Author

tkak commented Apr 22, 2016

Thank you @stack72, @chrislovecnm and @jen20. I fixed my PR.

@chrislovecnm
Copy link
Contributor

@jen20 much thanks for the help! How are we looking on the merge now?

"memory_reservation": &schema.Schema{
Type: schema.TypeInt,
Optional: true,
ForceNew: true,
Copy link
Contributor

Choose a reason for hiding this comment

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

Do you really want to force a new resource when memory_reservation changes? Can it not be changed once created?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It can change on existing VMs with VMware vSphere. But it needs to be set ForceNew option because there is no support to update resources now.

@stack72
Copy link
Contributor

stack72 commented Apr 22, 2016

@tkak (@chrislovecnm) - 2 small nit picks that could potentially be taken care of post-merge. Well 1 nit pick and 1 question I guess

@chrislovecnm
Copy link
Contributor

@stack72 please nit pick away ... We want good code ... lol

@tkak tkak force-pushed the f-vsphere-memory-reservation branch from 6ebfcce to cba1567 Compare April 25, 2016 01:25
@stack72
Copy link
Contributor

stack72 commented Apr 25, 2016

Hi @tkak

Thanks for the updates here. I understand now why the Update func hasn't been added to the schema for the memory_reservation

@chrislovecnm it may be worth adding that to the overall tracking for the issues for vsphere provider :)

Thanks all for the work here - this looks good to merge :)

P.

@stack72 stack72 merged commit a9a607d into hashicorp:master Apr 25, 2016
@chrislovecnm
Copy link
Contributor

@stack72 sorry please more info

@stack72
Copy link
Contributor

stack72 commented Apr 25, 2016

@chrislovecnm currently, this vm resource only supports Create, Read and Delete. There are no update operations included, therefore if someone changes a value it will not get updated, it will create a new resource

So the large list of enhancements that were being tracked may want to have this included on it - to support the appropriate update operations

Make sense?

@chrislovecnm
Copy link
Contributor

@stack72 now makes sense! We are missing a U...

@tkak you want to pipe in or shall I?

@chrislovecnm
Copy link
Contributor

@stack72 thanks and appreciate the merge

@ghost
Copy link

ghost commented Apr 26, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants