-
Notifications
You must be signed in to change notification settings - Fork 48
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
Any interest in VRA7 support? #235
Comments
In theory yes. You can just send "dummy" responses for things it doesn't support. e.g. just return true for migration. I would like to eventually have providers surface their capabilities and then the pool manager can determine what to do, but that's WAAAY off in the distance :-) |
I am maybe a month or two away from implementing this. What is the status with #181? I liked what you wrote so far looks like you just need the time to finish it. |
Provider support is implemented. I have closed #181. If you would like to add a VRA7 provider I'm happy to offer review. |
@logicminds Did you implement a VRA provider? |
I did not as my contract with the client at the time ended before I could implement it. Since I don't run VRA at my house I have no way to develop this. |
I can contribute a vra7 provider since I have a direct need to make vmpooler work with vra7. Would vmpooler be compatible with vra7 since some of the functions don't translate easily from vcenter speak.
Specifically:
https://github.com/puppetlabs/vmpooler/blob/master/lib/vmpooler/providers/base.rb#L108
https://github.com/puppetlabs/vmpooler/blob/master/lib/vmpooler/providers/base.rb#L118
The text was updated successfully, but these errors were encountered: