How Hard Is It to Manage Your Intent?

This blog post was initially sent to subscribers of my SDN and Network Automation mailing list. Subscribe here.

Remember the “every device configuration is really an expression of our intent” discussion? Forgetting the wrong level of abstraction (we mostly don’t want to deal with all the idiosyncratic stuff network devices want to see in their configurations) and box-oriented thinking caused by device-level intent for the moment, let’s focus on another aspect: how hard is it to manage your intent?

For example:

  • If you want to change your intent (in plain English: device configuration), how hard is it to get from current configuration to the new one?
  • How hard is it to see what intent has been passed to the system (in plain English: how is the device or system configured)?

In you’re working with decent networking devices you’re probably wondering why I’m even bringing up these topics. After all, the answer to the first one is replace configuration and the answer to the second one is show configuration.

Interestingly, not all network devices support configuration replace functionality (for example, configure replace was added to Nexus OS in April 2018), and even if a network device supports non-disruptive replacement of its configuration, it might not allow you to replace parts of the configuration without an interesting carefully-choreographed dance of configuration commands.

Note: the only exception I know of is Junos that treats device configuration as a data model that can be manipulated in any way you wish and implemented when you’re satisfied with its state. Arista’s config sessions might work the same way.

Now imagine you’re evaluating an abstracted intent-based system with a beautiful GUI and a REST API. Don’t forget to ask these questions (and don’t back down until you get the answers):

  • Can you easily replace your intent when you want to or do you have to work through GUI (or API calls) to massage the current state of the system into what you want it to be?
  • Can you see all of your intent in a single place or do you have to navigate through GUI screens and take notes of what’s configured (or execute a dozen of API calls to get it)?
  • Can you track a history of changes to your intent?
  • Can you track the changes to your intent with standard version-control tools like Git/GitLab/GitHub/… or do you have to use tools embedded into the system? Are there any such tools available in the system?
  • How easy is it to automate changes to your intent (like implementing the same fix to all tenants configured in the system)?
  • How easy is it to integrate the intent-based system into whatever application testing/deployment pipeline?
You might have noticed that the above questions describe infrastructure-as-code concepts ;)

Finally, for an overview of intent-based networking fundamentals watch Intent-Based Networking section of Network Automation Concepts webinar, and if want to know even more, register for the Building Network Automation Solutions online course (it has a whole module dedicated to network infrastructure-as-code).

Add comment