gns3-server/docs/endpoints.rst

44 lines
1.0 KiB
ReStructuredText
Raw Normal View History

2016-06-21 11:47:22 +03:00
Endpoints
------------
2018-03-12 08:38:50 +02:00
GNS3 exposes two type of endpoints:
2016-06-21 11:47:22 +03:00
2018-03-12 08:38:50 +02:00
* Controller endpoints
* Compute endpoints
2016-06-21 11:47:22 +03:00
2018-03-12 08:38:50 +02:00
Controller endpoints
~~~~~~~~~~~~~~~~~~~~~
2016-06-21 11:47:22 +03:00
2018-03-12 08:38:50 +02:00
The controller manages everything, it is the central decision point
and has a complete view of your network topologies, what nodes run on
which compute, the links between them etc.
2016-06-21 11:47:22 +03:00
2018-03-12 08:38:50 +02:00
This is the high level API which can be used by users to manually control
the GNS3 backend. The controller will call the compute endpoints when needed.
A standard GNS3 setup is to have one controller and one or many computes.
2016-06-21 11:47:22 +03:00
.. toctree::
:glob:
:maxdepth: 2
api/v2/controller/*
2018-03-12 08:38:50 +02:00
Compute Endpoints
~~~~~~~~~~~~~~~~~~
2016-06-21 11:47:22 +03:00
2018-03-12 08:38:50 +02:00
A compute is the GNS3 process running on a host. It controls emulators in order to run nodes
(e.g. VMware VMs with VMware Workstation, IOS routers with Dynamips etc.)
2016-06-21 11:47:22 +03:00
.. WARNING::
2018-03-12 08:38:50 +02:00
These endpoints should be considered low level and private.
They should only be used by the controller or for debugging purposes.
2016-06-21 11:47:22 +03:00
.. toctree::
:glob:
:maxdepth: 2
api/v2/compute/*