Add support for Tenant Policy Templates (DCNE-66)

[andbyrne]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Add a resource and data source to manage tenant policy templates.

There are several objects that can be defined under a tenant policy template. Each of these will also require a corresponding resource and data source:

• Route Map Policy for Multicast
• Route Map Policy for Route Control
• Custom QoS Policy
• DHCP Relay Policy
• DHCP Option Policy
• IGMP Interface Policy
• IGMP Snooping Policy
• MLD Snooping Policy
• L3Out Node Routing Policy
• L3Out Interface Routing Policy
• BGP Peer Prefix Policy
• IPSLA Track List
• IPSLA Monitoring Policy

The priority would be the two DHCP policies as there is already support for referencing these in the mso_schema_template_bd resource and data source.

NDO version

• V 4.0+

References

https://www.cisco.com/c/en/us/td/docs/dcn/ndo/4x/configuration/cisco-nexus-dashboard-orchestrator-configuration-guide-aci-411/ndo-configuration-aci-managing-tenants-41x.html#task_zw1_gtl_ztb

[lhercot]

Hi @andbyrne ,

Thanks for opening this enhancement request.

FYI, the current API for the Tenant Policies does not allow us to modify single policies individually. We are working with the NDO API team to resolve this issue and will only be able to create dedicated resources once this is addressed.

[asmith432]

Has there been any progress made on this? Is there a potential work around to call the REST API directly?

[akinross]

Hi @asmith432,

No progress has been made yet, apologies for the inconvenience. The mso_rest resource can be leveraged in case you would like to communicate directly to the REST api.

Kind regards,

Akini