After more than 11 years, HashiCorp Co-Founder Mitchell Hashimoto pens a heartfelt goodbye letter to the company he helped create.
Co-Founders Armon Dadgar and Mitchell Hashimoto share their thoughts on HashiCorp’s 10th Anniversary.
As we officially enter the public markets, we plan to continue to do what we think we do best: solving problems for our end users.
Mitchell Hashimoto takes on a new individual contributor role at HashiCorp.
Configuration syncing, templating, and path variables come to Waypoint to enable you to better build, deploy, and release applications across any platform.
A consistent developer workflow to build, deploy, and release applications across any platform.
Today we are pleased to announce the HashiCorp Cloud Platform (HCP), a fully managed cloud offering to automate deployment of HashiCorp products on any cloud provider. Our first HCP service — HCP Consul — is now in private beta with support for AWS. HCP Vault will follow next. Get early access here.
We are pleased to announce the new HashiCorp Consul Service (HCS) on Azure, which is now in private beta. HCS on Azure enables Microsoft Azure customers to natively provision HashiCorp-managed Consul clusters in any Azure region directly through the Azure Marketplace.
Today we’re announcing the HashiCorp Community Portal, a single source for all members of our community to learn, share, and discuss HashiCorp products. The community portal includes a new discussion forum, video content, product guides, local in-person events (HashiCorp User Groups), and more. We recognize that individuals want to engage with the community in different ways at different moments and the community portal is meant to reflect this.
We're excited to announce that Talha Tariq has joined HashiCorp as Chief Security Officer.
We're introducing a CLA (Contributor License Agreement) requirement for any and all contributions across our open source projects. Open source is at the core of what we do and who we are as a company and deeply important to me personally, so I want to take time to explain why, what this means, and how we're rolling this out.
We are excited to announce the release of HashiCorp Consul 1.3. This release extends Consul to support Envoy as a proxy for Connect and enables automatic sidecar injection in Kubernetes for secure pod communication. Connect enables secure service-to-service communication with automatic TLS encryption and identity-based authorization. Since the initial release of Connect in June, the Consul team has focused on hardening Connect in production and expanding platform integrations to enable a global service mesh. This release delivers major improvements in both categories: Envoy is a high-performance, feature-rich, and production hardened proxy for Connect. And the Kubernetes integrations enable automatic secure pod communications across services both in and out of Kubernetes.
We're releasing HashiCorp Consul + Kubernetes features every week. This week we're releasing the service catalog sync functionality to sync Kubernetes services to the Consul catalog and vice versa. This enables cross-cluster or platform service discovery using the native service discovery tooling expected. Additionally, a central catalog allows organizations to gracefully migrate workloads into or out of Kubernetes.
We're releasing HashiCorp Consul + Kubernetes features every week. This week we're showcasing the auto-join feature to enable nodes running inside and outside of Kubernetes to join a Consul cluster running on Kubernetes. Rather than joining with a static IP address or DNS entry, the auto-join feature uses the Kubernetes API to discover pods running Consul agents, and joins those pods.
We're releasing HashiCorp Consul + Kubernetes features every week. This week we're releasing the official Consul Helm Chart for running and configuring Consul on Kubernetes. Using the Helm chart, you can start a complete Consul cluster on Kubernetes in minutes. The Helm chart can setup and configure a Consul server cluster, client agents, or both. The Helm chart will also be the primary mechanism for setting up future Consul and Kubernetes features.
We're excited to announce multiple features that deeply integrate HashiCorp Consul with Kubernetes.
Consul now provides secure service-to-service communication with automatic TLS encryption and identity-based authorization.
We're excited to announce that Preeti Somal has joined HashiCorp as our new Vice President of Engineering.
Sentinel is an embedded policy as code framework in the HashiCorp Enterprise products to enable fine-grained, logic-based policy guardrails.
We are excited to announce the availability of the HashiCorp Terraform Module Registry. HashiCorp Terraform is a tool to safely and efficiently build, change, and version on-premises and cloud infrastructure using a consistent workflow. Terraform uses automate infrastructure management through the use of infrastructure as code. Terraform configurations can be composed with modules to encapsulate groups of resources in your infrastructure.
We're announcing HashiCorp Vagrant 2.0. Vagrant is a tool for building and distributing development environments. Vagrant 2.0 supports provisioning development environments on VirtualBox, VMware, Hyper-V, Docker, AWS, GCP, and more. It can virtualize Windows, macOS, and a dozen other new operating systems. Vagrant 2.0 is paired with Vagrant Cloud for finding and consuming boxes. It has come a long way since Vagrant 1.0 when it only supported VirtualBox, and the community has grown significantly since then. Vagrant 2.0 is available immediately from the Vagrant website. You can find the full list of changes in recent Vagrant releases in the Changelog.
We're announcing HashiCorp Packer 1.0. Packer is a tool for building images for cloud platforms, virtual machines, containers, and more from a single source configuration. Packer 1.0 is a significant milestone. Packer is a powerful and full-featured tool to create cloud images and application packages. Today, Packer is in use by tens of thousands of organizations worldwide to automate their image creation. Packer 1.0 is a promise of stability and backwards compatibility. We will continue to develop releases for 1.0 to fix any issues that may exist. At the same time, development on major new versions of Packer are underway.
We've released Terraform 0.9. Terraform is a tool for safely and efficiently building, combining, and launching any infrastructure. Since our last major Terraform release, we had 8 minor releases to add and improve hundreds of resources and dozens of providers and the number of community contributors has increased from 750 to just over 900. Terraform 0.9 adds major new functionality to Terraform. Highlights include: Destroy Provisioners State Locking Interruptable Provisioners State Environments Remote State Revamp Provider Changes
We've released Terraform 0.8. Terraform is a tool for safely and efficiently building, combining, and launching any infrastructure. Terraform continues to grow extremely fast! Since our last major Terraform release, downloads have increased 100% month over month and the number of community contributors has increased 50% from 500 to over 750. We had 14 minor releases of 0.7.x to add and improve hundreds of resources and dozens of providers. Terraform 0.8 adds major new functionality to Terraform. Highlights include: Console Conditional Values Terraform Version Requirement Depending on Modules Vault Provider Nomad Provider
We've released Terraform 0.7. Terraform is a tool for safely and efficiently building, combining, and launching infrastructure. Terraform continues to be HashiCorp's fastest growing project. Over the past year, we've released over 20 minor versions of Terraform expanding resource and provider coverage as well as fixing bugs. Terraform 0.7 is the first new major feature release in a year. Terraform 0.7 adds new functionality to Terraform. Highlights include: Import Data Sources State Management CLI List and Map Types
We've released Nomad 0.4. Nomad is a distributed, scalable and highly available cluster manager and scheduler designed for both microservice and batch workloads. Nomad 0.4 ships a number of new features focused on improving the operational aspects of the tool. Highlights include: Nomad Plan Live Resource Utilization Simpler Clustering
We are excited to announce the first HashiConf EU from June 13th to June 15th at Westerliefde in Amsterdam, Netherlands. HashiConf EU will be one day of training followed by two days of talks dedicated to all things HashiCorp. The training day will have four training courses across beginner and advanced levels taught by HashiCorp engineers. Conference presentations will be given by experienced users of our tools and HashiCorp's project leads. We are delighted that Xebia is our conference and knowledge partner, and is fully committed to make it a success.Join us for three days in Amsterdam to celebrate the HashiCorp community and apply our collective experience to automate infrastructure management.
Terraform growth has been explosive. It is exciting to see the community grow, embrace, and extend Terraform in ways we never imagined. At the time of writing, Terraform ships with support for almost 500 resources across 30 providers. Because Terraform has always had a high bar for testing, each of these resources and providers is well tested. Terraform in total has thousands of unit tests and over 500 black box acceptance tests. With this growth, we've been able to maintain a positive pulse ratio while averaging multiple releases per month. Despite this, we believe we can do better. We believe we can merge PRs more quickly, we can release more often, and we can dedicate more time to core improvements. For weeks, the Terraform team and HashiCorp have planned a set of improvements towards these goals and today we're announcing those changes.
Today we announce the release of Vagrant 1.8. Vagrant is a tool for building and managing development environments. Vagrant 1.8 introduces a number of major features and hundreds of improvements and bug fixes. The major features are outlined below and the full list of improvements can be found in the official CHANGELOG. Thanks to the hundreds of contributors that helped make this release bigger and better than it could've been with just us working on it. You can download Vagrant 1.8 from the project website. There are no major backward incompatibilities so you should be able to drop-in the update and get working right away! Read on to learn more about the major new features in Vagrant 1.8.
We've released Packer 0.8. Packer is a tool for building virtual machine images, containers, and other deployable artifacts. Packer 0.7 has been out for almost a year (with minor releases since then), and we decided it was time for a major release. Packer 0.8 is an immensely large release, with over a dozen new features. A big thanks to the community who had over 100 pull requests, as well as to HashiCorp employees Chris Bednarski and Clint Shryock who both dedicated time to this release. Packer 0.8 is available immediately for download and is already running within Atlas.
We're having our first ever HashiConf September 28 and September 29, 2015 at the Gerding Theater at the Armory in Portland, OR. HashiConf is a conference dedicated to modern datacenter automation, from development to production. The two day conference will have highly technical talks covering all our tools: Vagrant, Packer, Serf, Consul, Terraform, and Vault. Talks will range from tool introductions to advanced usage, and we'd like to invite talks about any other tools in the ecosystem as well. And without saying too much, the keynote is an event you'll not want to miss. Join us for this two day event this fall with the entire HashiCorp team and meet the smartest and most passionate HashiCorp users from around the world. Let's experience the future of the datacenter together.
We've released Terraform 0.5. Terraform is a tool for safely and efficiently building, combining, and launching infrastructure. Terraform is currently HashiCorp's fastest growing project, and we decided to focus on a strong 0.5 release following last month's major release. Terraform 0.5 adds some huge features, improves the core significantly, and adds significantly more support for AWS resources.
Today we announce Vault—a tool for securely managing secrets and encrypting data in-transit. From storing credentials and API keys to encrypting passwords for user signups, Vault is meant to be a solution for all secret management needs. A modern system requires access to a multitude of secrets: credentials for databases, API keys for external services, credentials for service-oriented architecture communication, etc. Understanding who is accessing what secrets is already very difficult and often platform-specific. Adding on key rolling, secure storage, and detailed audit logs is almost impossible without a custom solution. Vault solves all of these problems. Vault is already being deployed in very large infrastructures. We are excited for the future of Vault, and what we have for you today is just the beginning of what we believe is an incredible tool. Read on to learn more.
We are releasing Terraform 0.4. Terraform is a tool for safely and efficiently building, combining, and launching infrastructure. Terraform 0.4 is our biggest release ever. We're shipping with multiple major features as well as a vast improvement to support for AWS. Terraform 0.4 had the most community involvement ever with 80 contributors, including new core committers Paul Hinze and Clint Shryock.
Vagrant 1.7 comes with a new command: vagrant push. Just as vagrant up is a single command to create a development environment for any application, vagrant push is a single command to deploy any application. The goal of Vagrant is to give developers a single workflow to develop applications effectively. vagrant up creates a development environment for any application and vagrant share enables collaboration for any application. Deploying was the next logical step for Vagrant, now possible with vagrant push. Like every other component of Vagrant, push can be configured using multiple strategies. vagrant push can deploy via FTP, Heroku, Atlas, or by executing any local script. Other strategies can be added via plugins and more will be added to core as time goes on. Read on to learn more.
The Tao of HashiCorp is the foundation that guides our vision, roadmap, and product design. As you evaluate using or contributing to HashiCorp's products, it may be valuable to understand the motivations and intentions for our work.
We are releasing Terraform 0.3. Terraform is a tool for safely and efficiently building, combining, and launching infrastructure. Terraform 0.3 is a massive release filled with both features and a wealth of stability improvements. If you've been waiting for a strong version to try Terraform, this is the version to use. This version of Terraform introduces modules, dynamic resource counts, user input for parameterization, JSON-based state, provisioner output, improvements to existing providers, and much more. In this post, we'll highlight the major features added, as well as show videos of Terraform showcasing the new features.
This guide exists for historical purposes, but a more up-to-date guide can be found on the Terraform guides. In Terraform, a "provider" is the logical abstraction of an upstream API. This guide details how to build a custom provider for Terraform. Custom providers in Terraform let you use Terraform to build and manage new infrastructure components. These custom providers can be written for public components (such as a new SaaS provider) or private components (such as a private cloud). In this blog post, we'll show you how easy it is to write a complete custom provider.
We are releasing Terraform 0.2. Terraform is a tool for safely and efficiently building, combining, and launching infrastructure. Terraform 0.1 was released just under a month ago, and Terraform 0.2 fixes many bugs, introduces new providers, and exposes a way to very easily create new providers. There are a handful of minor backwards incompatibilities, as well. The major changes in Terraform 0.2 are the introduction of a Mailgun provider, a Google Cloud provider for Google Compute Engine, and a framework for writing new providers. Terraform 0.2 can be downloaded here, and the full changelog can be viewed here. The changelog includes the list of backwards incompatibilities. Read on to learn more about the new features, improvements, and changes to Terraform.
Today we announce Terraform, a tool for safely and efficiently building, combining, and launching infrastructure. From physical servers to containers to SaaS products, Terraform is able to create and compose all the components necessary to run any service or application. With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel. Terraform codifies knowledge about your infrastructure unlike any other tool before, and provides the workflow and tooling for safely changing and updating infrastructure. We're excited to release Terraform today. The possibilities with Terraform are deep and what we have for you today is just the beginning. Read on to learn more.
Vagrant 1.6 is now available! This is a new major release building upon Vagrant 1.5 to add new features to improve workflow, expand Vagrant to support more development environment types, and more. Vagrant 1.6 introduces no breaking backwards compatibilities. There are some configuration options that have changed but they still work and will now just output deprecation warnings. There are a few major features in Vagrant 1.6. We covered the major features in feature previews leading up to this release. You can find more information by clicking on the feature name below: Global Status and Control Windows Guests Docker-Based Development Environments You can download Vagrant now or read the complete CHANGELOG. Or, continue reading to get an overview of the new features and improvements in Vagrant 1.6, as well as the direction we're heading for Vagrant 1.7.
Vagrant 1.6 comes with a new built-in provider: Docker. The Docker provider allows Vagrant to manage development environments that run within containers, rather than virtual machines. This works without any additional software required on Linux, Mac OS X, and Windows. The Docker provider in Vagrant makes it incredibly easy to keep the workflow you're used to with both Vagrant and Docker while gaining all the benefits of Vagrant: cross-platform portability, synced folders, networking, provisioners, vagrant share, plugins, etc. On platforms that don't support Linux Containers natively such as Mac OS X and Windows, Vagrant automatically brings up and shares a proxy virtual machine to run Docker. This proxy VM is completely customizable, and Vagrant ensures that synced folders and networking work as you would expect. Users of Vagrant don't need to worry about doing any of this manually. Read on to learn more.
Vagrant 1.6 will add a monumental feature to Vagrant: full Windows guest support. The ability of Vagrant to manage Windows environments just as easy as Linux environments has been requested for years and the time for complete, official support has come. Please don't mistake guest support for running Vagrant on Windows. Vagrant has fully supported running on Windows for years, and works great. Vagrant 1.6 adds support for Vagrant to run Windows within the Vagrant environments (in VirtualBox, Hyper-V, EC2, etc.). The Windows guest support coming in Vagrant 1.6 allows you to spin up Windows environments just as easily as you would Linux environments, and lets you use PowerShell scripts, Chef, Puppet, etc. to install and configure software. And just as Linux has vagrant ssh as a first-class citizen, Windows guests have vagrant rdp, which allow single-command access to a complete remote desktop environment to your Windows environment. Read on to learn more.
Vagrant 1.5 was released just a month ago, but we already have big changes lined up for Vagrant 1.6. To prepare you for the release of 1.6, we're restarting our weekly "feature preview" blog post series to cover the new features that are on the way. The first new feature we'll be covering is something we're calling global status and control. Global status introduces a new global-status command to Vagrant that will show you the status of all created Vagrant environments on your system. You'll never again forget what Vagrant environments are running, not running, or using resources on your system. Global control lets you use a unique ID assigned to each of your Vagrant environments to control it from any directory, not only the directory where the Vagrantfile is. This is useful in many situations, but perhaps this is most useful when you forget to destroy a Vagrant environment. You can now destroy that Vagrant environment from anywhere! With these two features Vagrant environment management becomes much easier. Read on to learn more.
Vagrant 1.5 is now available! This is a new major release that adds some incredible new features to Vagrant. We've also obsessed over stability, so we expect this to be the most stable release, as well. We're also announcing Vagrant Cloud, a place for sharing, discovering, and creating Vagrant environments.
Vagrant has worked on Windows for over four years. Vagrant has worked well on Windows for about two years. With Vagrant 1.5, Vagrant is excellent on Windows with dozens of bug fixes and a couple big Windows-only features: Hyper-V and SMB synced folders. Vagrant 1.5 will ship with a Hyper-V provider out of the box. This is big news! This is the first provider other than VirtualBox to ship with Vagrant itself (with more to come). And, Hyper-V comes built-in to almost all editions of Windows 8+, meaning Vagrant works with nothing more than a Windows computer for most people. Additionally, Windows users have the option now to use SMB synced folders. SMB is a technology built right into Windows, just like Hyper-V, making it easy for Windows users to get high performance synced folders out of the box. Read on to learn more about these features.
Vagrant has a vibrant plugin community. We're always looking to improve the life of a plugin developer through better abstractions, documentation, and more. In Vagrant 1.5, we made some big improvements that should make developing plugins much, much nicer. With Vagrant 1.1, we both helped and hurt plugin development. Plugin development improved because plugins became a first class supported concept with the vagrant plugin command and much of the core dogfooding the API. But plugin development was hurt because Vagrant switched to an installer-only model, breaking many plugin development environments and causing some frustrating edge cases. With Vagrant 1.5, we've made some big changes that should make the life of a plugin developer much more enjoyable. Read on to find out more.
Vagrant 1.5 will feature a revamped system for finding, downloading, and using boxes. With Vagrant 1.5 boxes will be easier than ever to find, build, use, update, and share. For new users, Vagrant becomes much easier to use, and for existing users, the box system becomes much more powerful with new features to help teams using Vagrant. Here are some quick highlights of the new box system: box names are now as simple as hashicorp/precise64, which acts as both the address for the box as well as the name. A single box address can represent a box for multiple providers, so you no longer need to special-case box URLs depending on the provider in use. Boxes are now versionable, so you can deploy box updates and users of that box are notified when updates are available. And finally, we're launching a public service to share, discover, and build boxes. And, we're also happy to say that the new system is fully backwards compatible. All old CLI commands, box files, and Vagrantfiles continue to behave exactly the way they have before. Read on to learn more about how all these new features work as well as to learn some of the motivation behind the features.
Vagrant 1.5 is going to be the biggest release of Vagrant since 1.1, with dozens of new features and improvements coming in. Don't worry, we've also obsessed over stability, so we expect it'll be one of the most stable upgrades, too. Because Vagrant 1.5 will be so feature-packed, we're doing a series of blog posts that highlight the upcoming features so you know what to look forward to and how to use them. These posts will be weekly on Wednesdays, so keep an eye out for them! We're going to kick off the series by introducing rsync synced folders. These synced folders offer incredible I/O performance at the expense of a little bit of latency. Read on to learn more.
At nearly four years old, Vagrant is considered mature and stable software. Thousands of individuals depend on Vagrant every day to provide a stable working environment, crucial to their productivity. We pride ourselves on shipping software that can stand up to this requirement. Even so, we've noticed an unacceptable trend of &quot;upgrade pains&quot; whenever a major new version of Vagrant is released. In every case, once Vagrant is working, it is very stable. However, after an upgrade, the fact some environments have to be &quot;fixed&quot; is not okay. A big focus of the project for the past couple months has been improving stability, especially upgrade stability. In this post, I'd like to discuss some of the changes we've made so you can be confident that Vagrant upgrades won't break things for you.
Vagrant 1.4.2 has been released. This is a bug-fix release for Vagrant 1.4.x and is a safe drop-in upgrade for all Vagrant 1.4 users. Vagrant 1.4.2 can be downloaded today from the downloads page. The complete changelog for this release can be found here.
Vagrant 1.4.1 has been released. This is a bug-fix release for Vagrant 1.4.0 and is a safe drop-in upgrade for all Vagrant 1.4 users. Vagrant 1.4.0 has been the most stable release so far in the 1.x series and we're happy to make a bug-fix release to make it even more reliable. Vagrant 1.4.1 can be downloaded today from the downloads page. The complete changelog for this release can be found here. One notable improvement is that the Docker provisioner now works with RedHat-based guest machines. The remainder of changes are bug fixes.
We're approaching the end of the first full calendar year of HashiCorp, and it has been an incredible year in many ways. We wanted to share with you what we achieved in 2013 and to briefly touch upon 2014.
Vagrant 1.4 has been released! This is a major new release of Vagrant with an incredible amount of new features, improvements, and bug fixes. Vagrant 1.4 can be downloaded on our new downloads page. First, I have to thank the new core committers of Vagrant for building many of the incredible features and improvements that made it into this release: Fabio Rehm, Paul Hinze, and Teemu Matilainen. Vagrant 1.4 introduces no Vagrantfile backwards incompatibilities so it can be considered a drop-in upgrade for prior versions. Vagrant environments also do not need to be destroyed prior to upgrading. There are a huge number of new features introduced in Vagrant 1.4, and this blog post will attempt to cover the major ones. For all changes see the changelog.
Today, we're announcing support for VMware Workstation in addition to the VMware Fusion support we announced in March. Workstation is the desktop virtualization solution that VMware provides for Linux and Windows machines. The integration with Vagrant will allow you to run the same virtual machines in VMware across Mac OS X, Linux, and Windows. VMware technology offers improved performance, stability, and support for those who want it, and the Vagrant integration lets you keep the same great Vagrant workflow. The workstation provider is available now for the same price as the Fusion provider: $79 per seat. The provider will work on both Linux and Windows. In Windows, Vagrant works in cmd.exe, PowerShell, Cygwin, and MSYS/MingW environments.
I'm happy to announce the release and immediate availability of Vagrant 1.1 and the long-awaited VMware Fusion provider, allowing you to use Vagrant to control machines on top of the rock solid, ultra performant VMware hypervisor. This release introduces the concept of providers, which allows Vagrant to control machines on systems other than VirtualBox. This marks the beginning of a new era for Vagrant, an era unconstrained by the limitations of any specific provider. The VMware Fusion provider is the first paid add-on for Vagrant from HashiCorp. The Fusion provider has already been in use with great success by hundreds of early testers looking for improved stability and performance from their Vagrant environments. Open source providers for AWS and RackSpace are also available today. Vagrant 1.1 can be downloaded immediately from the Vagrant website. The Fusion provider can be purchased immediately from the VMware Fusion provider page.
Sponsored by Vocalocity, HashiCorp has developed a fully open-source, MIT licensed AWS provider plugin for Vagrant 1.1. Using the same Vagrant workflow you've come to know and love, you will be able to launch and provision instances in EC2 or VPC, just as you would a VirtualBox machine today. Paired with local virtualization, the AWS provider can vastly improve your end-to-end workflow, unlocking use cases for Vagrant which simply didn't exist before. The provider will be released as open source at the same time as Vagrant 1.1, and works on Mac, Windows, and Linux. While no release date has been set, Vagrant 1.1 is targeted for later this month.
To kick off the new year, Vagrant has a brand new look! Vagrant has a new logo for the first time in three years, and the website is redesigned and restructured. The new Vagrant logo is a simple "V" built up with isometric cubes. This matches the core HashiCorp style, visible on the HashiCorp homepage. The old logo or mascot, known as "Vince," is now retired. The main website has been completely redesigned and incorporates the new logo.
Today I announce the launch of HashiCorp. I am Mitchell Hashimoto, the creator and maintainer of Vagrant, and I am founding HashiCorp to drive Vagrant's development forward. Vagrant has become a trusted tool in the industry in the three years since its release, with users ranging from individuals to entire development teams in large companies. All this despite it being a side project for me, receiving 2-4 hours a day when I had free time. I want to make Vagrant better. I want to dedicate my time to the product, its ecosystem, and its users. Forming HashiCorp gives me the framework for realizing my goals for Vagrant.