You did, thanks Johannes. I've completed all of the provisioning setup steps, next issue is actually deploying a VM. I've had it begin the build process in VMware but then rollback with an error relating to DNS records. I don't want any DNS or DHCP management being handled by Foreman (we don't use DHCP and already have servers managing DNS). Is there a way to stop it attempting creating DNS records?
On Thursday, 30 March 2017 09:23:28 UTC+1, Johannes Kastl wrote: > > Nathan Slinn schrieb: > > Sorry, when I refer to network config in point 2 I'm referring to the > > provisioning setup steps still, I think network config is step 2? > > >>> 2.) Following on from Q1, in the network config should this be the > >>> domain/vlan I want to provision machines into or the domain/vlan of > >>> the Foreman server itself? > > The interface / subnet you define in the provisioning setup is the one, > that foreman should "listen" on. In your case we wanted to have it > listen to DNS, DHCP and PXE only on that VLAN, that the second NIC on > the foreman server was on, as well as the NICs in the VMs. > > Did I get you right? > > -- > Johannes Kastl > Linux Consultant & Trainer > Tel.: +49 (0) 151 2372 5802 > Mail: [email protected] <javascript:> > > B1 Systems GmbH > Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de > GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
