Multiple smart proxies - different sites and subnets

Support
1

Hi,

I'm using foreman 1.11 and discovery image 3.1.1 - and need to provision
locally i.e. multiple smart proxies - different sites and subnets, single
domain.

I've configured the _x-foreman._tcp SRV record in DNS and removed the *proxy.url=
in *PXELinux global default template, and discovery works correctly in
isolation, but when dealing with multiple sites routes to an incorrect
smart proxy.
How can you force discovery onto the local smart proxy?

Regards,
Graham

2

Hello,

I don't undestand exactly, but if you have separate domains for the
separate subnets, you simply put URL to your proxy for each domain
separately (use https://proxy.network1.com:8443 notation in SRV records)
and you keep proxy.type=proxy in the kernel command line so discovery node
will use proxy API instead foreman API.

Alternatively, you need to modify the default PXE template on each
individual proxy because Foreman currently can't do this (it only supports
one generic template for all proxies).

LZ

··· On Thu, Dec 1, 2016 at 2:43 PM, Graham wrote:

Hi,

I’m using foreman 1.11 and discovery image 3.1.1 - and need to provision
locally i.e. multiple smart proxies - different sites and subnets, single
domain.

I’ve configured the _x-foreman._tcp SRV record in DNS and removed the *proxy.url=
in *PXELinux global default template, and discovery works correctly in
isolation, but when dealing with multiple sites routes to an incorrect
smart proxy.
How can you force discovery onto the local smart proxy?

Regards,
Graham

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Later,
Lukas @lzap Zapletal

3

Thanks for you response Lukas,

It's a single domain for all subnets/sites otherwise could have done your
first suggestion.

Is it the /var/lib/tftpboot/pxelinux.cfg/default file you mean to modify on
each proxy? Will this get updated/overwritten when I hit "Build PXE Default
button" ?

Regards,
Graham

··· On Monday, December 5, 2016 at 2:10:24 PM UTC, Lukas Zapletal wrote:

Hello,

