Releases: GlobalNOC/OESS
Releases · GlobalNOC/OESS
OESS 2.0.10
Features
- #788 Ensure user and group
_oesscreated when installing oess - #1056 Add fwdctl or discovery to process name of switch processes
- #1116 When modifying a connection update cache only called on relevant nodes
- #1097 VLAN options updated after an Entity's interface is selected
- #1126 Add more descriptive message to delete connection confirm box
- #749 Forwarding impact on Connection edits now limited to nodes with modified endpoints
- #1057 Reserved and total bandwidth displayed on each interface under endpoint selection modal
- #1127 Class of service now applied to Azure express routes immediately on provisioning
- #1122 Connections may now be composed of a single Endpoint
- #1102 Limit max GCP interconnect size to 5Gb
Fixes
- #1032 Ensure
/var/run/oessexists when starting fwdctl - #1123 Fix case where not all values populated in endpoint selection modal while editing endpoint
- #1137 Numerous issues with GCP Interconnects
- Fix typo resulting in incorrect mtu being set on GCP endpoints.
- GCP peers incorrectly given auto-generated BGP keys
- Fix bandwidth enum format for interconnects 1Gb and greater
- Apply BGP multi-hop immediately upon provisioning
OESS 2.0.9
Features:
- #1110 added ability to specify the Azure base URL to support microsoft gov connections
Bugs:
- #1094 fixes to the unit name selection code - QinQ endpoints are handled better
- #1092 Removing additional warning statements that should be at debug level
- #1091 Notification daemon was dying because workgroup information not always loaded
- #1109 Azure integration was not always picking the proper interface
- #1114 removed MTU from Layer2 connections
OESS 2.0.8
Features
- #969 Allow admins to modify entities
- #1068 Trim whitespace from cloud account numbers for end users
- #1046 updating bandwidth options for AWS hosted connect for 1,2,5GBps
- #1047 Trim whitespaces from cloud_account_ids passed from frontend
- #1012 Add selection indicator to ports under entity selection
Fixes
- #1064 VRF update sometimes causes peers to be removed
- #1041 Commands section not updating interfaces to show interfaces on the selected node
- #1042 QinQ endpoints in commands not showing the proper unit
- #1048 removed excessive logging from various components
- #973 update circuit permissions to display based on selected workgroup
- #1031 IP addresses aren’t validated when creating new nodes
- #1065 sometimes OESS not properly calculating available VLANs
- #1039 Typo in the config object causing OESS to start in wrong mode
- #1060 AWS syncer returns wrong value on failure
- #971 Entities with children fail to show their ports
- #1027 CTags on Juniper must be < 4095 causing people who select 4095 to fail to provision
- #1059 sometimes when provisioning a cloud provider the entity was not specified in the API
- #1050 When BGP key was unspecified for a peering OESS would set -1 as the key
- #829 nodes were losing loopback address when failure to call get_system_info
- #1044 fixes to the Azure syncer script
- #1052 Error while decomissioning links in the admin UI related to path update failures
- #1008 Interface role is not reset to unknown after link decommissioned
- #1053 Include entity in web service request when selecting specific entity's interface
- #1049 Use correct default md5key for GCP endpoints
- #1007 Fixing case where active links couldn't be made 'available'
OESS 2.0.7
OESS 2.0.6-2
Features
Fixes
- #1010 Fixing issue preventing L3Connection Endpoints from moving during Interface Migration
OESS 2.0.6
Features
- #979 Support for EVPN-VXLAN based Layer 2 Connections
- #983 Adding class-of-service tags to Layer 2 Connections
Fixes
- #966 move_interface_configuration moves all confg except actual Endpoint while migrating interface
- #975 Cloud endpoints with auto-generated peers created without addresses
- #977 Undef bgp keys result in -1 being set as the configured bgp auth key
- #981 Entity not defined when user selects cloud entity interface
OESS 2.0.5
Features
- #874 Bi-Directional Forwarding Detection support for Layer 3 Endpoints
- #947 OESS Configuration Moved into Junos group
- #944 External CSS and JS now hosted locally
- #918 Adding ability to search for entities in phonebook
- #959 Adding customer endpoint templates to assist customers with network configuration
Fixes
- #922 More consistent terminology throughout the UI
- #945 Endpoint selector now defaults to Entity selection form
- #917 Fixes case where sub-entities are unable to be created
- #769 Fixed broken form validation for peering addresses
- #937 Fixes issue with endpoint selector that prevented selection of underlying interface
- #940 Fixed an issue where the unit number was improperly selected for provisioning
- #938 Refactoring User object to lazily load workgroups increasing load time of Connections.
- #923 Fixes case where traffic utilization displayed values for entire interface vs the expected sub-interface
OESS 2.0.4
Features
- #909 Making network diff interval configurable
- #921 Adding local ASN to layer 3 connection view
- #906 Adding ability to use back button on playbook
- #822 Now Enforcing uniqueness of entity names
- #851 Adding additional loading indicators for lengthy UI actions
- #886 Adding support for cloud provisioning with Layer 2 Connections
- #908 Syncing Max Bandwidth to OESS if modified from Azure portal
- #925 Adding ability to manage peerings on AWS Hosted Connection endpoints
Fixes
- #930 and #931 Fixing endpoint jumbo frame checkbox and selecting appropriate MTU based on endpoint type
- #897, #898, #899 and #900 Updating permissions for various web service endpoints
- #885 Now considering layer 2 connections when performing VLAN availability checks for layer 3 provisioning
- #878 Improving API error messages returned to end users
- #893 Removing unused database table
OESS 2.0.3
Features
- #878 Improving error message content for provisioning failures
- #876 Creating new admin action 'move configuration' to replace/supplement old 'move circuits' action
- #860 Adding new admin webservice to trigger cache rewrites
- #832 Improving display of circuit state on network status page
- #821 Adding SSL support to NSA endpoints
- #813 Displaying max bandwidth on network endpoints
Fixes
- #871 Fixing case where junos unit name improperly selected which prevented provisioning in some cases
- #867 Fixing issue where ACLs with workgroup of 'All' were disregarded
- #853 Fixing various issues related to interface selection when provisioning to an entity
- #847 and #846 Fixing UI bug which prevented configuration of peerings
- #844 Fixing issue where UI wouldn't render for workgroups who didn't own ports
- #828 Handling case where device configuration lock failure was improperly handled
OESS 2.0.2
OESS 2.0.2 - With Microsoft Azure support
Features:
#702 Added Microsoft Azure Support
#812 ACL update uses new DB Model and Libraries
#665 hide auto-generated BGP keys from end user for provider endpoints
#704 add ACL edits to the new UI
#786 Grafana URLs should be configurable
Added L2 Circuits to the new UI
Added the ability to edit L2 Circuits in the new UI
Bug Fixes:
#821 NSI not properly using SSL encrypt to endpoints
#804 problem when doing an edit of a VRF that it does not always get re-added
#788 _oess user is now added by the oess-core RPM
#782 oess aws syncer does not work when AWS circuit is removed from AWS but not OESS
#810 diff of GCP does not include multihop bit
#798 adding foreign keys to entity table
#803 OESS diffs are happening too frequently
#802 L3VPN removal leaves behind shaper
#791 some missing functions for NSI
#781 OESS unable to show endpoints when no entity is selected
#794 SOAP::Lite initialization not working with SSL
#787 diffing L3VPN has a problem trying to detect if site ID has changed
#784 OESS AWS/GCP syncers do not support ECP endpoints
#783 Discovery TSDS pusher does not support ECP endpoints
#530 NSI not detecting dataPlaneStateChangeEvents