Summary

ICN v0.3.0 is released as a part of ICN R2 release after the major intermediate release ICN v0.1.0, v0.2.0.

what is released?

We're pleased to announce the delivery of Akraino ICN R2 release. Our Stable release v1.0.0 after 3 intermediate release. All the components are de-coupled and they can run standalone and they all integrated with ICN installation script.

components of the release (Akraino new)

The main themes of this release are:

Metal3 Provisioning script:  Metal3 IPMI provisioning script and de-provisioning script for bare-metal and Virtual deployment with IPMI LAN protocol support

Binary Provisioning agent(BPA) Operator: 

  • BPA operator is provision k8s cluster in Bare-metal and virtual deployment provisioned by metal3. BPA operator uses the metal3 information  
  • BPA operator provision nested K8s cluster(K8s cluster inside a VM maintained by  K8s). BPA manages k8s based VM under Cloud

Binary Provisioning agent(BPA) Rest API controller: Binary Provisioning agent Rest API controller runs as K8s service in the bootstrap cluster. Allow the user to upstream software, container images and OS images

Kubernetes deployment(KuD): KuD is the multi-cluster installer having 3 installation provision type to install k8s multi-cluster in Baremetal, VM and containerized solution. KUD is part of Multicloud-k8s project in ONAP. KUD is released with multiple components as folllows:

Software released and packaged with ICN:


Components

Link

Akraino Release

(ICN - v1.0.0)

Provision stack - Metal3

https://github.com/metal3-io/baremetal-operator/

R2

Host Operating system

Ubuntu 18.04

R2

NIC drivers

XL710 - https://www.intel.com/content/dam/www/public/us/en/documents/datasheets/xl710-10-40-controller-datasheet.pdf

R2

ONAP

https://git.onap.org/multicloud

R2

Workloads

OpenWRT SDWAN - https://openwrt.org/

R2

KUD

https://git.onap.org/multicloud/k8s/ 

R2

Kubespray

https://github.com/kubernetes-sigs/kubespray v2.10.4

R2

K8s

https://github.com/kubernetes/kubeadm - v1.14

R2

Docker

https://github.com/docker - 18.09

R2

Virtlet

https://github.com/Mirantis/virtlet -1.4.4

R2

SDN - OVN

https://github.com/ovn-org/ovn-kubernetes - 0.3.0

R2

OpenvSwitch

https://github.com/openvswitch/ovs - 2.10.1

R2

Ansible

https://github.com/ansible/ansible - 2.7.10

R2

Helm

https://github.com/helm/helm - 2.9.1

R2

Istio

https://github.com/istio/istio - 1.0.3

R2

Rook/Ceph

https://rook.io/docs/rook/v1.0/helm-operator.html v1.0

R2

MetalLB

https://github.com/danderson/metallb/releases - v0.7.3

R2

Device Pluginshttps://github.com/intel/intel-device-plugins-for-kubernetes - SRIOVR2

Node Feature Discovery

R2

CNI

https://github.com/coreos/flannel/ - release tag v0.11.0

https://github.com/containernetworking/cni - release tag v0.7.0

https://github.com/containernetworking/plugins - release tag v0.8.1

https://github.com/containernetworking/cni#3rd-party-plugins - Multus v3.3tp, SRIOV CNI v2.0( with SRIOV Network Device plugin)

R2

dependencies of the release (upstream version, patches)

ICN BP depends on all software version in the table Software released and packaged with ICN:

Upgrade Procedures

not applicable

Release Data

TBD

Enhancements

Functionality changes

not applicable

New Features

not applicable

Version change

Module version changes

not applicable

Document Version Changes

not applicable

Deliverable

Software Deliverable

ICN repo is available here: ICN repo

Documentation Deliverable

versionDocuments nameAuthorslast update
v1.0ICN Architecture DocumentICN Contributors

 

v1.0ICN Installation GuideICN Contributors

 

v1.0ICN Release Notes for ICNICN Contributors

 

v1.0ICN Test DocumentICN Contributors

 

Document Version Changes

VersionAuthorsData released
v1.0ICN Contributors

 

v2.0ICN Contributors

 

Fixed Issues and Bugs

Issues are captured  here- ICN fixed Issues and Bugs

Known Limitations, Issues and Workarounds

System Limitations

ICN BP works on Ubuntu 18.04

Known Issues

IssuesDescription

ICN-173 - Getting issue details... STATUS

  • The BPA operator does not throw an error if the same MAC address is specified in multiple provisioning CR and so this will cause a failure or interfere with an already provisioned cluster.
MULTICLOUD-879add CMK support in multicloud/k8s KuD

Workarounds

no work appliable

References

  • No labels