-
Notifications
You must be signed in to change notification settings - Fork 189
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
[berkshelf] Berkshelf is for Workstations #12
[berkshelf] Berkshelf is for Workstations #12
Conversation
This makes the Vagrant driver behave more like the LXC driver, relying on the SSH Base semantics set forth in test-kitchen@1.0 I prefer to have berkshelf resolve cookbooks on the workstation -- temporarily install them somewhere, and then have an intermediate system, in this case, TK, ship cookbooks and so-on from a combined, resolved, cookbook directory. Previously Vagrant was trying to interact with Berkshelf on the guest, which would mean that the guest would need to have access to Git, etc
I've been leaning in this direction over the last week as this helps keep this driver more in line with all the others. I'm also hoping to speed up the chef artifact uploading (trim down files, concat into tarball or similar) which helps all SSH-based drivers. I'll take another look later today and bug @jtimberman when we meet up tonight. |
Happy to help with testing. |
…t directly for provision
…ty, enhance synced folders
I'm screwing around with this more -- have added synced folders and made sure that we can talk to vagrant instances without relying on vagrant provision. The old functionality is enabled with config[:use_vagrant_provision] and config[:use_vagrant_berkshelf_plugin] I have convergence now with no synced folders and @fnichol Data Uploader / Vagrantfile generator. |
a.k.a Fuck Vagrant and Fuck Berkshelf |
So good, this is great! @fujin, do you have a use for the synced folders? Was surprised to see that part |
[berkshelf] Berkshelf is for Workstations
Thanks team! ❤️ |
This makes the Vagrant driver behave more like the LXC driver, relying on the SSH Base semantics set forth in test-kitchen@1.0
I prefer to have berkshelf resolve cookbooks on the workstation -- temporarily install them somewhere, and then have an intermediate system, in this case, TK, ship cookbooks and so-on from a combined, resolved, cookbook directory. Previously Vagrant was trying to interact with Berkshelf on the guest, which would mean that the guest would need to have access to Git, etc
Thoughts? @portertech says this is already WIP by @fnichol ?
I'm still having some trouble with this, but prefer the SSH Base / LXC behavior.. it was much faster.