openstack
/
tripleo-quickstart
Code Issues Proposed changes

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
This commit is contained in:
John Trowbridge 2017-05-25 13:42:53 +00:00
parent 7c3fd05f98
commit c8268da9b8
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
config/general_config/featureset001.yml
View File

@ -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