Hi all, I'm very interested in what would be needed to get XenServer gated by the CI system. I've read the thread at http://lists.openstack.org/pipermail/openstack-infra/2013-April/000045.html - but unfortunately I wasn't a member of the infra list at the time so didn't follow up in real time. There were a number of options discussed, but it's not clear to me who has the next action in getting XenServer gated.
We are very pleased that XenServer is now back and being tested in SmokeStack (thanks mainly to Dan in fixing the puppet manifests), but as we all know this is not currently gating master and so I would like to understand the next steps in moving towards some form of gate in addition to (or using) the SmokeStack tests. Was there a consensus that the approach we should take for this is to improve SmokeStack's deployment so it can run on the existing CI infrastructure, or would the preferred approach be to set up tests which mirror the current CI system but running with the xenserver driver instead? I'd also like to find out if there is anyone else interested (perhaps Dan and Brian and someone from the existing team who can advise?) who I can work with on this to thrash out the steps to getting XenServer gating and figure out who is best placed to do each bit. Thanks, Bob
_______________________________________________ OpenStack-Infra mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
