Closed AJNOURI closed 6 years ago
No bug, works as designed.
The controller manages only the projects, nodes, links, ... that are created/modified by controller API calls. By using compute API calls you bypass the controller. It gets no information about those changes.
In short: Don't use the compute API unless you want to implement your own controller. Exclusively use the controller API.
See also the warning in http://api.gns3.net/en/2.1/endpoints.html#compute-endpoints
Warning These endpoints should be considered low level and private. They should only be used by the controller or for debugging purposes.
Here an example to create a docker node with the controller API (done with Postman). Mandatory parameters are compute_id ("vm" for the GNS3-VM), name and node_type. In the properties parameter you add the node specific parameters. Those are documented in the compute API for that node type.
ok, got it. Thanks @ehlers for your explanations.
Thank you very much Mr. ehlers, it worked for me. Could you help me adding an Ubuntu virtual machine the same way? Thanks :)
No, after this initial help you have to figure that out by yourself.
Tip: Besides using the documentation you can use the debug logging or Wireshark to look, how the GNS3 GUI uses the API.
Which documentation? Ok I'll do that but I need your help in case it doesn't work hh. Thank you
I won't answer here. This is for discussing issues in GNS3, use https://gns3.com for support. But as I don't have an account there, other people will (hopefully) answer your questions.
Please I am kind of stuck here, would you like to show me how to do it? Thank you
Using the API to create a contrainer, the command seems to be executed propertly:
But the container is neither listed in the list of nodes nor showed in the GUI: