Simultaneous client workloads

Challenge

drake-no-img

Working with multiple clients simultaneously often requires that we do the VPN Shuffle to hop between client environments, limiting our ability to multi-task when possible, or even necessary.​

These hops could potentially interfere with...

  • File transfers.
  • SSH session operations; e.g., monitoring/logging a switch upgrade.
  • Etc.

Solution

drake-yes-img

We can create "client" VMs, that we'll call jump hosts, to work around this...

  • ClientA_VM is our jump host with Client A's VPN client.
  • ClientB_VM is our jump host with Client B's VPN client.
  • ClientC_VM is our jump host with Client C's VPN client.

Since these are separate jump hosts, we can connect to Client A, B, and C VPNs simultaneously, simply switching between them to access their respective remote environments.​ This is a step in the right direction but carries it's own challenge... the tooling, or software that we use to manage the remote environments.