On Aug 23 20:02, Murilo Opsfelder Araújo wrote:
On 08/22/2017 07:54 AM, Nigel Babu wrote:
These are things I'd love to see fixed:
- Request nodes in specific chasis, for instance, if we're trying to
test performance and want a continuous baseline.
- Given that Duffy v2 is going to be open source, is there going to be a
tiny focus on someone who's not CentOS CI being able to deploy it? (I'm happy to be involved to do this)
Automating the deployment of a Duffy server with Ansible would be nice too.
This should be handled by the client side of the house, cicoclient: https://github.com/CentOS/python-cicoclient
can provision using ansible, and we'll continue using cicoclient as our client reference implementation for duffy2.
If Duffy server can be deployed on a distro-agnostic box, that'd be even better.
Talking about distros, is there any plan to provision/serve non-rpm distros? My bet is no. I think that should be in mind just not to couple things on rpm only.
RPM distros are much easier for us, and we have enough folks requesting Fedora that I think we can consider doing that much.
Would a 'bring-your-own-image' scenario to provision openstack VMs be sufficient for this case?