prep for release 0.4.1

Author: mtarking

CHANGELOG.rst

@@ -8,6 +8,49 @@ This project adheres to `Semantic Versioning <http://semver.org/>`_.
 
 .. contents:: ``Release Versions``
 
+
+`0.4.1`_
+=====================
+
+**Release Date:** ``2025-04-24``
+
+Added
+-----
+
+* Added ability to manage edge connections to external fabrics
+* Added support for checking if a fabric is in a multisite domain and disallow management of ``vxlan.overlay.vrfs`` and ``vxlan.overlay.networks`` under the child fabric
+
+Modified
+--------
+
+* Added various multisite fixes and introduced new ``child_fabrics`` model key under ``vxlan.multisite.overlay.vrfs`` and ``vxlan.multisite.overlay.networks`` for defining site-specific attributes
+
+Fixed
+-----
+
+* https://github.com/netascode/ansible-dc-vxlan/issues/232
+* https://github.com/netascode/ansible-dc-vxlan/issues/274
+* https://github.com/netascode/ansible-dc-vxlan/issues/292
+* https://github.com/netascode/ansible-dc-vxlan/issues/293
+* https://github.com/netascode/ansible-dc-vxlan/issues/294
+* https://github.com/netascode/ansible-dc-vxlan/issues/295
+* https://github.com/netascode/ansible-dc-vxlan/issues/296
+* https://github.com/netascode/ansible-dc-vxlan/issues/302
+* https://github.com/netascode/ansible-dc-vxlan/issues/303
+* https://github.com/netascode/ansible-dc-vxlan/issues/308
+* https://github.com/netascode/ansible-dc-vxlan/issues/311
+* https://github.com/netascode/ansible-dc-vxlan/issues/314
+* https://github.com/netascode/ansible-dc-vxlan/issues/320
+* https://github.com/netascode/ansible-dc-vxlan/issues/325
+* https://github.com/netascode/ansible-dc-vxlan/issues/327
+* https://github.com/netascode/ansible-dc-vxlan/issues/331
+* https://github.com/netascode/ansible-dc-vxlan/issues/335
+* https://github.com/netascode/ansible-dc-vxlan/issues/336
+* https://github.com/netascode/ansible-dc-vxlan/issues/340
+* https://github.com/netascode/ansible-dc-vxlan/issues/343
+* https://github.com/netascode/ansible-dc-vxlan/issues/345
+* https://github.com/netascode/ansible-dc-vxlan/issues/355
+
 `0.4.0`_
 =====================
 
@@ -161,6 +204,7 @@ The following roles have been added to the collection:
 
 This version of the collection includes support for an IPv4 Underlay only.  Support for IPv6 Underlay will be available in the next release.
 
+.. _0.4.1: https://github.com/netascode/ansible-dc-vxlan/compare/0.4.0...0.4.1
 .. _0.4.0: https://github.com/netascode/ansible-dc-vxlan/compare/0.3.0...0.4.0
 .. _0.3.0: https://github.com/netascode/ansible-dc-vxlan/compare/0.2.0...0.3.0
 .. _0.2.0: https://github.com/netascode/ansible-dc-vxlan/compare/0.1.0...0.2.0

README.md

@@ -306,7 +306,7 @@ The following quickstart repository is available to provide a step by step guide
 
 This collection is intended for use with the following release versions:
 
-* `NDFC Release 12.2.1` or later.
+* `Cisco Nexus Dashboard Fabric Controller (NDFC) Release 12.2.1` or later.
 
 <!--start requires_ansible-->
 ## Ansible Version Compatibility
@@ -408,10 +408,10 @@ This capability is not available under the following conditions:
 
 ### See Also
 
