From c8268da9b869a2374fb3b02a2b54a60b563eed65 Mon Sep 17 00:00:00 2001 From: John Trowbridge Date: Thu, 25 May 2017 13:42:53 +0000 Subject: [PATCH] Disable telemetry services in featureset001 Currently all of our jobs using this featureset fail due to OOM errors. By disabling telemetry services, we can free up a large chunk of memory on the overcloud nodes, allowing these jobs to pass again. Change-Id: Id022e57dfdffbabbf78ba9deb4481d2815e9ea66 Depends-On: Idefe9f0de47c5b0f29b7326642d697ed179e2eb8 Depends-On: I26b340ba13382df55b5ce178b208cef6bb3f2e75 --- config/general_config/featureset001.yml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/config/general_config/featureset001.yml b/config/general_config/featureset001.yml index 0ffbaa38c..bd5917a39 100644 --- a/config/general_config/featureset001.yml +++ b/config/general_config/featureset001.yml @@ -17,6 +17,11 @@ network_isolation_args: >- -e {{ tripleo_root }}/tripleo-ci/test-environments/network-templates/network-environment.yaml -e {{ tripleo_root }}/tripleo-ci/test-environments/net-iso.yaml +# This featureset is extremely resource intensive, so we disable telemetry +# in order to reduce the overall memory footprint +telemetry_args: >- + -e {{ overcloud_templates_path }}/environments/disable-telemetry.yaml + # Network settings external_interface: eth2 external_interface_ip: 10.0.0.1