MV5 Servers

Overview

This is a cluster of vagrant virtualbox servers that will provision individually, on seperate ports so as to not conflict. They are for learning, are a work in progress and probably will never be finished.

Features

• Each server on different ssh ports that don't conflict
• Vagrantfile dependancy checking
• Provisioning and provisioned checks
• Proxy config's copied from host
• Private network interconnect between hosts
• Common perf and diag utils on all hosts
• Many security considerations

Requirements

• Windows 10/11 64bit host OS assumed
• VirtualBox Installed
  • NOTE: Don't install Virtualbox Extension Pack on corporate machines unless it's licenced.
• Vagrant Installed
• Powershell Core latest for host scripts. V7.2 Tested.
• OS Minimum: 8GB ram, 4 cores for one VM to start.
• OS Recommended: 32GB ram and 16 cores to run all VM's in parallel.

Virtualbox Setup

(Optional) File -> Preferences 
 -> General - Default Machine Folder: C:\var\VirtualBox VMs
 -> Display : Scaling(150% for 4K monitor)
 -> Extension Pack : Only for home users or Corporate Oracle License

Vagrant Setup

vagrant plugin install vagrant-vbguest
vagrant plugin install vagrant-proxyconf
vagrant plugin install vagrant-reload

Network Config

virtualbox intnet is the default internal network name

Vagrant-DevOps-Desktop     - 192.168.0.8  : 22 -> 2221, 
Vagrant-XE18c-Apex19c      - 192.168.0.2  : 22 -> 2222, 1521, 5500, 8080 # Depricated
Vagrant-XE21c-Apex22       - 192.168.0.2  : 22 -> 2222, 1521, 5500, 8080
Vagrant-Docker-Host        - 192.168.0.3  : 22 -> 2223, 8080 -> 8081
Vagrant-OpenSense-Firewall - 192.168.0.1  : 22 -> 2224, 443 -> 10443
Vagrant-Postgres-Timescale - 192.168.0.5  : 22 -> 2225, 5432
Vagrant-Nginx              - 192.168.0.2  : 22 -> 2226, 8080 -> 8082
Vagrant-Win10-Official     - 192.168.0.9  : 22 -> 2229, 3389 -> 3390, 5985 -> 5986, 5985 -> 5986
Vagrant-Win10-Official     - 192.168.0.10 : 22 -> 2230

History

Jun 2022 Updates

• Copied Vagrant-XE18c-Apex19c to Vagrant-XE21c-Apex22 and upgraded to Oracle Linux 8, Oracle XE DB 21c and Apex 22.1.

Dec 2019 Updates

• Vagrant-Nginx

Aug 2019 Updates

• Vagrant-XE-Apex - Working, with backup, private & public networks etc.
• Vagrant-Docker-Host - Docker tests ok, private & public networks etc.
• Vagrant-Postgres - TODO: Postgres built ok, not configured or tested.
• Vagrant-OpenSense-Firewall - Builds.
  • Occasional startup errors, unknown cause.
  • Command: ["modifyvm", "85124747-6da8-4397-8d27-5d3a3070842f", "--natpf1", "ssh,tcp,,2224,,22"]
  • Stderr: VBoxManage.exe: error: A NAT rule of this name already exists

TODO and Issues

opnsense 
- 10.2.0.1 - lan nic1 intnet
- 10.0.3.15 - Wan nic2

dockerhost & other hosts
10.0.2.15 - nat network
192.168.0.3 - intnet static ip - connects to all other hosts with static intnet

assigning 10.2.0.3 to the intnet of a guest for example, makes the guest unreachable.