-* [Ansible Using collections](https://docs.ansible.com/ansible/latest/user_guide/collections_using.html) for more details.
+* [Ansible Using Collections](https://docs.ansible.com/ansible/latest/user_guide/collections_using.html) for more details.
 
 ## Multi-Site Domain for VXLAN BGP EVPN Fabrics
-A Multi-Site Domain (MSD) is a multifabric container that is created to manage multiple member fabrics. An MSD is a single point of control for definition of overlay networks and VRFs that are shared across member fabrics. When you move fabrics (that are designated to be part of the multifabric overlay network domain) under the MSD as member fabrics, the member fabrics share the networks and VRFs created at the MSD-level. This way, you can consistently provision network and VRFs for different fabrics, at one go. It significantly reduces the time and complexity involving multiple fabric provisionings.
+A Multi-Site Domain (MSD) is a multifabric administrative domain that is created to manage multiple member fabrics. An MSD is a single point of control for definition of overlay VRFs and Networks that are shared across member fabrics. When you move fabrics under the MSD as child fabrics, the child fabrics share the VRFs and networks created at the MSD-level. This way, you can consistently provision VRFs and networks for different fabrics, at one go. It significantly reduces the time and complexity involving multiple fabric provisionings.
 
 ### To configure and manage MSD fabrics with VXLAN as Code, you should use the following workflow:
 1. Create each member/child fabric that will be managed by MSD using the normal data models for each fabric (or use a combined data model with all child fabrics)
@@ -432,9 +432,10 @@ We welcome community contributions to this collection. If you find problems, ple
 
 ## More Information
 
-- [NDFC installation and configuration guides](https://www.cisco.com/c/en/us/td/docs/dcn/ndfc/1201/installation/cisco-ndfc-install-and-upgrade-guide-1201.html)
-- [Ansible User guide](https://docs.ansible.com/ansible/latest/user_guide/index.html)
-- [Ansible Developer guide](https://docs.ansible.com/ansible/latest/dev_guide/index.html)
+- [Cisco Nexus Dashboard and Services Deployment and Upgrade Guide](https://www.cisco.com/c/en/us/td/docs/dcn/nd/3x/deployment/cisco-nexus-dashboard-and-services-deployment-guide-321.html) 
+- [Cisco Nexus Dashboard Fabric Controller (NDFC) User Content for LAN Configuration Guide](https://www.cisco.com/c/en/us/td/docs/dcn/ndfc/1222/collections/ndfc-user-content-1222-lan.html)
+- [Ansible User Guide](https://docs.ansible.com/ansible/latest/user_guide/index.html)
+- [Ansible Developer Guide](https://docs.ansible.com/ansible/latest/dev_guide/index.html)
 
 ## Licensing
 

docs/maintainers.md

@@ -0,0 +1,61 @@
+# Maintainers Guide
+
+Guidelines for the core maintainers of the VXLAN as Code Ansible Collection - above and beyond the [general developer guidelines](../CONTRIBUTING.md).
+
+## Release Process Checklist
+
+### Pre-Merge to `main` branch:
+
+When we are considering publishing a new release, all of the following steps must be carried out (using the latest code base in `develop`):
+
+1. Run full fabric profile integration regression tests against `develop`
+     * Fix all bugs
+
+1. Update [galaxy.yml](https://github.com/netascode/ansible-dc-vxlan/blob/develop/galaxy.yml) file
+    * Update Version
+        ```diff
+        -  "version": "1.0.0",
+        +  "version": "1.0.1",
+        ```
+    * Update authors as required
+    * Update dependencies as required
+
+1. Update [changelog.](https://github.com/netascode/ansible-dc-vxlan/blob/develop/CHANGELOG.rst)
+     * Make sure CHANGELOG.md accurately reflects all changes since the last release
+        * Apply a search filter: `is:issue closed:>=2025-03-01`
+     * Add any significant changes that weren't documented in the changelog
+     * Clean up any entries that are overly verbose, unclear, or otherwise could be improved
+     * Indicate new support (if any)
+     * Create release tag
+       ```diff
+       ...
+       +.. _0.4.1: https://github.com/netascode/ansible-dc-vxlan/compare/0.4.0...0.4.1
+        .. _0.4.0: https://github.com/netascode/ansible-dc-vxlan/compare/0.3.0...0.4.0
+       ```
+
+1. Scrub README docs
+     * Update README docs for new support and where applicable
+
+1. Pull release branch based on the `develop` branch
+      * 0.0.x - a bugfix release
+      * 0.x.0 - new feature(s)
+      * x.0.0 - backward-incompatible change (if unvoidable!)
+
+1. Open pull request from release branch against the `main` branch.
+     * Ensure all GitHub Actions tasks have passed
+     * Merge after approval
+
+### Post-Merge to `main` branch:
+
+1. Create annotated git tag for the release
+     * [HowTo](https://git-scm.com/book/en/v2/Git-Basics-Tagging#Annotated-Tags)
+  
+1. Draft a [new release](https://github.com/netascode/ansible-dc-vxlan/releases) on GitHub
+  
+1. Merge `main` branch back into `develop` branch
+     * Resolve any merge conflicts
+     * Optional: Delete release branch (May want to keep for reference)
+
+### Publish Release to Ansible Galaxy:
+
+1. Publish to Ansible Galaxy

galaxy.yml

@@ -1,7 +1,7 @@
 ---
 namespace: cisco
 name: nac_dc_vxlan
-version: 0.4.0
+version: 0.4.1
 readme: README.md
 authors:
   - Devendra Gupta <devegupt>