Open Stack

Hi.

IMO, you should add a BP and start by adding a v2 driver in /contrib.

Cheers,
Spyros

On Jan 24, 2017 20:44, "Kevin Lefevre" <lefevre.kevin at gmail.com> wrote:

> Hi,
>
> The CoreOS template is not really up to date and in sync with upstream
> CoreOS « Best Practice » (https://github.com/coreos/coreos-kubernetes),
> it is more a port of th fedora atomic template but CoreOS has its own
> Kubernetes deployment method.
>
> I’d like to implement the changes to sync kubernetes deployment on CoreOS
> to latest kubernetes version (1.5.2) along with standards components
> according the CoreOS Kubernetes guide :
>   - « Defaults » add ons like kube-dns , heapster and kube-dashboard
> (kube-ui has been deprecated for a long time and is obsolete)
>   - Canal for network policy (Calico and Flannel)
>   - Add support for RKT as container engine
>   - Support sane default options recommended by Kubernetes upstream
> (admission control : https://kubernetes.io/docs/
> admin/admission-controllers/, using service account…)
>   - Of course add every new parameters to HOT.
>
> These changes are difficult to implement as is (due to the fragment
> concept and everything is a bit messy between common and specific template
> fragment, especially for CoreOS).
>
> I’m wondering if it is better to clone the CoreOS v1 template to a new v2
> template en build from here ?
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170124/6ab18b19/attachment.html>