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

Set Vlan ID on switch and VM NICs #188

Open
KacperMucha opened this issue Feb 5, 2017 · 3 comments
Open

Set Vlan ID on switch and VM NICs #188

KacperMucha opened this issue Feb 5, 2017 · 3 comments

Comments

@KacperMucha
Copy link

I'm not sure if it's not possible, but I wasn't able to find a way to set Vlan ID on virtual switch or on VM NICs during the deployment. Also setting the CompatibilityForMigrationEnabled on vCPU or other VM settings would be useful. Ideally it could be set through Lability_ metadata properties.

A little side question - as there is no Contributing guideline yet, is there a way to ask more specific questions regarding contribution? Like Slack group etc.? Because if I'd like to help with this functionality for example. I could search the whole module or I could ask somebody, where exactly this metadata properties code is placed and develop it further from there.

@iainbrighton
Copy link
Contributor

iainbrighton commented Feb 6, 2017

Hi @KacperMucha - thanks for the feedback!

Internally Lability uses the xHyper-V DSC Resource to deploy/configure the host/VMs. Therefore, this functionality needs to be available there first. @rchaganti has a new xVMNetworkAdapterVlan resource for this in the works. Once there's a PR out for this functionality, we can pull it into the Lability module!

As for the contributing comment - there is no Slack or Gitter channel. Feel free to ask questions here or we could set a channel up, but there would probably only be two of us in it!? Do you think that this is still worth it?

@KacperMucha
Copy link
Author

I just wanted to ask about general preferences, because I don't want to spam the issues list. :) But if it's ok for you than I'll post my questions as issues and I'll try to not generate too many of them. :)

@iainbrighton
Copy link
Contributor

@KacperMucha An issue per question here is fine. If you would rather you could DM me on Twitter (at iainbrighton). If you were to use any other method there's a high probability that I'll not see it for a while!

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

No branches or pull requests

2 participants