https://choria-io.github.io/provisioner/Overview In a typical Choria environment Puppet is used to provision a uniform Choria infrastructure integrated into the Puppet CA. This does not really work in large enterprises or dynamic environments.. Choria supports a provisioning mode where the process of enrolling a node can be managed on a per-environment basis, this is where we manage the vast differences in environments, platforms, etc. Once Choria is installed we have a unified overlay interface:Hugoen-ushttps://choria-io.github.io/provisioner/installtion/Mon, 01 Jan 0001 00:00:00 +0000https://choria-io.github.io/provisioner/installtion/We distribute an RPM or Docker container for the Provisioner package. Debian is not supported at present. YUM Repository For RPMs we publish releases but also nightly builds to our repositories. Users of our Puppet modules will already have these repositories available. Release [choria_release] name=Choria Orchestrator Releases mirrorlist=http://mirrorlists.choria.io/yum/release/el/$releasever/$basearch.txt enabled=True gpgcheck=True repo_gpgcheck=True gpgkey=https://choria.io/RELEASE-GPG-KEY metadata_expire=300 sslcacert=/etc/pki/tls/certs/ca-bundle.crt sslverify=True Nightly Nightly releases are named and versioned choria-provisioner-0.99.0.20221109-1.el7.x86_64.rpm where the last part of the version is the date.https://choria-io.github.io/provisioner/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://choria-io.github.io/provisioner/configuration/Configuring the Provisioner requires exact knowledge of your deployment needs, we suggest you start with first configuring servers by hand while exploring your needs, once the specific configuration file contents and security needs are defined those can be configured into the Provisioner system. Deploying a Provisioner should not be the first thing you do. General Requirements Choria Broker You must be running the Choria Broker and it will need a few extra configuration items.https://choria-io.github.io/provisioner/managing/Mon, 01 Jan 0001 00:00:00 +0000https://choria-io.github.io/provisioner/managing/Choria Server that is enabled for Provisioning expose a number of endpoints that can be used to interact with it in ways that is not otherwise possible. Warning These features are almost all extremely dangerous and should be used with great caution. These abilities are not possible without enabling Provisioning in the server, so they are off by default. You should ensure your site security policies have adequate control over these actions.https://choria-io.github.io/provisioner/monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://choria-io.github.io/provisioner/monitoring/Watching the Provisioning Process Choria Servers publish lifecycle events, these can be viewed using choria tool event --component provision_mode_server. Servers will publish startup, shutdown and provisioned events that will be shown in the rolling display. These lifecycle events are published in JSON mode on the network and could be stored in a Stream for analysis. $ choria tool event --component provision_mode_server Waiting for events from topic choria.lifecycle.event.> on nats://broker.choria.local:4222 14:35:46 [startup] n1.choria.local: provision_mode_server version 0.26.15 14:36:30 [provisioned] n1.choria.local: provision_mode_server 14:36:31 [shutdown] n1.choria.local: provision_mode_server Viewing servers waiting for provisioning One can view the active connections in the Choria Broker, these are nodes waiting to be provisioned. Typically one would also see connections for the Provisioner in addition to these.https://choria-io.github.io/provisioner/design/Mon, 01 Jan 0001 00:00:00 +0000https://choria-io.github.io/provisioner/design/How Choria Provisioner is built: package layout, the provisioning sequence, and credential handling.