Configuration Loader - nihole/PSEFABRIC GitHub Wiki

In fact, it is not the task of this project to provide tools for this layer.

Different methods may be used here:

• python/perl/... scripts
• Ansible/puppet
• cisco UCSD
• ...

There may also be some vendors management systems between PSEFABRIC and equipment control planes, such as Palo Alto Panorama or Cisco ACI APIC (see p002 project).

We use python/Perl scripts in our projects (see p001 for example).

At this stage, we have created all the configuration files corresponding to the PSEFABIRIC configuration change and now we have to implement it to our underlying network.

A few general notices about the process.

We may do it automatically, semi-automatically or manually.

• Full automation
  • Automatically upload the data received from Layer 5 of DMDFM to the Control Planes (CP) of Managed Objects (MO) (or intermediate management systems)
• Semi-automation
  • We may use configuration files saved on the disc. We may want to verify them before uploading and after that use some scripts to upload configuration to CP of MOs (we use this approach for p001 project)
• Manual
  • Copy & Paste the configuration to the CP of MOs or to some application for configuration uploading (Postman for example) (we use this approach for p002 project).

The recommended method is to use the “Manual” or “Semi-Automation” methods to change the configuration you are doing the first time or are not sure the results for any reason. When you have repeatedly tested some changes, you can add them to the automation processes.

And, of course, having some kind of laboratory environment in which you can test any changes before production is the best approach.