On 03/28/2014 01:46 PM, Spico Florin wrote: > Hello, all! > Thank you very much for your helpful responses. Regarding Wirbelsturm, > even it looks quite appealing at the first glance, in my opinion it is a > little bit complex > (https://github.com/miguno/wirbelsturm/blob/master/docs/AWS.md) than the > initial storm-deploy. It is still in beta version and there are too many > steps that should be performed for configuring. Also you have to to > install ec2 cli utilities.
I agree -- the UX to deploy to AWS can still be improved. There are currently two main reasons why the latest version of Wirbelsturm cannot yet deploy to AWS in the same simple way as you can for local deployments: 1. A known Vagrant bug that causes problems with stock Amazon Linux AMI. 2. Vagrant's AWS support in general, notably the lack of options to configure DNS/networking on AWS as easily as you can with local deployments (for e.g. VirtualBox). I am looking into ways to address both 1 and 2 above. Regarding #1, the most recent versions of Vagrant have a new SSH-related setting that may address the Amazon Linux AMI compatibility problem. Unfortunately this new feature is poorly documented, and when I gave it a first try it didn't help to fix bug #1. Regarding #2, there has been progress on Vagrant plugins such as vagrant-hostmanager (which I am currently test-driving) that may allow us to configure DNS related settings on deployed machines without having to go through Amazon Route 53 as we do currently. The main drawback of Route 53 is that it requires additional, one-time configuration steps for Vagrant (and thus Wirbelsturm) because Route 53 e.g. requires delegation of a DNS sub-domain to Route 53 (and for good reasons such as security you must explicitly enable such delegation for your DNS domains). The benefit of Route 53 however is that any additional machines you run alongside Storm & friends will also learn about the machines you have deployed via Wirbelsturm/Vagrant. That's nice if you already have existing infrastructure on AWS. Hence one idea that I have is to make Route 53 an optional configuration, as long as we can find another way to configure DNS etc. on AWS instances without Route 53 (such as I hope we can do with vagrant-hostmanager). I am just writing this to let you know what the current status of Wirbelsturm is, and what the plans are moving forward. The AWS user experience is definitely on the list of things to improve, as is adding OpenStack support. > If you have successfully used Wirbelsturm on Windows environment , > please let me know how complex was for you. There are no plans to support Wirbelsturm on Windows -- neither as host machines nor as guest machines. Best, Michael
