TL;DR: Devcloud 4 cleaned up a bit, chef attributes no longer hidden, further user customisation allowed, Testers wanted.
** advanced zone on 4.4.* isn't supported due to a change on some API param for setting tags on interfaces ** Hi All, https://github.com/imduffy15/devcloud4/tree/dev/binary-installation-basic I've pushed some clean up work for binary-installation versions DevCloud4. I've moved a few things about so chef attributes are no longer completely black boxed and are more exposed to the user so they are aware they can change system vm locations, rpm locations, etc. Along with this I've moved to using berkshelf for pulling in the chef cookbooks. Sadly this adds a dependency on ChefDK but it works better for cookbook updates. I've also upped the amount of RAM given to XenServer and the System VMs. (6gb for XenServer and 256 for ssvm cpvm rvm)... I would suggest running on a system with 16gb of ram. I may lower this down in the future but I felt their was some performance issues in allocating only 100mb of ram to the system vms. URLs to resources should now be more stable. I'm no longer hosting a marvin binary, its pulled in from pypi. All default URLs for RPMs and SystemVM images are pointing to shapeblues repo :). The chef cookbook powering it all is a modification from the one created by the folks over at CloudOps. If anybody is interested in testing I'd love to hear some feedback: ** Note should work on osx, linux and windows (in theory, windows remains untested)** ** you need chefdk installed on your machine along with vagrant-berkshelf ** ** you need virtualbox interfaces vboxnet0 vboxnet1 vboxnet2 with ips 192.168.22.1, 192.168.23.1 and 192.168.24.1 respectively along with disabling the DHCP Server ** git clone https://github.com/imduffy15/devcloud4.git git checkout -b dev origin/dev cd binary-installation-basic or binary-installation-advanced vagrant up Thanks, Ian
