...
- Currently Kubespray is chosen to install K8S and related components.
Activities:
| Activity (Non ONAP related, but necessary to prove K8S plugin) | Owner | Status |
|---|---|---|
| Add K8S installation scripts | ||
| Add flannel installation scripts | ||
| Add OVN installation scripts | ||
| Add virtlet installation script | ||
| Prove deployment with EdgeXFoundry containers with flannel network | ||
| Prove deployment with one VM and container sharing flannel network | ||
| Prove deployment with one VM and container sharing CNI network | ||
| Add Multus CNI installation script | ||
| Prove deployment with one VM (firewall VM) and container (simple router container) sharing two networks (both from OVN) | ||
| Prove deployment with one VM and container sharing two networks (one from OVN and another from Flannel |
K8S Plugin development
| Activity | Owner | Status |
|---|---|---|
| K8S Plugin API definition towards rest of ONAP for compute | ||
| K8S Plugin API definition towards rest of ONAP for networking | ||
| K8S plugin API definition towards rest of ONAP for storage (May not be needed) | ||
| SO Simulator for compute | ||
| K8S plugin for compute | ||
| Testing with K8S reference deployment with hardcoded flannel configuration at the site (Using EdgeXFoundry) - Deployment yaml files to be part of K8S plugin (uploaded manually) | ||
| K8S Plugin implementation for OVN | ||
| SO simulator for network | ||
| Testing with K8S reference deployment with OVN networking (using EdgeXFoundry) | ||
| Testing with K8S reference deployment with OVN with VM and containers having multiple interfaces | ||
| K8S plugin - Artifact distribution Client to receive artifacts from SDC | ||
| Above test scenario without harcoding yaml files in K8S plugin |
Note: Once above list is decided, appropriate JIRA stories will be created.
FOLLOWING SECTIONS are YET TO BE UPDATED
...