Hey folks, I wanted to highlight some of the discussion that was held at summit and outline goals for kolla-kubernetes in the Ocata cycle.
The number one goal for the kolla-kubernetes project in the Ocata cycle is to have a 1.0 release. As discussed at summit, the community is going to pursue Helm, the Kubernetes package manager, as the means for deployment. The goal is to have Helm fill the gap for orchestration that is challenging to solve with only native Kubernetes. Action items: - Spec outlining how the community will use Helm to fill the orchestration gap and any missing features with Helm. - POC using kolla-kubernetes with Helm For the Ocata cycle and beyond, the community needs to look at the interop between Kubernetes and OpenStack. In order for OpenStack to function best on Kubernetes, there needs to be features added to both Kubernetes and OpenStack. Since this project exists in both spaces, the community needs to be familiar with and identify areas for improvement in each. Action items: - Define the interop between Kubernetes and OpenStack community by mailing list or spec. Let's start with these action items to get things rolling post summit. Thanks, - Ryan The etherpads from Summit design sessions for further reading: https://etherpad.openstack.org/p/kolla-ocata-summit-kolla-k8s-architecture https://etherpad.openstack.org/p/kolla-ocata-summit-kolla-k8s-road-map Blueprints: https://blueprints.launchpad.net/kolla-kubernetes __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
