Add Group Management API proposal documentation

[gmuratk]

What type of PR is this?

Add one of the following kinds:

• enhancement/feature

What this PR does / why we need it:

See Issue #288 description and uploaded API Proposal template.

Which issue(s) this PR fixes:

Fixes #288

Special notes for reviewers:

Changelog input

 release-note
- API Proposal for Group Management

Additional documentation

This section can be blank.

docs

[hubertp-ericsson]

Thanks for this proposal. Looking at it from the perspective of Dedicated Networks APIs in CQM and the need for device groups I would like to better understand the intention with status and notifications. Is status a generic property to allow another service API to define its own states and state transitions or is the status rather to reflect the group membership status? Related question is whether the notifications are about group membership changes or status changes or both. There will anyway be a need for Service API specific properties on the group level and member level.

[gmuratk]

Hi @hubertp-ericsson ,
Thanks for the question. Along with many other questions this will need to be discussed during the design of the API. But as a quick response, 'status' in the context of the Group Management, will only apply to membership status and it is not intended as a 'generic' property. New Event Types will need to be defined for the Group Management domain only.

Service APIs (both Subscription and non-Subscription) will continue to have their domain specific event types, and states, which should maintain support for the currently defined events and support both single resource and multiple resource, and the list of events may be extended to handle partial success cases (e.g. such as subscription failing to be created for some of the members of the Group resource)