Open Stack

On Mon, Jul 10, 2017 at 11:19 AM, Giulio Fidente <gfidente at redhat.com> wrote:
> On 07/10/2017 03:19 PM, Steven Hardy wrote:
>> On Fri, Jul 7, 2017 at 6:50 PM, James Slagle <james.slagle at gmail.com> 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 configuration of the nodes.
>
> +1
>
> as per my previous email, if splitstack was available we might have been
> able to use that for the ceph-ansible integration : "if we had migrated
> to splitstack already, it might have been possible"

Can you expand on what isn't available? I've primarily been the one
working on different parts of splitstack, and I'm not sure what it
can't do that you need it to do :).

>
> splitstack though requires changes in how the *existing* openstack
> services are deployed and we didn't want to do that just for the purpose
> of integrating ceph-ansible so I still believe (3) to be a sensible
> compromise to provide the needed functionalities and not breaking the
> existing deployment logic

We might be talking about different definitions of "splitstack", as
I'm not sure what changes are required for existing services. FWIW, I
refer to what we do in CI with multinode to be splitstack in that the
nodes are already provisioned and we deploy the services on those
nodes using the same templates that we do for a "full" stack.

Those nodes could have just as easily been provisioned with our
undercloud and the services deployed using 2 separate stacks, and that
model works just as well.

-- 
-- James Slagle
--