[openstack-dev] [tripleo] Updates on the TripleO on Kubernetes work

Dan Prince dprince at redhat.com
Thu Nov 30 15:33:56 UTC 2017

On Thu, Nov 16, 2017 at 11:56 AM, James Slagle <james.slagle at gmail.com>
> When we consume these ansible-role-k8s-* roles from t-h-t, I think
> that should be a stepping stone towards migrating away from having to
> use Heat to deploy and configure those services. We know that these
> new ansible roles will be deployable standalone, and the interface to
> do that should be typical ansible best practices (role defaults, vars,
> etc).
> We can offer a mechanism such that one can migrate from a
> tripleo-heat-templates/docker/services/database/mysql.yaml deployed
> mariadb to one deployed via
> ansible-role-k8s-mariadb. The config-download mechanism could be
> updated to generate or pull from Heat the necessary ansible vars files
> for configuring the roles. We should make sure that the integration
> with tripleo-heat-templates results in the same inputs/outputs that
> someone would consume if using the roles standalone. Future iterations
> would then not have to require Heat for that service at all, unless
> the operator wanted to continue to configure the service via Heat
> parameters/environments.
> What I'm trying to propose is a path towards deprecating the Heat
> parameter/environment driven and hieradata driven approach to
> configuring the services. The ansible-role-k8s-* roles should offer a
> new interface, so I don't think we have to remain tied to Heat
> forever, so we should consider what we want the long term goal to be
> in an ideal world, and take some iterative steps to get there.

I like the idea of a leaner set of deployment tooling very much. I think we
are to the point where we need to consider "clean rooming" some things.

That said in moving towards a new interface like you talk about I think we
do have to have feature parity with things like composability and parameter
validation. Otherwise we are going to break things we currently rely on in
our high level (Mistral) deployment workflow. Specifically, I've yet to see
something that would give us the nested parameter validations we leverage
from Heat.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20171130/ed09d395/attachment.html>

More information about the OpenStack-dev mailing list