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've tried to follow the guide [1] for adding RDO packages and the package review [2] and didn't succeed. There should be a simpler solution to host a package somewhere outside of RDO, and being able to add it for an external deployment managed by tripleo. My 2c.

[0] https://github.com/kubernetes-incubator/kubespray
[1] https://www.rdoproject.org/documentation/add-packages/
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1482524

available and packaged in RDO. I'll then look into the actual TripleO composable service.

Any input and contributions are welcome!

[1] https://github.com/JAORMX/tripleo-ipsec

--
Juan Antonio Osorio R.
e-mail: jaosor...@gmail.com <mailto:jaosor...@gmail.com>


__________________________________________________________________________
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



--
Best regards,
Bogdan Dobrelya,
Irc #bogdando

__________________________________________________________________________
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

Reply via email to