...
ONAP Component | Life cycle phase | Enhancements |
---|
OOM - ONAP Central | Deploy | - Separate ONAP-edge Instance per 'edge domain', (ie., separate from onap-central instance, of course)
- Note: Independent of any Edge CP's Orchestration components.
- SP uses a central-OOM with a 'policy' for deployment of an onap-edge instance, e.g., xyz edge provider with abc components, etc.
- However, onap-edge instance can be 'lighter weight' with subset of components needed (per MVP discussed below)
- Desirable to managed as a separate K8s cluster (ie., separate from onap-central instance, of course) and, only for onap-edge use, ie., don't use for other 'workloads' like network apps or 3rd party apps
- Central OOM to deploy the following ONAP edge instance
- DMaaP with mirror capability
|
Multi-Cloud Deployment in Edge Cloud - Stretch Goal
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | MULTICLOUD-262 |
---|
|
Value:
- Multi-Cloud service to assist in central A&AI scaling by caching A&AI data locally and syncing up with A&AI periodically