On Thu, Jun 19, 2014 at 09:20:14AM -0600, Kevin Fenzi wrote:
On Thu, 19 Jun 2014 00:24:55 +0530
Kashyap Chamarthy <kchamart(a)redhat.com> wrote:
> [I'm not subscribed to this list, please keep me in CC.]
> A little while ago, we (Matthew Miller, myself, Attila Fazekas
> (upstream OpenStack developer) had an IRC discussion (on
> #openstack-qa, Freenode) with OpenStack upstream CI infrastructure
> folks about their concerns for continuing to have Fedora as a default
> to run as CI voting guest (Nova instance). They (mostly Sean Dague -
> a major upstream OpenStack contributor who voiced these) outlined a
> few issues:
I'm not famillar with the terminology, what does a 'voting guest' mean?
Sorry for being unclear. It means, any proposed OpenStack change/patch
has to be executed on a Fedora virtual machine too, only once it passes
the tests on Fedora, patches will be merged to upstream git. I cc'd
Attila, he can correct me if I said something wrong.
> 1. It's not possible to download from the fedora infrastructure
> reliably - 10% failure rate from their cloud providers (HP and
> - About this point, when mattdm inquired - "is the failure in
> hitting the fedora mirrors or fedora core infrastructure?",
> their response - "I don't fully know, I think going through
> the url we are using we get bounced to mirrors".
Yeah, more data would be very nice here... what url(s) they are using,
what error codes if any they get back?
Looking at the script that creates the CI VM, it uses this URL --
Are these the released cloud images? f19/20? Or nightlies or ?
Released, official images.
How often do they download? Once a image is loaded, I am not sure
they would re-download it unless it's changed?
I just confirmed, they (CI infra) download and cache it. But, once every
24 hours, they rebuild the caches. It's the humans that download it
manually (without any caching environment) that face the bottlenecks
Or unless they are
grabbing nightly rawhide images?
They won't prefer to do this as only distribution tested image will be
used used in OpenStack CI environment.
> 2. There are possibly issues with the normal upstream fedora
> that could be fixed with custom respin.
> - NOTE: I'm doubtful of this idea, as existing Fedora cloud
> images itself are not really extensively tested. I'd think focusing on
> _official_ cloud images and having a solid set of tests so
> that it can be consumed by cloud projects (OpenStack, etc).
> - Having a custom respin means that we're off the main path for
> testing of the image -- which again needs _some_ level of
> assurance that it can be used in a higher-level cloud
> project's CI infr- which again needs _some_ level of assurance that
> it can be used in a higher-level cloud project's CI infra.
Yeah, I would think we would like to avoid that... and try and merge in
the changes they need for images instead of them going and making their
own that only they use.
Oh, it's my poor wording, they didn't mean to say _they'd_ create these
custom images. OpenStack infra is clear - they'd only use reasonably
well-tested imges from Distributions.
> 3. Another important point OpenStack infra folks emphasized is
> these images will get 4000 test runs a week on them
> Any suggestions to allay these are welcome.
Happy to try and solve any bottlenecks they are having...
Yeah, folks are testing more than ever with Fedora lately.
OpenStack infra/qa folks have an upcoming meet up discuss several,
Fedora is also on their topic. Will let you know if they provide more
specific, technical feedback from OpenStack infra.