Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On 07/12/2017 04:18 AM, Steve Baker wrote: On Wed, Jul 12, 2017 at 11:47 AM, James Slagle > wrote: On Tue, Jul 11, 2017 at 6:53 PM, Steve Baker > wrote: > > > On Tue,

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Wed, Jul 12, 2017 at 2:04 AM, Giulio Fidente wrote: > On 07/12/2017 01:53 AM, James Slagle wrote: > >> On Tue, Jul 11, 2017 at 5:53 PM, Steve Baker wrote: >> >>> >>> > >> What would be nice is when a heat->mistral->ansible upgrade step fails, >>> the

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On 07/12/2017 01:53 AM, James Slagle wrote: On Tue, Jul 11, 2017 at 5:53 PM, Steve Baker wrote: [...] I think its important that we allow full support for both mistral-driven and manually running playbooks. If there was no option to run ansible-playbook directly then

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Wed, Jul 12, 2017 at 11:47 AM, James Slagle wrote: > On Tue, Jul 11, 2017 at 6:53 PM, Steve Baker wrote: > > > > > > On Tue, Jul 11, 2017 at 6:51 AM, James Slagle > > wrote: > >> > >> On Mon, Jul 10, 2017 at 11:37 AM, Lars

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Tue, Jul 11, 2017 at 5:53 PM, Steve Baker wrote: > > > On Tue, Jul 11, 2017 at 3:37 AM, Lars Kellogg-Stedman > wrote: >> >> On Fri, Jul 7, 2017 at 1:50 PM, James Slagle >> wrote: >>> >>> There are also some ideas forming around

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Tue, Jul 11, 2017 at 6:53 PM, Steve Baker wrote: > > > On Tue, Jul 11, 2017 at 6:51 AM, James Slagle > wrote: >> >> On Mon, Jul 10, 2017 at 11:37 AM, Lars Kellogg-Stedman >> wrote: >> > On Fri, Jul 7, 2017 at 1:50 PM, James Slagle

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Tue, Jul 11, 2017 at 6:51 AM, James Slagle wrote: > On Mon, Jul 10, 2017 at 11:37 AM, Lars Kellogg-Stedman > wrote: > > On Fri, Jul 7, 2017 at 1:50 PM, James Slagle > wrote: > >> > >> There are also some ideas forming around

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Tue, Jul 11, 2017 at 3:37 AM, Lars Kellogg-Stedman wrote: > On Fri, Jul 7, 2017 at 1:50 PM, James Slagle > wrote: > >> There are also some ideas forming around pulling the Ansible playbooks >> > and vars out of Heat so that they can be rerun (or run

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On 07/10/2017 09:23 PM, James Slagle wrote: > On Mon, Jul 10, 2017 at 2:54 PM, Giulio Fidente wrote: >> On 07/10/2017 07:06 PM, James Slagle wrote: >>> On Mon, Jul 10, 2017 at 11:19 AM, Giulio Fidente >>> wrote: splitstack though requires changes

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

...@redhat.com] Sent: Monday, July 10, 2017 12:14 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [TripleO] Forming our plans around Ansible On Mon, Jul 10, 2017 at 6:19 AM, Steven Hardy <sha...@redhat.com> wrote: [...] > 1. How to perform e

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Fri, Jul 7, 2017 at 11:50 AM, James Slagle wrote: > I proposed a session for the PTG > (https://etherpad.openstack.org/p/tripleo-ptg-queens) about forming a > common plan and vision around Ansible in TripleO. > > I think it's important however that we kick this

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Mon, Jul 10, 2017 at 2:54 PM, Giulio Fidente wrote: > On 07/10/2017 07:06 PM, James Slagle wrote: >> On Mon, Jul 10, 2017 at 11:19 AM, Giulio Fidente wrote: >>> splitstack though requires changes in how the *existing* openstack >>> services are

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Mon, Jul 10, 2017 at 6:19 AM, Steven Hardy wrote: [...] > 1. How to perform end-to-end configuration via ansible (outside of > heat, but probably still using data and possibly playbooks generated > by heat) I guess we're talking about removing Puppet from TripleO and use

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On 07/10/2017 07:06 PM, James Slagle wrote: > On Mon, Jul 10, 2017 at 11:19 AM, Giulio Fidente wrote: >> On 07/10/2017 03:19 PM, Steven Hardy wrote: >>> On Fri, Jul 7, 2017 at 6:50 PM, James Slagle wrote: >> >> [...] >> >>> Yeah, I think the first

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Mon, Jul 10, 2017 at 11:37 AM, Lars Kellogg-Stedman wrote: > On Fri, Jul 7, 2017 at 1:50 PM, James Slagle wrote: >> >> There are also some ideas forming around pulling the Ansible playbooks >> >> and vars out of Heat so that they can be rerun (or run

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

I'll throw a second grenade in. Kayobe[1][2] is an OpenStack deployment tool based on kolla-ansible that adds sounds in some ways similar to what you're describing. It roughly follows the TripleO undercloud/overcloud model, with Bifrost used to deploy the overcloud. Kayobe augments kolla-ansible

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Mon, Jul 10, 2017 at 11:19 AM, Giulio Fidente wrote: > On 07/10/2017 03:19 PM, Steven Hardy wrote: >> On Fri, Jul 7, 2017 at 6:50 PM, James Slagle wrote: > > [...] > >> Yeah, I think the first step is to focus on a clean "split stack" >> model

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Mon, Jul 10, 2017 at 9:19 AM, Steven Hardy wrote: > On Fri, Jul 7, 2017 at 6:50 PM, James Slagle wrote: > Yeah so my idea with (4), and subsequent patches such as[1] is to > gradually move the deploy steps performed to configure services (on >

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

Hey, I'll just throw a grenade (pun intended) into your discussion - sorry! How about kolla-kubernetes? State awareness is done by kubernetes, it's designed for containers and we already have most of services ready and we'll be running ansible inside containers on top of k8s, for all the things

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Fri, Jul 7, 2017 at 1:50 PM, James Slagle wrote: > There are also some ideas forming around pulling the Ansible playbooks > and vars out of Heat so that they can be rerun (or run initially) > independently from the Heat SoftwareDeployment delivery mechanism: > I think

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On 07/10/2017 03:19 PM, Steven Hardy wrote: > On Fri, Jul 7, 2017 at 6:50 PM, James Slagle wrote: [...] > Yeah, I think the first step is to focus on a clean "split stack" > model where the nodes/networks etc are still deployed via heat, then > ansible handles the

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

That sounds like a good fit for an Ansible plugin to control how variables or host inventories are designed [1] and is the intended use case for extending Ansible behavior. [1]: http://docs.ansible.com/ansible/dev_guide/developing_plugins.html#vars-plugins David Moreau Simard Senior Software

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Sun, Jul 9, 2017 at 8:44 AM, Yolanda Robla Mota wrote: > What i'd like to dig more is how Ansible and Heat can live together. And > what features do Heat offer that are not covered by Ansible as well? Is > there still the need to have Heat as the main engine, or could that

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Fri, Jul 7, 2017 at 6:50 PM, James Slagle wrote: > I proposed a session for the PTG > (https://etherpad.openstack.org/p/tripleo-ptg-queens) about forming a > common plan and vision around Ansible in TripleO. > > I think it's important however that we kick this

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On 07/07/2017 07:50 PM, James Slagle wrote: > I proposed a session for the PTG > (https://etherpad.openstack.org/p/tripleo-ptg-queens) about forming a > common plan and vision around Ansible in TripleO. > > I think it's important however that we kick this discussion off more > broadly before the

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Fri, Jul 7, 2017 at 6:20 PM, James Slagle wrote: > On Fri, Jul 7, 2017 at 5:31 PM, David Moreau Simard > wrote: > > On Fri, Jul 7, 2017 at 1:50 PM, James Slagle > wrote: > >> (0) tripleo-quickstart which follows the common and

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

What i'd like to dig more is how Ansible and Heat can live together. And what features do Heat offer that are not covered by Ansible as well? Is there still the need to have Heat as the main engine, or could that be replaced by Ansible totally in the future? On Sat, Jul 8, 2017 at 12:20 AM, James

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Fri, Jul 7, 2017 at 5:31 PM, David Moreau Simard wrote: > On Fri, Jul 7, 2017 at 1:50 PM, James Slagle wrote: >> (0) tripleo-quickstart which follows the common and well accepted >> approach to bundling a set of Ansible playbooks/roles. > > I don't

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Fri, Jul 7, 2017 at 10:17 PM, James Slagle wrote: > On Fri, Jul 7, 2017 at 5:00 PM, Luke Hinds wrote: > > I can't offer much in-depth feedback on the pros and cons of each > scenario. > > My main point would be to try and simplify as much as we can,

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Fri, Jul 7, 2017 at 1:50 PM, James Slagle wrote: > (0) tripleo-quickstart which follows the common and well accepted > approach to bundling a set of Ansible playbooks/roles. I don't want to de-rail the thread but I really want to bring some attention to a pattern that

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Fri, Jul 7, 2017 at 5:00 PM, Luke Hinds wrote: > I can't offer much in-depth feedback on the pros and cons of each scenario. > My main point would be to try and simplify as much as we can, rather then > adding yet more tooling to the stack. At the moment ooo is spread across

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On Fri, Jul 7, 2017 at 6:50 PM, James Slagle wrote: > I proposed a session for the PTG > (https://etherpad.openstack.org/p/tripleo-ptg-queens) about forming a > common plan and vision around Ansible in TripleO. > > I think it's important however that we kick this

[openstack-dev] [TripleO] Forming our plans around Ansible

I proposed a session for the PTG (https://etherpad.openstack.org/p/tripleo-ptg-queens) about forming a common plan and vision around Ansible in TripleO. I think it's important however that we kick this discussion off more broadly before the PTG, so that we can hopefully have some agreement for