teleport/vagrant
Ev Kontsevoy 30a1724927 .tsh profile change
`tsh` profiles shoudl only "kick in" when no --proxy flag is given.
If a user explicitly specifies --proxy flag, profiles should be ignored.
2016-11-30 15:46:36 -08:00
..
data Added a bunch of machines to vagrant's cluster-a 2016-06-22 12:17:11 -07:00
libvirt Version bump 2016-09-15 16:57:00 -07:00
virtualbox .tsh profile change 2016-11-30 15:46:36 -08:00
.gitignore Zero-config Vagrant environment with trusted clusters 2016-06-21 12:09:55 -07:00
base.rb Version bump 2016-09-15 16:57:00 -07:00
docker.service User Manual 2016-03-18 12:56:59 -07:00
docker.socket User Manual 2016-03-18 12:56:59 -07:00
README.md Better OSX support for Vagrant 2016-06-21 13:22:08 -07:00
teleport.service Better OSX support for Vagrant 2016-06-21 13:22:08 -07:00

Vagrant

This directory contains scripts to create multiple Vagrant machines for experimenting with Teleport on multiple nodes.

There are two nearly identical Vagrantfiles: one for Virtualbox and another for KVM/Libvirt, they both share base.rb

Default Configuration

data/var contains pre-created contents of guest's /var/lib/teleport data/opt contains pre-created contents of guest's /opt/teleport (configuration)

Three machines are created, grouped in two clusters, cluster_a and cluster_b:

  • a-auth: CA+node+proxy for "cluster_a"
  • a-node: Standalone node for "cluster_a"
  • b-auth: CA+node+proxy for "cluster_b"

A reverse tunnels from cluster_a to cluster_b is created. This allows users of cluster_b to login into any machine of cluster_a.

How to use

Easy:

~: vagrant up

Then you need to vagrant ssh into a-auth and b-auth and on both CAs you need to create 'vagrant' user:

~: tctl users add