diff --git a/README.md b/README.md index c76ffd11bb88c20dfe630610d0267714b2326a95..123e8becb666efda6bdb2a7ee89ea45dd00550c2 100644 --- a/README.md +++ b/README.md @@ -10,16 +10,16 @@ Vagrantfile and additional configuration to deploy a development environment lik The full environment consists of: - 1 Ubuntu VM for the Ansible control node -- 3 vSRXs fully interconnected +- 3 fully-interconnected Juniper vSRXs + +The VM specifications are as follows: -VM specifications: * vSRXs have 2 vCPUs and 4GB RAM * The Ansible control node has 2vCPUs and 1GB RAM -In order to keep the initial demands on the host machine low, only one vSRX will be spun up; -the second and third vSRX's are commented out in the `Vagrantfile`. +In order to keep the initial demands on the host machine low, only one vSRX will be spun up; the second and third vSRX's are commented out in the relevant Vagrant control file. -## What's in this repo? +## What's in this repository? Here is the directory structure: @@ -134,12 +134,16 @@ above with their current state. For more information about a specific VM, run `vagrant status NAME`. ``` +Good. Vagrant know about the two devices (remember, the second and third devices are commented out in the control file) but they are not yet active. + +__Yet.__ + 4. Activate Vagrant -Type ```vagrant up``` without any argument to activate all of the virtual devices. This may take up to 10-15 mins depending on your device and its connection to the Internet. +Type ```vagrant up``` (yes, without any arguments) to activate all of the virtual devices. This may take between and 15 mins depending on your host machine device and its connection to the Internet. ``` -dcunningham@hellfire ~/D/g/ansible-minilab (master)> vagrant up +testhost> vagrant up Bringing machine 'vsrx1' up with 'virtualbox' provider... Bringing machine 'ansible-node' up with 'virtualbox' provider... ==> vsrx1: Box 'juniper/ffp-12.1X47-D15.4-packetmode' could not be found. Attempting to find and install... @@ -151,12 +155,8 @@ Bringing machine 'ansible-node' up with 'virtualbox' provider... vsrx1: Downloading: https://vagrantcloud.com/juniper/boxes/ffp-12.1X47-D15.4-packetmode/versions/0.5.0/providers/virtualbox.box ==> vsrx1: Successfully added box 'juniper/ffp-12.1X47-D15.4-packetmode' (v0.5.0) for 'virtualbox'! ==> vsrx1: Importing base box 'juniper/ffp-12.1X47-D15.4-packetmode'... -==> vsrx1: Matching MAC address for NAT networking... -==> vsrx1: Checking if box 'juniper/ffp-12.1X47-D15.4-packetmode' version '0.5.0' is up to date... -==> vsrx1: Setting the name of the VM: ansible-minilab_vsrx1_1639066331007_61178 -==> vsrx1: Clearing any previously set network interfaces... ... -...lots and lots of output including software updates... +...lots and lots of output including software downloads and OS updates... ... ==> ansible-node: Running provisioner: file... ansible-node: ./ansible-minilab => /home/vagrant/ansible-minilab @@ -164,7 +164,7 @@ Bringing machine 'ansible-node' up with 'virtualbox' provider... 5. Post-activation vSRX commands -Once the vSRX device is up, you have to do a __little__ manual configuration. The commands are as follows; +Once the vSRX device is fully active you have to do a __little__ manual configuration. The commands are as follows; ``` set system login user vagrant class super-user