Skip to content

Latest commit

 

History

History
341 lines (232 loc) · 22.4 KB

CHANGELOG.md

File metadata and controls

341 lines (232 loc) · 22.4 KB
Raw

Changelog QualityOnDemand

Table of Contents

Version numbers 0.2.x to 0.7.x were intentionally not used to avoid conflicts with local implementations.

Please be aware that the project will have frequent updates to the main branch. There are no compatibility guarantees associated with code in any branch, including main, until it has been released. For example, changes may be reverted before a release is published. For the best results, use the latest published release.

v0.10.1

v0.10.1 is a patch release of v0.10.0 of the Quality-On-Demand (QoD) API. Please read also the notes and changes for v0.10.0 release

Fixed

  • Updated the documentation to address the lack of statusInfo in SessionInfo temporary by @hdamker in camaraproject#269
    • Note: The parameter statusInfo will be added to SessionInfo within next regular release
  • Fixed maximum duration in session info and improved documentation by @emil-cheung in camaraproject#277
    • Improved the documentation of "Extend the duration of an active session"
    • Improved the datatype "SessionInfo" to remove the maximum limit of duration

Further changes within the project

v0.10.0

This release contains the fourth alpha version of the Quality-On-Demand (QoD) API.

Please note:

  • This release contains significant changes compared to v0.9.0, and the QoD API is not backward compatible
    • Within notifications the schema EventNotificationhas been replace by CloudEvent in accordance with the updated CAMARA Design Guidelines
    • If within device an IPv6 address is used it must be a single IPv6 address (out of the prefix used by the device)
  • This release includes changes to be compliant with the Design Guidelines and other documents in release v0.2 of CAMARA Commonalities
  • This is another v0.x release and further releases before the first stable major v1.x release might introduce breaking changes (e.g. API changes to align with Commonalities updates)

