Re: [openstack-dev] [goal][python3] week 3 update
On Wed, Aug 29, 2018 at 1:02 PM Doug Hellmann wrote: > Excerpts from Doug Hellmann's message of 2018-08-29 09:50:58 -0400: > > Excerpts from David Peacock's message of 2018-08-29 08:53:26 -0400: > > > On Mon, Aug 27, 2018 at 3:38 PM Doug Hellmann > wrote: > > > > > > > If your team is ready to have your zuul settings migrated, please > > > > let us know by following up to this email. We will start with the > > > > volunteers, and then work our way through the other teams. > > > > > > > > > > TripleO team is ready to participate. I'll coordinate on our end. > > > > I will generate the patches today and watch for a time when the CI load > > is low to submit them. > > > > Doug > > > > It appears that someone who is not listed as a goal champion has > already submitted a bunch of patches for importing the zuul settings > into the TripleO repositories without updating our tracking story. > The keystone team elected to abandon a similar set of patches because > some of them were incorrect. I don't know whether that applies to > these. > > Do you want to review the ones that are open, or would you like for me > to generate a new batch? > > Doug > Please would you mind pasting me the reviews in question, then I'll take a look and let you know which direction. Thanks! > > __ > 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 > __ 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
Re: [openstack-dev] [goal][python3] week 3 update
On Mon, Aug 27, 2018 at 3:38 PM Doug Hellmann wrote: > If your team is ready to have your zuul settings migrated, please > let us know by following up to this email. We will start with the > volunteers, and then work our way through the other teams. > TripleO team is ready to participate. I'll coordinate on our end. __ 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
[openstack-dev] [TripleO] Prototyping dedicated roles with unique repositories for Ansible tasks in TripleO
Hi everyone, During the recent PTG in Dublin, it was decided that we'd prototype a way forward with Ansible tasks in TripleO that adhere to Ansible best practises, creating dedicated roles with unique git repositories and RPM packaging per role. With a view to moving in this direction, a couple of us on the TripleO team have begun developing tooling to facilitate this. Initially we've worked on a tool [0] to extract Ansible tasks lists from tripleo-heat-templates and move them into new formally structured Ansible roles. An example with the existing keystone docker service [1]: The upgrade_tasks block will become: ``` upgrade_tasks: - import_role: name: tripleo-role-keystone tasks_from: upgrade.yaml ``` The fast_forward_upgrade_tasks block will become: ``` fast_forward_upgrade_tasks: - import_role: name: tripleo-role-keystone tasks_from: fast_forward_upgrade.yaml ``` And this role [2] will be structured: ``` tripleo-role-keystone/ └── tasks ├── fast_forward_upgrade.yaml ├── main.yaml └── upgrade.yaml ``` We'd love to hear any feedback from the community as we move towards this. Thank you, David Peacock [0] https://github.com/davidjpeacock/openstack-role-extract/blob/master/role-extractor-creator.py [1] https://github.com/openstack/tripleo-heat-templates/blob/master/docker/services/keystone.yaml [2] https://github.com/davidjpeacock/tripleo-role-keystone __ 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
