I agree, but I recently started at this position which initially was running on Vagrant v1.0.7 with a v1 config. The initial Vagrantfile was a single file, with 8 or 9 nodes configured inline and roughly ~600 lines. I've completed a big portion of reducing that complexitiy to simplify the management by creating a hash of the nodes with their basic settings, adding some logic for VM specs, and also moving some or most of the external stuff out to individual node-specific files to be parsed at runtime.
Chef Roles are already in use. I agree that some/most of this JSON could be moved to Chef Environments, but I'm also learning Chef (and the current work's Chef configuration) at this time. I come from a Puppet background with multiple environments and corresponding YAML files handling the environmental-specific configuration settings. While my learning process is still in progress, I'm hoping to address this without drastically changing the Vagrant or Chef setup. They're also running with Chef v10.14.4 so part of my milestones for this project is also to get their infrastructure running on v11 (or latest) once this works with the existing version. On Jul 16, 2014, at 7:20 PM, Shawn Neal <[email protected]> wrote: > Why do you have such a large and complex Vagrantfile? It sounds like you have > a lot of attributes that would be better managed outside Vagrant via Chef > Server roles and environments. -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
