Comparison of open-source configuration management software: Difference between revisions

Content deleted Content added
Basic properties: Small WP:COPYEDITs WP:EoS: WP:TERSE, clarify. MOS:FIRSTABBReviation clarify, define before WP:ABBR in parentheses. WP:BADEMPHASIS MOS:QUOTEMARKS > WP:ITALICs or <code>s. WP:LINKs: needless WP:PIPEs > WP:NOPIPEs, update-standardizes, adds. Avoidable WP:SLASH > comma.
m Basic properties: Expression format simplify.
Line 12:
"Verify mode" (also called [[dry run (testing)|dry run]]) refers to having an ability to determine whether a node is conformant with a guarantee of not modifying it, and typically involves the exclusive use of an internal language supporting read-only mode for all potentially system-modifying operations. ''[[Mutual authentication]]'' (mutual auth) refers to the client verifying the server and vice versa.
 
''Agent'' describes whether additional [[Daemon (computing)|software daemons]] are required. Depending on the management software these agents are usually deployed on the target system or on one or many central ''controller'' servers. Although <code>Agent-less</code> = <code>No</code> is colored red and might seem to be a negative, instead, having an agent can be considered quite advantageous to many. Consider the impact if an agent-less tool loses connectivity to a node while making critical changes—leaving the node in an indeterminate state that compromises its (production?) function.
 
<div class="overflowbugx" style="overflow:auto; width:99%;">