[openstack-ansible][tripleo] creating collaborative acl
Hi everyone, I briefly brought this up in the TripleO Ansible meeting however there seems to be more work happening together on OpenStack Ansible roles from the TripleO side (alongside cross-project gating, which is awesome!) Having said that, it seems like we're building more of an upstream relationship to TripleO but I think there is a lot of benefit of making it more of a collaboration between the teams. Therefore, I'd like to propose that we create a Gerrit group called "openstack-ansible-collab". This ACL will be seeded with tripleo-ansible-core and openstack-ansible-core and it will ideally be placed on two initial repositories: - openstack/ansible-config_template - openstack/ansible-role-python_venv_build - openstack/openstack-ansible-os_tempest Those are repositories that are actively being used by TripleO and they are even getting CI tested from TripleO. They make the most sense to start with. TripleO has been around for a while and they have a solid core team that I (personally) feel okay with having core to those repos for now (and more as we work on them together). In terms of governance, these projects will remain under OpenStack-Ansible governance. Please let me know what you think of this proposal? Thanks, Mohammed
On Thu, Jul 18, 2019 at 10:17 AM Mohammed Naser <mnaser@vexxhost.com> wrote:
Hi everyone,
I briefly brought this up in the TripleO Ansible meeting however there seems to be more work happening together on OpenStack Ansible roles from the TripleO side (alongside cross-project gating, which is awesome!)
Having said that, it seems like we're building more of an upstream relationship to TripleO but I think there is a lot of benefit of making it more of a collaboration between the teams. Therefore, I'd like to propose that we create a Gerrit group called "openstack-ansible-collab".
This ACL will be seeded with tripleo-ansible-core and openstack-ansible-core and it will ideally be placed on two initial repositories:
- openstack/ansible-config_template - openstack/ansible-role-python_venv_build - openstack/openstack-ansible-os_tempest
We need to be careful about tripleo-ansible-core, it's actually including all TripleO cores: https://review.opendev.org/#/admin/groups/448,members We usually trust ourselves enough to not merge things we're not comfortable with but if that doesn't work for you, we can remove that group inclusion and select a group of people to add in tripleo-ansible-core.
Those are repositories that are actively being used by TripleO and they are even getting CI tested from TripleO. They make the most sense to start with. TripleO has been around for a while and they have a solid core team that I (personally) feel okay with having core to those repos for now (and more as we work on them together).
In terms of governance, these projects will remain under OpenStack-Ansible governance. Please let me know what you think of this proposal?
I don't think it's a problem, +1. Thanks for the great proposal! -- Emilien Macchi
On 18/07/2019 16.09, Mohammed Naser wrote:
Hi everyone,
I briefly brought this up in the TripleO Ansible meeting however there seems to be more work happening together on OpenStack Ansible roles from the TripleO side (alongside cross-project gating, which is awesome!)
Having said that, it seems like we're building more of an upstream relationship to TripleO but I think there is a lot of benefit of making it more of a collaboration between the teams. Therefore, I'd like to propose that we create a Gerrit group called "openstack-ansible-collab".
This ACL will be seeded with tripleo-ansible-core and openstack-ansible-core and it will ideally be placed on two initial repositories:
- openstack/ansible-config_template - openstack/ansible-role-python_venv_build - openstack/openstack-ansible-os_tempest
Why not add triploe-core as group to the existing ACLs? Andreas -- Andreas Jaeger aj@suse.com Twitter: jaegerandi SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg GF: Nils Brauckmann, Felix Imendörffer, Enrica Angelone, HRB 247165 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Thu, Jul 18, 2019 at 8:31 AM Andreas Jaeger <aj@suse.com> wrote:
On 18/07/2019 16.09, Mohammed Naser wrote:
Hi everyone,
I briefly brought this up in the TripleO Ansible meeting however there seems to be more work happening together on OpenStack Ansible roles from the TripleO side (alongside cross-project gating, which is awesome!)
Having said that, it seems like we're building more of an upstream relationship to TripleO but I think there is a lot of benefit of making it more of a collaboration between the teams. Therefore, I'd like to propose that we create a Gerrit group called "openstack-ansible-collab".
This ACL will be seeded with tripleo-ansible-core and openstack-ansible-core and it will ideally be placed on two initial repositories:
- openstack/ansible-config_template - openstack/ansible-role-python_venv_build - openstack/openstack-ansible-os_tempest
Why not add triploe-core as group to the existing ACLs?
The goal isn't necessarily to add tripleo-core, but rather tripleo-ansible-core. It just so happens that tripleo-ansible-core contains tripleo-core at the moment. We might want to add folks to tripleo-ansible but not tripleo-core. I think tripleo-ansible-core is the correct group in this case. We'll probably want to evaluate how we're doing this now that it'll be reused.
Andreas -- Andreas Jaeger aj@suse.com Twitter: jaegerandi SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg GF: Nils Brauckmann, Felix Imendörffer, Enrica Angelone, HRB 247165 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On 2019-07-18 10:09:44 -0400 (-0400), Mohammed Naser wrote: [...]
two initial repositories:
- openstack/ansible-config_template - openstack/ansible-role-python_venv_build - openstack/openstack-ansible-os_tempest
[...] I see that you, like any proper computer scientist, always count from zero. ;)
In terms of governance, these projects will remain under OpenStack-Ansible governance. Please let me know what you think of this proposal?
This is awesome; I'm thrilled to see another good example of cross-project collaboration surfacing in the community! -- Jeremy Stanley
On Thu, 2019-07-18 at 10:09 -0400, Mohammed Naser wrote:
(snipped) Therefore, I'd like to propose that we create a Gerrit group called "openstack-ansible-collab".
Not sure we need to create yet another group (if we are using groups it's easy to just use existing groups), but it's fine for me if you prefer.
TripleO has been around for a while and they have a solid core team that I (personally) feel okay with having core to those repos for now (and more as we work on them together).
Fine for me. In fact, it's not just "fine". It's great to have more cores! :)
In terms of governance, these projects will remain under OpenStack-Ansible governance. Please let me know what you think of this proposal?
OK. Regards, Jean-Philippe (evrardjp)
participants (6)
-
Alex Schultz
-
Andreas Jaeger
-
Emilien Macchi
-
Jean-Philippe Evrard
-
Jeremy Stanley
-
Mohammed Naser