[RANGER-2019] Handle upgrade scenario to rename the old ATLAS service def and use the new service def

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1.0
• Fix Version/s: 1.1.0
• Component/s: Ranger
• Assignee: Pradeep Agrawal
• Reporter: Pradeep Agrawal
• Created: 14/Mar/18 04:43
• Updated: 20/Mar/18 03:37
• Resolved: 20/Mar/18 03:37

Description

Based on this RANGER-2004 commit, Atlas service def is updated. During the upgrade of existing env, old Atlas service def should be renamed so that new service def can be used.

 

During migration to Ranger 1.1.0, this Jira should address the following:

1. Check for service-def named 'atlas'. If it is not found - nothing more to do.
2. Rename all service instances of type 'atlas', with the addition of a suffix "-v1". Existing service named 'cl1_atlas' will become 'cl1_atlas-v1'. If 'cl1_atlas-v1' already exists, append an count like 'cl1_atlas-v1.1', 'cl1_atlas-v1-2'
3. After all service instances are renamed, rename service-def as 'atlas-v1'.

Issue Links

• is related to: RANGER-2004 Update Ranger Atlas Authorizer for the authorization model changes in Atlas
• links to: Review request link