I'm having an idea of testing container images in OpenShift just after the container image itself is built&tested. For that we may use either `oc cluster up` or minishift, but installing both means to pull a lot of MB.
So, I'm thinking about whether it would make sense to have an option to request a machine with `oc` already available -- basically a machine where the openshift containers are already up and running.. and tests would only depend on `oc` being available.
Would something like that make sense for anybody else as well? And would the bandwidth saved for pulling the openshift images be worth it?
Honza
On 08/22/2017 04:55 AM, Brian Stinson wrote:
Hi Folks,
You're likely familiar with our node provisioner Duffy (https://wiki.centos.org/QaWiki/CI/Duffy).
In order to support new features, and encourage interested folks to participate in development with us, we are gathering requirements to get started soon on Duffy Version 2. Duffy2 will be developed with an OSS license, and posted in a public repository.
Some of you have pending RFEs that we'll deal with during development:
- Support Fedora Images (https://bugs.centos.org/view.php?id=13626)
- Support for cloud VMs in cloud.ci.centos.org
- Support for VLAN Isolation on the Seamicro hardware
- Support for extending an existing session (https://bugs.centos.org/view.php?id=9773)
If you have a feature request for us to track let's talk about it here.
If you're interested in participating in the development effort, please get in touch with me.
Happy Testing!
-- Brian Stinson CentOS CI Infrastructure Team _______________________________________________ Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users