Version 1.0.3

Compatible with SONiC 4.0.3 GA release

Improvements

• Support persisted distributed sessions between Portal backends

Bug fixes

• [UI] Topology view overlaps

• Network segment creation - disable autostate on border leaf VLANs

• Port Channel creation is failing

• [UI] Topology view with Watford DC topology shows overlapping racks

• [UI] Hide management address if it is null

• Reconciliation failing

• Filter uninstantiated ports in response from api/inventory/interfaces

• Switchport mapping | Check ports step doesn't shows configuration conflict if port already has existing mapping

Version 1.0.2

Compatible with SONiC 4.0.3 GA release

Improvements

• Significantly improved performance of DC plan file export

• Maximum gRPC message size is configurable for Device Controller via its application configuration

Bug fixes

• Fixed a bug where maximum gRPC response payload size was reached when reading configuration from devices

• Fixed UI bug where notification about DC plan file import incorrectly mentioned Inventory file import instead

Version 1.0.1

Compatible with SONiC 4.0.3 GA release

Improvements

This release significantly improves (orders of magnitude) DB queries performed for various API calls, DC plan and inventory file Import operations.

Bug fixes

• When processing DC plan file, validate the Port breakout speed with the speeds available in the port breakout definition

Version 1.0.0

HW equivalent of version below

Use cases included in this release

(no changes since 0.0.21)

• DHCP Relay Management

• Modify network segment - DHCP Relay update

• Configuration changes stored to startup configuration

• Device model change

• L2/L3 Portchannel management UI

• Loopback management

• Device configuration snapshot (pull & push) including ZTP - Push configuration to switch

• Device blueprint names

• OS Image Server UI

• Topology view - UI Draft using mocked data

• Backend/API implementation for OS Image server use case

• Portchannel creation/deletion

• Network segment creation/deletion

• Add/Remove L2 VNI and subnet to switchport

• DC Plan Import/Export

• Inventory view

• Fabric view

• Port change

• Cable check

• Brownfield

• Reconcilliation

• Audit logs available in the UI

• IPv6 Support

Improvements

• Kubernetes services now have anti-affinity configured to prefer scheduling on separate Kubernetes nodes for higher availability.

• Session stickiness added to Ingress configuration to allow connections to reach same portal service during a session

• [UI] Prefill fallback and fastrate in pc create in case of mode=STATIC

• [UI] Add warning to switchport mapping UI when device does not have loopback/VRF

Brownfield update

Updated Brownfield file import and Brownfield file model to allow configuration of DHCP Relays

• New entity DhcpRelayDto was introduced

  • This entity contains data to create a DHCP Relay via a Brownfield import file

• New array entity dhcpRelays was introduced

  • This array entity contains DhcpRelayDto entities

These entities were introduced to add the ability to create DhcpRelayDto via a Brownfield file.

• Property dhcpRelays of NetworkSegmentParametersDto entity was replaced with dhcpRelay

  • New property is a string which references the DhcpRelayDto entity

• Property dhcpRelaysIpv6 of NetworkSegmentParametersDto entity was replaced with dhcpRelayIpv6

  • New property is a string which references the DhcpRelayDto entity

Open

Bug fixes

• Cable check error - single switch

• Add tooltip for switchport mapping for POD selection dropdown

• NPE when updating to DHCP relay with loopback, which is not configured on the device

• [UI] No descriptive error message for uploading the invalid DC plan

• Copy config to startup after configuring leaf switchport mapping is also done on bleaf devices

Known issues

Reconciliation

During reconciliation there is a chance that some interface will be reported as missing on device (see image below).

Open

Falsely identified missing interface

This issue is caused by SONiC and will be resolved in future SONiC versions.

Switchport mapping - cannot replace untagged VLAN in single step

Due to a SONiC issue, you cannot replace the untagged VLAN on a switch port in one operation.

As a workaround, first remove the untagged VLAN mapping from the interface, then create the new mapping.

Open

Replacing an untagged VLAN with another untagged VLAN on a switch port causes validation failure

Open

Validation error occurs when user replaces untagged VLAN on switch port

Version 0.0.21

HW equivalent of version below (should be compatible with 4.0.3 GA)

Use cases included in this release

Improvements

• Speedup switchport mapping requests

Bug fixes

• Version 0.0.12 reconciliation portchannel members display members from dc plan file in the intent

• Version 0.0.16 hide spines and BLs from switchport mapping switch list

• Version 0.0.18 label is not shown correctly under switchport mapping window

• Version 0.0.18 prune eth0 and other management interfaces from switchport mapping

• PortChannel creation with LACP

• [UI] Switchport Mapping view freezes on window resize - large number of items and grouping enabled

• [UI] UI should check if DHCP relay with the same name already exists

