[SLIDER-3] Design and implement service registry -for slider and beyond

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Slider 0.30
• Fix Version/s: Slider 0.50
• Sprint: slider may 1, slider may 2, slider June 1, slider June 2, Slider July #1, Slider August #1
• Assignee: Steve Loughran
• Reporter: Steve Loughran
• Created: 05/May/14 09:59
• Updated: 04/Aug/14 19:09
• Resolved: 04/Aug/14 19:09

Description

Design and implement the service registry for

1. locating Slider AM instances
2. locating deployed applications
3. publishing & retrieving published internal & external service bindings (IPC, REST, WS, ZK)
4. publishing & retrieving configurations
5. publishing & retrieving other documents

Sub-Tasks

• initial registry designs -> slider site: Resolved
• CLI to list and retrieve service bindings & configs: Resolved
• limit conf filenames to exclude ".", make filetype the suffix: Resolved
• providers to publish registry information: Resolved
• change URL for published key-val pairs to .filetype, not /filetype: Resolved
• add a "self" publishing URL serving up an AM's registry entry: Resolved
• have a naming policy that handles users and app instances: Resolved
• add functional test for registry entries against hbase provider: Resolved
• registry CLI to return new NOT_FOUND exit code if there was no registry entry: Resolved
• PublishedConfiguration XML conf values are not resolved until client-side: Resolved
• registration data to allow for listing of ZK bindings: Resolved