From 41cdb61d77ab5c32638ee19e6a6b4a9854088e4e Mon Sep 17 00:00:00 2001 From: "Scott S. Lowe" Date: Wed, 29 Jun 2016 21:53:58 -0600 Subject: [PATCH] Update master README.md Add new learning environments to master README.md. --- README.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/README.md b/README.md index d14d1d1..578fc03 100644 --- a/README.md +++ b/README.md @@ -8,10 +8,14 @@ This repository contains a variety of files and tools for learning new technolog **consul**: In this folder you'll find a `Vagrantfile` and supporting documents to run a Consul cluster under Vagrant on your local laptop. The provisioning is handled via shell scripts. +**containerd-runc**: _This is a placeholder for future work._ + **coreos-cloudinit-toolbox**: This folder contains files for using cloud-init to customize the CoreOS toolbox. This learning environment can be used with local Vagrant VMs, with OpenStack instances, or with AWS instances. **debian-generic**: This folder has a Vagrant environment for spinning up a generic, 64-bit Debian 8.0 ("Jessie") VM. Note there's nothing special here---just a plain, generic Debian VM. No custom provisioning is provided in this environment. +**docker-ipvlan-l3**: This folder has files to create a learning environment for using ipvlan L3 interfaces with Docker containers. + **docker-ipvlan**: This folder has files to create a learning environment for using ipvlan interfaces with Docker containers. **docker-macvlan**: This folder has files to create a learning environment for using macvlan interfaces with Docker containers. @@ -24,8 +28,12 @@ This repository contains a variety of files and tools for learning new technolog **etcd-2.0**: Use the `Vagrantfile` and other files in this directory to turn up an etcd 2.0.9 cluster running on Ubuntu 14.04. The provisioning is handled via shell scripts. +**ipvs-docker**: Use this learning environment to experiment with using IPVS/LVS for load balancing Docker containers. + **kvm-macvtap**: This learning environment has a `Vagrantfile` and supporting files for working with KVM and macvtap interfaces on Ubuntu 14.04. The provisioning is handled via Ansible (pre-2.0) installed on the Vagrant host. +**junos**: _This is a placeholder for future work._ + **kvm**: The files in this folder allow you to create a learning environment for working with KVM and Libvirt on Ubuntu 14.04. The provisioning is handled via Ansible (pre-2.0) installed on the Vagrant host. **lxc**: This folder holds a `Vagrantfile` and supporting files to create an environment for working with LXC (pronounced "lex-see"). LXC is a set of tools for working with OS containers. The provisioning is handled via Ansible (pre-2.0) installed on the Vagrant host. @@ -40,6 +48,8 @@ This repository contains a variety of files and tools for learning new technolog **ovs-geneve**: This folder contains a Vagrant environment and supporting files for compiling Open vSwitch (OVS) from source and using Geneve tunneling to connect network namespaces on two different VMs. +**ovs-multi-br**: In this folder is a Vagrant environment, Ansible playbook, and related data files for experimenting with multiple Open vSwitch (OVS) bridges. + **photon-ansible**: In this folder is a Vagrant environment for using Ansible with VMware Photon; specifically, for using Ansible to configure Photon's pre-installed Docker daemon to listen over a network socket. Naturally, the provisioning is handled via Ansible (pre-2.0) installed on the Vagrant host. **photon-cloudinit**: This folder contains the files to spin up VMs, using Vagrant and customized via `cloud-init`, running the VMware Photon Technical Preview. The provisioning is handled via shell scripts. @@ -70,6 +80,8 @@ This repository contains a variety of files and tools for learning new technolog **vagrant-json**: The files in this folder illustrate the use of an external JSON data file to drive Vagrant. +**vagrant-multi-platform**: This Vagrant environment demonstrates one possible way to create a `Vagrantfile` that supports multiple virtualization platforms without any edits needed across platforms. + **vagrant-openstack-multi**: This folder is similar to `vagrant-openstack`, but supports Vagrant operations on multiple instances. **vagrant-openstack**: This folder contains a `Vagrantfile` and supporting files for using Vagrant with the OpenStack provider. This allows you to use Vagrant to provision and destroy an instance in an OpenStack cloud.