[openstack-dev] [tripleo] Testing optional composable services in the CI
james.slagle at gmail.com
Tue Aug 16 20:49:35 UTC 2016
On Mon, Aug 15, 2016 at 4:54 AM, Dmitry Tantsur <dtantsur at redhat.com> wrote:
> Hi everyone, happy Monday :)
> I'd like to start the discussion about CI-testing the optional composable
> services in the CI (I'm primarily interested in Ironic, but I know there are
> a lot more).
> Currently every time we change something in an optional service, we have to
> create a DO-NOT-MERGE patch making the service in question not optional.
> This approach has several problems:
> 1. It's not usually done for global refactorings.
> 2. The current CI does not have any specific tests to check that the
> services in question actually works at all (e.g. in my experience the CI was
> green even though nova-compute could not reach ironic).
> 3. If something breaks, it's hard to track the problem down to a specific
> patch, as there is no history of gate runs.
> 4. It does not test the environment files we provide for enabling the
> So, are there any plans to start covering optional services? Maybe at least
> a non-HA job with all environment files included? It would be cool to also
> somehow provide additional checks though. Or, in case of ironic, to disable
> the regular nova compute, so that the ping test runs on an ironic instance.
There are no immediate plans. Although I think the CI testing matrix
is always open for discussion.
I'm a little skeptical we will be able to deploy all services within
the job timeout. And if we are, such a job seems better suited as a
periodic job than in the check queue.
The reason being is that there are already many different services
that can break TripleO, and I'd rather focus on improving the testing
of the actual deployment framework itself, instead of testing the
"whole world" on every patch. We only have so much capacity. For
example, I'd rather see us testing updates or upgrades on each patch
instead of all the services.
That being said, if you wanted to add a job that covered Ironic, I'd
at least start with adding a job in the experimental queue. If it
proves to be stable, we can always consider moving it to the check
-- James Slagle
More information about the OpenStack-dev