Otto, the successor to Vagrant
hashicorp.com
Otto, the successor to Vagrant
1–10 of 185 posts
Re: Otto, the successor to Vagrant
#2There's a lot of magic here. I'd love to know what's going on beneath the hood.
Re: Otto, the successor to Vagrant
#3If I understand correctly, this is actually a bridge between several existing Hashicorp tools like Vagrant, Terraform and Consul (as hinted in "What is Otto?") integrated into a one-stop solution.
Re: Otto, the successor to Vagrant
#4Wow, there goes my business idea. Kudos.
Re: Otto, the successor to Vagrant
#5"The creators of Otto are also the creators of Vagrant. After working on Vagrant for over six years, we've learned a lot and we believe Otto is a superior tool for development plus so much more." - another successful project written on Go! Nice!
Re: Otto, the successor to Vagrant
#6Heads up blank page for docs on custom types: https://ottoproject.io/docs/apps/custom-plugin
Eagerly waiting to see what goes there eventually - very exciting!
Also, will there be a way to create custom Infra Types?
Re: Otto, the successor to Vagrant
#7There's a lot of magic here. I'd love to know what's going on beneath the hood.
That magic will surely prove to be problematic. I see lots of potential issues. It automatically installs other Hashicorp tools, presumably outside of your system's package manager, which means that it is a package manager in addition to whatever else it does. Where does it install software? How does it verify integrity? Does it build from source or use pre-built binaries? If they are pre-built binaries, how do I get the corresponding source code and build scripts? Does it bundle all other dependencies? How do I make sure I get security patches for the whole dependency tree? I don't expect that Hashicorp would have satisfactory answers to all these questions.
Furthermore, automatic dependency installation sounds like it will make reproducibility difficult, and I imagine automatic application type detection will fail in spectacular ways. What happens when the magic doesn't work? The Appfile looks like yet another ad-hoc domain specific language that you need to learn that has the usual major deficiencies compared with using an existing general purpose programming language.
Re: Otto, the successor to Vagrant
#8Does this use Heroku buildpacks or do they reinvent the wheel?
Edit: Otto appears to do a lot of things. But the part that everybody's complaining about is the "magic" part, the part that sets up a system automatically based on the language of the app. Heroku buildpacks also perform this magic, and have been open sourced and have a large community that helps maintain them. They're useful outside of Heroku -- for instance you can use them with docker via https://github.com/progrium/buildstep
It seems crazy to me that Hashicorp would try and reinvent this wheel. It's a problem that's fairly easy to do as a proof of concept, but it's the niggling details and number of combinations that can really explode.
Re: Otto, the successor to Vagrant
#9All Ruby development environments look alike, all PHP development environments look alike, etc.
Did they do any user research? Doesn't feel like it based on the above statement.
Re: Otto, the successor to Vagrant
#10All Ruby development environments look alike, all PHP development environments look alike, etc. Did they do any user research? Doesn't feel like it based on the above statement.
What do you mean? How is the statement false?