Re: [TEST] DevCloud4 - rework / Cleanup
Hi Ian, I'm trying to run the binary-advanced, in the Public IPs of the zone the gateway is 192.168.23.5, should my box have the IP 192.168.23.5 instead of the current 192.168.23.1 ? thanks, On Sun, Nov 16, 2014 at 2:57 PM, Ian Duffy i...@ianduffy.ie wrote: Hi Pierre, So advanced and basic are running from code on the host machine. Only a NFS, MySQL and hypervisor box is supplied. Testing is for binary-installation-advanced and binary-installation-basic. On 16 November 2014 19:44, Pierre-Luc Dion pd...@cloudops.com wrote: Hi Ian, I'm trying it as it seams quite strait forward. although, the instruction to install cloudstack [1]: I should run that in the management VM right, not locally ? does IPs are hardcoded somewhere? Thanks, that's awesome to have a local cloudstack running without effort. I'm testing this on OSX and so far the installation process is easy and well documented (still few things missing :-P )! [1] https://github.com/imduffy15/devcloud4/tree/master/advanced#start-cloudstack *Pierre-Luc DION* Architecte de Solution Cloud | Cloud Solutions Architect t 855.652.5683 *CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.com *|* tw @CloudOps_ On Sun, Nov 16, 2014 at 11:18 AM, Ian Duffy i...@ianduffy.ie wrote: 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
Re: [TEST] DevCloud4 - rework / Cleanup
Hi Pierre, No that is correct. We cannot control the .1 interface which is on the host machine. We can however control .5 and get it to do forwarding On 17 Nov 2014 12:28, Pierre-Luc Dion pdion...@apache.org wrote: Hi Ian, I'm trying to run the binary-advanced, in the Public IPs of the zone the gateway is 192.168.23.5, should my box have the IP 192.168.23.5 instead of the current 192.168.23.1 ? thanks, On Sun, Nov 16, 2014 at 2:57 PM, Ian Duffy i...@ianduffy.ie wrote: Hi Pierre, So advanced and basic are running from code on the host machine. Only a NFS, MySQL and hypervisor box is supplied. Testing is for binary-installation-advanced and binary-installation-basic. On 16 November 2014 19:44, Pierre-Luc Dion pd...@cloudops.com wrote: Hi Ian, I'm trying it as it seams quite strait forward. although, the instruction to install cloudstack [1]: I should run that in the management VM right, not locally ? does IPs are hardcoded somewhere? Thanks, that's awesome to have a local cloudstack running without effort. I'm testing this on OSX and so far the installation process is easy and well documented (still few things missing :-P )! [1] https://github.com/imduffy15/devcloud4/tree/master/advanced#start-cloudstack *Pierre-Luc DION* Architecte de Solution Cloud | Cloud Solutions Architect t 855.652.5683 *CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.com *|* tw @CloudOps_ On Sun, Nov 16, 2014 at 11:18 AM, Ian Duffy i...@ianduffy.ie wrote: 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
[TEST] DevCloud4 - rework / Cleanup
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
Re: [TEST] DevCloud4 - rework / Cleanup
Hi Ian, I'm trying it as it seams quite strait forward. although, the instruction to install cloudstack [1]: I should run that in the management VM right, not locally ? does IPs are hardcoded somewhere? Thanks, that's awesome to have a local cloudstack running without effort. I'm testing this on OSX and so far the installation process is easy and well documented (still few things missing :-P )! [1] https://github.com/imduffy15/devcloud4/tree/master/advanced#start-cloudstack *Pierre-Luc DION* Architecte de Solution Cloud | Cloud Solutions Architect t 855.652.5683 *CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.com *|* tw @CloudOps_ On Sun, Nov 16, 2014 at 11:18 AM, Ian Duffy i...@ianduffy.ie wrote: 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
Re: [TEST] DevCloud4 - rework / Cleanup
Hi Pierre, So advanced and basic are running from code on the host machine. Only a NFS, MySQL and hypervisor box is supplied. Testing is for binary-installation-advanced and binary-installation-basic. On 16 November 2014 19:44, Pierre-Luc Dion pd...@cloudops.com wrote: Hi Ian, I'm trying it as it seams quite strait forward. although, the instruction to install cloudstack [1]: I should run that in the management VM right, not locally ? does IPs are hardcoded somewhere? Thanks, that's awesome to have a local cloudstack running without effort. I'm testing this on OSX and so far the installation process is easy and well documented (still few things missing :-P )! [1] https://github.com/imduffy15/devcloud4/tree/master/advanced#start-cloudstack *Pierre-Luc DION* Architecte de Solution Cloud | Cloud Solutions Architect t 855.652.5683 *CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.com *|* tw @CloudOps_ On Sun, Nov 16, 2014 at 11:18 AM, Ian Duffy i...@ianduffy.ie wrote: 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
