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

Vsphere_virtual_machine: Network interfaces #3652

Merged
merged 2 commits into from
Nov 5, 2015
Merged

Conversation

eloycoto
Copy link
Contributor

Hi,

This PR fix #3559 and #3560, when a template is cloned we deleted all the interfaces so the createNetworkInterfaces will work correctly.

Regards.

@eloycoto
Copy link
Contributor Author

Hi,

I've just added a few changes in this PR. Now template didn't change.

The process of the server is the following:

  • Get the template.
  • Clone template server and keep it off.
  • Delete all old network devices and add the spec ones.
  • Apply VM customizations (hostname, domain, dns, etc.. )
  • PowerOn
  • WaitForIP.

This has a new dependency in govmomi, and this PR need to be accepted.

vmware/govmomi#365

P.S: I'll update the godeps when the govmomi get merged.

Cheers

@chrislovecnm
Copy link
Contributor

@eloycoto you sign the CLA for govmomi? See their comments on your PR.

@eloycoto
Copy link
Contributor Author

Hi,

@chrislovecnm: Yep, is merged now. vmware/govmomi#365

@radeksimko: This should be ok, I've just check that no godeps or glide for the dependencies. So this PR can be merged if you want ;-)

Thanks.

@phinze
Copy link
Contributor

phinze commented Oct 29, 2015

Hi @eloycoto - thanks for this!

A few questions:

  • Are you able to run the acceptance tests in your environment?
  • Do they pass on this branch?
  • Is it possible to add or enhance a test for this new behavior?

@tkak
Copy link
Contributor

tkak commented Nov 2, 2015

@eloycoto I tried to run the acceptance tests in my environment. The test has passed in case of a template containing some network devices. Thank you!

@phinze
Copy link
Contributor

phinze commented Nov 2, 2015

@tkak that is great to hear!

Does that mean you can add a test covering the new behavior if we merge this as is?

@chrislovecnm
Copy link
Contributor

@phinze can we get this merged?

@phinze
Copy link
Contributor

phinze commented Nov 5, 2015

Sounds good - it would still be nice to get a covering acceptance test for the new behavior. But we can merge as-is push that to a separate task.

phinze added a commit that referenced this pull request Nov 5, 2015
Vsphere_virtual_machine: Network interfaces
@phinze phinze merged commit b95e3fd into hashicorp:master Nov 5, 2015
@chrislovecnm
Copy link
Contributor

@eloycoto any ideas on acceptance testing for this?

@phinze might be tough to write a specific test, because this behavior is based on how the virtual machine template is configured.

@eloycoto
Copy link
Contributor Author

eloycoto commented Nov 9, 2015

Hey @chrislovecnm!

Sorry, I was on vacation. I'll send a new PR this week with new test.

Cheers

@chrislovecnm
Copy link
Contributor

👍 @eloycoto

@ghost
Copy link

ghost commented Apr 30, 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 30, 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.

vSphere: do not add new network adapters by default
5 participants