Open Mierdin opened 10 years ago
might need to dumb down existing snippets to the lowest-denominator config. FC is a good example of this. FC config requires a feature add, QoS stuff, VLAN/VSAN stuff, zoning, etc. There's not just one snippet for this idea. May need to go back after the "common" stuff and say - oh, you want FC? Cool, here's a snippet that touches it all.
The "first version" will basically be a way to get from YAML to a running config. This above use case is a great candidate for a first "architecture change" branch.
Just a quick note - FabricPath is another good example for the above
vPC technically qualifies for this as well. Might actually need to make a list of everything that qualifies as lowest-common denominator config, and assume everything else is a special feature like this. This means this entire idea is DEFINITELY something for a separate branch, since it's really an architectural change.
Just a quick note - "mode fabricpath", and FCoE VLAN ID ____ under vlan configuration
Need to be able to turn small portions of a snippet on or off based on the presence of another feature. For instance, fabricpath has an impact on a vPC configuration. So in the vPC snippet, you need to do some if statements to decide to put in configs based off of the enablement of FP
QoS is another good example. No need for FCoE snippets in QoS if the switch isn't running that option