On 24/08/17 01:43, Brian Stinson wrote: > On Aug 23 19:23, Brian Stinson wrote: >> 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. > > And of course, now I'm realizing that you may have meant deploying the duffy > service itself using ansible, in which case: also yes! We'll be opening up > the ansible roles we use in CICO to get duffy up and running. > tempted to just go openshift for duffy2 here, then its just a single manifest to apply ( and local instances can be either minishift or a 'oc cluster up' setup ) -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc