#77: Jeremy explains the GNS3 2.2 Architecture - podcast episode cover

#77: Jeremy explains the GNS3 2.2 Architecture

Sep 02, 201914 min
--:--
--:--
Download Metacast podcast app
Listen to this episode in Metacast mobile app
Don't just listen to podcasts. Learn from them with transcripts, summaries, and chapters for every episode. Skim, search, and bookmark insights. Learn more

Episode description

How does the GNS3 work? Jeremy (creator of GNS3) explains the GNS3 architecture. Note: The Server component is also called the Compute Server or Compute. GNS3 consists of four parts: - the user interface or GUI (gns3-gui or gns3-web projects) - the controller (gns3-server project) - the compute server (part of the gns3-server project) - the emulators (Qemu, Dynamips, VirtualBox…) The controller pilots everything, it manages the state of each project. Only one controller should run. The GUI displays a topology representing a project on a canvas and allow to perform actions on given project, sending API requests to the controller. The compute controls emulators to run nodes. A compute that is on the same server as the controller is the same process. The compute usually starts an emulator instance for each node. GNS3 Architecture: https://gns3-server.readthedocs.io/en/latest/general.html David’s details: YouTube: https://www.youtube.com/davidbombal Twitter: https://www.twitter.com/davidbombal Instagram: https://www.instagram.com/davidbombal LinkedIn: https://www.linkedin.com/in/davidbombal Facebook: https://www.facebook.com/davidbombal.co Website: http://www.davidbombal.com
For the best experience, listen in Metacast app for iOS or Android