network_configuration - chef-boneyard/chef-summit-2014 GitHub Wiki

Configure Network with Chef

2014/10/15, Green House

  • Convener / Facilitator

Nicolas Blanc (BlaBlaCar)

  • Note taker

Nicolas Blanc (BlaBlaCar)

Participants

  • Nicolas Blanc (BlaBlaCar)
  • Remi Paulmier (BlaBlaCar)
  • Matt Ray (Chef)
  • ?? (Chef)
  • ??

Summary of Discussions

The question was: how to manage the network equipment with chef. And by the way how to synchronize the node and the network equipment when there's a need of (typical example is the LACP mode for more than 1 interface).

Matt Ray from Chef, explains that Chef works with Juniper, Cumulus and Arista to have a running chef-client on all newtork equipments. But there's a big lack concerning Cisco. From my understanding, Chef will develop a recipe or a driver to manage existing Cisco equipment as no one will do it inside Cisco.

Another person from Chef (please if you are the personn concerned, put your name here, and apologize my lack of notes), explain that today it use either a virtual node under linux to execute expect script to configure an equipment, either the native api when this api exist. But except for some big and expensives hardware, there's no equipment with a native chef-client which can facilitate chef's configuration or orchestration.

What will we do now? What needs to happen next?

So generally, everyone accept that today, managing networking is a pain. No LBs, firewall or switch or router are easily manageable with Chef. We need to write some workaround to achieve the goal.

But thanks to Matt, we are expecting a lot more from Chef Software Company :) Please sign more partnership with all newtork vendors guys!!!

⚠️ **GitHub.com Fallback** ⚠️