• [UI] User should only be able to update the DHCP network segment relay in the same address family

• [UI] Port Group view scrolling doesn't work

• [UI] Members are not visible at low screen resolution

• [UI] Incorret input data in /api/portchannel/create

• [UI] DHCP relay Update missing "successfully done" message

• [UI] Add Create Portchannel range validation

• [UI] No validation error message for IPV4 when creating a new DHCP relay

• [UI] Incorrect description of change port speed button

• [UI] Add a number range for the loopback number in the DHCP relay dialog

• Loading of switchport mapping page takes long time

• Unable to import DC plan file larger than 4 MB

• DHCP relay update operation does not check if device is installed or call sync-from-network RPC

• CopyConfig can fail silently without throwing an exception

• It is not possible to create a portchannel with interfaces from bleaf1 and interfaces from bleaf2.

• Exception in service controller logs from copy config

• When removing DHCP relay in use, the error message is not understandable

• Source interface and VRF dissapears when DHCP relay IP addresses are fully replaced

• Fix check connection rpc

• SwitchportMappings Dialog not all switches are loaded after advancing and then returning to first page

• Update dhcp is reporting wrong device ids as affected.

• Do not allow update of dhcp relay when subnet does not contain any subnet data for that address family

• The workflow is stuck with process for the device model change

• Do not delete missing relay from device during update

• Re-importing the inventory view file results in a violation exception

• Reconciliation conflicts in VRF and Loopback after NS - DHCP relay update

• Delete of dhcp relay fails when there are multiple mappings for the same vlan

• Do not update relays for the port channel mappings created in network segment create

• Dhcp relay configuration on device seems to be merged instead of replaced

• A validation error is displaying for the correct subnet value

• NS Create - Copyconfig performed when device is not in MANAGED state

• Unable to create Portchannel after filling all required fields

• Unable to remove switchport mapping after DHCP NS relay update

• Portchannels, Loopbacks tables don't display all entities

• Creating a switchport mapping fails with the REPLACE strategy

• Reconciliation fails after Portchannel creation

Version 0.0.20

HW equivalent of version below (should be compatible with 4.0.3 GA)

Use cases included in this release

DHCP Relay Management - UI

New section was added under settings to specify DHPC relays. When defining the DHCP relays, the data is only stored in the inventory database until it’s assigned to a network segment and assigned to a switch port.

The DHCP relay can be modified - the IP addresses can be changed. If the DHCP relay is assigned to a network segment on a device, the device configuration is updated.

The DHCP relay can only be removed, when it's no longer assigned to any network segment in the controller database.

Modify network segment - DHCP Relay update

Use case description

It’s now possible to also change the DHCP relay assigned to the network segment. This change is propagated to all devices, where network segment is assigned.

The Network segment creation dialog was changed slightly to provide dropdown of the relays.

Configuration changes stored to startup configuration

From now on, each configuration workflow will trigger copy of running configuration to startup.

Device model change

New API was introduced to add capability to perform device model update.

Introduce L2/L3 Portchannel management page

New page was introduced to provide UI for Portchannel management

Improvements

Add authentication to RBAC endpoints for user/permission management

[UI] Inform user about not pushing snapshot after upload

Append prefix mask to IPv4/IPv6 address in api/inventory/loopbacks/device/deviceId response

Implement endpoint to check if device has loopback and VRF configured

Bug fixes

[UI] Last step in switchport mapping wizard reports incorrect device state

[UI] With no DC plan imported Fabric/Devices page shows Data loading failed!

[UI] Topology view console errors and device details not shown

[UI] Unselecting VNI results in incorrect VNI list

[UI] NS Create dialog doesn't check managed state for the selected pod

[UI] Topology view - warnings 'Unsupported node type' shown in console when opening POD_1

[UI] Topology view - text on top of another text is not readable

[UI] DHCP Relay creation - validation not performed when switching between IPv4 and IPv6

[UI] Loopback interface view has no button to configure columns

[UI] After importing DC plan, the link in notification should target DC Designer/Devices not Fabric/Devices

When conflicting untagged mappings are checked, backend returns duplicate conflicting responses

Mclag domain conflict for portchannel after reconciliation

IPv4 DHCP relay Update from two IP addresses to a single IP address removes all addresses on the device

Version 0.0.19

HW equivalent of version below (should be compatible with 4.0.3 GA)

Use cases included in this release

Device blueprint names - move blueprint devices and DC plan operations to a separate page

Original Fabric/Devices page was split into two views - DC Designer/Devices and Fabric/Devices.

DC Designer - Devices view

DC Designer view covers the management of blueprint devices.

DC plan Import/Export operations were moved to the DC Designer view since devices imported at this stage are just planned devices without any connection information.

Fabric - Devices view

