Hi Martin,On Mon, 2018-09-03 at 21:16 +0200, Martin Magr wrote: > Gretings, > > since I did not find any blueprint regarding proper usage of > tripleo-ansible, I would like to ask how exactly we plan to use > tripleo-ansible project, what should be the proper structure of > roles/playbooks, etc. Given the discussion in [1] it is the best place > for backup and restore playbooks and I'd like to start preparing > patches for B&R. Currently the development being done in [2], but I > hope that is only temporary location.
I've added the backup task example to the ansible roles blueprint[0]. Generally you'll want to add your tasks, variables, role-specific handlers, etc to the appropriate ansible role repo (in this case ansible-role-openstack-operations) and the playbooks for using those role tasks to the tripleo-ansible project repo. TripleO-specific shared handlers/libraries/etc - things your playbooks will use that are not specific to one single role - would also go in the tripleo-ansible repo. [0] https://blueprints.launchpad.net/tripleo/+spec/ansible-tasks-to-role > > Thanks in advance for answers, > Martin > > [1] https://review.openstack.org/#/c/582453/ > [2] https://github.com/centos-opstools/os-backup-ansible > > -- > Martin Mágr > Senior Software Engineer > Red Hat Czech > ______________________________________________________________________ > ____ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubsc > ribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
signature.asc
Description: This is a digitally signed message part
__________________________________________________________________________ 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
