Alternatives to Otto logo

Alternatives to Otto

Vagrant, boot2docker, XenServer, libvirt, and Azk are the most popular alternatives and competitors to Otto.
25
84
+ 1
18

What is Otto and what are its top alternatives?

Otto automatically builds development environments without any configuration; it can detect your project type and has built-in knowledge of industry-standard tools to setup a development environment that is ready to go. When you're ready to deploy, otto builds and manages an infrastructure, sets up servers, builds, and deploys the application.
Otto is a tool in the Virtual Machine Management category of a tech stack.
Otto is an open source tool with 4.3K GitHub stars and 240 GitHub forks. Here’s a link to Otto's open source repository on GitHub

Top Alternatives to Otto

  • Vagrant
    Vagrant

    Vagrant provides the framework and configuration format to create and manage complete portable development environments. These development environments can live on your computer or in the cloud, and are portable between Windows, Mac OS X, and Linux. ...

  • boot2docker
    boot2docker

    boot2docker is a lightweight Linux distribution based on Tiny Core Linux made specifically to run Docker containers. It runs completely from RAM, weighs ~27MB and boots in ~5s (YMMV). ...

  • XenServer
    XenServer

    It is a leading virtualization management platform optimized for application, desktop and server virtualization infrastructures. It is used in the world's largest clouds and enterprises. ...

  • libvirt
    libvirt

    It is an open-source API, daemon and management tool for managing platform virtualization. It can be used to manage KVM, Xen, VMware ESXi, QEMU and other virtualization technologies. ...

  • Azk
    Azk

    azk lets developers easily and quickly install and configure development environments on their computers. ...

  • Xen Orchestra
    Xen Orchestra

    It provides a web based UI for the management of XenServer installations without requiring any agent or extra software on your hosts nor VMs. ...

  • PuPHPet
    PuPHPet

    It is a web application that allows you to easily and quickly generate custom Vagrant and Puppet controlled virtual machines. ...

  • KubeVirt
    KubeVirt

    It addresses the needs of development teams that have adopted or want to adopt Kubernetes but possess existing Virtual Machine-based workloads that cannot be easily containerized. More specifically, the technology provides a unified development platform where developers can build, modify, and deploy applications residing in both Application Containers as well as Virtual Machines in a common, shared environment. ...

Otto alternatives & related posts

Vagrant logo

Vagrant

9.1K
6.7K
1.5K
A tool for building and distributing development environments
9.1K
6.7K
+ 1
1.5K
PROS OF VAGRANT
  • 352
    Development environments
  • 290
    Simple bootstraping
  • 238
    Free
  • 139
    Boxes
  • 132
    Provisioning
  • 84
    Portable
  • 81
    Synced folders
  • 69
    Reproducible
  • 51
    Ssh
  • 44
    Very flexible
  • 5
    Works well, can be replicated easily with other devs
  • 5
    Easy-to-share, easy-to-version dev configuration
  • 3
    Great
  • 2
    Quick way to get running
  • 2
    Just works
  • 1
    What is vagrant?
  • 1
    Container Friendly
  • 1
    DRY - "Do Not Repeat Yourself"
  • 1
    Good documentation
CONS OF VAGRANT
  • 2
    Can become v complex w prod. provisioner (Salt, etc.)
  • 2
    Multiple VMs quickly eat up disk space
  • 1
    Development environment that kills your battery

related Vagrant posts

Tymoteusz Paul
Devops guy at X20X Development LTD · | 23 upvotes · 5.1M views

Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

See more
Tim Abbott
Shared insights
on
VirtualBoxVirtualBoxVagrantVagrantZulipZulip
at

We use VirtualBox primarily as a Vagrant provider for macOS for the Zulip development environment. It's totally reasonable software for providing a convenient virtual machine setup on macOS (and for debugging when things go wrong, which is mostly how we use it since the Vagrant provider for macOS just works).

See more
boot2docker logo

boot2docker

274
208
95
Lightweight Linux for Docker
274
208
+ 1
95
PROS OF BOOT2DOCKER
  • 43
    Lightweight
  • 35
    Use docker when it's not natively possible
  • 11
    Use it for fast demo without big image
  • 3
    Easy to use
  • 3
    Containers
CONS OF BOOT2DOCKER
    Be the first to leave a con

    related boot2docker posts

    XenServer logo

    XenServer

    44
    44
    0
    An open source virtualization platform
    44
    44
    + 1
    0
    PROS OF XENSERVER
      Be the first to leave a pro
      CONS OF XENSERVER
        Be the first to leave a con

        related XenServer posts

        libvirt logo

        libvirt

        39
        53
        8
        An open-source virtualization API
        39
        53
        + 1
        8
        PROS OF LIBVIRT
        • 1
          Low overhead
        • 1
          VirtIO direct hardware access
        • 1
          Can fully manage via CLI or VirtManager
        • 1
          Native hypervisor
        • 1
          Native KVM and QEMU
        • 1
          Fast
        • 1
          Built into most Linux distros
        • 1
          Free
        • 0
          VirtIO direct hardware support
        CONS OF LIBVIRT
          Be the first to leave a con

          related libvirt posts

          Azk logo

          Azk

          11
          30
          3
          A lightweight open source engine to orchestrate development environments
          11
          30
          + 1
          3
          PROS OF AZK
          • 2
            Easy setup
          • 1
            Preview and use ANY project, hassle-free
          CONS OF AZK
            Be the first to leave a con

            related Azk posts

            Xen Orchestra logo

            Xen Orchestra

            9
            15
            0
            The Web Interface for XenServer
            9
            15
            + 1
            0
            PROS OF XEN ORCHESTRA
              Be the first to leave a pro
              CONS OF XEN ORCHESTRA
                Be the first to leave a con

                related Xen Orchestra posts

                PuPHPet logo

                PuPHPet

                8
                12
                0
                A simple GUI to set up virtual machines for Web development
                8
                12
                + 1
                0
                PROS OF PUPHPET
                  Be the first to leave a pro
                  CONS OF PUPHPET
                    Be the first to leave a con

                    related PuPHPet posts

                    KubeVirt logo

                    KubeVirt

                    3
                    13
                    0
                    Virtual Machine Management on Kubernetes
                    3
                    13
                    + 1
                    0
                    PROS OF KUBEVIRT
                      Be the first to leave a pro
                      CONS OF KUBEVIRT
                        Be the first to leave a con

                        related KubeVirt posts