Feat(eos_cli_config_gen): Adding options for path-selection lb policies

[gmuloc]

Change Summary

Adding new options to router_path_selection.load_balancing_policies

NOTE - updating the schema for path_groups but it is ok as we have not released it yet (except in a dev release)

       load_balance_policies:
         - name: <str>
+          hop_count_lower: <bool>
+          jitter: <int>
           latency: <int>
+          loss_rate: <str>
           path_groups:
-            - <str>
+            - name: <str>
+              priority: <int>

Component(s) name

arista.avd.eos_cli_config_gen

Proposed changes

cf schema update.

NOTE: The sorting of path-groups is done per priority and then per alphabetical order. When no priority is given by the user in the schema, the priority is 1 and when priority is set to 1 in CLI it is not rendered (Cf below)

For now because of Ansible version 2.13 and its overwriting of Jinja2 groupby filter that does not support default, a cumbersome injection of priority 1 is made when it is not set to allow for a proper sorting.

router path-selection
   load-balance policy DEMO
      no latency
      no jitter
      loss-rate 42.42
      path-group BLAH priority 42
host1(config-load-balance-policy-DEMO)#path-group BLEH priority 12
host1(config-load-balance-policy-DEMO)#show active
router path-selection
   load-balance policy DEMO
      loss-rate 42.42
      path-group BLEH priority 12
      path-group BLAH priority 42
host1(config-load-balance-policy-DEMO)#path-group BLUH pr 1
host1(config-load-balance-policy-DEMO)#show active
router path-selection
   load-balance policy DEMO
      loss-rate 42.42
      path-group BLIH
      path-group BLUH
      path-group BLEH priority 12
      path-group BLAH priority 42

How to test

molecule

Checklist

Repository Checklist

• My code has been rebased from devel before I start
• I have read the CONTRIBUTING document.
• My change requires a change to the documentation and documentation have been updated accordingly.
• I have updated molecule CI testing accordingly. (check the box if not applicable)

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[github-actions]

Conflicts have been resolved. A maintainer will review the pull request shortly.

[ClausHolbechArista]

Breaking data model change is OK since we have not released the old data model. LGTM (a few comments)

[carlbuchmann]

LGTM once CI passes!