From 0ee3f7539eb744ce5dcb356ed9fa126f1b4b2127 Mon Sep 17 00:00:00 2001 From: Nigel Jones Date: Tue, 30 Nov 2021 09:04:18 +0000 Subject: [PATCH] remove release notes from master #5929 Signed-off-by: Nigel Jones Signed-off-by: Nigel Jones --- .github/ISSUE_TEMPLATE/release.yml | 7 +- release-notes/README.md | 225 +--------------------------- release-notes/release-notes-1-0.md | 38 ----- release-notes/release-notes-1-1.md | 68 --------- release-notes/release-notes-1-2.md | 59 -------- release-notes/release-notes-1-3.md | 67 --------- release-notes/release-notes-1-4.md | 21 --- release-notes/release-notes-1-5.md | 47 ------ release-notes/release-notes-1-6.md | 39 ----- release-notes/release-notes-1-7.md | 37 ----- release-notes/release-notes-1-8.md | 33 ---- release-notes/release-notes-2-0.md | 30 ---- release-notes/release-notes-2-1.md | 31 ---- release-notes/release-notes-2-10.md | 173 --------------------- release-notes/release-notes-2-11.md | 178 ---------------------- release-notes/release-notes-2-2.md | 34 ----- release-notes/release-notes-2-3.md | 46 ------ release-notes/release-notes-2-4.md | 51 ------- release-notes/release-notes-2-5.md | 59 -------- release-notes/release-notes-2-6.md | 132 ---------------- release-notes/release-notes-2-7.md | 58 ------- release-notes/release-notes-2-8.md | 155 ------------------- release-notes/release-notes-2-9.md | 70 --------- release-notes/release-notes-3-0.md | 47 ------ release-notes/release-notes-3-1.md | 111 -------------- release-notes/release-notes-3-2.md | 54 ------- release-notes/release-notes-3-3.md | 54 ------- release-notes/release-notes-3-4.md | 37 ----- 28 files changed, 7 insertions(+), 1954 deletions(-) delete mode 100644 release-notes/release-notes-1-0.md delete mode 100644 release-notes/release-notes-1-1.md delete mode 100644 release-notes/release-notes-1-2.md delete mode 100644 release-notes/release-notes-1-3.md delete mode 100644 release-notes/release-notes-1-4.md delete mode 100644 release-notes/release-notes-1-5.md delete mode 100644 release-notes/release-notes-1-6.md delete mode 100644 release-notes/release-notes-1-7.md delete mode 100644 release-notes/release-notes-1-8.md delete mode 100644 release-notes/release-notes-2-0.md delete mode 100644 release-notes/release-notes-2-1.md delete mode 100644 release-notes/release-notes-2-10.md delete mode 100644 release-notes/release-notes-2-11.md delete mode 100644 release-notes/release-notes-2-2.md delete mode 100644 release-notes/release-notes-2-3.md delete mode 100644 release-notes/release-notes-2-4.md delete mode 100644 release-notes/release-notes-2-5.md delete mode 100644 release-notes/release-notes-2-6.md delete mode 100644 release-notes/release-notes-2-7.md delete mode 100644 release-notes/release-notes-2-8.md delete mode 100644 release-notes/release-notes-2-9.md delete mode 100644 release-notes/release-notes-3-0.md delete mode 100644 release-notes/release-notes-3-1.md delete mode 100644 release-notes/release-notes-3-2.md delete mode 100644 release-notes/release-notes-3-3.md delete mode 100644 release-notes/release-notes-3-4.md diff --git a/.github/ISSUE_TEMPLATE/release.yml b/.github/ISSUE_TEMPLATE/release.yml index 25ce2bec2cd..e3fee4d402d 100644 --- a/.github/ISSUE_TEMPLATE/release.yml +++ b/.github/ISSUE_TEMPLATE/release.yml @@ -29,8 +29,6 @@ body: Final updates to the release - [ ] Ensure any remaining fixes are merged into branch (and vice-versa to master) - - [ ] Remove release notes from branch - - [ ] update release notes in master & rename Generate a release image for testing - [ ] Start release pipeline manually to generate docker image @@ -55,10 +53,13 @@ body: - [ ] CTS - graph - [ ] CTS - inmemory + Final Docs + - [ ] Update release notes in egeria-docs + Final build and publish - [ ] Run 'release' pipeline on branch to push candidates to oss.sonatype.org - [ ] 'close' staging repo & Validate artifacts ok (number, structure, validations) on oss.sonatype.org - - [ ] Create final github releases for egeria (use release notes from master as text) + - [ ] Create final github releases for egeria (add link to egeria docs) - [ ] Close repo on oss.sonatype.org (once updated) for egeria, release - [ ] Check 'release' repo on oss.sonatype.org has artifacts - [ ] Update final versions of egeria-charts to release ie x.y diff --git a/release-notes/README.md b/release-notes/README.md index d6a73201d3b..39375b06f92 100644 --- a/release-notes/README.md +++ b/release-notes/README.md @@ -3,229 +3,10 @@ # Egeria Release Notes -Below are the official releases of Egeria. The project aims to -produce a new release about once a month. Each release includes -new features and fixes to existing function. The team aims to -provide complete backward compatibility for all components that -are officially released (to understand more about what it means to have released function see -[Egeria Content Status](../open-metadata-publication/website/content-status)). -If backwards compatible changes are not possible, it will be called out explicitly in the -release notes with an explanation on how to upgrade. - -Each release will also upgrade the level of its dependencies to -ensure Egeria is running with all of the latest security patches. -We therefore recommend that you keep moving forward with us to -get the best Egeria experience possible. - -One way you can help us is to feedback on your experiences, both good -and bad. We would love to hear from you. - -## Latest Release - -Below are the release notes for the latest Egeria release: - -* [Release 3.3](release-notes-3-3.md) - November 2021 - * Open Metadata Type changes - * New hand-on lab introducing Lineage management - -## Older Releases - -* [Release 3.2](release-notes-3-2.md) - October 2021 - * Open Metadata Type changes - * New beta documentation site - * Deprecations - * Dependency Updates - * Bug Fixes - -* [Release 3.1](release-notes-3-1.md) - September 2021 - * Open Metadata Type changes - * New beta documentation site - * Deprecation of Docker Compose environment - * Helm charts moved - * Changes to the Coco Pharmaceuticals lab environment - * Dependency Updates - * Bug Fixes - -* [Release 3.0](release-notes-3-0.md) - August 2021 - * Java 11 is now required for build and runtime - * Multiple topics are now the default for a new cohort member - * Passwords for the demo users in the Egeria UI have been changed - * Dependency updates - * Additional notes including known issues - -* [Release 2.11](release-notes-2-11.md) - July 2021 - * New option to have multiple topics for a cohort - * New support for automatic extraction of metadata from event brokers and API managers - * Open Metadata Types - changes - * Removed functionality - * Bug Fixes - * Dependency updates - * Additional notes including known issues - -* [Release 2.10](release-notes-2-10.md) - June 2021 - * Changes to metadata types - * Updates to Governance Program OMAS API - * Bug Fixes - * Dependency updates - * Important notes included on known issues - -* [Release 2.9](release-notes-2-9.md) - May 2021 - * Updates to open metadata types - * Changes to building Egeria on Windows - * Bug Fixes - * Dependency updates - * Important notes included on known issues - -* [Release 2.8](release-notes-2-8.md) - April 2021 - * New support for event and property filtering for the open metadata server security connector - * Changes to metadata types - * New performance workbench for the CTS (technical preview) - * New interface for retrieving the complete history of a single metadata instance - * Splitting of CTS results into multiple smaller files - * Bug Fixes - * Dependency updates - * Important notes included on known issues - -* [Release 2.7](release-notes-2-7.md) - March 2021 - * Bug Fixes - * Dependency updates - -* [Release 2.6](release-notes-2-6.md) - February 2021 - * Governance Server, replacing Stewardship, Discovery & Security Server - * Changes to location of configuration files - * New metadata types for Governance Actions, Duplicate Processing - * Improvements and build changes for the React based UI - * A new simple helm chart deployment sample - * Bug Fixes - * Dependency updates - -* [Release 2.5](release-notes-2-5.md) - December 2020 - * User Interface improvements - * Additional tests - * Bug fixes - * Dependency updates - -* [Release 2.4](release-notes-2-4.md) - November 2020 - * Integration Daemon - * Rex/Tex in Presentation Server - * Additional tests - * Bug fixes - * Dependency updates - -* [Release 2.3](release-notes-2-3.md) - October 2020 - * Presentation Server User Interface - * Dino UI function - * Bug fixes - * Dependency updates - -* [Release 2.2](release-notes-2-2.md) - September 2020 - * Bug fixes - * Dependency updates - -* [Release 2.1](release-notes-2-1.md) - August 2020 - * Bug fixes - * Dependency updates - -* [Release 2.0](release-notes-2-0.md) - July 2020 - * https security for server chassis - * encrypted file connector - * Bug fixes - * Dependency updates - -* [Release 1.8](release-notes-1-8.md) - June 2020 - * Additional tutorial content in the form of the Egeria Dojo - * Repository explorer usability and functionality improvements - * Improved packaging for samples and utilities - * reliability improvement for Kafka connector - * metrics and monitoring using spring boot actuator and adding prometheus support - * Bug fixes - * Dependency updates - -* [Release 1.7](release-notes-1-7.md) - May 2020 - * Bug fixes - * Dependency updates - -* [Release 1.6](release-notes-1-6.md) - April 2020 - * Audit Log Framework (ALF) technical preview - * Repository Explorer (REX) - -* [Release 1.5](release-notes-1-5.md) - March 2020 - * Metadata de-duplication identification and notification - * Data Engine OMAS Technical Preview - * Data Engine Proxy Server Technical Preview - -* [Release 1.4](release-notes-1-4.md) - February 2020 - * Bug fixes, documentation - * Dependency updates - -* [Release 1.3](release-notes-1-3.md) - January 2019 - * Conformance test suite improvements - * Open Metadata Archives - -* [Release 1.2](release-notes-1-2.md) - December 2019 - * Conformance test suite - * Asset cataloging and consumption - * Governance zones and metadata security - * Open metadata archives - -* [Release 1.1](release-notes-1-1.md) - November 2019 - * Multi-tenant OMAG Server Platform - * JanusGraph based metadata repository - -* [Release 1.0](release-notes-1-0.md) - February 2019 - * Peer-to-peer metadata exchange - - -## Future Releases - -Our master branch is currently taking code for all future releases. -Many of the features are large and the teams integrate code for -partial function as soon as it is stable and has no impact on released function. -So you will see support for much more function than is officially released. -This way you can monitor and feedback on future items as they are developed. - -The [Road map for Egeria](../open-metadata-publication/website/roadmap) -describes the end vision for Egeria and our current status. - - -## Reporting issues - -If you discover an issue in the release you are using, we recommend -first upgrading to the latest available release. If this does not -resolve the problem, please raise a new -[git issue](https://github.com/odpi/egeria). - -You can also follow our discussions by joining the LF AI & Data Foundation Slack team. -Sign up at https://slack.lfai.foundation/ & join the -`egeria-discussions` channel. - - - - - - - - - - - - - - - - - - - - - - - - - - +Follow [this link](https://odpi.github.io/egeria-docs/release-notes/overview/) to read the release notes for all releases. +Release notes are no longer maintained within the source tree, and can now be found in the official [Egeria Documentation](https://odpi.github.io/egeria-docs) ---- License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. +Copyright Contributors to the Egeria project. diff --git a/release-notes/release-notes-1-0.md b/release-notes/release-notes-1-0.md deleted file mode 100644 index 3763ed95b68..00000000000 --- a/release-notes/release-notes-1-0.md +++ /dev/null @@ -1,38 +0,0 @@ - - - - -# Release 1.0 (February 2019) - -Release 1.0 provides the open metadata integration and exchange between -metadata repositories: - -* The [Open Connector Framework (OCF)](../open-metadata-implementation/frameworks/open-connector-framework) - provides standard interfaces for implementing connectors. These are used - to access the data stored in [Assets](../open-metadata-implementation/access-services/docs/concepts/assets) - and to plug in platform capabilities into the Open Metadata Repository Services (OMRS). - -* The implementation of the [Open Metadata Repository Services (OMRS)](../open-metadata-implementation/repository-services). - The repository services provide support for the [open metadata types](../open-metadata-publication/website/open-metadata-types), - the interfaces used by a repository technology the wants to support the - open metadata protocols, the event management for open metadata replication - and the cohort registration and management. - - The repository services can be used as embeddable libraries - in technologies that wish to participate in an - [open metadata repository cohort](../open-metadata-implementation/repository-services/docs/open-metadata-repository-cohort.md). - - -## Egeria Implementation Status at Release 1.0 - -![Egeria Implementation Status](../open-metadata-publication/website/roadmap/functional-organization-showing-implementation-status-for-1.5.png#pagewidth) - - Link to Egeria's [Roadmap](../open-metadata-publication/website/roadmap) for more details about the - Open Metadata and Governance vision, strategy and content. - ----- - * Return to [Release Notes](.) - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. \ No newline at end of file diff --git a/release-notes/release-notes-1-1.md b/release-notes/release-notes-1-1.md deleted file mode 100644 index 24380b1e0c6..00000000000 --- a/release-notes/release-notes-1-1.md +++ /dev/null @@ -1,68 +0,0 @@ - - - -# Release 1.1 (November 2019) - -Release 1.1 focuses on establishing a secure, multi-tenant platform for -metadata servers and governance servers. -There is also a new JanusGraph based metadata repository. - -Below are the highlights: - -* A [persistent metadata repository](../open-metadata-implementation/adapters/open-connectors/repository-services-connectors/open-metadata-collection-store-connectors/graph-repository-connector) based on JanusGraph. - -* A multi-tenant [OMAG Server Platform](../open-metadata-publication/website/omag-server) - that is able to host one to many metadata servers and/or governance servers. - This platform supports APIs to administer servers, start and stop servers and query their - status. The platform offers a connector to change the store used for configuration - documents and to control who can issue platform API calls. - -* There are now [tutorials](../open-metadata-resources/open-metadata-tutorials) and - [hands-on labs](../open-metadata-resources/open-metadata-labs) demonstrating - the configuring and start up of servers on the OMAG Server Platform. - The aim is to help people to get up and running - with the Egeria technology. In addition, there are both [docker scripts and - Kubernetes helm charts](../open-metadata-resources/open-metadata-deployment) to deploy - the platforms and related technology used in the tutorials, samples and labs. - - + Note that currently we do not push release specific docker containers to dockerhub. If you are using the - docker/kubernetes environments it is recommended to work from the 'master' branch instead of this release. This will - be addressed in a future release. - -* The [Open Metadata Repository Services (OMRS)](../open-metadata-implementation/repository-services) shipped in the [first release](release-notes-1-0.md) - have been enhanced with REST APIs to query the cohorts that a server - is connected to. There are also REST APIs to issue federated queries across - the cohorts that a metadata server is connected to. - -* There is a new user interface to explore the open metadata types. It is called the **Type Explorer**. - -## Code fixes and changes to released function - -* Release 1.1 fixes a problem in the open metadata cohort registration when - there was a metadata server without a local repository. The wrong registration - message was being used which meant that the registration details were not being properly - distributed around the cohort. - -* Release 1.1 changed the type of the AdditionalProperties from a map of String to Object to a map of - String to String in order to match the open metadata types. There is a new property called - ConfigurationProperties which is a map from String to Object. - -* Release 1.1 changed the implementation of the data primitive type from - a Java Date object to a Java Long object. This was to overcome a problem - deserialization dates from JSON to Java. - -## Egeria Implementation Status at Release 1.1 - -![Egeria Implementation Status](../open-metadata-publication/website/roadmap/functional-organization-showing-implementation-status-for-1.1.png#pagewidth) - - Link to Egeria's [Roadmap](../open-metadata-publication/website/roadmap) for more details about the - Open Metadata and Governance vision, strategy and content. - ----- - * Return to [Release Notes](.) - - - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. diff --git a/release-notes/release-notes-1-2.md b/release-notes/release-notes-1-2.md deleted file mode 100644 index 8a6e6766ee7..00000000000 --- a/release-notes/release-notes-1-2.md +++ /dev/null @@ -1,59 +0,0 @@ - - - -# Release 1.2 (December 2019) - -Release 1.2 provides the ability to build an asset catalog, search for assets and also -access the data and function provided by these assets. -It is also possible to group Assets into governance zones to control the -discoverability and visibility of the Assets. - -In addition, we release the Egeria conformance test suite and four -conformant repositories. - -Below are the highlights: - -* A [conformance test suite](../open-metadata-conformance-suite) - that validates implementations of open metadata repository connectors. - In addition we are highlighting the repositories that are conformant. - These are: - * The [JanusGraph metadata repository](../open-metadata-implementation/adapters/open-connectors/repository-services-connectors/open-metadata-collection-store-connectors/graph-repository-connector). - * The [In-memory metadata repository](../open-metadata-implementation/adapters/open-connectors/repository-services-connectors/open-metadata-collection-store-connectors/inmemory-repository-connector) used for testing and demos. - * The [Apache Atlas repository proxy](https://github.com/odpi/egeria-connector-apache-atlas). - * The [IBM Information Governance Catalog repository proxy](https://github.com/odpi/egeria-connector-ibm-information-server). - -* There are new access services to support the cataloging of assets: - * The [Asset Consumer OMAS](../open-metadata-implementation/access-services/asset-consumer) supports the access to both the data and metadata associated with an asset. - * The [Asset Owner OMAS](../open-metadata-implementation/access-services/asset-owner) supports the manual cataloging of new Assets. - - The assets cataloged by these access services can be scoped by governance zones. - -* The metadata servers and future governance servers running on the OMAG Server Platform - support [metadata-centric security](../open-metadata-implementation/common-services/metadata-security) - that is controlled by a connector. This connector can validate access to individual servers, - services, and assets based on the identity of the caller and the service or asset - they wish to access. - -* The [Open Metadata Repository Services (OMRS)](../open-metadata-implementation/repository-services) - have been enhanced to support support dynamic types and type patching. - There is also function to load archives of metadata instances. - -* There are [tutorials](../open-metadata-resources/open-metadata-tutorials), - [hands-on labs](../open-metadata-resources/open-metadata-labs) and - [samples](../open-metadata-resources/open-metadata-samples) demonstrating - the new Asset cataloging capabilities. - -## Egeria Implementation Status at Release 1.2 - -![Egeria Implementation Status](../open-metadata-publication/website/roadmap/functional-organization-showing-implementation-status-for-1.2.png#pagewidth) - - Link to Egeria's [Roadmap](../open-metadata-publication/website/roadmap) for more details about the - Open Metadata and Governance vision, strategy and content. - ----- - * Return to [Release Notes](.) - - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. \ No newline at end of file diff --git a/release-notes/release-notes-1-3.md b/release-notes/release-notes-1-3.md deleted file mode 100644 index 074fe4677c1..00000000000 --- a/release-notes/release-notes-1-3.md +++ /dev/null @@ -1,67 +0,0 @@ - - - -# Release 1.3 (January 2020) - -Release 1.3 focuses on the support for open metadata archives, and formal versioning of open metadata types. -It includes much of the ground-work for -supporting design lineage and the detection and management of duplicate assets but that function is officially -released in [1.4](release-notes-1-4.md). - -Below are the highlights of the 1.3 release: - -* The [hands-on labs](../open-metadata-resources/open-metadata-labs) have been updated to provide - reusable Python functions for working with Egeria. - -* The management of open metadata types includes formal versioning and patching of types. - This makes it clearer where additions and updates are being made to the open metadata types. - See [open metadata types archive](../open-metadata-resources/open-metadata-archives/open-metadata-types). - -* There are the following changes to the open metadata types: - * The [EmbeddedConnection](../open-metadata-publication/website/open-metadata-types/0205-Connection-Linkage.md) has a new property called `position`. - * The [OpenDiscoveryAnalysisReport](../open-metadata-publication/website/open-metadata-types/0605-Open-Discovery-Analysis-Reports.md) has a new property called `discoveryRequestStep`. - * There is a new collection of [Annotations](../open-metadata-publication/website/open-metadata-types/0655-Asset-Deduplication.md) for recording suspected duplicates and divergent values in acknowledged duplicates. - This is to support the asset deduplication work scheduled for the next release. - -* There are new [open metadata archive](../open-metadata-resources/open-metadata-archives) utilities for creating your own open metadata archives. - See the [open connector archives](../open-metadata-resources/open-metadata-archives/open-connector-archives) and - [design model archives](../open-metadata-resources/open-metadata-archives/design-model-archives). - -* The Conformance Suite Repository Workbench is now at Version 1.1, with the following enhancements: - - * Tests for relationship searches have moved into a separate, optional RELATIONSHIP_SEARCH profile. A repository connector can be fully conformant with the (mandatory) METADATA_SHARING profile despite not supporting the `findRelationshipsByProperty` or `findRelationshipsByPropertyValue` methods. - - * The ADVANCED_SEARCH profile is now divided into two profiles: ENTITY_ADVANCED _SEARCH and RELATIONSHIP_ADVANCED_SEARCH. They are both optional profiles. A repository connector can be fully conformant with the ENTITY_ADVANCED _SEARCH profile, despite not supporting either of the RELATIONSHIP_SEARCH or RELATIONSHIP_ADVANCED_SEARCH profiles. - - * New test verify the correct handling of mappingProperties in the InstanceAuditHeader. - - * The tests for 're-home' of a reference copy now use an instance mastered by a third (virtual) repository rather than the CTS Server's repository. - - * Type verification of relationship end types now cater for connectors that do not support all the supertypes of an entity type. - - * Search result checking is improved. - - * The CTS notebook (under open-metadata-resources/open-metadata-labs) has been enhanced: - - * The Conformance Profile Results cell there is additional reporting for the new profiles - - * A new cell "Polling for Status" shows how to determine whether the repository-workbench has completed its synchronous tests. The new API it demonstrates could be used to support automated testing - - * A new cell "Monitoring Progress" show how progress can be monitored based on workbench results retrieved during a test run. - - * Improvements to HTTP response checking and reporting of errors - -## Egeria Implementation Status at Release 1.3 - -![Egeria Implementation Status](../open-metadata-publication/website/roadmap/functional-organization-showing-implementation-status-for-1.3.png#pagewidth) - - Link to Egeria's [Roadmap](../open-metadata-publication/website/roadmap) for more details about the - Open Metadata and Governance vision, strategy and content. - ----- - * Return to [Release Notes](.) - - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. \ No newline at end of file diff --git a/release-notes/release-notes-1-4.md b/release-notes/release-notes-1-4.md deleted file mode 100644 index ff7a6979502..00000000000 --- a/release-notes/release-notes-1-4.md +++ /dev/null @@ -1,21 +0,0 @@ - - - -# Release 1.4 (February 2020) - -Release 1.4 focused on bug fixes and documentation. - -## Egeria Implementation Status at Release 1.4 - -![Egeria Implementation Status](../open-metadata-publication/website/roadmap/functional-organization-showing-implementation-status-for-1.4.png#pagewidth) - - Link to Egeria's [Roadmap](../open-metadata-publication/website/roadmap) for more details about the - Open Metadata and Governance vision, strategy and content. - ----- - * Return to [Release Notes](.) - - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. \ No newline at end of file diff --git a/release-notes/release-notes-1-5.md b/release-notes/release-notes-1-5.md deleted file mode 100644 index 381b2bccdcb..00000000000 --- a/release-notes/release-notes-1-5.md +++ /dev/null @@ -1,47 +0,0 @@ - - - -# Release 1.5 (March 2020) - -Release 1.5 delivers the automatic metadata discovery of duplicate assets. -Additional, in Tech Preview, Data Engine OMAS, and a data engine proxy server. - -## Released Components - -* The first governance server is released: - * The [Discovery Server](../open-metadata-implementation/frameworks/open-discovery-framework/docs/discovery-server.md) supports the scanning of assets and the notification when duplicate suspects are detected. - - This server is supported by: - * The [Discovery Engine OMAS](../open-metadata-implementation/access-services/discovery-engine) supports the detection, recording and notification of exceptions and duplicate suspects. - - * The [Open Discovery Framework (ODF)](../open-metadata-implementation/frameworks/open-discovery-framework) is now defined and - implemented to support the interfaces for automated discovery services. - It complements the [Open Connector Framework (OCF)](../open-metadata-implementation/frameworks/open-connector-framework) delivered in release 1.0. - -* There are new [tutorials](../open-metadata-resources/open-metadata-tutorials), - [hands-on labs](../open-metadata-resources/open-metadata-labs) and - [samples](../open-metadata-resources/open-metadata-samples) demonstrating - the new de-duplication detection features. - -## Technical Previews - - * The [Data Engine OMAS](../open-metadata-implementation/access-services/data-engine) supports the processing of notifications from data engines such as ETL platforms in order to catalog information about the data movement, transformation and copying they are engaged in. - - * The [Data Engine Proxy Server](../open-metadata-implementation/governance-servers/data-engine-proxy-services) is also included in the technical preview. - It supports the polling of data engines such as ETL platforms - in order to catalog information about the data movement, transformation and copying they are engaged in. - It calls the Data Engine OMAS. - -## Egeria Implementation Status at Release 1.5 - -![Egeria Implementation Status](../open-metadata-publication/website/roadmap/functional-organization-showing-implementation-status-for-1.5.png#pagewidth) - - Link to Egeria's [Roadmap](../open-metadata-publication/website/roadmap) for more details about the - Open Metadata and Governance vision, strategy and content. - ----- - * Return to [Release Notes](.) - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. diff --git a/release-notes/release-notes-1-6.md b/release-notes/release-notes-1-6.md deleted file mode 100644 index 894be323dbf..00000000000 --- a/release-notes/release-notes-1-6.md +++ /dev/null @@ -1,39 +0,0 @@ - - - -# Release 1.6 (April 2020) - -Release 1.6 adds support for: - * Audit Log Framework (ALF) technical preview - * Repository Explorer (REX) - -Below are the highlights: - -* There is a new framework: - * The [Audit Log Framework](../open-metadata-implementation/frameworks/audit-log-framework) (ALF) provides interface definitions and classes to enable connectors to support natural language enabled diagnostics such as exception messages and audit log messages. - -* There is a new user interface module: - * The [Repository Explorer](../open-metadata-implementation/user-interfaces/ui-chassis/ui-chassis-spring/docs/RepositoryExplorer/RepositoryExplorerGuide.md) (Rex) can help you explore and visualize the metadata in a repository. It retrieves entities and relationships from the repository and displays them. A details panel also shows the properties and other information about an object. Each entity or relationship is added to a network diagram, which shows how they are connected. - -* The Swagger-based API documentation for the Egeria server chassis has been reorganized to align with our modules structure & to provide links into our other documentation which also will clarify if the module is released, in Tech Preview, or still in development. The docs can be found at `https://:/swagger-ui.htm`. Further enhancements will follow in future releases. - -* Many dependencies have been updated including: - * Kafka client upgraded to 2.4.1 - * Spring updated to 5.2.4, spring boot to 2.2.5 & other spring components accordingly. - - For a full list refer to the git commit logs. - -## Egeria Implementation Status at Release 1.6 - -![Egeria Implementation Status](../open-metadata-publication/website/roadmap/functional-organization-showing-implementation-status-for-1.6.png#pagewidth) - - Link to Egeria's [Roadmap](../open-metadata-publication/website/roadmap) for more details about the - Open Metadata and Governance vision, strategy and content. - ----- - * Return to [Release Notes](.) - - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. diff --git a/release-notes/release-notes-1-7.md b/release-notes/release-notes-1-7.md deleted file mode 100644 index b52cb48ddf1..00000000000 --- a/release-notes/release-notes-1-7.md +++ /dev/null @@ -1,37 +0,0 @@ - - - -# Release 1.7 (May 2020) - -Release 1.7 contains many bug fixes & preparatory development work for future new features. - -Below are the highlights: - -* There is support for loading standard glossaries and design models coded in OWL/JSON-LD into - the open metadata ecosystem. The input file is converted to an - [Open Metadata Archive](../open-metadata-resources/open-metadata-archives) which can be loaded directly - into a metadata server. - -* Many dependencies have been updated including: - * Kafka client upgraded to 2.5 - * Spring security updated to 5.3.1, spring boot,data to 2.2.6, spring to 5.2.5 - - For a full list refer to the git commit logs. - -## Known Issues - -* (https://github.com/odpi/egeria/issues/2935)[2935] - Governance Engine OMAS reports exception when entities added -* (https://github.com/odpi/egeria/issues/3005)[3005] - Occasional failure in 'Building a Data Catalog' notebook - -## Egeria Implementation Status at Release 1.7 - -![Egeria Implementation Status](../open-metadata-publication/website/roadmap/functional-organization-showing-implementation-status-for-1.7.png#pagewidth) - - Link to Egeria's [Roadmap](../open-metadata-publication/website/roadmap) for more details about the - Open Metadata and Governance vision, strategy and content. - ----- - * Return to [Release Notes](.) - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), diff --git a/release-notes/release-notes-1-8.md b/release-notes/release-notes-1-8.md deleted file mode 100644 index 40cfde507ba..00000000000 --- a/release-notes/release-notes-1-8.md +++ /dev/null @@ -1,33 +0,0 @@ - - - -# Release 1.8 (June 2020) - -Below are the highlights of Release 1.8: - -* New tutorial information has been added in the form of the [Egeria Dojo](../open-metadata-resources/open-metadata-tutorials/egeria-dojo/README.md) -* Usability & Capability improvements to [Repository Explorer](../open-metadata-implementation/user-interfaces/ui-chassis/ui-chassis-spring/docs/RepositoryExplorer/RepositoryExplorerGuide.md) -* Samples & utilities are now also packaged into jars with dependencies to make them easier to use (java -jar) -* Connections to kafka will now retry to improve availability. See 'Bring up Issues' in the [connector documentation](../open-metadata-implementation/adapters/open-connectors/event-bus-connectors/open-metadata-topic-connectors/kafka-open-metadata-topic-connector/README.md)\ - -* New dependencies has been included: - * [Spring Boot Actuator](../open-metadata-implementation/server-chassis/server-chassis-spring/README.md) - Provides features to help you monitor and manage your application when you push it to production - * micrometer-registry-prometheus - Exposes metrics in a format that can be scraped by a Prometheus server - -* Many dependencies have been updated. The most relevant include: - * Spring has been updated to 5.2.6 - * Spring Boot, Spring Security, Spring Security, Spring Data have been updated to 2.3.0 - -## Egeria Implementation Status at Release 1.8 - -![Egeria Implementation Status](../open-metadata-publication/website/roadmap/functional-organization-showing-implementation-status-for-1.8.png#pagewidth) - - Link to Egeria's [Roadmap](../open-metadata-publication/website/roadmap) for more details about the - Open Metadata and Governance vision, strategy and content. - ----- - * Return to [Release Notes](.) - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. diff --git a/release-notes/release-notes-2-0.md b/release-notes/release-notes-2-0.md deleted file mode 100644 index 4d9226e055e..00000000000 --- a/release-notes/release-notes-2-0.md +++ /dev/null @@ -1,30 +0,0 @@ - - - -# Release 2.0 (July 2020) - -Release 2.0 adds support for: - -- Encryption by default (HTTPS/SSL, encrypted configuration file) -- bug fixes -- dependency updates - -Below are the highlights: - -- The Egeria server chassis default URL is now https://localhost:9443 - the server now listens on port 9443 and supports https only. All clients have been updated accordingly. At this point SSL certificate validation is disabled. This will be enabled in a future release. -- Docker containers, docker-compose scripts, kubernetes deployments have all been updated to use https accordingly. -- The [Encrypted Configuration File Store Connector](../open-metadata-implementation/adapters/open-connectors/configuration-store-connectors/configuration-encrypted-file-store-connector/README.md) is now used by default to ensure security of sensitive configuration details like credentials. - -## Egeria Implementation Status at Release 2.0 - - ![Egeria Implementation Status](../open-metadata-publication/website/roadmap/functional-organization-showing-implementation-status-for-2.0.png#pagewidth) - - Link to Egeria's [Roadmap](../open-metadata-publication/website/roadmap) for more details about the - Open Metadata and Governance vision, strategy and content. - ----- - * Return to [Release Notes](.) - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. diff --git a/release-notes/release-notes-2-1.md b/release-notes/release-notes-2-1.md deleted file mode 100644 index eb70e56a99f..00000000000 --- a/release-notes/release-notes-2-1.md +++ /dev/null @@ -1,31 +0,0 @@ - - - -# Release 2.1 (August 2020) - -Release 2.1 primarily contains bug fixes and preparatory work for future capabilities. - -A full list of changes can be seen [by comparing on github](https://github.com/odpi/egeria/compare/egeria-release-2.0...egeria-release-2.1) . - -The highlights include: - -* Bug fixes - - Subject Area OMAS has added testing including automated FVTs, code cleanup & bug fixes - - User Interface fixes & usability improvements -* Dependency Updates - - Spring updated to 5.2.8 - - additional dependencies to remain current - -## Egeria Implementation Status at Release 2.1 - - ![Egeria Implementation Status](../open-metadata-publication/website/roadmap/functional-organization-showing-implementation-status-for-2.1.png#pagewidth) - - Link to Egeria's [Roadmap](../open-metadata-publication/website/roadmap) for more details about the - Open Metadata and Governance vision, strategy and content. - ----- - * Return to [Release Notes](.) - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. diff --git a/release-notes/release-notes-2-10.md b/release-notes/release-notes-2-10.md deleted file mode 100644 index 03ae68bc98d..00000000000 --- a/release-notes/release-notes-2-10.md +++ /dev/null @@ -1,173 +0,0 @@ - - - -# Release 2.10 (June 2021) - -Release 2.10 adds: -* New and improved open metadata types for governance -* New API for Governance Program OMAS - -See also an important notice about removal of Java 8 support in a future release. - -Details of these and other changes are in the sections that follow. - -## Description of Changes - -### Metadata Types - -* Correction to the **Campaign** classification. - - The Campaign classification is supposed to connect to a **Project** entity to indicate the project - is a grouping of a series of projects designed to achieve a large goal. Unfortunately it was coded to connect to - the **Collection** entity. In 2.10, the Campaign classification has been changed to attach to **Referenceable** - to allow it to be connected to **Project** without affecting backward compatibility. - - See new type description in model [0130](../open-metadata-publication/website/open-metadata-types/0130-Projects.md). - -* Extension of the **UsedInContext** relationship. - - The UsedInContext relationship linked two **GlossaryTerm** entities together to show that one glossary term described - the context in which the other was valid. This relationship has been updated to allow the end that describes - the context to be a **Referenceable**. This means that the context where glossary terms are valid can be expressed - as elements such as projects, business capabilities, parts of an organization, subject areas, zones and many more. - - See new type description in model [0360](../open-metadata-publication/website/open-metadata-types/0360-Contexts.md). - -* Allowing ownership to be expressed as a **PersonRole**. - - Issue [#5104](https://github.com/odpi/egeria/issues/5104) described the problem that the - governance open metadata types allowed owners to be expressed as **PersonalProfile** or **UserIdentity** - entities. - The properties did not identify if the owner was identified as a GUID or as a qualifiedName. - In 2.10, a new classification for expressing ownership called, not surprisingly, **Ownership**, - was introduced which allows and type and property name for the owner to be specified with the - owner's identifier. The types for entities such as **GovernanceActionType** and **IncidentReport** that include - ownership properties in them have been updated to deprecate these properties in favor of using - the Ownership classification. The **AssetOwnership** classification is also deprecated. - - See new type description in model [0445](../open-metadata-publication/website/open-metadata-types/0445-Governance-Roles.md). - -* Update to **Certification** relationship. - - The Certification relationship supports the identification of the people involved in the certification of an element. 2.10 adds - new attributes to specify the type and property names of the identifier used to identify these people. - This is consistent with the new **Ownership** classification. - - See new type descriptions in model [0482](../open-metadata-publication/website/open-metadata-types/0482-Certifications.md). - -* Update to **License** relationship. - - The License relationship supports the identification of the people involved in the licencing of an element. 2.10 adds - new attributes to specify the type and property names of the identifier used to identify these people. - This is consistent with the new **Ownership** classification. - - See new type descriptions in model [0481](../open-metadata-publication/website/open-metadata-types/0481-Licenses.md). - -* Governance role updates. - - The **GovernanceOfficer** entity now inherits from **GovernanceRole** rather than **PersonRole**. - This means it is just another governance role that can be linked with **GovernanceResponsibility** - definitions. In addition there are new types for different types of owners. These are **ComponentOwner** - and **DataItemOwner**. - - See new type descriptions in model [0445](../open-metadata-publication/website/open-metadata-types/0445-Governance-Roles.md). - -* Extend the **GovernanceResponsibilityAssignment** - - The GovernanceResponsibilityAssignment relationship identifies the responsibilities for a particular role. - It used to link to a **GovernanceRole** and in 2.10, it has been updated to link to a **PersonRole**. This means - that governance responsibilities can be added to any role, such as **ProjectManager** and **CommunityMember**, - rather than just specialized governance roles. - - See new type descriptions in model [0445](../open-metadata-publication/website/open-metadata-types/0445-Governance-Roles.md). - -* Deprecating the **domain** attribute in various governance types. - - The domain attribute is typed by the **GovernanceDomain** enum. This provides a fixed list of governance domains. - An extensible mechanism for expressing the governance domain was added in release 2.4 using the - **GovernanceDomainDescription** entity and the **domainIdentifier** attribute. - In this release, the use of **domain** is deprecated in **GovernanceDefinition**, - **GovernanceZone**, **SubjectAreaDefinition**, **GovernanceMetric**, **GovernanceRole** and **GovernanceOfficer**. - - See new type descriptions in model [0401](../open-metadata-publication/website/open-metadata-types/0401-Governance-Definitions.md). - -* Extensions to governance drivers. - - There are now new subtypes of the **GovernanceDriver** entity called **RegulationArticle** and - **BusinessImperative**. It is also possible to link governance drivers using the new - **GovernanceDriverLink** relationship. - - See new type descriptions in model [0405](../open-metadata-publication/website/open-metadata-types/0405-Governance-Drivers.md). - -* Update to **AssetOrigin** classification. - - The AssetOrigin classification supports the identification of the origin of an asset. This can be in terms of the - organization, business capability and other values. 2.10 adds new attributes to identify if the - organization or business capability is identified by its GUID or qualifiedName. - - See new type descriptions in model [0440](../open-metadata-publication/website/open-metadata-types/0440-Organizational-Controls.md). - -* Improve IncidentClassifiers. - - If is possible to define multiple sets of **IncidentClassifier** values that can be - used on **IncidentReport** entities to help to group and prioritize them. The IncidentClassifier entity - now inherits from **Referencable** and there is a new classification called **IncidentClassifierSet** - to mark a **Collection** entity as containing IncidentClassifier definitions. - - See new type descriptions in model [0470](../open-metadata-publication/website/open-metadata-types/0470-Incident-Reporting.md). - -* Deprecation of **ResponsibilityStaffContact**. - - The ResponsibilityStaffContact relationship has been deprecated in favor of the - **GovernanceResponsibilityAssignment** relationship. - -### New Services for Governance Program OMAS - -The APIs defined for Governance Program OMAS have been updated to reflect the changes -to the open metadata types described above. The APIs and client implementations -are in place. The server-side is coming in a future release. - -### Bug fixes and other updates - -* Additional Bug Fixes - - * Cascaded deletes for entities grouped using the **Anchors** classification - are now deleting the correct entities. Prior to this release, some entities were - missed and others were deleted incorrectly. - -* Dependency Updates - -For details on both see the commit history in GitHub. - -## Known Issues - -* It is recommended to use a chromium-based browser such as Google Chrome or Microsoft Edge, or Apple Safari for the Egeria React UI. Some parts of the UI experience such as Dino currently experience problems with Firefox. See [odpi/egeria-react-ui#96](https://github.com/odpi/egeria-react-ui/issues/96) . -* When running the 'Understanding Platform Services' lab, ensure you run the 'egeria-service-config' notebook first and do not restart the python kernel before running this lab. See [#4842](https://github.com/odpi/egeria/issues/4842) . -* When logging in to the react UI for the coco pharma lab demo, ensure to use http://myhost.mydomain/coco/login as otherwise the login will not work. see [odpi/egeria#41](https://github.com/odpi/egeria-react-ui/issues/41) -* A few further bugs are noted at https://github.com/odpi/egeria/issues/5211#issuecomment-850321243 including for samples and UI. - -## Removal of Java 8 Support - -Egeria will drop support for Java 8 in a forthcoming release within the next -few months. We have been building and testing with Java 11 for over a year -and will move to build all packages with Java 11, and require Java 11. At this -point Java 8 will no longer be supported for new releases. - -# Egeria Implementation Status at Release 2.10 - -![Egeria Implementation Status](../open-metadata-publication/website/roadmap/functional-organization-showing-implementation-status-for-2.10.png#pagewidth) - -Link to Egeria's [Roadmap](../open-metadata-publication/website/roadmap) for more details about the -Open Metadata and Governance vision, strategy and content. - - -# Further Help and Support - -See the [Community Guide](../Community-Guide.md). - ----- -* Return to [Release Notes](.) - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. diff --git a/release-notes/release-notes-2-11.md b/release-notes/release-notes-2-11.md deleted file mode 100644 index 19dc5a14b6f..00000000000 --- a/release-notes/release-notes-2-11.md +++ /dev/null @@ -1,178 +0,0 @@ - - - -# Release 2.11 (July 2021) - -Release 2.11 adds: -* New option to have multiple topics for a cohort. -* New support for automatic extraction of metadata from event brokers and API managers. - -Details of these and other changes are in the sections that follow. - -## Description of Changes - -### New option to have multiple topics for a cohort - -An [open metadata repository cohort](../open-metadata-implementation/admin-services/docs/concepts/cohort-member.md) -uses three types of events to enable peer-to-peer sharing of metadata. -In previous releases, these events have all been exchanged through a single -event topic. Release 2.11 provides the option for a cohort to -use a dedicated topic for each type of event. -This improves the time to register a new member in the cohort -and allows multiple instances of a [Metadata Server](../open-metadata-implementation/admin-services/docs/concepts/metadata-server.md) -or a [Metadata Access Point](../open-metadata-implementation/admin-services/docs/concepts/metadata-access-point.md) -to access the cohort. - -Details of these new options can be found in the -[Administration Guide](../open-metadata-implementation/admin-services/docs/user/configuring-registration-to-a-cohort.md). - -### Extensions to the support for Data Managers - -The [Data Manager OMAS](../open-metadata-implementation/access-services/data-manager) -has been extended to support the capture of metadata from -Event Brokers such as Apache Kafka and API Managers -such as an API Gateway. - -There are two new associated -Open Metadata Integration Services (OMISs) -to support integration connectors -that extract metadata from these types of data managers: - -* [Topic Integrator OMIS](../open-metadata-implementation/integration-services/topic-integrator) -supports integration connectors extracting metadata -from Event Brokers. - -* [API Integrator OMIS](../open-metadata-implementation/integration-services/api-integrator) -supports integration connectors extracting API information from API managers. - -For more information on the use of the Data Manager OMAS with -these integration services, see the -[Data Manager Integration](../open-metadata-publication/website/solutions/data-manager-integration) -solution. - -### Open Metadata Types - -The following changes have been made to the open metadata types: - -* Deprecation of properties in **Asset** - - A number of properties that where originally defined in Asset were moved to - classifications to allow them to be managed independently of the original asset. - This occurred before the TypeDefPatch support was in place and so these properties - were not marked as deprecated at that time. In 2.11, this deprecation has now been - officially recorded in the Asset TypeDef. The properties are: - - * **owner** - now captured in the [Ownership](../open-metadata-publication/website/open-metadata-types/0445-Governance-Roles.md) classification - * **ownerType** - also captured in the Ownership classification - * **zoneMembership** - now captured in the [AssetZoneMembership](../open-metadata-publication/website/open-metadata-types/0424-Governance-Zones.md) classification - * **latestChange** - now captures]d in the [LatestChange](../open-metadata-publication/website/open-metadata-types/0011-Managing-Referenceables.md) classification - - See new type description in model [0010](../open-metadata-publication/website/open-metadata-types/0010-Base-Model.md). - -* New types for **APIManager** and **EventBroker**. - These types inherit from [SoftwareServerCapability](../open-metadata-publication/website/open-metadata-types/0042-Software-Server-Capabilities.md). - These are used in the new Data Manager OMAS APIs. - - See new type descriptions in model [0050](../open-metadata-publication/website/open-metadata-types/0050-Applications-and-Processes.md). - -* New type for a **Threat** governance driver and a relationship to connect - a [GovernanceDefinition](../open-metadata-publication/website/open-metadata-types/0401-Governance-Definitions.md) - with a metadata element that defines the scope where it is applicable. - - See new type descriptions in models [0401](../open-metadata-publication/website/open-metadata-types/0401-Governance-Definitions.md) and - [0405](../open-metadata-publication/website/open-metadata-types/0405-Governance-Drivers.md). - -* Deprecated type called **TabularColumnType** because it restricts tabular columns to primitive types when it could be a literal for example. - Also a new subtype for **TabularColumn** called **TabularFileColumn** is added to be able to distinguish between tabular columns from - files and **RelationalColumn** (which also inherits from **TabularColumn**). - - See type descriptions in model [0530](../open-metadata-publication/website/open-metadata-types/0530-Tabular-Schemas.md). - -* Deprecated types called **SimpleDocumentType**, **StructDocumentType** and **MapDocumentType** because they - offer little value since the type is typically stored in the **TypeEmbeddedAttribute** classification. - This change makes the document schemas consistent with other types of schema. - - See type descriptions in model [0531](../open-metadata-publication/website/open-metadata-types/0531-Document-Schemas.md). - -* Updated supertype of **RelationalTableType** to inherit from **ComplexSchemaType** rather than **TabularColumnType** - since TabularColumnType is now deprecated. - - See type descriptions in model [0534](../open-metadata-publication/website/open-metadata-types/0534-Relational-Schemas.md). - -* New type called **EventTypeList** to allow a list of event types to be associated with a topic - and a specific subtype of [SchemaAttribute](../open-metadata-publication/website/open-metadata-types/0505-Schema-Attributes.md) - for an attribute in an event type to make it easier to search for - data fields that are exclusively found in events. - - See new type descriptions in model [0535](../open-metadata-publication/website/open-metadata-types/0535-Event-Schemas.md). - -* New types for **APIParameter** and **APIParameter** to allow the capture of properties - related to the API's treatment of the parameters. There are also - properties for **APIOperation**. - - See new type descriptions in model [0536](../open-metadata-publication/website/open-metadata-types/0536-API-Schemas.md). - -* New types for **DisplayDataSchemaType**, **DisplayDataContainer**, **DisplayDataField**, **QuerySchemaType**, - **QueryDataContainer** and **QueryDataField** to allow the capture of properties related to the display of data to end users. - - See new type descriptions in model [0537](../open-metadata-publication/website/open-metadata-types/0537-Display-Schemas.md). - -* Deprecated **TermISATypeOFRelationship** because the ends are defined the wrong way round. When visualizing - end1 should point to end2. This relationship incorrectly has the super type pointing to the subtype. Use the new - **IsATypeOfRelationship** instead to represent an is-a-type-of relationship between two spine objects. - - See new type descriptions in model [0380](../open-metadata-publication/website/open-metadata-types/0380-Spine-Objects.md). - -### Bug fixes and other updates - -* Additional Bug Fixes -* Dependency Updates - -For details on both see the commit history in GitHub. - -## Removed Functionality - -The following capabilities have now been removed (they were previously deprecated and/or in not in 'Released' status): -* Information View OMAS. -* Virtualization Services & associated connectors. -* Security Officer Services, Security sync services & associated connectors including for Apache Ranger. -* Gaian database connector & additional authentication/impersonation support. - -Much of the above capability can be implemented via [Integration Services](https://egeria.odpi.org/open-metadata-implementation/integration-services/) . -Hadoop specifics may be developed in the future within the [Egeria Hadoop](https://github.com/odpi/egeria-connector-hadoop-ecosystem) GitHub repository. - -For more details of this change see [#5314](https://github.com/odpi/egeria/pull/5314). - -Similarly, the following services have been deleted: - -* Data Platform Services and Data Platform OMAS. For more details see [#5344](https://github.com/odpi/egeria/pull/5344) . -* Data Platform capabilities are already available in [Database Integrator](https://egeria.odpi.org/open-metadata-implementation/integration-services/database-integrator/) and [Files Integrator](https://egeria.odpi.org/open-metadata-implementation/integration-services/files-integrator/) already part of Integration Services. -* Cassandra connectors: cassandra-data-store-connector and cassandra-metadata-extractor-connector will be introduced back -in the [Data Connectors](https://github.com/odpi/egeria-data-connectors) GitHub repository. For more information see [#2671](https://github.com/odpi/egeria/issues/2671) . - -## Known Issues - -* It is recommended to use a chromium-based browser such as Google Chrome or Microsoft Edge, or Apple Safari for the Egeria React UI. Some parts of the UI experience such as Dino currently experience problems with Firefox. See [odpi/egeria-react-ui#96](https://github.com/odpi/egeria-react-ui/issues/96) . - -## Special note on Java Support - -* This is expected to be the last release supporting Java 8. The next release will commence the 3.x series of releases and require Java 11. - -# Egeria Implementation Status at Release 2.11 - -![Egeria Implementation Status](../open-metadata-publication/website/roadmap/functional-organization-showing-implementation-status-for-2.11.png#pagewidth) - -Link to Egeria's [Roadmap](../open-metadata-publication/website/roadmap) for more details about the -Open Metadata and Governance vision, strategy and content. - - -# Further Help and Support - -See the [Community Guide](../Community-Guide.md). - ----- -* Return to [Release Notes](.) - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. diff --git a/release-notes/release-notes-2-2.md b/release-notes/release-notes-2-2.md deleted file mode 100644 index 2d523b25a97..00000000000 --- a/release-notes/release-notes-2-2.md +++ /dev/null @@ -1,34 +0,0 @@ - - - -# Release 2.2 (September 2020) - -Below are the highlights of this release: - - * Additional connectors are now placed in our assembly under server/lib without dependencies. If you need to use a connector that requires additional dependencies that are not already part of the server chassis, you will need to add those libraries here. - * The [docker](https://hub.docker.com/repository/docker/odpi/egeria/tags?page=1&name=2.2) image has been updated to use a later openjdk alpine base image due to incompatibilities with our JanusGraph support in the old images for java 8. - * In the VDC chart, 2 new values have been added, 'ibmigc.connectorversion' and 'atlas.connectorversion'. In this release these are set to use the 2.1 connectors, since the connectors run to a different release cycle than the main Egeria code. Once new connectors are released you can update these values to get the latest connectors - * Further code to support lineage has been added, but in this release it remains in development and is not yet ready for use in production. - * User interface improvements. - * Ongoing bug fixes and refactoring especially in subject-area omas. - -## Known Issues - * In the VDC helm chart, the Apache Atlas initialization job fails to complete. This is due to a problem with the Apache Atlas server and Apache SOLR. See https://github.com/odpi/egeria/issues/3587 for more information. - -## Dependencies - * Spring Boot is updated to 2.3.3. - -## Egeria Implementation Status at Release 2.2 - - ![Egeria Implementation Status](../open-metadata-publication/website/roadmap/functional-organization-showing-implementation-status-for-2.2.png#pagewidth) - - Link to Egeria's [Roadmap](../open-metadata-publication/website/roadmap) for more details about the - Open Metadata and Governance vision, strategy and content. - ----- - * Return to [Release Notes](.) - - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. diff --git a/release-notes/release-notes-2-3.md b/release-notes/release-notes-2-3.md deleted file mode 100644 index ae564ee0609..00000000000 --- a/release-notes/release-notes-2-3.md +++ /dev/null @@ -1,46 +0,0 @@ - - - -# Release 2.3 (October 2020) - -## New capabilities & Major changes - * A new Presentation Server User interface has been added, making use of [React](https://reactjs.org/) & [Carbon](https://www.carbondesignsystem.com/) - - Presentation Server is still in development - - For developers not contributing to Presentation Server, running in a container under Kubernetes or docker-compose is the easiest way to get started - - See the last section of the [Presentation Server README](https://github.com/odpi/egeria/tree/egeria-release-2.3/open-metadata-implementation/user-interfaces/presentation-server) for instructions on running Presentation Server - - For contributors, The [Presentation Server README](https://github.com/odpi/egeria/tree/egeria-release-2.3/open-metadata-implementation/user-interfaces/presentation-server) also documents 'Configuring the Presentation Server' - this is done automatically in our k8s/compose environment. However - if doing this manually note (4th point) that the environment variable is called `EGERIA_PRESENTATIONSERVER_SERVER_` where - the `` is the tenant's serverName.. The examples in the document are correct. - * The Dino User Interface for presentation server now allows an Egeria operations user to display a graph and details of Egeria resources including - platforms, servers, services and cohort memberships. - * Type Explorer & Repository Explorer, previously found in the Polymer based UI, are now available - in Presentation Server. - * Raise a github issue or Contact the Egeria team via slack at slack.odpi.com if you experience issues or have questions. - * The Egeria Docker image is now based on Redhat's UBI-8 openjdk-11 image, to improve security & operational support. See issue #3580 - * Bug Fixes & ongoing feature work - -## Known Issues - * Several maven artifacts have not been published to maven central/JCenter. See issue #3675 They can be retrieved from JFrog Artifactory at 'https://odpi.jfrog.io/odpi/egeria-release-local' if needed and it is not possible to build locally. - - org.odpi.egeria:presentation-server - - org.odpi.egeria:subject-area-fvt - - org.odpi.egeria:dev-ops-api - - org.odpi.egeria:digital-service-spring - -## Dependencies - * Spring has been updated to 2.3.9 - * Spring Security has been updated to 5.4.0 - * For a full list run 'mvn dependency:tree' against top level directory and/or review the top level pom.xml - - ## Egeria Implementation Status at Release 2.3 - -![Egeria Implementation Status](../open-metadata-publication/website/roadmap/functional-organization-showing-implementation-status-for-2.3.png#pagewidth) - - Link to Egeria's [Roadmap](../open-metadata-publication/website/roadmap) for more details about the - Open Metadata and Governance vision, strategy and content. - ----- - * Return to [Release Notes](.) - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. diff --git a/release-notes/release-notes-2-4.md b/release-notes/release-notes-2-4.md deleted file mode 100644 index 82f3f6c1167..00000000000 --- a/release-notes/release-notes-2-4.md +++ /dev/null @@ -1,51 +0,0 @@ - - - -# Release 2.4 (November 2020) - -* The [Integration Daemon](https://github.com/odpi/egeria/blob/master/open-metadata-implementation/admin-services/docs/concepts/integration-daemon.md) - now makes it simpler to exchange metadata with third party technology such as catalogs and databases. -* The Repository Explorer User Interface ('REX') must now be configured with a list of available - platforms and servers to improve security and usability. -* The latest version of Repository Explorer, Type Explorer and Dino, is found - in the 'Presentation Server' UI. - * The Repository Explorer User Interface ('REX') must now be configured with a list of available - platforms and servers to improve security and usability. See - [Presentation Server component documentation](https://github.com/odpi/egeria/tree/master/open-metadata-implementation/user-interfaces/presentation-server) - and - [Configuring the Presentation Server](https://github.com/odpi/egeria/blob/master/open-metadata-implementation/admin-services/docs/user/configuring-the-presentation-server.md). -* The [UI Server Chassis](https://github.com/odpi/egeria/tree/master/open-metadata-implementation/user-interfaces/ui-chassis/ui-chassis-spring) - no longer includes static content. It is now required to deploy the [egeria-ui]( https://github.com/odpi/egeria-ui) - project in addition to the spring application. - A [docker image](https://hub.docker.com/r/odpi/egeria-uistatic) is available, - and the [docker-compose](https://github.com/odpi/egeria/blob/master/open-metadata-resources/open-metadata-tutorials/lab-infrastructure-guide/running-docker-compose.md) - & [Kubernetes](https://github.com/odpi/egeria/blob/master/open-metadata-resources/open-metadata-tutorials/lab-infrastructure-guide/running-kubernetes.md) - lab environments include this pre-configured. -* Additional [Access Services Functional Verification tests](https://github.com/odpi/egeria/tree/master/open-metadata-test/open-metadata-fvt/access-services-fvt) have been added to improve code quality -* Bug fixes -* Dependency updates - * Spring has been updated to 5.2.9 - * Spring Security has been updated to 5.4.1 - * Spring Boot has been updated to 2.3.3 - * For a full list run 'mvn dependency:tree' against top level directory and/or review the top level pom.xml - -## Known Issues - -* The docker-compose based lab environment is incorrectly pulling docker images from the wrong repository. To correct this change `open-metadata-resources/open-metadata-deployment/compose/tutorials/.env` to `egeria_repo=odpi`. The original repository -has however been updated to include 2.4 images, so will now work even if unchanged. - - - -## Egeria Implementation Status at Release 2.4 - -![Egeria Implementation Status](../open-metadata-publication/website/roadmap/functional-organization-showing-implementation-status-for-2.4.png#pagewidth) - -Link to Egeria's [Roadmap](../open-metadata-publication/website/roadmap) for more details about the -Open Metadata and Governance vision, strategy and content. - ----- -* Return to [Release Notes](.) - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. diff --git a/release-notes/release-notes-2-5.md b/release-notes/release-notes-2-5.md deleted file mode 100644 index e1d55939e89..00000000000 --- a/release-notes/release-notes-2-5.md +++ /dev/null @@ -1,59 +0,0 @@ - - - -# Release 2.5 (December 2020) - -Below are the highlights of the 2.5 release: - - -* The following improvements to the presentation-server user interface: - - * The Type Explorer UI - - * supports options to show/hide deprecated types and/or deprecated attributes. Please refer to the Type Explorer help.md for details. - * preserves the user-selected focus type across reloads of type information from the repository server. - - * The Repository Explorer UI - - * has the Enterprise option enabled by default. It can be disabled to perform more specific, localized queries. - * now indicates whether an instance was returned by an enterprise or local scope operation against its home repository or is a reference copy or proxy. - * has a user-settable limit on the number of search results (and a warning to the user if it is exceeded) - * now colors nodes based on their home metadata collection's ID. This previously used metadata collection's name but a metadata collection's name can be changed, whereas the metadata collection's ID is permanent. - * has improved help information covering search - - * The Dino UI - - * displays a server's status history in a separate dialog instead of inline in the server details view. - - -* The following improvements to the repositories: - - * The Graph Repository - - * find methods have reinstated support for core properties, previously temporarily disabled due to property name clashes that are now resolved - -* A new type **OpenMetadataRoot** has been added as the root type for all Open Metadata Types. See the [base model](../open-metadata-publication/website/open-metadata-types/0010-Base-Model.md) - -* The admin services guide has some [additional information](../open-metadata-implementation/admin-services/docs/user/omag-server-platform-transport-level-security.md) on configuring TLS security - -* Improvements to the gradle build scripts, but at this point it remains incomplete and build of egeria still requires maven - -* Bug Fixes - -* Dependency Updates - - - -## Egeria Implementation Status at Release 2.5 - -![Egeria Implementation Status](../open-metadata-publication/website/roadmap/functional-organization-showing-implementation-status-for-2.5.png#pagewidth) - -Link to Egeria's [Roadmap](../open-metadata-publication/website/roadmap) for more details about the -Open Metadata and Governance vision, strategy and content. - ----- -* Return to [Release Notes](.) - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. diff --git a/release-notes/release-notes-2-6.md b/release-notes/release-notes-2-6.md deleted file mode 100644 index 84ef490df89..00000000000 --- a/release-notes/release-notes-2-6.md +++ /dev/null @@ -1,132 +0,0 @@ - - - -# Release 2.6 (February 2021) - -Release 2.6 adds support for: - * New Governance Server called [Engine Host](../open-metadata-implementation/admin-services/docs/concepts/engine-host.md) - with associated [Open Metadata Engine Services (OMES)](../open-metadata-implementation/engine-services). - This Governance Server replaces the Discovery Server, Stewardship Server, Virtualizer and Security Officer Server. - - * Extensions to Open Metadata Types for lineage, duplicate processing, governance actions, - the software development lifecycle and analytics models. - -The release also changes the default location of some important files in order to facilitate deployment -and seperate program files from writeable data. - -Details of these and other changes are in the sections that follow. - -## Description of Changes -### Changes to data files created/used by Egeria - -Up to and including release 2.5, various data files were created in the current working directory when Egeria was run. This included -configuration files, cohort information, graph repositories etc. This made it difficult to manage Egeria in a container environment -where we want to manage persistent data explicitly - for example via a docker volume, or a kubernetes persistent volume (claim). - -Because of this the default locations of a number of files have changed, so when deploying release 2.6 make sure you copy any existing -files you need to preserve over to their new locations. If this is not done server configs and repository data may not -be found, or configuration files may not be decrytable. - -| usage | old | new | variables | -| -------------------- | ------------------------- | ------------------------------------------ | -------------------------------- | -| Server configuration | omag.server.{0}.config | data/servers/{0}/config/{0}.config | 0 = server Name | -| File based audit log | omag.server.{0}.auditlog/ | data/servers/{0}/logs/auditlog/ | 0 = server Name | -| cohort registry | {0}.{1}.registrystore | data/servers/{0}/cohorts/{1}.registrystore | 0 = server Name, 1 = cohort name | -| Graph repository | {0}-graph-repository/ | data/servers/{0}/repository/graph/ | 0 = server Name | -| Encrypted config key | keystore_* | data/platform/keys/keystore_* | | - -The result of this is that all the dynamic data created by egeria locally in the filesystem is restricted to the 'data' directory -so this can be mapped to a volume easily. - -If you have already explicitly configured the relevant connector yourself there will be no change. this updates the defaults only. - -### Removal of the Discovery Server and Stewardship Server - -The Discovery Server, Stewardship Server, Virtualizer and Security Officer Server have been consolidated into a new -type of server called the [Engine Host OMAG Server](../open-metadata-implementation/admin-services/docs/concepts/engine-host.md). -The Engine Host runs one-to-many [Open Metadata Engine Services (OMES)](../open-metadata-implementation/engine-services). -Each engine services hosts a specific type of governance engine. The first engine service called -[Asset Analysis OMES](../open-metadata-implementation/engine-services/asset-analysis) will be for -[discovery engines](../open-metadata-implementation/frameworks/open-discovery-framework/docs/discovery-engine.md) -and others for the different types of [governance action engines](../open-metadata-implementation/frameworks/governance-action-framework/docs/governance-action-engine.md). -from the -[Governance Action Framework (GAF)](../open-metadata-implementation/frameworks/governance-action-framework). - -The reason for this change is that there is a lot of duplicated code in the original servers and this change simplifies -the [Governance Server Services](../open-metadata-implementation/governance-servers) and -[Server Administration](../open-metadata-implementation/admin-services/docs/user). -With this change it will also be easier for Egeria to host other types of governance engines such as Palisade and Gaian. - -### New open metadata types for Governance Actions - -The following types have been added to support the governance action engines: - -* [0461 Governance Action Engines](../open-metadata-publication/website/open-metadata-types/0461-Governance-Engines.md) -* [0462 Governance Action Types](../open-metadata-publication/website/open-metadata-types/0462-Governance-Action-Types.md) -* [0463 Governance Actions](../open-metadata-publication/website/open-metadata-types/0463-Governance-Actions.md) - -### Updates to open metadata types for Lineage Mapping - -The [LineageMapping](../open-metadata-publication/website/open-metadata-types/0770-Lineage-Mapping.md) -open metadata relationship type has been updated to link **Referenceables** rather than **SchemaElements**. -This is to capture lineage between components at different levels of detail since the data field mappings may not -always be available. Lineage mapping is described in more detail [here](../open-metadata-publication/website/lineage). - -### New open metadata types for Duplicate Processing - -Since Egeria is integrating and distributing metadata from many different sources, it is inevitable that -there will be multiple metadata instances that represent the same real-world "thing". The -[0465 Duplicate Processing](../open-metadata-publication/website/open-metadata-types/0465-Duplicate-Processing.md) -types allow these elements to be linked together. - -### Presentation Server / React UI - -* The node based User Interface component known as 'Presentation Server' has now fully moved to it's own -[GitHub Repository](https://github.com/odpi/egeria-react-ui). -* The docker image has been renamed to [egeria-react-ui](https://hub.docker.com/repository/docker/odpi/egeria-react-ui) -* Dino - Adds display of integration servers’ integration services and engine hosts’ engine services, including display of a dependency on a partnerOMAS. -* Rex - Improved error reporting and geometry management plus more consistent handling of focus objects. -Enterprise queries are now the default, but can be over-ridden to perform a local operation. -* At this time 'Server Author' and 'Glossary Author' are still in development. - -### New Helm Chart - -In addition to our 'lab' helm chart to support the Coco Pharmaceuticals environment, we have now added an [additional -helm chart](../open-metadata-resources/open-metadata-deployment/egeria-base) which provides a simpler environment with just a single platform, and a single server, but configured with -persistence and auto start. This offers an example of a simple Kubernetes deployment. - -### Graph Repository -* Now implements the findEntities and fnidRelationships methods of the OMRS MetadataCollection API. -* Added detailed documentation for the graph repository - -### Conformance Test Suite -* CTS now has tests for findEntities and findRelationships methods and search tests have been realigned into profiles so that all search operations are in optional profiles, with basic and advanced profiles for each of entities and relationships. - -### Other changes - -Release 2.6 also contains many bug fixes and minor improvements & dependency updates -### Removals and Deprecations - -* Discovery Server, Stewardship Server, Virtualizer and Security Officer Server have been replaced with more extensive capability - see above. -* Information View OMAS has now been removed following earlier deprecation. - -# Egeria Implementation Status at Release 2.6 - -![Egeria Implementation Status](../open-metadata-publication/website/roadmap/functional-organization-showing-implementation-status-for-2.6.png#pagewidth) - -Link to Egeria's [Roadmap](../open-metadata-publication/website/roadmap) for more details about the -Open Metadata and Governance vision, strategy and content. - - -# Further Help and Support - -As part of the Linux AI & Data Foundation, our slack channels have moved to the [LF AI & Data Slack workspace](slack.lfaidata.foundation), and our mailing lists can now be found at https://lists.lfaidata.foundation/groups - -Continue to use these resources, along with GitHub to report bugs or ask questions. - ----- -* Return to [Release Notes](.) - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. diff --git a/release-notes/release-notes-2-7.md b/release-notes/release-notes-2-7.md deleted file mode 100644 index dd6324a1ea2..00000000000 --- a/release-notes/release-notes-2-7.md +++ /dev/null @@ -1,58 +0,0 @@ - - - -# Release 2.7 (March 2021) - -Release 2.7 adds: -* Performance improvements in the graph repo -* Changes to metadata types -* Changes to the distribution process - -Details of these and other changes are in the sections that follow. - -## Description of Changes - -### Build & Release changes - -* Previously release maven artifacts have been pushed to JCenter (in addition to Maven Central), and snapshots have been pushed to odpi.jfrog.io/odpi/egeria-snapshot. As of 2.7 this no longer occurs and release and snapshots are pushed only to Maven Central. -* Due to the above, maven artifacts may be signed by a different user to previously (and this may change in a future release). - -### Performance Improvements - -* Release 2.7 includes performance improvements to the graph repository's search methods, which select an efficient query strategy based on the properties and type filters supplied to the search. - -### Metadata Types - -* We have removed overloaded properties that existed at multiple levels in a type definition: for example, length was defined both on SchemaAttribute and again on RelationalColumn (which is a subtype of SchemaAttribute). This change removes them from being defined again the lower level (RelationalColumn in this example); however, the property itself will still be available at the lower level due to inheriting it from the supertype. - -### Bug fixes and other updates -* Additional Bug Fixes -* Dependency Updates - -For details on both see the commit history in GitHub. - -## Known Issues - -* It is recommended to use a chromium-based browser such as Google Chrome or Microsoft Edge, or Apple Safari for the Egeria React UI. Some parts of the UI experience such as Dino currently experience problems with Firefox. See [odpi/egeria-react-ui#96](https://github.com/odpi/egeria-react-ui/issues/96) . -* When running the 'Understanding Platform Services' lab, ensure you run the 'egeria-service-config' notebook first and do not restart the python kernel before running this lab. See [#4842](https://github.com/odpi/egeria/issues/4842) . - -# Egeria Implementation Status at Release 2.7 - -![Egeria Implementation Status](../open-metadata-publication/website/roadmap/functional-organization-showing-implementation-status-for-2.7.png#pagewidth) - -Link to Egeria's [Roadmap](../open-metadata-publication/website/roadmap) for more details about the -Open Metadata and Governance vision, strategy and content. - - -# Further Help and Support - -As part of the Linux AI & Data Foundation, our slack channels have moved to the [LF AI & Data Slack workspace](slack.lfaidata.foundation), and our mailing lists can now be found at https://lists.lfaidata.foundation/groups - -Continue to use these resources, along with GitHub to report bugs or ask questions. - ----- -* Return to [Release Notes](.) - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. diff --git a/release-notes/release-notes-2-8.md b/release-notes/release-notes-2-8.md deleted file mode 100644 index 70ebdc4990f..00000000000 --- a/release-notes/release-notes-2-8.md +++ /dev/null @@ -1,155 +0,0 @@ - - - -# Release 2.8 (April 2021) - -Release 2.8 adds: -* New support for event and property filtering for the open metadata server security connector -* Changes to metadata types -* New performance workbench for the CTS (technical preview) -* New interface for retrieving the complete history of a single metadata instance -* Splitting of CTS results into multiple smaller files - -Details of these and other changes are in the sections that follow. - -## Description of Changes - -### Updates to the Open Metadata Security Connector - -Before this release, the repository services support 3 filtering points for managing events for the OMRS Cohort Topic. - -* Should an event be sent to the cohort -* Should an event be retrieved from the cohort -* Should a received event be stored in the local repository - -These filtering points are set up in the configuration document of the server. -It is possible to specify rules to determine which types of events and which types of metadata elements are filtered out. -However this configuration provides no control to allow filtering of events for specific instances. - -This release extends the metadata server security connector so it can be called at these same filter points. -This will be through optional interfaces that the security connector can choose to implement. - -If the current rules are set up, they will still be executed. This change complements the existing filtering. - -The server security connector also implements the repository security interface called when metadata is being -added/updated/deleted/retrieved through the APIs. Extending the security connector for event filtering means that it can make consistent decisions on the sharing of metadata through the cohorts and through the APIs. - -##### Configuring the server security connector - -Configuring the server security connector will not change with this feature. -If the connector needs custom attributes to select rule sets etc, these can be specified in the configuration properties. - -See [https://egeria.odpi.org/open-metadata-implementation/admin-services/docs/user/configuring-the-server-security-connector.html](../open-metadata-implementation/admin-services/docs/user/configuring-the-server-security-connector.md). - -##### Implementing the server security connector - -The security server connector will have two new interfaces that it can implement: one for the cohort events and one for saving events to the local repository. - -* The event interface will have two methods, one for sending and one for receiving. The parameters will include the cohort name and the event contents. It can return the event unchanged, return a modified event (eg with sensitive content removed) or return null to say that the event is filtered out. - -* The event saving interface will receive the instance header and can return a boolean to indicate if the local repository should store it. If true is returned, the refresh event sequence is initiated. The repository connector then has the ultimate choice when the refreshed instance is returned from the home repository as to whether to store it or not. - -There is a single instance of the connector in the server so it is able to maintain counts and cache rules etc. It can also be implemented as a facade to a proprietary service. - -More information on the security connector can be found -on this page: - -[https://egeria.odpi.org/open-metadata-implementation/common-services/metadata-security/metadata-security-apis](../open-metadata-implementation/common-services/metadata-security/metadata-security-apis) - -### Metadata Types - -* Updates to the location types in [model 0025](../open-metadata-publication/website/open-metadata-types/0025-Locations.md): - * Add the **mapProjection** property to the **FixedLocation** classification - * Change the **address** property to **networkAddress** in the **CyberLocation** classification - * Deprecated **HostLocation** in favor of the **AssetLocation** relationship - -* Deprecate the **RuntimeForProcess** relationship since it is superfluous - use **ServerAssetUse** since - **Application** is a **SoftwareServerCapability**. - See [model 0045](../open-metadata-publication/website/open-metadata-types/0045-Servers-and-Assets.md). - -* Replace the **deployedImplementationType** property with the **businessCapabilityType** in the **BusinessCapability** - since it is a more descriptive name. - See [model 0440](../open-metadata-publication/website/open-metadata-types/0440-Organizational-Controls.md). - -### Performance workbench - -The performance workbench intends to test the response time of all repository (metadata collection) methods for the -technology under test. The volume of the test can be easily configured to also test scalability. - -More information is available [in the workbench's documentation](../open-metadata-conformance-suite/docs/performance-workbench/README.md). - -### Instance history interface - -Two new (optional) methods have been introduced to the metadata collection interface: - -* `getEntityDetailHistory` -* `getRelationshipHistory` - -Both methods take the GUID of the instance for which to retrieve history, an optional range of times between which to -retrieve the historical versions (or if both are `null` to retrieve _all_ historical versions), and a set of paging -parameters. - -If not implemented by a repository, these will simply throw `FunctionNotSupported` exceptions by default -to indicate that they are not implemented. - -### CTS results output - -Up to this release, the detailed results of a CTS run could only be be retrieved by pulling a huge -(100's of MB) file across the REST interface for the CTS. Aside from not typically working with most REST clients -(like Postman), this had the additional impact of a sudden huge hit on the JVM heap to serialize such a large JSON -structure (immediately grabbing ~1GB of the heap). - -While this old interface still exists for backwards compatibility, the new default interface provided in this release -allows users to pull down just an overall summary of the results separately from the full detailed results, and the -detailed results are now broken down into separate files by profile and test case: each of which can therefore be -retrieved individually. - -(So, for example, if you see from the summary that only 1-2 profiles are not conformant, you can retrieve just the -details for those profiles rather than all details.) - -### Changes to deployment of the Polymer based UI - -In previous releases, a zuul router component was used within the UI server chassis to route requests -for static content to a separate server. - -In this release any routing needs to be setup externally, for example by placing a nginx proxy in front of both the ui -chassis and static content server. This is now done by our docker-compose environment & helm charts so to access -the UI you need to go to the nginx proxy. Further summary information can be found in the documentation for those assets. - -### Bug fixes and other updates - -* Additional Bug Fixes -* Dependency Updates - -For details on both see the commit history in GitHub. - -## Known Issues - -* It is recommended to use a chromium-based browser such as Google Chrome or Microsoft Edge, or Apple Safari for the Egeria React UI. Some parts of the UI experience such as Dino currently experience problems with Firefox. See [odpi/egeria-react-ui#96](https://github.com/odpi/egeria-react-ui/issues/96) . -* Egeria source code currently fails to build on Windows natively. Please use Linux, MacOS, or compile under WSL/WSL2 on Windows. See [#4917](https://github.com/odpi/egeria/issues/4917) -* Several Java samples fail (governance, admin) - [#4656](https://github.com/odpi/egeria/issues/4656), [#4662](https://github.com/odpi/egeria/issues/4656), [#4056](https://github.com/odpi/egeria/issues/4056) -* The React UI used by the helm charts and compose is based on react UI release 2.7.0 due to layout issues found with 2.8.0. See [#5022](https://github.com/odpi/egeria/issues/5022) -* The platform services notebook may fail to query servers correctly. See [#5023](https://github.com/odpi/egeria/issues/5023) -* The building a data catalog notebook may fail if run quickly. See [#2688](https://github.com/odpi/egeria/issues/2688) -* The data curation notebook is incomplete and still being developed. The final steps may fail to work in a container environment. See [#5021](https://github.com/odpi/egeria/issues/5021) - -# Egeria Implementation Status at Release 2.8 - -![Egeria Implementation Status](../open-metadata-publication/website/roadmap/functional-organization-showing-implementation-status-for-2.8.png#pagewidth) - -Link to Egeria's [Roadmap](../open-metadata-publication/website/roadmap) for more details about the -Open Metadata and Governance vision, strategy and content. - - -# Further Help and Support - -As part of the Linux AI & Data Foundation, our slack channels have moved to the [LF AI & Data Slack workspace](slack.lfaidata.foundation), and our mailing lists can now be found at https://lists.lfaidata.foundation/groups - -Continue to use these resources, along with GitHub to report bugs or ask questions. - ----- -* Return to [Release Notes](.) - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. diff --git a/release-notes/release-notes-2-9.md b/release-notes/release-notes-2-9.md deleted file mode 100644 index 1a350760d81..00000000000 --- a/release-notes/release-notes-2-9.md +++ /dev/null @@ -1,70 +0,0 @@ - - - -# Release 2.9 (May 2021) - -Release 2.9 adds: -* Changes to metadata types -* Changes to building Egeria on Windows - -Details of these and other changes are in the sections that follow. - -## Description of Changes - -### Metadata Types - -* The **UserProfileManager**, **UserAccessDirectory** and **MasterDataManager** classification for **Referenceables** has been added -to model [0056 Asset Managers](../open-metadata-publication/website/open-metadata-types/0056-Asset-Managers.md). -* A new relationship called **ActionTarget** to link a **To Do** to the elements that need work has been added -to model [0137 Actions for People](../open-metadata-publication/website/open-metadata-types/0137-Actions.md). -* A new attribute called **filterExpression** has been added to the **Port** entity in -model [0217 Ports](../open-metadata-publication/website/open-metadata-types/0217-Ports.md). -* A new classification called **PrimaryCategory** has been added to -model [0335 Primary Category](../open-metadata-publication/website/open-metadata-types/0335-Primary-Category.md). -* A new classification called **GovernanceMeasurements** has been added to -model [0450 Governance Rollout](../open-metadata-publication/website/open-metadata-types/0450-Governance-Rollout.md). -* The **RelationalColumnType** entity in -model [0534 Relational Schema](../open-metadata-publication/website/open-metadata-types/0534-Relational-Schemas.md). -only allows for a column to be primitive. It could be a literal, enum or external and so this type has been deprecated -and the appropriate schema types should be used directly. - -### Building Egeria on Windows - -To build Egeria on Windows you should use [Windows Subsystem for Linux](https://docs.microsoft.com/en-us/windows/wsl/) Version 2 or above & install an -appropriate Linux distribution. - -Egeria should then be built & run within this environment. - -IDEs such as IntelliJ and VSCode support editing and code management within the Windows GUI alongside build and execution in Linux. - -See [PR #5084](https://github.com/odpi/egeria/pull/5084) for more information. - -### Bug fixes and other updates -* Additional Bug Fixes -* Dependency Updates - -For details on both see the commit history in GitHub. - -## Known Issues - -* It is recommended to use a chromium-based browser such as Google Chrome or Microsoft Edge, or Apple Safari for the Egeria React UI. Some parts of the UI experience such as Dino currently experience problems with Firefox. See [odpi/egeria-react-ui#96](https://github.com/odpi/egeria-react-ui/issues/96) . -* When running the 'Understanding Platform Services' lab, ensure you run the 'egeria-service-config' notebook first and do not restart the python kernel before running this lab. See [#4842](https://github.com/odpi/egeria/issues/4842) . - -# Egeria Implementation Status at Release 2.9 - -![Egeria Implementation Status](../open-metadata-publication/website/roadmap/functional-organization-showing-implementation-status-for-2.9.png#pagewidth) - -Link to Egeria's [Roadmap](../open-metadata-publication/website/roadmap) for more details about the -Open Metadata and Governance vision, strategy and content. - - -# Further Help and Support - -See the [Community Guide](../Community-Guide.md). - ----- -* Return to [Release Notes](.) - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. diff --git a/release-notes/release-notes-3-0.md b/release-notes/release-notes-3-0.md deleted file mode 100644 index 9f5174665c8..00000000000 --- a/release-notes/release-notes-3-0.md +++ /dev/null @@ -1,47 +0,0 @@ - - - -# Release 3.0 (August 2021) - -Release 3.0 adds: -* Requirement to build & run with Java 11 (LTS) or above - -Details of these and other changes are in the sections that follow. - -## Description of Changes - -### Java 11 - -As of Release 3.0 of Egeria, Java 11 is **required** to build and run Egeria. - -Egeria will not build/run/be supported on Java 8. Developers are now able to use Java 11 only functionality. - -Java releases beyond Java 11 up to the current release have some informal testing, and we do build verification on the current release (currently 16). - -See [Java](../developer-resources/languages/Java.md) for further information. - -### Cohort members - -* The option added in release 2.11 to allow multiple topics per cohort now becomes the default in release 3.0 . See [open metadata repository cohort](../open-metadata-implementation/admin-services/docs/concepts/cohort-member.md) - -### Egeria UI -* Passwords for the samples Coco Pharmaceuticals users changed to 'secret'; - -### Known Issues - -* It is recommended to use a chromium-based browser such as Google Chrome or Microsoft Edge, or alternatively Apple Safari for the Egeria React UI. Some parts of the UI experience such as Dino currently experience problems with Firefox. See [odpi/egeria-react-ui#96](https://github.com/odpi/egeria-react-ui/issues/96) . - -### Other changes -* Dependencies have been updated -* Bug Fixes - -# Further Help and Support - -See the [Community Guide](../Community-Guide.md). - ----- -* Return to [Release Notes](.) - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. diff --git a/release-notes/release-notes-3-1.md b/release-notes/release-notes-3-1.md deleted file mode 100644 index ad0ccabe5e6..00000000000 --- a/release-notes/release-notes-3-1.md +++ /dev/null @@ -1,111 +0,0 @@ - - - -# Release 3.1 (September 2021) - -Release 3.1 adds: -* Open Metadata Type changes -* Deprecation of Docker Compose environment -* Changes to the Coco Pharmaceuticals lab environment -* Dependency Updates -* Bug Fixes - - -Details of these and other changes are in the sections that follow. - -## Description of Changes - -### Open Metadata Types - -The following changes have been made to the open metadata types: - -* New types for modeling data processing purposes. - See new type descriptions in models [0485](../open-metadata-publication/website/open-metadata-types/0485-Data-Processing-Purposes.md). - -* The following types have been deprecated: **BoundedSchemaType**, **BoundedSchemaElementType**, - **ArraySchemaType**, **ArrayDocumentType**, **SetSchemaType**, and **SetDocumentType**. - See description in model [0507](../open-metadata-publication/website/open-metadata-types/0507-External-Schema-Type.md). - -* The **ServerEndpoint** relationship can now connect to any **ITInfrastructure** elements, not just **SoftwareServers**. - See description in model [0040](../open-metadata-publication/website/open-metadata-types/0040-Software-Servers.md). - -* The **OperatingPlatform** entity can now record the patch level of the operating system. There are also new types for describing - the contents of an operating platform. - See description in model [0030](../open-metadata-publication/website/open-metadata-types/0030-Hosts-and-Platforms.md). - -* There are now types for distinguishing between virtual machines and virtual containers as well as bare metal hardware. - There are also new types for specific technologies such as **HadoopCluster**, **KubernetesCluster** and **DockerContainer** - to provide concrete examples of different types of hosts using popular technologies. - Finally the **DeployedVirtualContainer** relationship has been deprecated in favor of a more generic **HostedHost** relationship. - See description in model [0035](../open-metadata-publication/website/open-metadata-types/0035-Complex-Hosts.md). - -* There are new types for define a storage volume that has been attached to a host. - See description in model [0036](../open-metadata-publication/website/open-metadata-types/0036-Storage.md). - -* A new subtype of software server for reusable business functions (such as microservices) has been added called **ApplicationService**. - See description in model [0057](../open-metadata-publication/website/open-metadata-types/0057-Software-Services.md). - -## Beta documentation site - -We are in the process of moving our documentation across to a new site at https://odpi.github.io/egeria-docs/ . This is still work in progress so some material is currently missing, and some links will fail. - -This site should offer improved usability including navigation & search. - -Please continue to refer to the main documentation site for any missing content until this migration is complete. - -## Deprecation of docker-compose - -The docker-compose environment for running our Coco Pharmaceuticals lab demo/tutorial is now deprecated. The configuration is still available, but will not -be further developed or tested, and will be removed in a future release. - -Our Kubernetes Helm charts are now recommended to quickly setup the same lab -environment, and the [documentation](https://odpi.github.io/egeria-charts/site/index.html) for these has been improved to cover -a Kubernetes introduction, and example based on 'microk8s' which are suited to -an end user desktop environment (and can also be run in enterprise/cloud environments) - -## Egeria Helm charts repository - -The Helm charts are now being developed at https://github.com/odpi/egeria. Charts are now published as a proper Helm Repository, making installation easier. This move also keeps their lifecycle independent of our various code repositories, and issues/features should be opened on that repository. - -Charts are now installable without cloning the git repository. Instead first add the repository: -```shell -helm repo add egeria https://odpi.github.io/egeria-charts -``` - -You can list charts with: -```shell -helm search repo egeria -``` -And install with : -```shell -helm install lab egeria/odpi-egeria-lab -``` -The documentation is temporarily available at https://odpi.github.io/egeria-charts/site/ but will move to our new cross-repository Egeria docs repository soon. - -## Coco Pharmaceuticals lab environment changes - -The Egeria UI is not available by default in the labs environment & is not tested. This is because at this time we don't have suitable test data or notebook walkthroughs available. To avoid confusion this is now disabled by default. It can be renabled through a feature flag (at cli or in an override file) ie: -```shell -helm install --set egeria.egeria-ui=true lab egeria/odpi-egeria-lab -``` - -Note that the Egeria UI continues to be developed. This change is purely due to ensuring consistency of the demo/tutorial environment. - -For browsing the type system and repository within this environment, use the React UI. - - -### Known Issues - -* It is recommended to use a chromium-based browser such as Google Chrome or Microsoft Edge, or alternatively Apple Safari for the Egeria React UI. Some parts of the UI experience such as Dino currently experience problems with Firefox. See [odpi/egeria-react-ui#96](https://github.com/odpi/egeria-react-ui/issues/96) . - - -# Further Help and Support - -See the [Community Guide](../Community-Guide.md). - ----- -* Return to [Release Notes](.) - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. diff --git a/release-notes/release-notes-3-2.md b/release-notes/release-notes-3-2.md deleted file mode 100644 index ddbac820858..00000000000 --- a/release-notes/release-notes-3-2.md +++ /dev/null @@ -1,54 +0,0 @@ - - - -# Release 3.2 (October 2021) - -Release 3.2 adds: -* Open Metadata Type changes -* Dependency Updates -* Bug Fixes - - -Details of these and other changes are in the sections that follow. - -## Description of Changes - -### Open Metadata Types - -The following changes have been made to the open metadata types: - -* New types for setting up the list of status for governance definitions. - See new type descriptions in model [0421](../open-metadata-publication/website/open-metadata-types/0421-Governance-Classification-Levels.md). - -* There is a new type called **SoftwareArchive** to describe a software archive such as a JAR file for java. - See description in model [0030](../open-metadata-publication/website/open-metadata-types/0030-Hosts-and-Platforms.md). - -## Beta documentation site - -We are in the process of moving our documentation across to a new site at https://odpi.github.io/egeria-docs/ . This is still work in progress so some material is currently missing, and some links will fail. - -This site should offer improved usability including navigation & search. - -Please continue to refer to the main documentation site for any missing content until this migration is complete. - -## Deprecations - -* The docker-compose environment was deprecated in release 3.1 . It will be removed in 3.3 . See https://github.com/odpi/egeria/issues/5721 . - -## Known Issues - -* It is recommended to use a chromium-based browser such as Google Chrome or Microsoft Edge, or alternatively Apple Safari for the Egeria React UI. Some parts of the UI experience such as Dino currently experience problems with Firefox. See https://github.com/odpi/egeria-react-ui/issues/96 . -* Config documents cannot be displayed in the Egeria React UI (Dino). See https://github.com/odpi/egeria-react-ui/issues/264 . -* If deploying helm charts to OpenShift, a security policy change is needed. See https://github.com/odpi/egeria-charts/issues/18 -* When using the 'understanding platform services' lab notebook, the query for active servers will fail. See https://github.com/odpi/egeria/issues/5023 . - -# Further Help and Support - -See the [Community Guide](../Community-Guide.md). - ----- -* Return to [Release Notes](.) - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. diff --git a/release-notes/release-notes-3-3.md b/release-notes/release-notes-3-3.md deleted file mode 100644 index 7f777ab3f92..00000000000 --- a/release-notes/release-notes-3-3.md +++ /dev/null @@ -1,54 +0,0 @@ - - - -# Release 3.3 (November 2021) - -Release 3.3 adds: - * Open Metadata Type changes - * New hand-on lab introducing **Lineage management** - - -Details of these and other changes are in the sections that follow. - -## Description of Changes - -**Lineage management** is new chapter in our hand-on labs describing different scenarios to capture, preserve and use lineage information. -[Open Lineage Lab](https://github.com/odpi/egeria/blob/master/open-metadata-resources/open-metadata-labs/asset-management-labs/open-lineage.ipynb) brings the first exercise focusing on design time lineage using Open Lineage Services. - - -### Open Metadata Types - -The following changes have been made to the open metadata types: - -* New type **Incomplete** for classifying referencable entities used in special lineage cases. One example for such case is representing 'virtual asset' form IBM IGC external repository. - See description in model [0790](https://odpi.github.io/egeria-docs/types/7/0790-Incomplete/). - -## Beta documentation site - -We are in the process of moving our documentation across to a new site at https://odpi.github.io/egeria-docs/ . This is still work in progress so some material is currently missing, and some links will fail. - -This site should offer improved usability including navigation & search. - -Please continue to refer to the main documentation site for any missing content until this migration is complete. - -## Deprecations & Removals - -None. - -## Known Issues - -* It is recommended to use a chromium-based browser such as Google Chrome or Microsoft Edge, or alternatively Apple Safari for the Egeria React UI. Some parts of the UI experience such as Dino currently experience problems with Firefox. See https://github.com/odpi/egeria-react-ui/issues/96 . - -* If deploying helm charts to OpenShift, a security policy change is needed. See https://github.com/odpi/egeria-charts/issues/18 -* When using the 'understanding platform services' lab notebook, the query for active servers will fail. See https://github.com/odpi/egeria/issues/5023 . - -# Further Help and Support - -See the [Community Guide](../Community-Guide.md). - ----- -* Return to [Release Notes](.) - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project. diff --git a/release-notes/release-notes-3-4.md b/release-notes/release-notes-3-4.md deleted file mode 100644 index dc611055db8..00000000000 --- a/release-notes/release-notes-3-4.md +++ /dev/null @@ -1,37 +0,0 @@ - - - -# Release 3.4 (December 2021) - -Release 3.4 adds: - * OMAG Server Platform Chassis for Spring & Connector Configuration Factory are built without Egeria graph repository - - -Details of these and other changes are in the sections that follow. - -## OMAG Server Platform Chassis & Connector Configuration Factory change - -[Graph repository connector](https://github.com/odpi/egeria/open-metadata-implementation/adapters/open-connectors/repository-services-connectors/open-metadata-collection-store-connectors/graph-repository-connector/README.md) -it is not dependency of [Connector configuration factory](https://github.com/odpi/egeria/open-metadata-implementation/adapters/open-connectors/connector-configuration-factory/README.md) -anymore therefore will not be included by the build into [ OMAG Server Platform Chassis ](ohttps://github.com/odpi/egeria/open-metadata-implementation/server-chassis/server-chassis-spring/README.md). -Jar with dependencies of [Graph repository connector](https://github.com/odpi/egeria/open-metadata-implementation/adapters/open-connectors/repository-services-connectors/open-metadata-collection-store-connectors/graph-repository-connector/README.md) -it is now part of the build (maven and gradle) and to run a platform that have server(s) with Egeria graph repository, -the connector jar have to be placed into classpath. Easy way is to use Spring boot loader.path functionality. Place the -jar in the 'lib' folder next to server-chassis-spring jar and run it with -Dloader.path=lib - -## Deprecations & Removals - -None. - -## Known Issues - -# Further Help and Support - -See the [Community Guide](../Community-Guide.md). - ----- -* Return to [Release Notes](.) - ----- -License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), -Copyright Contributors to the ODPi Egeria project.