-
Notifications
You must be signed in to change notification settings - Fork 54
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.
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
Language and terminology updates #153
Conversation
…luster where appropriate
Manual test 1
|
AWS large build
|
AWS XL build
|
google standard build 2018.1 and upgrade to 2018.5
Upgrade performed locally
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! I am going to suggest one change.
For peadm::oid('peadm_role')
, we should use puppet/server
, instead of puppet/primary
. This is to avoid potential confusion about what is primary, and what is replica. Those terms expand out to, respectively, "primary Puppet server" and "replica Puppet server" so that label should be congruent.
Besides that, I think we're good to go!
I'm also going to create a 2.x tracking branch before merging this PR to main, since this change marks where we'll have to cut a new major version.
Curious, @reidmv, why peadm doesn't deploy https://puppet.com/docs/puppet/7/config_file_oid_map.html? |
@vchepkov good quesiton. I think the summary is, the feature is difficult to use and rely on. The decision not to use a
In essence, a friendly short-name cannot be used in addition to an OID, it can only be used instead of an OID. A correctly configured For us to use We don't do any catalog-based management of files today, and so can't automatically fix or correct changes to Overall, it seems questionable if the benefit is worth the complexity cost. It's certainly possible to revisit the idea if someone has an idea for a cleaner way around these problems. |
Agree with the changesmakes a lot more sense, updated and tested. See output below. We do haver a ticket for that new release so can pull that in if we create the branch SOLARCH-397
|
…ith primary and replica
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💯 👍
The terms, variables and values that have changed are as follows
deployment to cluster
master_host to primary_host
master_replica_host to primary_replica_host
master_target to primary_target
master_replica_target to primary_replica_target
master_certname to primary_certname
master to primary
HA to DR
high-availability to disaster-recovery
TRUSTED FACT
peadm::oid('peadm_role') => 'puppet/master', to peadm::oid('peadm_role') => 'puppet/primary',
NODE GROUP
PE Master B to PE Primary B
PE Master A to PE Primary A
None of the following puppet settings can be updated as all appear to still be in with no alternative https://github.com/puppetlabs/puppet-enterprise-modules/tree/main/modules/puppet_enterprise/manifests/profile and https://github.com/puppetlabs/puppet-enterprise-modules/tree/main/modules/puppet_enterprise/manifests
puppet_enterprise::profile::master
puppet_enterprise::profile::master::puppetdb
puppet_enterprise::profile::primary_master_replica
puppet_enterprise::profile::master::java_args
puppet_enterprise::puppet_master_host