Difference between revisions of "Satori/glossary"
< Satori
m |
(links) |
||
Line 3: | Line 3: | ||
==== Control Plane Discovery ==== | ==== Control Plane Discovery ==== | ||
− | :Using native bindings, client libraries (pyrax, boto, libcloud, etc.) or cloud APIs to attain information about a configuration. This requires credentials/api tokens, and could provide: a server's image data, a server's region, a load-balancer's VIPs and nodes, networking info, etc. | + | :Using native bindings, client libraries ([https://github.com/rackspace/pyrax pyrax], [https://github.com/boto/boto boto], [https://github.com/openstack/python-novaclient novaclient], [https://github.com/apache/libcloud libcloud], [https://www.destroyallsoftware.com/talks/wat etc.]) or cloud APIs to attain information about a configuration. This requires credentials/api tokens, and could provide: a server's image data, a server's region, a load-balancer's VIPs and nodes, networking info, etc. |
==== Data Plane Discovery ==== | ==== Data Plane Discovery ==== | ||
:Making direct observations about a configuration by running commands/utilities directly on the system, or accessing and analyzing a system's network interface. This might require login credentials for the host resource, and could provide information ranging from disk usage to packages installed to motherboard fan speeds. | :Making direct observations about a configuration by running commands/utilities directly on the system, or accessing and analyzing a system's network interface. This might require login credentials for the host resource, and could provide information ranging from disk usage to packages installed to motherboard fan speeds. |
Revision as of 22:33, 6 March 2014
Configuration Discovery Terms
- The following terms are used to describe discovery more narrowly and differentiate configuration discovery concepts, while in combination they specify much of what Satori aims to accomplish.
Control Plane Discovery
- Using native bindings, client libraries (pyrax, boto, novaclient, libcloud, etc.) or cloud APIs to attain information about a configuration. This requires credentials/api tokens, and could provide: a server's image data, a server's region, a load-balancer's VIPs and nodes, networking info, etc.
Data Plane Discovery
- Making direct observations about a configuration by running commands/utilities directly on the system, or accessing and analyzing a system's network interface. This might require login credentials for the host resource, and could provide information ranging from disk usage to packages installed to motherboard fan speeds.