The Fabric/Devices view now contains only devices that were imported via Inventory file. Inventory file and Brownfield file operations remain in this view as before.

Both views now contain a new drop-down in the top-right section to filter devices by POD.

DHCP relay manager - APIs

APIs are implemented to manage the DHCP relays in the inventory DB and the device configuration

See API documentation for following endpoints

The UI for DHCP Relay manager will be implemented in upcoming release.

Topology view

The topology view UI is no longer using mocked data, but displays information stored in the inventory database.

Port breakout API (alpha)

Backend implementation of the Port breakout use case

NOTE: The backend only updates the service intent, not device configuration. The breakout needs to be performed manually on the device and reconciled with the controller.

Actual port breakout and are UI planned for a later phase.

DC plan model was updated to include information needed to perform port breakout (see later section for DC plan model change).

New API introduced /api/portbreakout/change to store the port breakout intent in controller inventory.

Same as previous version

Important changes

DC plan model change

To add support for the port break-out use case, following modification are needed in the DC plan:

• Topology section moved from interface level to device level and renamed to neighbors list and now contains:

  • localInterfaceRef

  • neighborInterfaceRef

• Port breakout schema changed, property renamed from breakoutPorts to portBreakouts

• Ports list is expected to contain all ports on a device (even those that can be created via port breakout)

• Property Port.name removed, name is provided via Port.interfaceRef

• Property Port.availableSpeeds added, expected when port is a non breakout port nor it is a port group member, available speeds for such ports are provided via portBreakouts or portGroups properties.

• Property Portgroup.ports renamed to memberInterfaceRefs and is expected to contain InterfaceReference instances.

• Property Portgroup.availableSpeeds added

• Property defaultDhcpRelaySource removed, dhcp is now managed by dhcp relay crud

Open

Improvements

Inform user when config will not be pushed to device during service intent creation

To ensure the user is informed when creating network intents through the UI, he’s now warned if the device he’s about to configure is or is not in MANAGED state.

• [UI] LAMP 0.0.7 add more details to error message for the import inventory file

• [UI] Interconnect UI with portal-backend api endpoints for Topology view

• [UI] Add device filtering based on podId and device state

• [UI] Inform user when config will not be pushed to device during service intent creation

• [UI] Add message on hover to select at least one device for operations in Fabric/Devices

• Prevent and communicate to user imposibility of creating switchport mapping if Inventory file is not imported

• Update api/inventory/devices EP with fields for DC Designer/Devices

• Add filtering by podId for EP api/inventory-view/devices

• Create endpoints to submit Create/Remove/Update DHCP relay workflow

• Reorganize UI acording the sketches

• Reorganize the devices view acording to the sketches

• Check IP address duplicity as part of validation of DHCP relay intents

Bug fixes

• [SD] - Version 0.0.11 Switchport removal notification is showing a warning

• [SD] - Version 0.0.12 DATA_ACCESS_EXCEPTION on importing brownfield file after a sequence of triggers

• [SD] - Version 0.0.12 reconciliation shows conflict for ipv6 only VNI

• [SD] - Version 0.0.12 [intermittent] seeing Null pointer exception when ipv6 address remove/add on NS vlan and run reconcilation

• [SD] - Version 0.0.16 With no Switch port mappings and 1000 NS, switchport mapping takes 7 seconds to load

• [UI] Change the state transition button in the cable check result dialog

• [UI] | Loopback creation | Addresses (ipv4 and ipv6) and also VRF should be optional

• Conflicting new mappings are not marked in the switchport mapping wizard

• Unable to create subnet with the same vlan in two different pods

• UI interpretes workflow results for stage transition incorrectly

• gNOI's copyConfig gets stuck when connection with device is lost

• Switchport mapping removal fails when multiple mappings are removed

Version 0.0.18

Required SONiC version

No change from Version 0.0.17

Use cases included in this release

Loopback management UI

This release includes the frontend implementation for the Loopback management.

This adds a new section Loopbacks in the device details view, that lists existing loopback service intents and provides option to either remove the Loopback or add a new one.

Same as previous version

Improvements

• [UI] Enable user to run cablecheck for any stage state

• Create/remove switchport mappings in one transaction

• [UI] Remove redundant filters in tables (configuration snapshosts, system config)

• Fix the issues in OpenAPI schema

• Address Java vulnerabilities reported by twistlock

• [UI] Introduce top menu item breadcrumb to the breadcrumbs view

Bug

• [SD] - Version 0.0.14 Unable to load data center file using REST API

• [SD] - Version 0.0.14 Stream Error n service controller and RESOURCE_EXHAUSTED on portal container

• [SD] - Version 0.0.16, import bownfield file. NS cannot be deleted

• [SD] - Version 0.0.17 /api/inventory-view/devices return type should be list in the open-api spec