Hi, Sorry, it looks like I missed this e-mail.
On Mon, 2011-05-09 at 14:45 -0700, Douglas Garstang wrote: > I was looking at the new feature of puppet to manage switches, and it > says: > > > "A current limitation is that it isn’t possible to have 2 switches > with the same interface name" > > > Does this mean that if one switch has an interface called FastEthernet > 0/1, that puppet can't manage a second switch with an interface called > FastEthernet 0/1? If so, that probably means you can manage a sum > total of... 1 switch, given that interface names are pretty common... > I hope I'm reading this wrong... Actually, there are two ways to apply network devices configurations: 1) use "puppet apply" with a standalone manifest. In this case you are limited to configure one switch at a time because of the two resources with same name conflict described above. 2) use the shiny new "puppet device" application which is the "puppet agent" of devices. This application aims to configure remote network device by asking the puppet master for a given device catalog, and then applying it on the said device. As seen from the master a network device becomes a full blown puppet node with its certificate (yikes) but also all the good things like reports, ENC, etc... Puppet device just reads the /etc/puppet/device.conf file which contains the list of network device to manage (with how to connect to them). Note: all this is still experimental, use at your own risk, blah blah. HTH, -- Brice Figureau Follow the latest Puppet Community evolutions on www.planetpuppet.org! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
