On 08/12/2014 03:40 PM, Kashyap Chamarthy wrote: > On Mon, Aug 11, 2014 at 08:05:26AM -0400, Russell Bryant wrote: >> On 08/11/2014 07:58 AM, Russell Bryant wrote: >>> On 08/11/2014 05:53 AM, Daniel P. Berrange wrote: >>>> There is work to add support for this in devestack already which I >>>> prefer since it makes it easy for developers to get an environment >>>> which matches the build system: >>>> >>>> https://review.openstack.org/#/c/108714/ >>> >>> Ah, cool. Devstack is indeed a better place to put the build scripting. >>> So, I think we should: >>> >>> 1) Get the above patch working, and then merged. >>> >>> 2) Get an experimental job going to use the above while we work on #3 >>> >>> 3) Before the job can move into the check queue and potentially become >>> voting, it needs to not rely on downloading the source on every run. >>> IIRC, we can have nodepool build an image to use for these jobs that >>> includes the bits already installed. >>> >>> I'll switch my efforts over to helping get the above completed. >>> >> >> I still think the devstack patch is good, but after some more thought, I >> think a better long term CI job setup would just be a fedora image with >> the virt-preview repo. > > So, effectively, you're trying to add a minimal Fedora image w/ > virt-preview repo (as part of some post-install kickstart script). If > so, where would the image be stored? I'm asking because, previously Sean > Dague mentioned of mirroring issues (which later turned out to be > intermittent network issues with OpenStack infra cloud providers) of > Fedora images, and floated an idea whether an updated image can be > stored on tarballs.openstack.org, like how Trove does. But, OpenStack > infra folks (fungi) raised some valid points on why not do that. > > IIUC, if you intend to run tests w/ this CI job with this new image, > there has to be a mechanism in place to ensure the cached copy (on > tarballs.o.o) is updated. > > If I misunderstood what you said, please correct me.
Patches for this here: https://review.openstack.org/#/c/113349/ https://review.openstack.org/#/c/113350/ The first one is the important part about how the image is created. nodepool runs some prep scripts against the cloud's distro image and then snapshots it. That's the image stored to be used later for testing. In this case, it enables the virt-preview repo and then calls out to the regular devstack prep scripts to cache all packages needed for the test locally on the image. If there are issues with the reliability of fedorapeople.org, it will indeed cause problems, but at least it's local to image creation and not every test run. -- Russell Bryant _______________________________________________ OpenStack-dev mailing list OpenStackemail@example.com http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev