how to set cv tags to selected devices with cv_deploy

[kmueller68]

Hello.

I would like to assign custom tags to selected devices with cv_deploy.

I know the pissibility of custom tags by using

generate_cv_tags:
  device_tags:
    - name: mytag
      value: myvalue

but this puts mytag on all devices in the inventory.

My idea is to assign special custom tags on selected devices, like:

• only my storage dc leafs (for example based on hostname) should get a custom tag dc_storage: high|low.
• other dc leafs should get a customer tag for security role: dc_sec: vs.

Is there a why to mamnage this with latest cv_deploy and custom device tags?

thank you very much
Karlheinz

[ClausHolbechArista]

you would have to use some inline jinja to get this working.
like

generate_cv_tags:
  device_tags: |-
    {% if "STORAGE" in inventory_hostname %}
    - name: dc_storage
      value: high
    {% else %}
    - name: dc_storage
      value: low
    {% endif %}

This was written adhoc so test it out and adjust as needed.

[kmueller68]

@ClausHolbechArista

Thank you for your reply.

This is not working

TASK [arista.avd.eos_designs : Set eos_designs facts] **************************************************************************************
ERROR! [spine-1a7-01.LAN.MU]: 'Validation Error: generate_cv_tags.device_tags': Invalid type 'str'. Expected a 'list'.
ERROR! [spine-2a7-01.LAN.MU]: 'Validation Error: generate_cv_tags.device_tags': Invalid type 'str'. Expected a 'list'.
ERROR! [leaf-1d4-03.DC.MU]: 'Validation Error: generate_cv_tags.device_tags': Invalid type 'str'. Expected a 'list'.
ERROR! [leaf-2d4-04.DC.MU]: 'Validation Error: generate_cv_tags.device_tags': Invalid type 'str'. Expected a 'list'.
ERROR! [distri-02-01.LAN.MU]: 'Validation Error: generate_cv_tags.device_tags': Invalid type 'str'. Expected a 'list'.
ERROR! [distri-02-02.LAN.MU]: 'Validation Error: generate_cv_tags.device_tags': Invalid type 'str'. Expected a 'list'.

But I managed it this way:

  device_tags:
    - name: Campus
      value: "{% if 'spine' in inventory_hostname %}MU_LAN{% endif %}"
    - name: Campus_Pod
      value: "{% if 'spine' in inventory_hostname %}MU_LAN_SPINE{% endif %}"
    - name: Role
      value: "{% if 'spine' in inventory_hostname %}Core{% endif %}"
    - name: topology_hint_network_type
      value: "{% if 'spine' in inventory_hostname %}campusV2{% endif %}"
    - name: topology_hint_type
      value: "{% if 'spine' in inventory_hostname %}LAN_SPINE{% endif %}"

[ClausHolbechArista]

did you check out the campus option under the generate_cv_tags? We handle all the relevant tags for the campus dashboards and integrations there.

# Generate CloudVision Tags based on AVD data.
generate_cv_tags:

  # PREVIEW: This option is marked as "preview", meaning the data models or generated configuration can change at any time.
  # Generate CloudVision device and interface Topology Tags for Campus fabric devices.
  # Device is treated as a Campus fabric device if:
  #   - The `campus` variable is assigned, either as native Ansible variable or as part of the `<node_type_keys.key>` AVD data construct.
  #   - The `generate_cv_tags.campus_fabric` variable is set to `True`.
  # When campus-related tags are generated for a device, generation of the DC-related tags is automatically disabled for that device.
  # AVD generates the following device tags for the Campus fabric devices based on the provided Campus-related input variables:
  #   - `Campus`
  #   - `Campus-Pod`
  #   - `Access-Pod`
  #   - `topology_hint_type`
  #   - `Role`
  # These tags are later used by CloudVision to render the correct network layout in the Topology view (`campusV2` network hierarchy) and Campus dashboards.
  campus_fabric: <bool; default=False>

[kmueller68]

@ClausHolbechArista
I know this options and I use it, but it currently supports a more classic campus topology.

See my additional discussion here:
#6840