Difference between revisions of "Satori/glossary"
< Satori
(Differentiate configuration discovery concepts) |
m (style) |
||
Line 1: | Line 1: | ||
− | === Discovery === | + | === 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. | :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, 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 (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. | ||
− | + | ==== 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:28, 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, 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.