I'm in the process of migrating our bare metal provisioning infrastructure
over to Foreman. We have a large number of subnets we need to create in
Foreman, and I am planning to use Hammer. I can associate the DHCP, DNS,
and TFTP proxies with a subnet as follows:
However, there isn't an option for the discovery proxy. I added the
rubygem-hammer_cli_foreman_discovery package, and that gives hammer a new
subcommand, but no option to add the discovery proxy to the subnet.
Is there a way to do this in Foreman 1.7.1 without going directly into the
database?
Hey Kyle,
Did you ever figure this out out ? I'm running into the same issue myself
···
On Tuesday, November 17, 2015 at 2:31:20 PM UTC-5, Kyle Flavin wrote:
>
> I'm in the process of migrating our bare metal provisioning infrastructure
> over to Foreman. We have a large number of subnets we need to create in
> Foreman, and I am planning to use Hammer. I can associate the DHCP, DNS,
> and TFTP proxies with a subnet as follows:
>
> hammer -u user -p password subnet create --name "subnet name" ...*
> -dhcp-id 9 --dns-id 9 --tftp-id 9*
>
>
> However, there isn't an option for the discovery proxy. I added the
> rubygem-hammer_cli_foreman_discovery package, and that gives hammer a new
> subcommand, but no option to add the discovery proxy to the subnet.
>
> Is there a way to do this in Foreman 1.7.1 without going directly into the
> database?
>
The change in API will allow setting any proxy via ID options.
LZ
Lukas Zapletal píše v Út 11. 10. 2016 v 09:50 +0200:
···
> > Did you ever figure this out out ? I'm running into the same issue
> > myself
>
> Please file a bug. We don't have that.
--
Later,
Lukas "lzap" Zapletal
