Foreman and openstack and private ips

Hi,

We have forman, a dns smart-proxy and an openstack installation with
private IPs.

In this configuration it looks like we can't create VMs from foreman
because it will always try to create a dns entry for the private IP,
which fails.

Is there any possibility to not do dns registry for this compute
resource? Or at least to use the public IP in case it exists?

Thank you,
Cristian Falcas

Ok, we created a dummy domain that is not attached to any dns
smart-proxy and use that one.

Sorry for the noise.

··· On Thu, Feb 5, 2015 at 9:24 AM, Cristian Falcas wrote: > Hi, > > We have forman, a dns smart-proxy and an openstack installation with > private IPs. > > In this configuration it looks like we can't create VMs from foreman > because it will always try to create a dns entry for the private IP, > which fails. > > Is there any possibility to not do dns registry for this compute > resource? Or at least to use the public IP in case it exists? > > Thank you, > Cristian Falcas

We are having the same problem here. All instances provisioned with foreman
get the Private IP address by default, and its not possible to specify the
public.

I we have to create a VPN between our Foreman (AWS) and the Opentstack
private network, but wondering if anyone have found any other solution.

··· On Thursday, February 5, 2015 at 8:29:35 AM UTC+1, Cristian Falcas wrote: > > Ok, we created a dummy domain that is not attached to any dns > smart-proxy and use that one. > > Sorry for the noise. > > On Thu, Feb 5, 2015 at 9:24 AM, Cristian Falcas > wrote: > > Hi, > > > > We have forman, a dns smart-proxy and an openstack installation with > > private IPs. > > > > In this configuration it looks like we can't create VMs from foreman > > because it will always try to create a dns entry for the private IP, > > which fails. > > > > Is there any possibility to not do dns registry for this compute > > resource? Or at least to use the public IP in case it exists? > > > > Thank you, > > Cristian Falcas >