[chef] Re: Re: Managing network interfaces

[Jesse Nelson < >]

you can manage the files directly or use the resources.   we use the resource and data bags to manage static assignments for sub-interface and vlan interfaces on some (not all) hosts..  

this model has allowed me to name interfaces in json data in a data bag and reuse or search against those names in other recipes. this has worked out well for me. 

i am happy to share the very simple recipe that achieves this, but its not up anywhere atm. 

On Jul 13, 2010, at 4:23 PM, Ryan C. Creasey wrote:

I've played around with managing auxiliary interfaces on my nodes (eth1, loopback aliases, etc) for some of our DSR nodes and took the easy way out and had the recipe manage the templates to the "/etc/sysconfig/network-scripts/ifcfg-#{interface[:device]}" (yes, we're redhat based).

I'd also be interested to hear other use cases for interface management with chef.

Ryan C. Creasey

PRINCIPAL SYSTEMS ENGINEER

IGN Entertainment

T: 714.460.6789  |  C: 949.378.9023 | AIM: ryancreasey

On Jul 13, 2010, at 4:19 PM, Jacobo García wrote:

Hi,

I have to manage some network interfaces, routes and and ipip tunnels.
I know about chef's route and ifconfig resource. But I'd like to know
experiences of people playing with these sensitive stuff, specially
about configuring network interfaces, is the resource reliable enough?
does it work with virtual interfaces?

Thanks :)

Jacobo García López de Araujo
blog: http://robotplaysguitar.com
http://workingwithrails.com/person/13395-jacobo-garc-a