I like the swift/HTTP proposal.
In kayobe we've considered how to customise the deployment process, with
hook points [1] looking like the right approach.
Another possibility when deploy steps [2] land could be to break up the
ansible deployment into multiple steps, and allow each step to be
overridden.
[1] https://github.com/stackhpc/kayobe/issues/52
[2] https://review.openstack.org/#/c/412523/
On 31 January 2018 at 13:16, Dmitry Tantsur wrote:
> Hi all,
>
> I'd like to discuss one idea that came to me while trying to use the
> ansible deploy in TripleO.
>
> The ansible deploy interface is all about customization. Meaning, we
> expect people to modify the playbooks. I have two concerns with it:
>
> 1. Nearly any additions requires a full copy of the playbooks. Which will
> make the operators miss any future updates to the shipped version (e.g.
> from packages).
>
> 2. We require operators to modify playbooks on the hard drive in a
> location, available to ironic-conductor. This is inconvenient when there
> are many conductors and quite hairy with containers.
>
> So, what came to my mind is:
>
> 1. Let us maybe define some hook points in our playbooks and allow
> operators to overwrite only them? I'm not sure how it's going to look, so
> suggestions are welcome.
>
> 2. Let us maybe allow a swift or http(s) URL for the playbooks_path
> configuration? That will be a link to a tarball that will be unpacked by
> ironic to a temporary location before executing.
>
> What do you think?
>
> __
> 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
>
__
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
