This message was deleted.
# bolt
s
This message was deleted.
t
What do you want to manage? Usually it means: Installing bolt, add a ssh key, configure your PuppetDB location to fetch node lists via facts.
The module which you found only makes sense in a Puppet Enterprise environment. In PE bolt is integrated and uses the PE PXP/PCP Transport instead of SSH.
Usually Bolt in PE is automatically configured.
w
We are using PE, so if it is better practice to use it via PE I should maybe look into that. To explain a bit more about our situation, we have 1 primary and 3 compilers, which each run in a separate oci tenants. We create cron entries for shutting down and starting groups of nodes in OCI, where we connect to via seperate accounts. So what I did now was install bolt by hand and edit the bolt-defaults and bolt-project. I can add these files to be created, but was just wondering if someone found an easier way. Maybe there just isn't and that might be why no one has created such a module.
b
why do you want to use bolt at all when you're on PE?
w
lack of proper knowledge to do it better?
b
PE has the Orchestrator build in to run tasks and plans, via the pxp agent
w
I know that I can run plans with PE, but not in the complicated manner we are using our cron jobs at the moment. Most nodes are shut down after office hours and started the next day. So weekdays only and as far as I can tell PE only has limited options (hourly/daily/(1,2,4)weekly).
t
The PE Bolt integration is done by the PE Orchestrator. You dont need to install bolt, you should install pe-utils package which gives you some new puppet commands:
puppet task
,
puppet plan
,
puppet access
puppet access
will generate a token, which can be used by
puppet task
and
puppet plan
. You benefit from everything being logged into PE Tasks and Plans Web UI and you have the freedom of using cron
w
t
w
Ah thanks. I will look into that. We also use bolt sometimes to look for certain files to be present on some systems, like bolt command run 'hostname' --query "inventory[certname] {facts.os.family = 'RedHat'}" Is that also possible with these tools?
b
yes
w
cool
b
the PE orchestrator is bolt, running as server with an API, in the background
w
Maybe it's relatively new and the previous developer of the code was still using an old way. We upgraded from 2019.4 to 2021.4 1.5 years ago (and are in the process of upgrading to 2021.7), so there might be some legacy