A complete Linux cluster setup with Slade as the master desktop controller and 4 worker nodes, featuring animated welcome screens and real IP connectivity.
- Slade Master: Desktop Linux with GUI, controls all worker nodes
- Worker Nodes 1-4: Headless servers controlled by Slade
- Real IP: Public network bridge for internet access
- Private Network: Internal cluster communication
- VirtualBox (hypervisor): https://www.virtualbox.org/wiki/Downloads
- Vagrant (VM automation): https://developer.hashicorp.com/vagrant/downloads
- Minimum System: 8GB RAM, 4 CPU cores (for full cluster)
- Network: Bridged adapter capability for real IP
Install VirtualBox first, then Vagrant. Reboot if either installer asks you to.
cd /path/to/vProfile-Ubuntu
vagrant up sladevagrant ssh sladevagrant up worker1 worker2 worker3 worker4vagrant upOnce connected to Slade master, use these commands:
# Connect to worker nodes
connect-worker1 # SSH to Worker Node 1
connect-worker2 # SSH to Worker Node 2
connect-worker3 # SSH to Worker Node 3
connect-worker4 # SSH to Worker Node 4
# Cluster management
cluster-status # Check all nodes status
status # Same as cluster-status (alias)
deploy-all # Deploy to all worker nodes- Slade Master: 192.168.56.10 + Real IP (DHCP)
- Worker 1: 192.168.56.11 + Real IP (DHCP)
- Worker 2: 192.168.56.12 + Real IP (DHCP)
- Worker 3: 192.168.56.13 + Real IP (DHCP)
- Worker 4: 192.168.56.14 + Real IP (DHCP)
- Public Network: Bridged for real internet IP
- Private Network: Internal cluster communication
- Colorful ASCII art with figlet and lolcat
- System information display with neofetch
- Role-specific welcome messages
- Interactive command suggestions
- Color-coded prompts for each node
- Custom aliases and shortcuts
- Enhanced bash experience
- Command history and completion
- SSH key-based authentication
- Cluster status monitoring
- Centralized deployment scripts
- Desktop GUI for visual management
# Start specific VMs
vagrant up slade # Start master only
vagrant up worker1 # Start worker 1 only
vagrant up worker2 worker3 # Start workers 2 & 3
# Connect to specific VMs
vagrant ssh slade # Connect to master
vagrant ssh worker1 # Connect to worker 1
# Halt specific VMs
vagrant halt worker1 # Stop worker 1
vagrant halt slade # Stop master
# Status check
vagrant status # Show all VM status- Check VirtualBox Host-Only Network settings
- Ensure bridged adapter is selected correctly
- Try different network interface in bridge settings
# From Slade master, regenerate SSH keys
ssh-keygen -t rsa -b 4096 -f ~/.ssh/id_rsa -N ""
# Copy keys to workers (replace X with worker number)
ssh-copy-id vagrant@192.168.56.1X- Start VMs one by one instead of all together
- Reduce worker memory if needed (edit Vagrantfile)
- Use
vagrant haltwhen not using specific nodes
# Graceful shutdown
vagrant halt
# Complete removal (frees disk space)
vagrant destroy
# Remove specific VMs
vagrant destroy slade worker1| VM | Memory | CPU | Purpose |
|---|---|---|---|
| Slade Master | 2048MB | 2 | Desktop controller with GUI |
| Worker 1-4 | 1024MB | 1 | Headless worker nodes |
| Total | 6GB | 6 cores | Full cluster |
- SSH key-based authentication between nodes
- Isolated private network for cluster communication
- Real IP access for internet connectivity
- User-based access control