--- features: - | Composable Networks now support creating L3 routed networks. L3 networks use multiple L2 network segments and multiple ip subnets. In addition to the base subnet automatically created for any composable network, additional subnets can be defined under the ``subnets`` key for each network in the data file (``network_data.yaml``) used by composable networks. Please refer to the ``network_data_subnets_routed.yaml`` file for an example demonstrating how to define composable L3 routed networks. - | For composable roles it is now possible to control which subnet in a L3 routed network will host network ports for the role. This is done by setting the subnet for each network in the role defenition (``roles_data.yaml``). For example:: - name: networks: InternalApi: subnet: internal_api_leaf2 Tenant: subnet: tenant_leaf2 Storage: subnet: storage_leaf2 - | To enable control of which subnet is used for virtual IPs on L3 routed composable networks the new parameter ``VipSubnetMap`` where added. This allow the user to override the subnet where the VIP port should be hosted. For example:: parameter_defaults: VipSubnetMap: ctlplane: ctlplane-leaf1 InternalApi: internal_api_leaf1 Storage: storage_leaf1 redis: internal_api_leaf1 upgrade: - | Deployments using custom names for subnets must also set the subnet to use for the roles used in the deployment. I.e if ``NetworkNameSubnetName`` parameter was used to define a non-default subnet name for any network, the role defenition (``roles_data.yaml``) and ``VipSubnetMap`` parameter must use the same value. .. Warning:: The update will fail if ``SubnetName`` was used to set a custom subnet name, and the role defenition and/or the ``VipSubnetMap`` is not set to match the custom subnet name.