Vagrant DotVM DocumentationRelease 1.0

Krzysztof Magosa & Justin Cook

March 21, 2016

Contents

1 Get Started 3

2 Best Practices 5

3 Machine Options 7

4 Networking 9

5 SSH Keys 11

6 Shared Folders 13

7 Variables 15

8 Partitioners 17

i

ii

Vagrant DotVM Documentation, Release 1.0

DotVm is a Vagrant plugin which makes your life easy modelling large development environments. DotVM unifiesmultiple infrastructure enclaves known as projects. Each project can contain several VMs – limited only by hardwareresources – described with one large or several YAML files.

YAML’s declarative syntax is ideal for describing the structure of platforms. Once you have completed the descriptionand provided relevant provisioning information, DotVM will translate this to Vagrant and build the environment asdescribed.

All environments supported by Vagrant are supported by DotVM since we only extend Vagrant’s interface by providingYAML support.

Contents 1

Vagrant DotVM Documentation, Release 1.0

2 Contents

CHAPTER 1

Get Started

For the impatient, click here

3

Vagrant DotVM Documentation, Release 1.0

4 Chapter 1. Get Started

CHAPTER 2

Best Practices

DotVM was developed by practitioners of 12 factor methodology. We strongly believe in the declarative formatfor modelling and automating as well as keeping things practical. We strive to keep our best practices verystraightforward so as to keep the learning curve to a minimum.

5

Vagrant DotVM Documentation, Release 1.0

6 Chapter 2. Best Practices

CHAPTER 3

Machine Options

7

Vagrant DotVM Documentation, Release 1.0

8 Chapter 3. Machine Options

CHAPTER 4

Networking

One of DotVM’s strongest advanced features is providing access to Vagrant provider network features. These dochange from provider to provider, but developing code in a local virtualised environment and communicating withother nodes in a cloud provider has never been easier. Here we show you how.

9

Vagrant DotVM Documentation, Release 1.0

10 Chapter 4. Networking

CHAPTER 5

SSH Keys

There are times you need to use existing private keys for various reasons and trust public keys for box-to-box com-munications or accessing them from other hosts outside the Vagrant provider’s environment. DotVM provides theinterface via Vagrant to assist.

11

Vagrant DotVM Documentation, Release 1.0

12 Chapter 5. SSH Keys

CHAPTER 6

Shared Folders

13

Vagrant DotVM Documentation, Release 1.0

14 Chapter 6. Shared Folders

CHAPTER 7

Variables

15

Vagrant DotVM Documentation, Release 1.0

16 Chapter 7. Variables

CHAPTER 8

Partitioners

17