THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Forward to Area 1 - Assets and Connectors ==>
In the Atlas build, model files are added in alphanumeric order to build up the type library. Therefore the model files are numbered to ensure its dependencies have been resolved before a model file is loaded. For the open metadata types, the model file number is shown in package name to document the intended load order. The numbering scheme of the metadata areas described in Building out the Apache Atlas Typesystem provides the high-level numbering system. For example, area 1 has models 0100-0199, area 2 has models 0200-299, etc. Each area's sub-models are dispersed along its range, ensuring there is space to insert additional models in the future.
In addition to the 7 metadata areas, the open metadata models introduces some base definitions and structures that used throughout the open metadata models. These need to be loaded first and so we have added an Area 0 that includes these base definitions. The current models defined for Apache Atlas have been moved to 1000. Thus the models numbers from 0000 to 0099 will look something like figure 1.
Figure 1: Summary of Area 0's packages |
Details of the new models are shown below. The original Apache models are linked to on page: Atlas Model.
Linked Media Types
Linked media types describes the simple structures that are used repeatedly in open metadata to connect it to documents and entities in other types of repositories.
Figure 2: Linked Media Types |
Versioned Assets
Versioned assets may follow a simple lifecycle where they can just be updated, or they can use a simple workflow where a draft can be prepared, reviewed and approved. Versions are linked together. The previous version may simply be a Referenceable if it is created before versioning is activated. The types for versioned metadata is shown in figure 3.
Figure 3: Versioning Model |
User Identities
Most metadata repositories are run in a secure mode requiring incoming requests to include the requestor’s security credentials. Therefore we have an identifier for each unique logged on security identity (aka userId). The UserIdentity can capture this identity.
 |
Locations
It is important to understand where assets are located to ensure they are properly protected and comply with data sovereignty laws. The open metadata model allows location information to be captured at many levels of granularity.
 |
Hosts and Platforms
The host and platform metadata entities provide a simple model for the system infrastructure (nodes, computers, etc) that data resources are hosted on.
 |
Complex Hosts
The Complex hosts handle environments where many nodes are acting together as a cluster, and where virtualized containers (such as Docker) are being used.
 |
Servers
Servers describe the middleware servers (such as application servers, data movement engines and database servers) that run on the Hosts.
 | |
Cloud Platforms and Services
The cloud platforms and services model show that cloud computing is not so different from what we have been doing before.
 |
Security Infrastructure
 |
Networks and Gateways
 |
Authoritative Assets
Assets often describe objects in the real world. They may have multiple names depending on the types of technology used to access them. As such an asset may have multiple identifiers. The Authoritative Asset supports the de-duplication and consolidation of asset descriptions. This is shown in figure 4.
Figure 4: The Authoritative Asset Model |
