I'm kind of glad to see this, as I wrote https://github.com/mpdehaan/strider https://github.com/mpdehaan/strider for the reason that Packer and Vagrant used dif

I'm kind of glad to see this, as I wrote https://github.com/mpdehaan/strider https://github.com/mpdehaan/strider for the reason that Packer and Vagrant used different config files. This appears to address that. OTOH, it says it's executing Vagrant and Packer under the covers, so I really need some of the Packer limitations I have (like https://github.com/mitchellh/packer/issues/409 https://github.com/mitchellh/packer/issues/409 ) addressed more than I want glue on top. Anyway, if people want to hack on Strider, pull requests are welcome. I'm not using it actively (yet), but it's a very very tiny amount of code to supply both. All the work gets done by boto. Back to otto - I am curious what otto means when it says it's going to start to talk to infrastructure and means that it's going ot be more of a workflow engine that can also invoke terraform or what. The DSL changes appear to maybe be a step in that direction? Would probably benefit from more than one liners on the homepage, to show what is really involved more quickly.