Thanks, it seems trickier than I expected. There's a bunch of modules for network configuration but I'd rather avoid to duplicate the network settings in Foreman and in Hiera. It would heavily affect the scalability of my setup :(
There's some interesting work being done on a module able to fetch infrastructure data from the Foreman-generated YAML: https://groups.google.com/d/topic/foreman-users/G6XXgYNbY44/discussion I hope this can progress. On Wednesday, July 1, 2015 at 11:23:52 AM UTC+2, Angel L. Mateo wrote: > > El 01/07/15 a las 11:20, Nicola V escribió: > > On Wednesday, July 1, 2015 at 8:20:00 AM UTC+2, Angel L. Mateo wrote: > > > > We are using what you called option 3. The main reason to > > use option 3 > > instead of 1 was that this way we can have our "truth" under version > > control. > > > > > > Thanks Angel, good to know it's a valid option. > > On a side note: how do you manage changes in the networking interfaces > > AFTER the machine has been installed? Say you want to change an ip. > > Would it be managed by some puppet module? > > > No. We are not managing ip interfaces from puppet. It's on my todo > list, but... > > -- > Angel L. Mateo Martínez > Sección de Telemática > Área de Tecnologías de la Información > y las Comunicaciones Aplicadas (ATICA) > http://www.um.es/atica > Tfo: 868887590 > Fax: 868888337 > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/61929896-6329-47fc-82a0-a61031c8e983%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
