From 9e05a7e99a1c794bb0a253f4c8bbabdeb9807298 Mon Sep 17 00:00:00 2001 From: Rob Cameron Date: Mon, 6 Apr 2015 16:57:28 -0700 Subject: [PATCH] added more docs --- docs/proctorconfiguration.md | 33 +++++++++++++++++++++++++++++++++ docs/recoveringthelab.md | 2 ++ proctor/Vagrantfile | 3 --- 3 files changed, 35 insertions(+), 3 deletions(-) diff --git a/docs/proctorconfiguration.md b/docs/proctorconfiguration.md index 453d048..693bcac 100644 --- a/docs/proctorconfiguration.md +++ b/docs/proctorconfiguration.md @@ -1,2 +1,35 @@ Configuring the Proctor Lab =========================== + +Everything that is needed to run the proctor lab is contained within this repository. + +Proctor VMs +----------- + +The proctor VMs are all run via Vagrant with VirtualBox. The vagrant file is located in the proctor directory at the root of the repository. + +There are three virtual machines contained within the proctor vagrant file. Please review the [topology](https://github.com/JNPRAutomate/JNPRAutomateDemo-Student/blob/master/docs/topologyoverview.md) as needed. The NetDevOps public and vSRX headend use fixed IP addresses. This simplifies the configuration within various modules of the lab. It is suggested to run the headend on a host within 16GB of RAM and a quad-core processor. It is possible to run a student VM set and the proctor VM set on the same host. However as you bring up more and more client hosts it may tax the headend SRX. + +- NetDevOps Public + + - Uses bridged interface for 10.10.0.10 + - Hosts registration server + - [Reggie](https://github.com/JNPRAutomate/reggie) + - Hosts license files + - You need to provide the license files as do to restrictions they are not in the lab + - vSRX licenses can be used accross multiple hosts + +- NetDevOps Private + + - Uses private network interface for 192.168.10.10 + - Connected to vSRX Headend only + - Only accessible through the vSRX headend host + - Used to test that the VPN is successfully up + +- vSRX Headend + + - Uses bridged interface for 10.10.0.5 + - Uses private network interface for 192.168.10.1 + - If your network does not provide a DHCP server this host can provide DHCP services + - This must be configured seperately + diff --git a/docs/recoveringthelab.md b/docs/recoveringthelab.md index a0cbd55..7984e11 100644 --- a/docs/recoveringthelab.md +++ b/docs/recoveringthelab.md @@ -265,3 +265,5 @@ vagrant@NetDevOps-Student:/vagrant/ansible$ ``` Your device should now have the complete configuration on it. + +![Success Wyatt](https://github.com/JNPRAutomate/AutomationMemes/blob/master/success_wyatt.gif) diff --git a/proctor/Vagrantfile b/proctor/Vagrantfile index d2f082b..7f3f619 100644 --- a/proctor/Vagrantfile +++ b/proctor/Vagrantfile @@ -16,9 +16,6 @@ Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| ndo.vm.network "public_network", netmask: "255.255.252.0", ip: "10.10.0.10" - ndo.vm.network "private_network", - ip: "192.168.10.128", - virtualbox__intnet: "NetDevOps-Private" ndo.vm.synced_folder "../", "/vagrant", disabled: false ndo.vm.provider "virtualbox" do |v|