I'm going to get this done. I got distracted by a new 👶 for a couple of weeks.

@jameskyle Congratulations on your 👶! I wanted support for Parallels, and thought I'd bang out both at the same time. I didn't see any branches addressing this issue in jameskyle/kubernetes, but I hope I didn't step on any toes? 😬 Check out PR #6879 #6983. I don't have VMWare, so perhaps you can help me test that part? 🙏

My toes are fully intact. Apparently raising these little tykes takes significant time and can be a bit disruptive to plans. Who knew!

I actually do have a branch locally and had made some headway. I'll compare to your branch.

@jameskyle, it looks like my PR was merged (that was fast), but please reopen this if there's something that I missed, especially on the VMWare side.

If there are issues unique to the non VirtualBox provider, who is signing up to maintain that? I am fine keeping the general Vagrant setup stable, but I am unable to debug issues specific to virtualization tool.

Sent from my iPhone

On Apr 17, 2015, at 2:46 PM, Matt Bogosian (formerly @mbogosian) notifications@github.com wrote:

@jameskyle, it looks like my PR was merged (that was fast), but please reopen this if there's something that I missed, especially on the VMWare side.

—
Reply to this email directly or view it on GitHub.

If there are issues unique to the non VirtualBox provider, who is signing up to maintain that? I am fine keeping the general Vagrant setup stable, but I am unable to debug issues specific to virtualization tool.

Perhaps only VirtualBox will be "officially supported" and the rest will be "community supported"? This ain't my rodeo 🏇, but it seems like with many aspects of Kubernetes, those making use of particular features can contribute to their maintenance? It appears that's how this issue and my attempt at a fix came about in the first place. The volume of this project is explosive (just look at the number of external merges in the past 24 hours 😮; it's insane). Don't underestimate the efficiency of emergent markets. ☺️

Between me and @jameskyle (when he's not busy being a 👨 tending to his 👶), we can probably make a pretty big dent in any issues that arise. Feel free to assign any non-VirtualBox Vagrant issues to me. If I can't handle them within a reasonable time, maybe someone else can take a stab?

Cc: @legal90 (hint, hint) 😏

Thanks

Sent from my iPhone

On Apr 17, 2015, at 10:06 PM, Matt Bogosian (formerly @mbogosian) notifications@github.com wrote:

If there are issues unique to the non VirtualBox provider, who is signing up to maintain that? I am fine keeping the general Vagrant setup stable, but I am unable to debug issues specific to virtualization tool.

Perhaps only VirtualBox will be "officially supported" and the rest will be "community supported"? This ain't my rodeo , but it seems like with many aspects of Kubernetes, those making use of particular features can contribute to their maintenance? It appears that's how this issue and my attempt at a fix came about in the first place. The volume of this project is explosive (just look at the number of external merges in the past 24 hours ; it's insane). Don't underestimate the efficiency of emergent markets.

Between me and @jameskyle (when he's not busy being a tending to his ), we can probably make a pretty big dent in any issues that arise. Feel free to assign any non-VirtualBox Vagrant issues to me. If I can't handle them within a reasonable time, maybe someone else can take a stab?

Cc: @legal90 (hint, hint)

—
Reply to this email directly or view it on GitHub.

@derekwaynecarr @posita Yes, I can help with issues related to Parallels Desktop for Mac and to the provider for Vagrant ("vagrant-parallels")