Now let’s go one step further and truly boost your automation capabilities. Imagine you can automatically build jobs and configurations by combining different data sources with this runtime engine. You can use data from the internal YCE database, your production network or from external sources (via the API).
First, the integrated, object oriented YCE database lets you store any kind of information specific to your design or ‘snowflake’ network, in a relational- and vendor agnostic way. This means you can store things like topology, ports, vrfs, ip plans, subnets, services and much more in one place. And then use them seamlessly with the netYCE engine and smart templates to generate data-driven jobs and configs.
So forget about using Excel and notepad or remembering everything from memory. Simply create and modify services by updating the database and generate configs & jobs that you want provisioned to your network with just a single mouse click or API call.
Second, imagine you can retrieve state information from your network devices and use it dynamically in your jobs. This is what 'command parsing' scenarios are all about. It lets you send show commands to your network devices and parse the requested information. The results can either be stored in the YCE database or used in realtime as input for your data-driven jobs.
It gets even better when you learn more about 'scenarios'. These data-driven 'scripts' allow you to build extremely powerful run-books with automated rules, validations and process steps for every job you send to your network.
Third, data can also come from external systems (e.g. OSS/NMS) or from an Excel/csv file. This can be sent to the netYCE API and processed as you like. You will be amazed with the possibilities you now have at your fingertips because anything that is possible
via the GUI can also be done via the API. Updating your inventory, creating new services or simply invoking the API to send data-driven jobs to your network is easy as pie.
All this will be covered in course 2.