Skip to content

Rename subdirectory "unit" to "action" #37

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 8, 2020
Merged

Rename subdirectory "unit" to "action" #37

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion documentation/basic_usage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ The current versions of those plans can be found at:
* [provision.pp](../plans/provision.pp)
* [upgrade.pp](../plans/upgrade.pp)

Provisioning can be broken down into two actions: [install](../plans/unit/install.pp), and [configure](../plans/unit/configure.pp). Installation currently requires ssh access to the un-provisioned nodes, but configure can be performed using the Orchestrator transport if installation has already been completed.
Provisioning can be broken down into two actions: [install](../plans/action/install.pp), and [configure](../plans/action/configure.pp). Installation currently requires ssh access to the un-provisioned nodes, but configure can be performed using the Orchestrator transport if installation has already been completed.

Besides getting Puppet Enterprise installed, the key configuration supporting Large and Extra Large architectures is laid out in four classification groups. Links are provided below to a Markdown document that describes the groups, and also to the Puppet manifest that actually configures them:

Expand Down
2 changes: 1 addition & 1 deletion plans/unit/configure.pp → plans/action/configure.pp
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# @summary Configure first-time classification and HA setup
#
plan peadm::unit::configure (
plan peadm::action::configure (
# Large
Peadm::SingleTargetSpec $master_host,
Optional[TargetSpec] $compiler_hosts = undef,
Expand Down
2 changes: 1 addition & 1 deletion plans/unit/install.pp → plans/action/install.pp
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@
# Config data to plane into pe.conf when generated on all hosts, this can be
# used for tuning data etc.
#
plan peadm::unit::install (
plan peadm::action::install (
# Standard
Peadm::SingleTargetSpec $master_host,
Optional[Peadm::SingleTargetSpec] $master_replica_host = undef,
Expand Down
4 changes: 2 additions & 2 deletions plans/provision.pp
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@
Optional[String] $stagingdir = undef,
) {

$install_result = run_plan('peadm::unit::install',
$install_result = run_plan('peadm::action::install',
# Standard
master_host => $master_host,
master_replica_host => $master_replica_host,
Expand All @@ -58,7 +58,7 @@
stagingdir => $stagingdir,
)

$configure_result = run_plan('peadm::unit::configure',
$configure_result = run_plan('peadm::action::configure',
# Standard
master_host => $master_host,
master_replica_host => $master_replica_host,
Expand Down