What feature should be changed? Please provide the URL of the feature if possible. ================================================================================== The Puppet manifest we're using to set up the dev VM should be based on Ansible to improve the maintenance situation. What problems would this solve? =============================== Maintenance bottleneck Who would use this? =================== Devs What would users see? ===================== n/a What would users do? What would happen as a result? =================================================== n/a Is there anything else we should know? ======================================
Assignee: nobody → jezdez
Status: NEW → ASSIGNED
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/889431918343714090575e1a2ff121ef2a079482 Fix bug 1165924 - Port dev VM Puppet manifests to Ansible roles. This also does: Fix bug 1132640 - Use more caching for VM (apt, gem, npm, pip, product details) Fix bug 962618 - Use Vagrant plugin for updating /etc/hosts Fix bug 1054285 - Revert temporarily disable SSL verification in NPM Fix bug 1054267 - Use provisioner to isntall npm packages instead of manually doing so. Fix bug 1054257 - Improve NFS performance and update guest additions in VM. Fix bug 1158149 - Use ansible role instead of Puppet manifest for ES. Fix bug 1158142 - Use ansible role instead of Puppet manifest for apt. https://github.com/mozilla/kuma/commit/50b40e72da25fc87adc6f044a7593b6a8b2ce58e Bug 1165924 - Added missing file that wasn't added before due to gitignore.
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/75fa4334e5e66c21bbabbc4a9460b6e2b6407478 Bug 1165924: Increase mysql_innodb_log_file_size The default value was too low for the sanitized database dump to be successfully imported. https://github.com/mozilla/kuma/commit/aac464db6e4cb75798fea66a4dcaff8286623d89 Fix bug 1165924: Make sure MySQL is really really restarted.
You need to log in before you can comment on or make changes to this bug.