I don’t undestand exactly, but if you have separate domains for the
separate subnets, you simply put URL to your proxy for each domain
separately (use https://proxy.network1.com:8443 notation in SRV records)
and you keep proxy.type=proxy in the kernel command line so discovery node
will use proxy API instead foreman API.

Alternatively, you need to modify the default PXE template on each
individual proxy because Foreman currently can’t do this (it only supports
one generic template for all proxies).

LZ

On Thu, Dec 1, 2016 at 2:43 PM, Graham <graham...@gmail.com <javascript:>> > wrote:

Hi,

I’m using foreman 1.11 and discovery image 3.1.1 - and need to provision
locally i.e. multiple smart proxies - different sites and subnets, single
domain.

I’ve configured the _x-foreman._tcp SRV record in DNS and removed the *proxy.url=
in *PXELinux global default template, and discovery works correctly in
isolation, but when dealing with multiple sites routes to an incorrect
smart proxy.
How can you force discovery onto the local smart proxy?

Regards,
Graham

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-user...@googlegroups.com <javascript:>.
To post to this group, send email to forema...@googlegroups.com
<javascript:>.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Later,
Lukas @lzap Zapletal

4

Yes, that's the one. Unfortunately it will be rewritten the if you hit the
button. You may want to prevent that using permissions on the filesystem
and put a dummy message into the template content to modify the file
manually (at least until we implement better behavior).

LZ

··· On Mon, Dec 5, 2016 at 5:46 PM, Graham wrote:

Thanks for you response Lukas,

It’s a single domain for all subnets/sites otherwise could have done your
first suggestion.

Is it the /var/lib/tftpboot/pxelinux.cfg/default file you mean to modify
on each proxy? Will this get updated/overwritten when I hit “Build PXE
Default button” ?

Regards,
Graham

On Monday, December 5, 2016 at 2:10:24 PM UTC, Lukas Zapletal wrote:

Hello,

I don’t undestand exactly, but if you have separate domains for the
separate subnets, you simply put URL to your proxy for each domain
separately (use https://proxy.network1.com:8443 notation in SRV records)
and you keep proxy.type=proxy in the kernel command line so discovery node
will use proxy API instead foreman API.

Alternatively, you need to modify the default PXE template on each
individual proxy because Foreman currently can’t do this (it only supports
one generic template for all proxies).

LZ

On Thu, Dec 1, 2016 at 2:43 PM, Graham graham...@gmail.com wrote:

Hi,

I’m using foreman 1.11 and discovery image 3.1.1 - and need to provision
locally i.e. multiple smart proxies - different sites and subnets, single
domain.

I’ve configured the _x-foreman._tcp SRV record in DNS and removed the *proxy.url=
in *PXELinux global default template, and discovery works correctly in
isolation, but when dealing with multiple sites routes to an incorrect
smart proxy.
How can you force discovery onto the local smart proxy?

Regards,
Graham

–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-user...@googlegroups.com.
To post to this group, send email to forema...@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Later,
Lukas @lzap Zapletal

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Later,
Lukas @lzap Zapletal

5

Lukas,

If I set the file read only I get the following error when using Build PXE
Default button in UI:
*Error: *There was an error creating the PXE Default file:
server.example.com: ERF12-9243 [ProxyAPI::ProxyException]: Unable to create
default TFTP boot menu ([RestClient::BadRequest]: 400 Bad Request) for
Capsule https://server.example.com:9090/tftp

Any suggestions on how to achieve?

Many thanks,
Graham

··· On Tuesday, December 6, 2016 at 10:26:14 AM UTC, Lukas Zapletal wrote:

Yes, that’s the one. Unfortunately it will be rewritten the if you hit the
button. You may want to prevent that using permissions on the filesystem
and put a dummy message into the template content to modify the file
manually (at least until we implement better behavior).

LZ

On Mon, Dec 5, 2016 at 5:46 PM, Graham <graham...@gmail.com <javascript:>> > wrote:

Thanks for you response Lukas,

It’s a single domain for all subnets/sites otherwise could have done your
first suggestion.

Is it the /var/lib/tftpboot/pxelinux.cfg/default file you mean to modify
on each proxy? Will this get updated/overwritten when I hit “Build PXE
Default button” ?

Regards,
Graham

On Monday, December 5, 2016 at 2:10:24 PM UTC, Lukas Zapletal wrote:

Hello,

I don’t undestand exactly, but if you have separate domains for the
separate subnets, you simply put URL to your proxy for each domain
separately (use https://proxy.network1.com:8443 notation in SRV
records) and you keep proxy.type=proxy in the kernel command line so
discovery node will use proxy API instead foreman API.

Alternatively, you need to modify the default PXE template on each
individual proxy because Foreman currently can’t do this (it only supports
one generic template for all proxies).

LZ

On Thu, Dec 1, 2016 at 2:43 PM, Graham graham...@gmail.com wrote:

Hi,

I’m using foreman 1.11 and discovery image 3.1.1 - and need to
provision locally i.e. multiple smart proxies - different sites and
subnets, single domain.

I’ve configured the _x-foreman._tcp SRV record in DNS and removed the *proxy.url=
in *PXELinux global default template, and discovery works correctly in
isolation, but when dealing with multiple sites routes to an incorrect
smart proxy.
How can you force discovery onto the local smart proxy?

Regards,
Graham

–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-user...@googlegroups.com.
To post to this group, send email to forema...@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Later,
Lukas @lzap Zapletal

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-user...@googlegroups.com <javascript:>.
To post to this group, send email to forema...@googlegroups.com
<javascript:>.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Later,
Lukas @lzap Zapletal

6

That's expected behavior, don't use the button anymore, this is to prevent
overwriting the file.

LZ

··· On Wed, Dec 7, 2016 at 12:58 PM, Graham wrote:

Lukas,

If I set the file read only I get the following error when using Build PXE
Default button in UI:
*Error: *There was an error creating the PXE Default file:
server.example.com: ERF12-9243 [ProxyAPI::ProxyException]: Unable to
create default TFTP boot menu ([RestClient::BadRequest]: 400 Bad Request)
for Capsule https://server.example.com:9090/tftp

Any suggestions on how to achieve?

Many thanks,
Graham

On Tuesday, December 6, 2016 at 10:26:14 AM UTC, Lukas Zapletal wrote:

Yes, that’s the one. Unfortunately it will be rewritten the if you hit
the button. You may want to prevent that using permissions on the
filesystem and put a dummy message into the template content to modify the
file manually (at least until we implement better behavior).

LZ

On Mon, Dec 5, 2016 at 5:46 PM, Graham graham...@gmail.com wrote:

Thanks for you response Lukas,

It’s a single domain for all subnets/sites otherwise could have done
your first suggestion.

Is it the /var/lib/tftpboot/pxelinux.cfg/default file you mean to
modify on each proxy? Will this get updated/overwritten when I hit “Build
PXE Default button” ?

Regards,
Graham

On Monday, December 5, 2016 at 2:10:24 PM UTC, Lukas Zapletal wrote:

Hello,

I don’t undestand exactly, but if you have separate domains for the
separate subnets, you simply put URL to your proxy for each domain
separately (use https://proxy.network1.com:8443 notation in SRV
records) and you keep proxy.type=proxy in the kernel command line so
discovery node will use proxy API instead foreman API.

Alternatively, you need to modify the default PXE template on each
individual proxy because Foreman currently can’t do this (it only supports
one generic template for all proxies).

LZ

On Thu, Dec 1, 2016 at 2:43 PM, Graham graham...@gmail.com wrote:

Hi,

I’m using foreman 1.11 and discovery image 3.1.1 - and need to
provision locally i.e. multiple smart proxies - different sites and
subnets, single domain.

I’ve configured the _x-foreman._tcp SRV record in DNS and removed the *proxy.url=
in *PXELinux global default template, and discovery works correctly
in isolation, but when dealing with multiple sites routes to an incorrect
smart proxy.
How can you force discovery onto the local smart proxy?

Regards,
Graham

–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-user...@googlegroups.com.
To post to this group, send email to forema...@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Later,
Lukas @lzap Zapletal

–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-user...@googlegroups.com.
To post to this group, send email to forema...@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Later,
Lukas @lzap Zapletal

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Later,
Lukas @lzap Zapletal