Open Stack

On Fri, Nov 17, 2017 at 10:27 AM, Bogdan Dobrelya <bdobreli at redhat.com> wrote:
> On 11/16/17 8:01 AM, Juan Antonio Osorio wrote:
>>
>> Hello folks!
>>
>> A few months ago Dan Sneddon and me worked in an ansible role that would
>> enable IPSEC for the overcloud [1]. Currently, one would run it as an extra
>> step after the overcloud deployment. But, I would like to start integrating
>> it to TripleO itself, making it another option, probably as a composable
>> service.
>>
>> For this, I'm planning to move the tripleo-ipsec ansible role repository
>> under the TripleO umbrella. Would that be fine with everyone? Or should I
>> add this ansible role as part of another repository? After that's
>
>
> This looks very similar to Kubespray [0] integration case. I hope that
> external deployments bits can be added without a hard requirement of being
> under the umbrella and packaged in RDO.

I don't have a strong opinion on it being under the TripleO umbrella
or not, but I agree with Bogdan that I think this could be a good fit
for the external_deploy_tasks interface that kubespray is currently
also consuming. You may find that is an easier way of consuming the
standalone Ansible roles you've already done as opposed to trying to
make those fit into the composable services framework that uses t-h-t
in tree Ansible tasks.


-- 
-- James Slagle
--