[
https://issues.apache.org/jira/browse/ATLAS-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16147506#comment-16147506
]
Nigel Jones commented on ATLAS-1768:
------------------------------------
In RANGER-1486 we propose a mechanism to scope the user groups retrieved from
LDAP to a subset that is 'interesting' in terms of data users. For example it
would be these users that might access a virtualized data resource through
gaiandb with it's associated ranger plugin.
So far I don't believe we have these groups -- more appropriately let's call
them roles here -- captured in any of the existing model definitions.
ATLAS-1696 will deliver governance engine OMAS, and one of the proposed APIs is
to retrieve user roles which will be added via subtask ATLAS-1796
These definitions probably belong in area 4 as they more broadly define the
governance landscape, though individuals themselves (and one could argue roles)
feature in area 3. In either case I think we need a new subtask to implement
this area - even if it's just a list of user roles.
In terms of what we need to know about roles, at this point it's mostly simple
a list that we can match against ldap, and report in ranger. For UI use the
usual description etc could be useful, but probably won't be used initially. A
guid of some form is always good, but probably can't be used for matching since
the association with ldap is via alphanumeric match of the name only. All of
these do become relevant as we build more information into atlas around the
definition of policies and their enforcement which also comes into area 4 &
would be influenced by RANGER-1869 along with more general operational
infrastructure metadata we capture (servers, nodes etc)
> Create common types for Open Metadata
> -------------------------------------
>
> Key: ATLAS-1768
> URL: https://issues.apache.org/jira/browse/ATLAS-1768
> Project: Atlas
> Issue Type: New Feature
> Components: atlas-core
> Affects Versions: 0.9-incubating
> Reporter: Mandy Chessell
> Assignee: Mandy Chessell
> Labels: OpenMetadata
>
> This JIRA describes a proposal for standard types for open metadata entities
> and relationships. For example, glossaries, database definitions, rules,
> policies, ...
> The value of having standard definitions for metadata is to enable type safe
> APIs and business level UIs plus be able to exchange metadata between
> different instances of metadata repositories.
> The implementation of these common types is divided into 8 areas:
> * Area 0 - for extensions to Apache Atlas's base model
> * Area 1 - for definitions of the data-related assets we are governing and
> using
> * Area 2 - for a glossary of meanings and semantic relationships
> * Area 3 - for information about asset use, crowd-sourced definitions and
> collaboration around the data-related assets
> * Area 4 - for governance such as policies, rules and classifications
> * Area 5 - for reference models and reference data
> * Area 6 - for metadata discovery processes (see
> https://issues.apache.org/jira/browse/ATLAS-1748)
> * Area 7 - for lineage
> Adaptation and flexibility are key in metadata environments so these common
> definitions must be extensible - and we still need to support the ad hoc
> definition of new types in Atlas.
> Apache Atlas supports meta-types that are used in the definition of new
> types. These are currently enumeration, struct, classification and entity.
> JIRA https://issues.apache.org/jira/browse/ATLAS-1690 adds relationships to
> this list. The open metadata models make use of all of these meta-types.
> These are represented by sterotypes on the classes of the open metadata
> definitions.
> The Atlas wiki has the models as a set of linked pages which are probably the
> easiest way to view the models.
> Start here:
> https://cwiki.apache.org/confluence/display/ATLAS/Building+out+the+Apache+Atlas+Typesystem
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
