DZone
DevOps Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > DevOps Zone > How Otto Puts Docker's Development and Deployment Capabilities to Shame

How Otto Puts Docker's Development and Deployment Capabilities to Shame

Otto is the successor to both Vagrant (also by developer HashiCorp) and Docker; Otto builds infrastructure from the app up.

Rodrigo Kyle Mehren user avatar by
Rodrigo Kyle Mehren
·
Apr. 14, 16 · DevOps Zone · Opinion
Like (3)
Save
Tweet
3.46K Views

Join the DZone community and get the full member experience.

Join For Free

Docker Who? That time-travelling Vagrant? Why is it so hard for DevOps to get the tools they need to quickly build scalable infrastructure that doesn't cause a provisioning headache?

Thanks to a new concept of development and deployment created by HashiCorp, you can get the benefits of emerging approaches Otto-matically. Image title

Otto is for Automated Development Environments

Both Docker and Vagrant have specific limitations; Docker is a single concept but a lot of tools and processes that are separate, Vagrant is ideal for building a virtual machine, but isn't, in and of itself, directed toward app development.

Otto is much simpler, runs in *nix, OSX, and Windows, and installs in seconds. Otto also supports key features like SSH and deployment to AWS. 

A Simplified Build Procedure

Otto needs a minimal set of instructions to work because it's purpose built to create microservices and was created, in large part, as a response to the burden of specialized knowledge that shouldn't concern devs who just want to code, not necessarily delve deep into infrastructure. 

appfile specifies and generates:

  1. Development environments,

  2. Build systems,

  3. Infrastructure, and

  4. Deployment.

otto devotto dev creates and configures:

  1. A virtual machine, and

  2. Upstream dependencies.

otto infra

  • Provisions servers

otto build

  • Packages the app for deployment

otto deploy

otto deploy

  • Takes the app from appfile, references the provisioning created by otto infra, and builds artifacts from otto build.

Resources

  • Otto Documentation

  • Otto Tutorial and Example Ruby App

Image Credits: Ottoproject.io
Docker (software)

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Data Visualization of Healthcare Expenses by Country Using Web Scraping in Python
  • Chopping the Monolith
  • How BDD Works Well With EDA
  • How to Hash, Salt, and Verify Passwords in NodeJS, Python, Golang, and Java

Comments

DevOps Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo