This post is the last one within a series that I’ve created primarily at the beginning of 2016. The topic was on How to build your own Network Config Generator. The last post within the series was some time ago and I like to finish it today with a short review of the process and my experience during the time.
This post is part of the series “How to build your own Network Configuration Generator”. You find the overview about the entire series here. The last state of the code is available at the Network Configuration Generator GitHub repository. This post discuss the first use case, where we provide the generated configurations “to the outside world”. I’ll like to show you today, how the Network Configuration Generator can be used on an “Appliance” to provide configurations using FTP and TFTP.
In the last posts, I described how the Web service is created and how it works. Now it is time to deploy it on a server. This post contains some background information about server-side python, the deployment of such applications and the automation of the deployment process itself. After reading this post, you’ll know how server-side python works and how to deploy the Network Configuration Generator on a server or within a VM.
I like to show you today, how I update the style of the Network Configuration Generator using the UIkit CSS framework. As mentioned in my last post, the (most) functional requirements are already satisfied, but plain HTML is not the best look and feel for a Web service.
I’ll like to discuss the Mako Template Engine and the integration to the Network Configuration Generator in this post. The initial Use Case for the Web service includes the following requirements: dynamically detection of configuration variables, control structures within the templates and the bulk generation of configuration data.