3 ms·
Running OpenStack locally on your linux machine and interacting with it via an API may help with some of the networking complexities you're running into. Is yo
by jakedahn 14y ago
Running OpenStack locally on your linux machine and interacting with it via an API may help with some of the networking complexities you're running into.
Is your project open source? I'd be interested to chat about how you're approaching the multi-node support in your stuff.
Please shoot me an email or send a tweet: jake@markupisart.com / @jakedahn on twitter
- contingencies 14y agoLooked at OpenStack locally but decided against it, can't remember precisely why but probably something to do with not wanting to use paravirtualization. Project is not open source but might be in future ... no time. Sent you an email.
- tateeskew 14y agoYou both should take a look at Salt Cloud. Since you are already working with Python Jake it may be worth looking into. The project is doing a lot of the same things and it has the advantage of bootstrapping with Salt.
- 23david 14y agoI hack on salt-cloud, and found it to be a useful tool. And getting better every day... http://github.com/saltstack/salt-cloud http://github.com/saltstack/salt-cloud If you build a few map files using salt-cloud, you have a quick vagrant-ish setup that you can start/stop/destroy with ease. Super easy to have a whole test cluster boot up for quick test/dev work. Fyi, salt is really awesome for people looking for alternatives to chef/puppet: http://saltstack.org http://saltstack.org
- jakedahn 14y agoI've actually already been experimenting with salt, seems like a decent option for a multi-node configuration setup.
- contingencies 14y agoI am personally less than enthusiastic when it comes to puppet-style solutions for their tendency to create configuration drift; running the same command in more than one place expecting the same results is in my view rarely the best solution in terms of maintainability and reliability.