122 lines
6.3 KiB
Markdown
122 lines
6.3 KiB
Markdown
|
---
|
||
|
|
layout: "intro"
|
||
|
|
page_title: "Use Cases"
|
||
|
|
sidebar_current: "use-cases"
|
||
|
|
description: |-
|
||
|
|
Before understanding use cases, it's useful to know what Vault is. This page lists some concrete use cases for Vault, but the possible use cases are much broader than what we cover. Due to its extensible nature, providers and provisioners can be added to further extend Vault's ability to manipulate resources.
|
||
|
|
---
|
||
|
|
|
||
|
|
# Use Cases
|
||
|
|
|
||
|
|
Before understanding use cases, it's useful to know [what Vault is](/intro/index.html).
|
||
|
|
This page lists some concrete use cases for Vault, but the possible use cases are
|
||
|
|
much broader than what we cover. Due to its extensible nature, providers and provisioners
|
||
|
|
can be added to further extend Vault's ability to manipulate resources.
|
||
|
|
|
||
|
|
#### Heroku App Setup
|
||
|
|
|
||
|
|
Heroku is a popular PaaS for hosting web apps. Developers create an app, and then
|
||
|
|
attach add-ons, such as a database, or email provider. One of the best features is
|
||
|
|
the ability to elastically scale the number of dynos or workers. However, most
|
||
|
|
non-trivial applications quickly need many add-ons and external services.
|
||
|
|
|
||
|
|
Vault can be used to codify the setup required for a Heroku application, ensuring
|
||
|
|
that all the required add-ons are available, but it can go even further: configuring
|
||
|
|
DNSimple to set a CNAME, or setting up CloudFlare as a CDN for the
|
||
|
|
app. Best of all, Vault can do all of this in under 30 seconds without
|
||
|
|
using a web interface.
|
||
|
|
|
||
|
|
#### Multi-Tier Applications
|
||
|
|
|
||
|
|
A very common pattern is the N-tier architecture. The most common 2-tier architecture is
|
||
|
|
a pool of web servers that use a database tier. Additional tiers get added for API servers,
|
||
|
|
caching servers, routing meshes, etc. This pattern is used because the tiers can be scaled
|
||
|
|
independently and provide a separation of concerns.
|
||
|
|
|
||
|
|
Vault is an ideal tool for building and managing these infrastructures. Each tier can
|
||
|
|
be described as a collection of resources, and the dependencies between each tier are handled
|
||
|
|
automatically; Vault will ensure the database tier is available before the web servers
|
||
|
|
are started and that the load balancers are aware of the web nodes. Each tier can then be
|
||
|
|
scaled easily using Vault by modifying a single `count` configuration value. Because
|
||
|
|
the creation and provisioning of a resource is codified and automated, elastically scaling
|
||
|
|
with load becomes trivial.
|
||
|
|
|
||
|
|
#### Self-Service Clusters
|
||
|
|
|
||
|
|
At a certain organizational size, it becomes very challenging for a centralized
|
||
|
|
operations team to manage a large and growing infrastructure. Instead it becomes
|
||
|
|
more attractive to make "self-serve" infrastructure, allowing product teams to
|
||
|
|
manage their own infrastructure using tooling provided by the central operations team.
|
||
|
|
|
||
|
|
Using Vault, the knowledge of how to build and scale a service can be codified
|
||
|
|
in a configuration. Vault configurations can be shared within an organization
|
||
|
|
enabling customer teams to use the configuration as a black box and use Vault as
|
||
|
|
a tool to manage their services.
|
||
|
|
|
||
|
|
#### Software Demos
|
||
|
|
|
||
|
|
Modern software is increasingly networked and distributed. Although tools like
|
||
|
|
[Vagrant](https://www.vagrantup.com/) exist to build virtualized environments
|
||
|
|
for demos, it is still very challenging to demo software on real infrastructure
|
||
|
|
which more closely matches production environments.
|
||
|
|
|
||
|
|
Software writers can provide a Vault configuration to create, provision and
|
||
|
|
bootstrap a demo on cloud providers like AWS. This allows end users to easily demo
|
||
|
|
the software on their own infrastructure, and even enables tweaking parameters like
|
||
|
|
cluster size to more rigorously test tools at any scale.
|
||
|
|
|
||
|
|
#### Disposable Environments
|
||
|
|
|
||
|
|
It is common practice to have both a production and staging or QA environment.
|
||
|
|
These environments are smaller clones of their production counterpart, but are
|
||
|
|
used to test new applications before releasing in production. As the production
|
||
|
|
environment grows larger and more complex, it becomes increasingly onerous to
|
||
|
|
maintain an up-to-date staging environment.
|
||
|
|
|
||
|
|
Using Vault, the production environment can be codified and then shared with
|
||
|
|
staging, QA or dev. These configurations can be used to rapidly spin up new
|
||
|
|
environments to test in, and then be easily disposed of. Vault can help tame
|
||
|
|
the difficulty of maintaining parallel environments, and makes it practical
|
||
|
|
to elastically create and destroy them.
|
||
|
|
|
||
|
|
#### Software Defined Networking
|
||
|
|
|
||
|
|
Software Defined Networking (SDN) is becoming increasingly prevalent in the
|
||
|
|
datacenter, as it provides more control to operators and developers and
|
||
|
|
allows the network to better support the applications running on top. Most SDN
|
||
|
|
implementations have a control layer and infrastructure layer.
|
||
|
|
|
||
|
|
Vault can be used to codify the configuration for software defined networks.
|
||
|
|
This configuration can then be used by Vault to automatically setup and modify
|
||
|
|
settings by interfacing with the control layer. This allows configuration to be
|
||
|
|
versioned and changes to be automated. As an example, [AWS VPC](http://aws.amazon.com/vpc/)
|
||
|
|
is one of the most commonly used SDN implementations, and [can be configured by
|
||
|
|
Vault](/docs/providers/aws/r/vpc.html).
|
||
|
|
|
||
|
|
#### Resource Schedulers
|
||
|
|
|
||
|
|
In large-scale infrastructures, static assignment of applications to machines
|
||
|
|
becomes increasingly challenging. To solve that problem, there are a number
|
||
|
|
of schedulers like Borg, Mesos, YARN, and Kubernetes. These can be used to
|
||
|
|
dynamically schedule Docker containers, Hadoop, Spark, and many other software
|
||
|
|
tools.
|
||
|
|
|
||
|
|
Vault is not limited to physical providers like AWS. Resource schedulers
|
||
|
|
can be treated as a provider, enabling Vault to request resources from them.
|
||
|
|
This allows Vault to be used in layers: to setup the physical infrastructure
|
||
|
|
running the schedulers as well as provisioning onto the scheduled grid.
|
||
|
|
|
||
|
|
#### Multi-Cloud Deployment
|
||
|
|
|
||
|
|
It's often attractive to spread infrastructure across multiple clouds to increase
|
||
|
|
fault-tolerance. By using only a single region or cloud provider, fault tolerance
|
||
|
|
is limited by the availability of that provider. Having a multi-cloud deployment
|
||
|
|
allows for more graceful recovery of the loss of a region or entire provider.
|
||
|
|
|
||
|
|
Realizing multi-cloud deployments can be very challenging as many existing tools
|
||
|
|
for infrastructure management are cloud-specific. Vault is cloud-agnostic
|
||
|
|
and allows a single configuration to be used to manage multiple providers, and
|
||
|
|
to even handle cross-cloud dependencies. This simplifies management and orchestration,
|
||
|
|
helping operators build large-scale multi-cloud infrastructures.
|
||
|
|
|