-
Story
-
Resolution: Done
-
Medium
-
None
-
None
As a developer, I want to provide the necessary deployment instructions and document on the ONAP wiki (https://wiki.onap.org/ )so that I can deploy a SDN-C high availability environment.
In particular, I want the OOM/Kubernetes solution evaluated for use in a resilient (multi-cluster) SDNC deployment, with particular care to look at concerns in the following areas
- Data replication
- Starting order of processes, etc (recipes)
- Restarting dead instances (or starting new ones in their place)
- Retrying operations interrupted by an SDNC instance dying mid flight.
- Status reporting
- load balancer (enough to distribute requests)
I expect the output of this exercise to include
- Instructions for multi-cluster SDNC deployments in SDNC
- Kubernetes recipe files
- A capture of any evaluation results.
Exclusions
- Deploying new instances due to load
- blocks
-
OOM-543 SDNC adjust docker pullPolicy to IfNotPresent to speed up initial deployment slowdown introduced by SDNC-163
-
- Closed
-
- is blocked by
-
OOM-544 Long docker pulls cause timeouts on pod startup - make crashLoopRestart policy configurable/extended
-
- Closed
-
- relates to
-
OOM-66
SDNC Version 1.1 Deployed in Kubernetes
-
- Closed
-
-
OOM-101
Deploy SDNC on K8S cluster by TOSCA description
-
- Closed
-
-
-
- Closed
-
-
OOM-435
OOM Documentation for R2 - readthedocs.io
-
- Closed
-
-
-
- Closed
-
-
SDNC-6
Deploy a SDN-C high availability environment
-
- Closed
-
- links to
- mentioned in
-
Page Loading...
- Wiki Page
-