canonical-ci-engineering team mailing list archive

[Celso Providelo <celso.providelo@xxxxxxxxxxxxx>]

On Tue, May 26, 2015 at 3:30 AM, Martin Pitt <martin.pitt@xxxxxxxxxx> wrote:

[snip]

> However, in terms of prioritization this is by far not urgent. The
> current numerous problems that we have with our CI autopkgtest cloud
> infrastructure are far more important/urgent: missing support for all
> architectures except amd64, a *lot* slower, no daily base images, they
> don't dynamically scale, inefficient controller vs. testbed
> allocation, not using ScalingStack, the layout of results in swift got
> totally broken, we still use Jenkins in between, frequent failures to
> start tests.
>
> So, respectfully, can we address the current problems in the
> infrastructure first before we start working on new things like test
> classes, regularly running those, and changing tests to work offline
> (or, in a lot of cases, just disabling them)?

Martin,

I've just split this thread so we can organise and discuss your
concerns about adt-cloud separately from the internet-access-for-tests
endless epic.

I think we should clarify what are actual *problems* (read
bugs/regressions) and what are missing features and future work. Those
are very different things with different priorities and I am quite
certain we agree on this.

I am particularly interested in your point about adt-cloud being a
'lot' slower that qemu-VMs, specially in backing it up with (rough)
data we already collect in jenkins:

http://d-jenkins.ubuntu-ci:8080/label/adt&&i386/load-statistics?type=hour
http://d-jenkins.ubuntu-ci:8080/label/adt&&amd64/load-statistics?type=hour

Can we schedule a hangout/meeting to discuss these in details and
establish a common view about the current solution status ?

[]


-- 
Celso Providelo
celso.providelo@xxxxxxxxxxxxx