Main Changes

  • Aligned event notification with CloudEvent spec which will allow API consumers and implementators to use standard libraries and tools which are available to handle CloudEvents (https://cloudevents.io/)
  • Added a new operation /sessions/{sessionId}/extend which allows to extend the duration of an active session

Added

Changed

  • Align event notification with CloudEvents spec by @jlurien in camaraproject#224
  • Moved "description" out of "allOf" declaration by @maxl2287 in camaraproject#205
    • Note: this change shouldn't have an impact for API consumers but is relevant for implementations of the API.
  • Single IP addresses in Device model specified with standard formats instead of patterns by @jlurien in camaraproject#237
  • Moved "basePath" /qod/v0 to "url"-property and introduced "apiroot" in definition of server @maxl2287 in camaraproject#252
  • Added statusInfo 'DELETE_REQUESTED' for qosStatus 'UNAVAILABLE' and clarified notification events in documentation by @hdamker in camaraproject#258

Fixed

  • NA

Removed

  • NA

New Contributors

Full Changelog: https://github.com/camaraproject/QualityOnDemand/compare/v0.9.0...v0.10.0

v0.10.0-rc2

This is the second release candidate of v0.10.0 - containing the upcoming fourth alpha version of the Quality-On-Demand (QoD) API

Changes compared to v0.10.0-rc

  • Added a new error example for DurationOutOfRangeForQoSProfile by @jlurien in camaraproject#259
  • Moved "basePath" /qod/v0 to "url"-property and introduced "apiroot" in definition of server @maxl2287 in camaraproject#252
  • Added a note to maxDuration parameter within qosProfile schema about the limit of 86400 seconds by @hdamker in camaraproject#256
  • Added statusInfo 'DELETE_REQUESTED' for qosStatus 'UNAVAILABLE' and clarified notification events in documentation by @hdamker in camaraproject#258:
    • notifications will be sent for all changes of QosStatus, even if initiated by the client.
    • what will happen when qosStatus changes from 'AVAILABLE' to 'UNAVAILABLE' due to 'NETWORK_TERMINATED'

Full Changelog: https://github.com/camaraproject/QualityOnDemand/compare/v0.10.0-rc...v0.10.0-rc2

v0.10.0-rc

This is the first release candidate of v0.10.0 - containing the upcoming fourth alpha version of the Quality-On-Demand (QoD) API

Please note:

  • This release will contain significant changes compared to v0.9.0, and it is not backward compatible
    • Within notifications the schema EventNotificationhas been replace by CloudEvent in accordance with the updated CAMARA Design Guidelines
    • If within device an IPv6 address is used it must be a single IPv6 address (out of the prefix used by the device)
  • This is only the pre-release, it should be considered as a draft of the upcoming release v0.10.0
    • The pre-release is meant for implementors, but it is not recommended to use the API with customers in productive environments.

Main Changes

  • Aligned event notification with CloudEvent spec which will allow API consumers and implementators to use standard libraries and tools which are available to handle CloudEvents (https://cloudevents.io/)
  • Added a new operation /sessions/{sessionId}/extend which allows to extend the duration of an active session

Added

Changed

Fixed

  • NA

Removed

  • NA

New Contributors

Full Changelog: https://github.com/camaraproject/QualityOnDemand/compare/v0.9.0...v0.10.0-rc

v0.9.0

This is the third alpha version of the Quality-On-Demand (QoD) API.

Please note:

  • This release contains significant breaking changes compared to v0.8.1, and it is not backward compatible
    • Especially a lot of the parameter names changed in line with the agreed glossary within CAMARA Commonalities
  • This is an alpha version, it should be considered as a draft.
  • There are bug fixes to be expected and incompatible changes in upcoming versions.
  • The release is suitable for implementors, but it is not recommended to use the API with customers in productive environments.

Added

  • Introduced qosStatus and corresponding notification event to fix issue #38 by @emil-cheung in camaraproject#67
  • Added basic tests with Cucumber framework using Java and Maven implementation by @mdomale in camaraproject#134
  • Added new methods to get service provider defined QoS Profile by @RandyLevensalor in camaraproject#138
  • Scopes specified and OAuth2 authorizationCode flow added as security mechanism, for operations dealing with QoD sessions by @jlurien in camaraproject#163
  • Added new model EventQosStatus by @jlurien in camaraproject#167

Changed

  • Aligned error format with CAMARA design guidelines by @jlurien in camaraproject#104
  • Renamed properties to new terms agreed in CAMARA Commonalitites by @jlurien in camaraproject#129
  • Updated method for identifying devices by IPv4 address by @eric-murray in camaraproject#139
  • Updated of the notification event related fields based on the CAMARA design guideline by @akoshunyadi in camaraproject#155
  • CAMARA documentation is now embedded within the OAS definition, and not separate by @jlurien in camaraproject#151

Fixed

  • Added error code 501 "Not Implemented" by @dfischer-tech in camaraproject#124
  • Added inheritance between Event and QosStatusChangedEvent and simplified notification payload model by @patrice-conil in camaraproject#177

Removed

  • Removed format lines from Datatypes Ipv4Address and Ipv6Address by @tlohmar in camaraproject#177
  • Removed markdown documentation (now embedded within the OAS definition, see above)

Full Changelog: https://github.com/camaraproject/QualityOnDemand/compare/v0.8.1...v0.9.0

v0.9.0-rc

This is the release candidate of v0.9.0 - the (third alpha (tbc)) release of the Quality-On-Demand (QoD) API

Please note:

  • This release contains significant changes compared to v0.8.1, and it is not backward compatible
    • Especially a lot of the parameter names changed in line with the agreed glossary within CAMARA Commonalities
  • This is only the pre-release, it should be considered as a draft of the upcoming release v0.9.0
  • The pre-release is meant for implementors, but it is not recommended to use the API with customers in productive environments.

Added

  • Introduced qosStatus and corresponding notification event to fix issue #38 by @emil-cheung in camaraproject#67
  • Added basic tests with Cucumber framework using Java and Maven implementation by @mdomale in camaraproject#134
  • Added new methods to get service provider defined QoS Profile by @RandyLevensalor in camaraproject#138
  • Scopes specified and OAuth2 authorizationCode flow added as security mechanism, for operations dealing with QoD sessions by @jlurien in camaraproject#163
  • Added new model EventQosStatus by @jlurien in camaraproject#167

Changed

  • Aligned error format with CAMARA design guidelines by @jlurien in camaraproject#104
  • Renamed properties to new terms agreed in CAMARA Commonalitites by @jlurien in camaraproject#129
  • Updated method for identifying devices by IPv4 address by @eric-murray in camaraproject#139
  • Updated of the notification event related fields based on the CAMARA design guideline by @akoshunyadi in camaraproject#155
  • CAMARA documentation is now embedded within the OAS definition, and not separate by @jlurien in camaraproject#151

Fixed

Removed

  • Removed format lines from Datatypes Ipv4Address and Ipv6Address by @tlohmar in camaraproject#153
  • Removed markdown documentation (now embedded within the OAS definition, see above)

New Contributors

Full Changelog: https://github.com/camaraproject/QualityOnDemand/compare/v0.8.1...v0.9.0-rc

v0.8.1

This is the second alpha release of the Quality-On-Demand (QoD) API

Please note:

  • This minor release contains minor fixes of v0.8.0, but is not backward compatible to v0.8.0
  • This is an alpha version, it should be considered as a draft.
  • There are bug fixes to be expected and incompatible changes in upcoming versions.
  • The release is suitable for implementors, but it is not recommended to use the API with customers in productive environments.

Added

  • Added Generic error 500 to remaining procedures by @SfnUser in camaraproject#86

Changed

  • Update from notificationsUri to notificationsUrl by @maxl2287 in camaraproject#89
  • Update and rename QoD_Latency_Bandwidth_User_Story.md by @hdamker in camaraproject#103

Fixed

Removed

New Contributors

Full Changelog: https://github.com/camaraproject/QualityOnDemand/compare/v0.8.0...v0.8.1

v0.8.0

This is the first alpha version of the Quality-On-Demand (QoD) API.

Please note:

  • This is an alpha version, it should be considered as a draft.
  • There are bug fixes to be expected and incompatible changes in upcoming versions.
  • The release is suitable for implementors, but it is not recommended to use the API with customers in productive environments.
  • Version numbers 0.2.x to 0.7.x were used in private versions during the development of the API and are here not used to avoid conflicts with local implementations.
  • Provider implementations (PI) will be provided within separate repositories:

What's Changed

  • Contribution of the QoD-API spec v0.8.0 by @akoshunyadi in camaraproject#54
  • Improvements for QoSProfile_Mapping_Table.md by @tlohmar in camaraproject#62 and @hdamker in camaraproject#73
  • Update qod api documentation to 0.8.0 by @shilpa-padgaonkar in camaraproject#71
  • Editorial updates of documentation QoD_API.md by @hdamker, @kaikreuzer, and @mariobodemann
  • Delete code/API_code directory by @hdamker in camaraproject#93

New Contributors

Full Changelog: https://github.com/camaraproject/QualityOnDemand/compare/v0.1.0...v0.8.0

v0.1.0 - Initial contribution

Initial contribution of two API definitions for Quality on Demand (stable bandwidth and stable latency), including initial documentation and implementation code.

Please note

  • this "release" is only tagged to document the history of the API, it is not intended to be used by implementors or API customers
  • it was implemented by Deutsche Telekom within lab environment and tested against two NEF implementations
  • going forward the implementation code will not be part of releases of QoD API. Instead it will be provided within separate repositories (QualityOnDemand_PIx).

What's Changed

New Contributors

Full Changelog: https://github.com/camaraproject/QualityOnDemand/commits/v0.1.0