On 14.07.2017 18:16, Fox, Kevin M wrote: > https://xkcd.com/927/ > > I don't think adopting helm as a dependency adds more complexity then writing > more new k8s object deployment tooling? > > There are efforts to make it easy to deploy kolla-kubernetes microservice > charts using ansible for orchestration in kolla-kubernetes. See: > https://review.openstack.org/#/c/473588/ > What kolla-kubernetes brings to the table is a tested/shared base k8s object > layer. Orchestration is done by ansible via TripleO, and the solutions > already found/debugged to how to deploy OpenStack in containers on Kubernetes > can be reused/shared. > > See for example: > https://github.com/tripleo-apb/ansible-role-k8s-keystone/blob/331f405bd3f7ad346d99e964538b5b27447a0ebf/provision-keystone-apb/tasks/main.yaml > > I don't see much by way of dealing with fernet token rotation. That was a > tricky bit of code to get to work, but kolla-kubernetes has a solution to it. > You can get it by: helm install kolla/keystone-fernet-rotate-job. > > We designed this layer to be shareable so we all can contribute to the > commons rather then having every project reimplement their own and have to > chase bugs across all the implementations. The deployment projects will be > stronger together if we can share as much as possible.
Thank you Kevin, this ^^ expresses my thoughts better than I could ever say. > > Please reconsider. I'd be happy to talk with you more if you want. > > Thanks, > Kevin -- Best regards, Bogdan Dobrelya, Irc #bogdando __________________________________________________________________________ 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
