So the way it exists today, is cobbler creates the underlying fence command to talk to the ucsm, via http only.
I initially thought we would have to add a new variable in site.pp to identify if the ucsm is setup to use http or https.
But in all the ucsm deployments I have seen https is always enabled, http may or may not be enabled. So I just changed the default fence command that cobbler creates to talk to the ucsm, via https.
The additional "-z" in the fence command is for sending the request via https.
So the way it exists today, is cobbler creates the underlying fence command to talk to the ucsm, via http only.
I initially thought we would have to add a new variable in site.pp to identify if the ucsm is setup to use http or https.
But in all the ucsm deployments I have seen https is always enabled, http may or may not be enabled. So I just changed the default fence command that cobbler creates to talk to the ucsm, via https.
The additional "-z" in the fence command is for sending the request via https.
https:/ /github. com/CiscoSystem s/puppet- cobbler/ pull/22