15:12:13 <sdoran> #startmeeting Ansible Core Public IRC Meeting https://github.com/ansible/community/issues/560
15:12:13 <zodbot> Meeting started Thu Sep 24 15:12:13 2020 UTC.
15:12:13 <zodbot> This meeting is logged and archived in a public location.
15:12:13 <zodbot> The chair is sdoran. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:12:13 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:12:13 <zodbot> The meeting name has been set to 'ansible_core_public_irc_meeting_https://github.com/ansible/community/issues/560'
15:12:45 <sdoran> felixfontein: Did you have anything you wanted to discuss today? There are a few other items on the agenda from you that it seems we haven't addressed yet.
15:12:56 <cyberpear> o/
15:17:21 <sdoran> #topic open floor
15:19:05 <resmo> Hi, I have a few minor things, unsure if this is the right meeting but anyways
15:20:14 <resmo> integration tests: historically we have a setup in ansible-test to set cloud apis, what is the plan with these?
15:20:48 <resmo> mainly https://github.com/ansible/ansible/tree/devel/test/lib/ansible_test/_internal/cloud
15:21:14 <sdoran> Hmm, let me look.
15:22:18 <sdoran> I don't think we have any plans to change that.
15:22:57 <sdoran> `ansible-test` is used for testing many community plugins and modules, so it will need to have the ability to work with different clouds.
15:23:48 <sdoran> So if changes need to be made to `ansible-test` to work with other cloud providers for the purpose of testing, then PRs should be made against the ansible/ansible repo.
15:24:06 <sdoran> I think that's what you were asking.
15:24:21 <resmo> this is probably a misunderstanding, it is not about to tests things on many clouds
15:24:35 <resmo> it's about to test cloud modules
15:24:57 <resmo> vultr cloud, hetzner cloud, cloudstack clouds... etc.
15:25:47 <sdoran> Right.
15:25:47 <resmo> so in our collection we bascially run an intergration tests with uses "ansible-test integratino" to bootstrap the setup.
15:26:25 <resmo> which comes from ansible-test
15:27:12 <resmo> with having distributed collections, having these in ansible.ansible looks not to be the right place anymore
15:28:01 <sdoran> I see what you're saying. We would have to make `ansible-test` pluggable in order to move that functionality elsewhere.
15:28:11 <resmo> exactly
15:28:17 <sdoran> We don't have any plans to do that currently.
15:28:39 <resmo> I see, it's not top prio for me but we should keep that in mind
15:28:57 <sdoran> It's probably worth opening an issue to explain the use case.
15:29:25 <sdoran> Currently our thinking is that changes to `ansible-test` need to happen in `ansible/ansible` and get released with `ansible-base` versions.
15:29:36 <sdoran> But I can see how that could be limiting.
15:29:58 <sdoran> Especially since we are slowing the release cadence of `ansible-base` a bit.
15:30:19 <sdoran> I would want mattclay to weigh in, which is why I suggested an issue may be helpful.
15:30:29 <sdoran> It's pretty early where he is and is not around.
15:30:42 <sdoran> Or I can just ask him when he's around later if you it's not worth writing up an issue.
15:31:01 <sdoran> s/you//
15:31:30 <resmo> agreed, I file an issue
15:31:35 <sdoran> Thanks!
15:52:11 <sdoran> Thank you everyone for attending today.
15:52:13 <sdoran> #endmeeting