Plugins » Boot disk

Sounds meaningless to me.

generating a bootdisk such that all the communication goes through a particular Capsule and is proxied to the main server where needed.

This is automatically covered by the templates feature in the smart proxy. I set up an isolated VM with no access to the Foreman server, and a local Template and TFTP proxy. As expected, since the Bootdisk templates call foreman_url(), the proxy's address is substituted for the foreman url.

I correctly saw requests for the iPXE template proxied to Foreman via the Proxy for the Host Image:

Proxy:
192.168.100.100 - - [05/Dec/2014:17:22:09 GMT] "GET /unattended/iPXE?token=48309204-e537-4346-ba82-09cb44871c08&mac=52%3A54%3A00%3Aea%3A04%3A67 HTTP/1.1" 200 737
Foreman:
Started GET "/unattended/iPXE?token=48309204-e537-4346-ba82-09cb44871c08&url=http%3A%2F%2F192.168.100.1%3A8000" for 172.20.10.149 at 2014-12-05 17:22:09 +0000

Likewise, when testing the Host Full Image, we see a proxied request for the provision template:

Proxy
192.168.100.193 - - [05/Dec/2014:17:23:30 GMT] "GET /unattended/provision?token=48309204-e537-4346-ba82-09cb44871c08 HTTP/1.1" 200 3558
Foreman
Started GET "/unattended/provision?token=48309204-e537-4346-ba82-09cb44871c08&url=http%3A%2F%2F192.168.100.1%3A8000" for 172.20.10.149 at 2014-12-05 17:23:30 +0000

I didn't test the Generic image due to running out of time, but I see no reason for it to behave differently - they all rely on foreman_url, and should be correctly substituted.

Tested with a host-specific bootdisk and a generic bootdisk.

On the host-specific bootdisk i do see it referencing the smart proxy:

chain http://smart-proxy.example.com:8000/unattended/iPXE?token=88cf7a69-1456-4b48-b7d0-0ac970b9d8e6&mac=26:11:b6:1f:ee:c5

(which is the correct smart proxy name). On the generic bootdisk however i just see:

:net0
isset ${net0/mac} || goto no_nic
echo net0 is a ${net0/chip} with MAC ${net0/mac}
dhcp net0 || goto net1
chain http://abed.example.com/unattended/iPXE?&mac=${net0/mac} || goto net1
exit 0

which is referencing the main foreman server. In fact the url to fetch the generic bootdisK: /bootdisk/disks/generic does not contain any host-specific information so I don't think there is anyway for it to know what tftp or template proxy to use when generating the generic bootdisk.

Reopening

Applied in changeset foreman_bootdisk|367b1e6d37475adfe3bad52fe58c05b53505514e.