Merge pull request #175 from miharp/feat/modernize-openvox-8x-small-batch

Modernize _openvox_8x: branding and link fixes (small batch)

Author: tuxmea

docs/_openvox_8x/bgtm.md

@@ -245,7 +245,7 @@ This means you must `include x` in the main class to ensure the dependency is in
 
 Ensure that the module works in a variety of conditions, and that the options and parameters of your module work together to an appropriate end result.
 
-We recommend several testing frameworks available to help you write unit and acceptance tests. Some of these tools are already included in the [Puppet Development Kit (PDK)](https://www.puppet.com/docs/pdk/latest/pdk.html).
+We recommend several testing frameworks available to help you write unit and acceptance tests. Some of these tools are already included in the Puppet Development Kit (PDK).
 
 > **Note:** The open source version of PDK is no longer supported by Puppet. It may still be functional, but no further updates or bug fixes will be provided.
 
@@ -277,7 +277,7 @@ require 'puppetlabs_spec_helper/rake_tasks'
 
 ### Beaker-rspec
 
-[Beaker-rspec](https://github.com/puppetlabs/beaker-rspec) is an acceptance/integration testing framework.
+[Beaker-rspec](https://github.com/voxpupuli/beaker-rspec) is an acceptance/integration testing framework.
 
 It provisions one or more virtual machines on various hypervisors (such as [Vagrant](https://www.vagrantup.com/)) and then checks the result of applying your module in a realistic environment.
 

docs/_openvox_8x/cheatsheet_core_types.md

@@ -71,7 +71,7 @@ Manages files, directories, and symlinks.
 #### For Normal Files
 
 * [`source`](./type.html#file-attribute-source) -- Where to download contents for the file. Usually a `puppet:///` URL.
-* [`content`](./type.html#file-attribute-content) -- The file's desired contents, as a string. Most useful when paired with [templates](https://docs.puppet.com/guides/templating.html), but you can also use the output of the [file function](./function.html#file).
+* [`content`](./type.html#file-attribute-content) -- The file's desired contents, as a string. Most useful when paired with [templates](./lang_template.html), but you can also use the output of the [file function](./function.html#file).
 
 {:.section}
 #### For Directories
@@ -148,7 +148,7 @@ If a service has a bad init script, you can work around it and manage almost any
 {:.concept}
 ### notify
 
-Logs an arbitrary message, at the `notice` log level. This appears in the POSIX syslog or Windows Event Log on the Puppet agent node and is also logged in reports.
+Logs an arbitrary message, at the `notice` log level. This appears in the POSIX syslog or Windows Event Log on the OpenVox agent node and is also logged in reports.
 
 ``` puppet
 notify { 'This message is getting logged on the agent node.': }

docs/_openvox_8x/functions_legacy.md

@@ -101,7 +101,7 @@ host converted to an integer, modulo 60. Neither
 guarantees uniqueness, but you can't really expect that with a range
 of no more than 60 anyway.
 
-But given that functions are run on the puppet master, how do you get at
+But given that functions are run on the OpenVox server, how do you get at
 the hostname or IP address of the agent node?
 The answer is that facts returned by facter can be used in our
 functions.

docs/_openvox_8x/functions_ruby_documenting.md

@@ -3,7 +3,7 @@ layout: default
 title: "Writing functions in Ruby: Documenting Ruby functions"
 ---
 
-[puppet strings]: https://github.com/puppetlabs/puppet-strings
+[puppet strings]: https://github.com/voxpupuli/openvox-strings
 [overview]: ./functions_ruby_overview.html
 [signatures]: ./functions_ruby_signatures.html
 

docs/_openvox_8x/indirection.md

@@ -3,7 +3,6 @@ layout: default
 built_from_commit: 8c9dd1ff315b738818307cc895942164aba30730
 title: Indirection Reference
 toc: columns
-canonical: "/puppet/latest/indirection.html"
 ---
 
 
@@ -18,7 +17,7 @@ canonical: "/puppet/latest/indirection.html"
 Puppet's indirector support pluggable backends (termini) for a variety of key-value stores (indirections).
 Each indirection type corresponds to a particular Ruby class (the "Indirected Class" below) and values are instances of that class.
 Each instance's key is available from its `name` method.
-The termini can be local (e.g., on-disk files) or remote (e.g., using a REST interface to talk to a puppet master).
+The termini can be local (e.g., on-disk files) or remote (e.g., using a REST interface to talk to an OpenVox server).
 
 An indirector has five methods, which are mapped into HTTP verbs for the REST interface:
 
@@ -328,12 +327,12 @@ A node is composed of its name, its facts, and its environment.
 ### `exec` terminus
 
 Call an external program to get node information.  See
-the [External Nodes](https://puppet.com/docs/puppet/latest/lang_write_functions_in_puppet.html) page for more information.
+the [External Nodes](./nodes_external.html) page for more information.
 
 ### `ldap` terminus
 
 Search in LDAP for node configuration information.  See
-the [LDAP Nodes](https://puppet.com/docs/puppet/latest/nodes_ldap.html) page for more information.  This will first
+the [LDAP Nodes](./nodes_ldap.html) page for more information.  This will first
 search for whatever the certificate name is, then (if that name
 contains a `.`) for the short name, then `default`.
 Requires ruby-ldap with MRI ruby or jruby-ldap with puppetserver/jruby
@@ -363,7 +362,7 @@ node instance before it is returned.
 
 ### `rest` terminus
 
-Get a node via REST. Puppet agent uses this to allow the puppet master
+Get a node via REST. OpenVox agent uses this to allow the OpenVox server
 to override its environment.
 
 ### `store_configs` terminus
@@ -423,6 +422,6 @@ Get status locally. Only used internally.
 
 ### `rest` terminus
 
-Get puppet master's status via REST. Useful because it tests the health
+Get OpenVox server's status via REST. Useful because it tests the health
 of both the web server and the indirector.
 

docs/_openvox_8x/lang_template.md

@@ -6,8 +6,8 @@ title: "Language: Using templates"
 [interpolate]: ./lang_data_string.html#interpolation
 [heredoc]: ./lang_data_string.html#heredocs
 [augeas]: ./resources_augeas.html
-[concat]: https://forge.puppetlabs.com/puppetlabs/concat
-[file_line]: https://forge.puppetlabs.com/puppetlabs/stdlib
+[concat]: https://forge.puppet.com/puppetlabs/concat
+[file_line]: https://forge.puppet.com/puppetlabs/stdlib
 [functions]: ./lang_functions.html
 [epp]: ./lang_template_epp.html
 [man epp]: ./man/epp.html
@@ -18,7 +18,7 @@ title: "Language: Using templates"
 [valid local variable names]: ./lang_reserved.html#variables
 [heredoc]: ./lang_data_string.html#heredocs
 [iteration functions]: ./lang_iteration.html
-[stdlib]: https://forge.puppetlabs.com/puppetlabs/stdlib
+[stdlib]: https://forge.puppet.com/puppetlabs/stdlib
 
 Templates are documents that combine code, data, and literal text to produce a final rendered output. The goal of a template is to manage a complicated piece of text with simple inputs.
 
@@ -48,7 +48,7 @@ Embedded Ruby (ERB)   | `template` | `inline_template`
 
 You can put template files in the `templates` directory of a [module][]. EPP files should have the `.epp` extension, and ERB files should have the `.erb` extension.
 
-To use a template file, evaluate it with the [`template`](https://docs.puppet.com/puppet/latest/function.html#template) (ERB) or [`epp`](https://docs.puppet.com/puppet/latest/function.html#epp) function:
+To use a template file, evaluate it with the [`template`](./function.html#template) (ERB) or [`epp`](./function.html#epp) function:
 
 ``` puppet
 # epp(<FILE REFERENCE>, [<PARAMETER HASH>])

docs/_openvox_8x/lang_template_epp.md

@@ -6,7 +6,7 @@ title: "Language: Embedded Puppet (EPP) template syntax"
 [erb]: ./lang_template_erb.html
 [epp]: /openvox/latest/function.html#epp
 [inline_epp]: /openvox/latest/function.html#inline_epp
-[ntp]: https://forge.puppetlabs.com/puppetlabs/ntp
+[ntp]: https://forge.puppet.com/puppetlabs/ntp
 [functions]: ./lang_functions.html
 [hash]: ./lang_data_hash.html
 [local scope]: ./lang_scope.html

docs/_openvox_8x/metaparameter.md

@@ -3,7 +3,6 @@ layout: default
 built_from_commit: 8c9dd1ff315b738818307cc895942164aba30730
 title: Metaparameter Reference
 toc: columns
-canonical: "/puppet/latest/metaparameter.html"
 ---
 
 
@@ -88,7 +87,7 @@ and the second run will log the edit made by Puppet.)
 ### before
 
 One or more resources that depend on this resource, expressed as
-[resource references](https://puppet.com/docs/puppet/latest/lang_data_resource_reference.html).
+[resource references](./lang_data_resource_reference.html).
 Multiple resources can be specified as an array of references. When this
 attribute is present:
 
@@ -97,7 +96,7 @@ attribute is present:
 This is one of the four relationship metaparameters, along with
 `require`, `notify`, and `subscribe`. For more context, including the
 alternate chaining arrow (`->` and `~>`) syntax, see
-[the language page on relationships](https://puppet.com/docs/puppet/latest/lang_relationships.html).
+[the language page on relationships](./lang_relationships.html).
 
 ### consume
 
@@ -173,14 +172,14 @@ When applying a resource in noop mode, Puppet will check whether it is in sync,
 like it does when running normally. However, if a resource attribute is not in
 the desired state (as declared in the catalog), Puppet will take no
 action, and will instead report the changes it _would_ have made. These
-simulated changes will appear in the report sent to the puppet master, or
+simulated changes will appear in the report sent to the OpenVox server, or
 be shown on the console if running puppet agent or puppet apply in the
 foreground. The simulated changes will not send refresh events to any
 subscribing or notified resources, although Puppet will log that a refresh
 event _would_ have been sent.
 
 **Important note:**
-[The `noop` setting](https://puppet.com/docs/puppet/latest/configuration.html#noop)
+[The `noop` setting](./configuration.html#noop)
 allows you to globally enable or disable noop mode, but it will _not_ override
 the `noop` metaparameter on individual resources. That is, the value of the
 global `noop` setting will _only_ affect resources that do not have an explicit
@@ -191,7 +190,7 @@ Valid values are `true`, `false`.
 ### notify
 
 One or more resources that depend on this resource, expressed as
-[resource references](https://puppet.com/docs/puppet/latest/lang_data_resource_reference.html).
+[resource references](./lang_data_resource_reference.html).
 Multiple resources can be specified as an array of references. When this
 attribute is present:
 
@@ -204,12 +203,12 @@ attribute is present:
 This is one of the four relationship metaparameters, along with
 `before`, `require`, and `subscribe`. For more context, including the
 alternate chaining arrow (`->` and `~>`) syntax, see
-[the language page on relationships](https://puppet.com/docs/puppet/latest/lang_relationships.html).
+[the language page on relationships](./lang_relationships.html).
 
 ### require
 
 One or more resources that this resource depends on, expressed as
-[resource references](https://puppet.com/docs/puppet/latest/lang_data_resource_reference.html).
+[resource references](./lang_data_resource_reference.html).
 Multiple resources can be specified as an array of references. When this
 attribute is present:
 
@@ -218,15 +217,15 @@ attribute is present:
 This is one of the four relationship metaparameters, along with
 `before`, `notify`, and `subscribe`. For more context, including the
 alternate chaining arrow (`->` and `~>`) syntax, see
-[the language page on relationships](https://puppet.com/docs/puppet/latest/lang_relationships.html).
+[the language page on relationships](./lang_relationships.html).
 
 ### schedule
 
 A schedule to govern when Puppet is allowed to manage this resource.
 The value of this metaparameter must be the `name` of a `schedule`
 resource. This means you must declare a schedule resource, then
 refer to it by name; see
-[the docs for the `schedule` type](https://puppet.com/docs/puppet/latest/type.html#schedule)
+[the docs for the `schedule` type](./type.html#schedule)
 for more info.
 
     schedule { 'everyday':
@@ -252,7 +251,7 @@ resources or on classes declared with `include`.
 By default, all classes are declared in the `main` stage. To assign a class
 to a different stage, you must:
 
-* Declare the new stage as a [`stage` resource](https://puppet.com/docs/puppet/latest/type.html#stage).
+* Declare the new stage as a [`stage` resource](./type.html#stage).
 * Declare an order relationship between the new stage and the `main` stage.
 * Use the resource-like syntax to declare the class, and set the `stage`
   metaparameter to the name of the desired stage.
@@ -270,7 +269,7 @@ For example:
 ### subscribe
 
 One or more resources that this resource depends on, expressed as
-[resource references](https://puppet.com/docs/puppet/latest/lang_data_resource_reference.html).
+[resource references](./lang_data_resource_reference.html).
 Multiple resources can be specified as an array of references. When this
 attribute is present:
 
@@ -283,7 +282,7 @@ attribute is present:
 This is one of the four relationship metaparameters, along with
 `before`, `require`, and `notify`. For more context, including the
 alternate chaining arrow (`->` and `~>`) syntax, see
-[the language page on relationships](https://puppet.com/docs/puppet/latest/lang_relationships.html).
+[the language page on relationships](./lang_relationships.html).
 
 ### tag
 

docs/_openvox_8x/nodes_external.md

@@ -13,15 +13,15 @@ Depending on the external data sources you use in your infrastructure, building
 
 ## What is an ENC?
 
-An external node classifier is an executable that Puppet Server or Puppet apply can call; it doesn't have to be written in Ruby. Its only argument is the name of the node to be classified, and it returns a YAML document describing the node.
+An external node classifier is an executable that OpenVox Server or puppet apply can call; it doesn't have to be written in Ruby. Its only argument is the name of the node to be classified, and it returns a YAML document describing the node.
 
 Inside the ENC, you can reference any data source you want, including [PuppetDB](/openvoxdb/latest). But from Puppet's perspective, it just puts in a node name and gets back a hash of information.
 
 ENCs can co-exist with standard node definitions in `site.pp`, and the classes declared in each source are merged together.
 
 ### How merging works
 
-Every node always gets a **node object** (which might be empty or might contain classes, parameters, and an environment) from the configured `node_terminus`. (This setting takes effect where the catalog is compiled; on Puppet Server when using an agent/master arrangement, and on the node itself when using Puppet apply. The default node terminus is `plain`, which returns an empty node object; the `exec` terminus calls an ENC script to determine what should go in the node object.) Every node **might** also get a [node definition][] from the [main manifest][].
+Every node always gets a **node object** (which might be empty or might contain classes, parameters, and an environment) from the configured `node_terminus`. (This setting takes effect where the catalog is compiled; on OpenVox Server when using an agent/server arrangement, and on the node itself when using puppet apply. The default node terminus is `plain`, which returns an empty node object; the `exec` terminus calls an ENC script to determine what should go in the node object.) Every node **might** also get a [node definition][] from the [main manifest][].
 
 When compiling a node's catalog, Puppet includes **all** of the following:
 
@@ -45,7 +45,7 @@ When compiling a node's catalog, Puppet includes **all** of the following:
 
 ## Connecting an ENC
 
-To tell Puppet Server to use an ENC, you need to set two [settings](./config_about_settings.html) in the Puppet master's `puppet.conf` file: `node_terminus` has to be set to "exec", and `external_nodes` must have the path to the executable.
+To tell OpenVox Server to use an ENC, you need to set two [settings](./config_about_settings.html) in the OpenVox server's `puppet.conf` file: `node_terminus` has to be set to "exec", and `external_nodes` must have the path to the executable.
 
     [master]
       node_terminus = exec

docs/_openvox_8x/nodes_ldap.md

@@ -125,7 +125,7 @@ The `testserver` node's classes would be `baseclass`, `testing`, and `solaris`.
 
 ## Modifying your LDAP schema
 
-You first have to provide the Puppet schema to your LDAP server. You can find the Puppet schema [in Git](http://github.com/puppetlabs/puppet/blob/master/ext/ldap/puppet.schema). Place this schema into your schema directory, on Debian for example this would be /etc/ldap/schema. I recommend keeping the puppet.schema name.
+You first have to provide the Puppet schema to your LDAP server. You can find the Puppet schema in the OpenVox source repository under `ext/ldap/puppet.schema`. Place this schema into your schema directory, on Debian for example this would be /etc/ldap/schema. I recommend keeping the puppet.schema name.
 
 With the schema file in place, modify your slapd.conf to load this schema by adding it to the list of schema files loaded: