官术网_书友最值得收藏!

The challenges of CLI

At the Interop expo in Las Vegas 2014, BigSwitch Networks CEO Douglas Murray displayed the following slide to illustrate what has changed in Data Center Networking (DCN) in 20 years between 1993 to 2013:

Datacenter Networking Changes (source: https://www.bigswitch.com/sites/default/files/presentations/murraydouglasstartuphotseatpanel.pdf)

While he might be negatively biased toward the incumbent vendors when displaying this slide, the point is well taken. In his opinion, the only thing in managing routers and switches that has changed in 20 years was the protocol changing from Telnet to the more secured SSH. It is right around the same time that we start to see the consensus around the industry for the clear need to move away from manual, human-driven CLI toward an automatic, computer-centric automation API. Make no mistake, we still need to directly communicate with the device when making network designs, bringing up initial proof of concepts, and deploying the topology for the first time. However, once we have moved beyond the initial deployment, the need becomes to consistently make the same changes error-free, over and over again without being distracted or feeling tired. Sounds like an ideal job for computers and our favorite language, Python.

Referring back to the slide, the challenge, is the interaction between the router and the administrator. The router expects the administrator to enter a series of manual inputs that requires human interpretation. For example, you have to type in enable to get into a privileged mode, and upon receiving the returned prompt with # sign, you then need to type in configure terminal in order to go into the configuration mode. The same process can further be expanded into interface configuration mode and routing protocol configuration mode. This is in a sharp contrast to an computer-driven mindset. When computer wants to accomplish a single task, say put an IP on an interface, it wants to structurally give all the information to the router at once, and then it expects a single yes or no answer from the router to indicate success or failure of the task.

The solution, as implemented by both Pexpect and Paramiko, is to treat the interactive process as a child process and watch over the interaction between the process and the destination device. Based on the returned value, the parent process will decide the subsequent action, if any.

主站蜘蛛池模板: 乐都县| 阿图什市| 万盛区| 望奎县| 大荔县| 镇巴县| 和平区| 莱芜市| 宁陵县| 余江县| 桐乡市| 彭阳县| 安宁市| 田林县| 颍上县| 梁山县| 荥阳市| 长治县| 巴青县| 黎川县| 博野县| 西昌市| 武夷山市| 安宁市| 香港| 邓州市| 邢台市| 多伦县| 黄大仙区| 桂平市| 高台县| 苏尼特右旗| 深州市| 重庆市| 河西区| 玉田县| 云梦县| 平昌县| 麻栗坡县| 永清县| 托克托县|