Skip to content

convert.md

Latest commit

 

History

History
32 lines (22 loc) · 1.59 KB

convert.md

File metadata and controls

32 lines (22 loc) · 1.59 KB

Convert infrastructure for use with the peadm module

The peadm::convert plan can be used to adopt manually deployed infrastructure for use with peadm, or to adopt infrastructure deployed with an older version of peadm.

Convert an Existing Deployment

Prepare to run the plan against all servers in the PE infrastructure, using a params.json file such as this one:

{
  "primary_host": "pe-xl-core-0.lab1.puppet.vm",
  "primary_replica_host": "pe-xl-core-1.lab1.puppet.vm",
  "compiler_hosts": [
    "pe-xl-compiler-0.lab1.puppet.vm",
    "pe-xl-compiler-1.lab1.puppet.vm"
  ],

  "compiler_pool_address": "puppet.lab1.puppet.vm",
}

See the provision documentation for a list of supported architectures. Note that for convert, all infrastructure being converted must already be functional; you cannot use convert to add new systems to the infrastructure, nor can you use it to change your architecture.

bolt plan run peadm::convert --params @params.json

Retry or resume plan

This plan is broken down into steps. Normally, the plan runs through all the steps from start to finish. The name of each step is displayed during the plan run, as the step begins.

The begin_at_step parameter can be used to facilitate re-running this plan after a failed attempt, skipping past any steps that already completed successfully on the first try and picking up again at the step specified. The step name to resume at can be read from the previous run logs. A full list of available values for this parameter can be viewed by running bolt plan show peadm::convert.