Merge pull request #253 from miharp/fix/puppet-master-rename-223

fix: rename Puppet master/agent to OpenVox Server/agent across 8x docs

Author: tuxmea

docs/_openvox_8x/config_about_settings.markdown

@@ -144,17 +144,17 @@ export LANGUAGE=''
 export LC_ALL=''
 ```
 
-To set the locale for the Puppet agent service, you can add these `export` statements to:
+To set the locale for the OpenVox agent service, you can add these `export` statements to:
 
 -   `/etc/sysconfig/puppet` on RHEL and its derivatives
 -   `/etc/default/puppet` on Debian, Ubuntu, and their derivatives
 
 After updating the file, restart the Puppet service to apply the change.
 
 {:.task}
-### Setting your locale for the Puppet agent service on macOS
+### Setting your locale for the OpenVox agent service on macOS
 
-To set the locale for the Puppet agent service on macOS, update the `LANG` setting in the `/Library/LaunchDaemons/com.puppetlabs.puppet.plist` file.
+To set the locale for the OpenVox agent service on macOS, update the `LANG` setting in the `/Library/LaunchDaemons/com.puppetlabs.puppet.plist` file.
 
 ```xml
 <dict>
@@ -181,4 +181,4 @@ Set-WinSystemLocale en-US
 
 Puppet 5.3.2 added the optional Boolean `disable_i18n` setting, which you can configure in `puppet.conf`. If set to `true`, Puppet disables localized strings in log messages, reports, and parts of the command-line interface. This can improve performance when using Puppet modules, especially if [environment caching](./environments_creating.markdown#environment_timeout) is disabled, and even if you don't need localized strings or the modules aren't localized. This setting is `false` by default in open source Puppet.
 
-If you're experiencing performance issues, configure this setting in the `[master]` section of the Puppet master's `puppet.conf` file. To force unlocalized messages, which are in English by default, configure this section in a node's `[main]` or `[user]` sections of `puppet.conf`.
+If you're experiencing performance issues, configure this setting in the `[server]` section of the OpenVox Server's `puppet.conf` file. To force unlocalized messages, which are in English by default, configure this section in a node's `[main]` or `[user]` sections of `puppet.conf`.

docs/_openvox_8x/config_file_auth.markdown

@@ -34,9 +34,9 @@ Access to Puppet's HTTPS API is configured in `auth.conf`.
 {:.concept}
 ## Puppet's HTTPS API
 
-The Puppet agent service requests configurations over HTTPS, and the Puppet master application provides several HTTPS endpoints to support this. (For example, requesting a catalog uses a different endpoint than submitting a report.) There are also a few endpoints that aren't used by Puppet agent.
+The OpenVox agent service requests configurations over HTTPS, and the OpenVox Server application provides several HTTPS endpoints to support this. (For example, requesting a catalog uses a different endpoint than submitting a report.) There are also a few endpoints that aren't used by OpenVox agent.
 
-Because some endpoints should have restricted access (for example, a node shouldn't request another node's configuration catalog), the Puppet master has a list of access rules for all of its HTTPS services. You can edit these rules in `auth.conf`.
+Because some endpoints should have restricted access (for example, a node shouldn't request another node's configuration catalog), the OpenVox Server has a list of access rules for all of its HTTPS services. You can edit these rules in `auth.conf`.
 
 ## Location
 
@@ -89,7 +89,7 @@ allow *
 ### clients can also access these paths, though they rarely need to.
 
 # allow access to the CA certificate; unauthenticated nodes need this
-# in order to validate the puppet master's certificate
+# in order to validate the OpenVox Server's certificate
 path /puppet-ca/v1/certificate/ca
 auth any
 method find
@@ -115,13 +115,13 @@ auth any
 
 ## Access control behavior
 
-Whenever Puppet master receives a valid HTTPS request, it checks it against its full list of authorization rules, in order. As soon as it finds a rule that matches the request, it will use that rule's `allow` and `allow_ip` permissions to decide whether to allow the request. If the request isn't allowed, Puppet will deny it, and will not check any further authorization rules.
+Whenever OpenVox Server receives a valid HTTPS request, it checks it against its full list of authorization rules, in order. As soon as it finds a rule that matches the request, it will use that rule's `allow` and `allow_ip` permissions to decide whether to allow the request. If the request isn't allowed, Puppet will deny it, and will not check any further authorization rules.
 
 In other words, authorization rules work like simple firewall rules. If you want to specifically allow a request that could be caught and rejected by some more general rule, you need to put the more specific rule earlier in the auth.conf file.
 
 ### Default auth rules
 
-Puppet master uses two sets of auth rules: the rules from auth.conf, which it checks first, and a set of hardcoded default rules, which it only checks if a request doesn't match any rules in auth.conf.
+OpenVox Server uses two sets of auth rules: the rules from auth.conf, which it checks first, and a set of hardcoded default rules, which it only checks if a request doesn't match any rules in auth.conf.
 
 If you are modifying auth.conf at all, **you should never rely on the hardcoded default rules.** Start with [a default auth.conf that explicitly includes copies of all of the default rules][default_file].
 
@@ -174,7 +174,7 @@ Which URLs the ACL applies to. **Required.** Must be the first directive in the
 
     path /puppet/v3/report
 
-If the value of `path` is just an absolute path, Puppet master interprets it as a prefix. The ACL will match any URL that _begins_ with that string.
+If the value of `path` is just an absolute path, OpenVox Server interprets it as a prefix. The ACL will match any URL that _begins_ with that string.
 
 #### Regular expression
 
@@ -215,7 +215,7 @@ Whether the ACL applies to client-verified or non-client-verified HTTPS requests
 
 **Allowed values:** `yes`, `any`, `no` (with `on` and `off` as synonyms). Must be a single value. Optional; defaults to `yes` (verified) if omitted.
 
-Puppet agent makes client-verified requests to fetch configuration data and submit reports, but makes unverified requests to ask for a certificate.
+OpenVox agent makes client-verified requests to fetch configuration data and submit reports, but makes unverified requests to ask for a certificate.
 
 If you set `auth any`, it allows nodes to access an endpoint without a valid certificate. (Setting it to `no` is not very useful, since it will _reject_ requests that have valid certificates.)
 

docs/_openvox_8x/config_file_autosign.markdown

@@ -7,27 +7,27 @@ title: "Config files: autosign.conf"
 [autosign setting]: ./configuration.html#autosign
 [confdir]: ./dirs_confdir.html
 
-The `autosign.conf` file can allow certain certificate requests to be automatically signed. It is only valid on the CA Puppet master server; a Puppet master not serving as a CA does not use `autosign.conf`.
+The `autosign.conf` file can allow certain certificate requests to be automatically signed. It is only valid on the CA OpenVox Server server; an OpenVox Server not serving as a CA does not use `autosign.conf`.
 
 ## More about autosigning
 
-> **Warning:** Because any host can provide any certname when requesting a certificate, basic autosigning is essentially **insecure**. Use it only when you fully trust any computer capable of connecting to the Puppet master.
+> **Warning:** Because any host can provide any certname when requesting a certificate, basic autosigning is essentially **insecure**. Use it only when you fully trust any computer capable of connecting to the OpenVox Server.
 
 Puppet also provides a policy-based autosigning interface using custom policy executables, which can be more flexible and secure than the `autosign.conf` whitelist but more complex to configure.
 
 For more information, see [the documentation about certificate autosigning][autosigning].
 
 ## Location
 
-Puppet looks for `autosign.conf` at `$confdir/autosign.conf` by default. To change this path, configure the [`autosign` setting][autosign setting] in the `[master]` section of `puppet.conf`.
+Puppet looks for `autosign.conf` at `$confdir/autosign.conf` by default. To change this path, configure the [`autosign` setting][autosign setting] in the `[server]` section of `puppet.conf`.
 
 The default `confdir` path depends on your operating system. [See the confdir documentation for more information.][confdir]
 
-> **Note:** The `autosign.conf` file must not be executable by the Puppet master's user account. If the `autosign` setting points to an executable file, Puppet instead treats it like a custom policy executable even if it contains a valid `autosign.conf` whitelist.
+> **Note:** The `autosign.conf` file must not be executable by the OpenVox Server's user account. If the `autosign` setting points to an executable file, Puppet instead treats it like a custom policy executable even if it contains a valid `autosign.conf` whitelist.
 
 ## Format
 
-The `autosign.conf` file is a line-separated list of certnames or domain name globs. Each line represents a node name or group of node names for which the CA Puppet master will automatically sign certificate requests.
+The `autosign.conf` file is a line-separated list of certnames or domain name globs. Each line represents a node name or group of node names for which the CA OpenVox Server will automatically sign certificate requests.
 
 ```
 rebuilt.example.com
@@ -39,4 +39,4 @@ Domain name globs do not function as normal globs: an asterisk can only represen
 
 > **Note:** The `autosign.conf` file can safely be an empty file or not-existent, even if the `autosign` setting is enabled. An empty or non-existent `autosign.conf` file is an empty whitelist, meaning that Puppet does not autosign any requests. If you create `autosign.conf` as a non-executable file and add certnames to it, Puppet then automatically uses the file to whitelist incoming requests without needing to modify `puppet.conf`.
 >
-> To _explicitly_ disable autosigning, set `autosign = false` in the `[master]` section of the CA Puppet master's `puppet.conf`, which disables CA autosigning even if `autosign.conf` or a custom policy executable exists.
+> To _explicitly_ disable autosigning, set `autosign = false` in the `[server]` section of the CA OpenVox Server's `puppet.conf`, which disables CA autosigning even if `autosign.conf` or a custom policy executable exists.

docs/_openvox_8x/config_file_device.markdown

@@ -7,7 +7,7 @@ title: "Config files: device.conf"
 [deviceconfig]: ./configuration.html#deviceconfig
 [confdir]: ./dirs_confdir.html
 
-The `puppet-device` subcommand retrieves catalogs from the Puppet master and applies them to remote devices.
+The `puppet-device` subcommand retrieves catalogs from the OpenVox Server and applies them to remote devices.
 Devices to be managed by the `puppet-device` subcommand are configured in `device.conf`.
 
 [See the puppet-device documentation for details.][puppet-device]

docs/_openvox_8x/config_file_environment.markdown

@@ -11,7 +11,7 @@ title: "Config files: environment.conf"
 [main manifest]: ./dirs_manifest.html
 [configuring_timeout]: ./environments_configuring.html#environmenttimeout
 
-Any [environment][] can contain an `environment.conf` file. This file can override several settings whenever the Puppet master is serving nodes assigned to that environment.
+Any [environment][] can contain an `environment.conf` file. This file can override several settings whenever the OpenVox Server is serving nodes assigned to that environment.
 
 ## Location
 
@@ -68,7 +68,7 @@ That is, Puppet will add the environment's `modules` directory to the value of t
 
 ### `manifest`
 
-The [main manifest][] the Puppet master will use when compiling catalogs for this environment. This can be one file or a directory of manifests to be evaluated in alphabetical order. Puppet manages this path as a directory if one exists or if the path ends with a slash (`/`) or dot (`.`).
+The [main manifest][] the OpenVox Server will use when compiling catalogs for this environment. This can be one file or a directory of manifests to be evaluated in alphabetical order. Puppet manages this path as a directory if one exists or if the path ends with a slash (`/`) or dot (`.`).
 
 If this setting isn't set, Puppet will use the environment's `manifests` directory as the main manifest, even if it is empty or absent. A directory environment will never use the global `manifest` from [puppet.conf][].
 
@@ -86,7 +86,7 @@ If this setting isn't set, the config version will be the **time** at which the
 
 ### `environment_timeout`
 
-How long the Puppet master should cache the data it loads from an environment. If present, this will override the value of `environment_timeout` from [puppet.conf][].
+How long the OpenVox Server should cache the data it loads from an environment. If present, this will override the value of `environment_timeout` from [puppet.conf][].
 
 * Unless you have a specific reason, we recommend only setting `environment_timeout` globally, in puppet.conf.
 * We also don't recommend using any value other than `0` or `unlimited`.

docs/_openvox_8x/config_file_main.markdown

@@ -15,7 +15,7 @@ title: "Config files: The main config file (puppet.conf)"
 [environmentpath]: ./configuration.html#environmentpath
 [puppetserver_diff]: /openvox-server/latest/puppet_conf_setting_diffs.html
 
-The `puppet.conf` file is Puppet's main config file. It configures all of the Puppet commands and services, including Puppet agent, Puppet master, Puppet apply, and Puppet cert. Nearly all of the settings listed in the [configuration reference][conf_ref] can be set in puppet.conf.
+The `puppet.conf` file is Puppet's main config file. It configures all of the Puppet commands and services, including OpenVox agent, OpenVox Server, Puppet apply, and Puppet cert. Nearly all of the settings listed in the [configuration reference][conf_ref] can be set in puppet.conf.
 
 It resembles a standard INI file, with a few syntax extensions. Settings can go into application-specific sections, or into a `[main]` section that affects all applications.
 
@@ -55,7 +55,7 @@ environment = production
 runinterval = 1h
 strict_variables = true
 
-[master]
+[server]
 dns_alt_names = puppetmaster01,puppetmaster01.example.com,puppet,puppet.example.com
 reports = puppetdb
 storeconfigs_backend = puppetdb
@@ -85,15 +85,15 @@ As soon as a new config section `[name]` appears in the file, the former config
 Puppet uses four **config sections**:
 
 * `main` is the global section used by all commands and services. It can be overridden by the other sections.
-* `master` is used by the Puppet master service and the Puppet cert command.
-* `agent` is used by the Puppet agent service.
+* `master` is used by the OpenVox Server service and the Puppet cert command.
+* `agent` is used by the OpenVox agent service.
 * `user` is used by the Puppet apply command, as well as many of the less common [Puppet subcommands][subcommands].
 
 Puppet prefers to use settings from one of the three application-specific sections (`master`, `agent`, or `user`). If it doesn't find a setting in the application section, it will use the value from `main`. (If `main` doesn't set one, it will fall back to the default value.)
 
 ### Puppet Server ignores some config settings
 
-If you're using Puppet Server, you should note that it honors almost all settings in `puppet.conf` and should pick them up automatically. However, [some Puppet Server settings differ from a Ruby Puppet master’s `puppet.conf` settings][puppetserver_diff].
+If you're using Puppet Server, you should note that it honors almost all settings in `puppet.conf` and should pick them up automatically. However, [some Puppet Server settings differ from a Ruby OpenVox Server’s `puppet.conf` settings][puppetserver_diff].
 
 ### Comment lines
 
@@ -144,7 +144,7 @@ You generally shouldn't do this, as the defaults are good for most users. Howeve
 The allowed keys in the hash are `owner`, `group`, and `mode`. There are only two valid values for the `owner` and `group` keys:
 
 * `root` --- the root or Administrator user or group should own the file.
-* `service` --- the user or group that the Puppet service is running as should own the file. (The service's user and group are specified by the `user` and `group` settings. On a Puppet master running open source Puppet, these default to `puppet`;  on Puppet Enterprise they default to `pe-puppet`.)
+* `service` --- the user or group that the Puppet service is running as should own the file. (The service's user and group are specified by the `user` and `group` settings. On an OpenVox Server running open source Puppet, these default to `puppet`;  on Puppet Enterprise they default to `pe-puppet`.)
 
 ### Interpolating variables in settings
 

docs/_openvox_8x/config_file_oid_map.md

@@ -11,11 +11,11 @@ title: "Config files: custom_trusted_oid_mapping.yaml"
 
 The `custom_trusted_oid_mapping.yaml` file lets you set your own short names for [certificate extension][extensions] object identifiers (OIDs), which can make [the `$trusted` variable][trusted] more useful.
 
-It is only valid on a Puppet master server; in Puppet apply, the compiler doesn't add certificate extensions to `$trusted`.
+It is only valid on an OpenVox Server server; in Puppet apply, the compiler doesn't add certificate extensions to `$trusted`.
 
 ## More about certificate extensions
 
-When a node requests a certificate, it can ask the CA to include some additional, permanent metadata in that cert. (Puppet agent uses [the `csr_attributes.yaml` file][csr_attributes] to decide what extensions to request.)
+When a node requests a certificate, it can ask the CA to include some additional, permanent metadata in that cert. (OpenVox agent uses [the `csr_attributes.yaml` file][csr_attributes] to decide what extensions to request.)
 
 If the CA signs a certificate with extensions included, those extensions are available as [trusted facts][trusted] in the top-scope `$trusted` variable. Your manifests or node classifier can then use those trusted facts to decide which nodes can receive which configurations.
 

docs/_openvox_8x/config_file_puppetdb.markdown

@@ -6,7 +6,7 @@ title: "Config files: puppetdb.conf"
 [puppetdb_connection]: /openvoxdb/latest/puppetdb_connection.html
 
 
-The `puppetdb.conf` file configures how Puppet should connect to one or more [PuppetDB](/openvoxdb/latest/) servers. It is only used if you are using PuppetDB and have [connected your Puppet master to it](/openvoxdb/latest/connect_puppet_master.html).
+The `puppetdb.conf` file configures how Puppet should connect to one or more [PuppetDB](/openvoxdb/latest/) servers. It is only used if you are using PuppetDB and have [connected your OpenVox Server to it](/openvoxdb/latest/connect_puppet_master.html).
 
 ## PuppetDB documentation