oneagent installation is now bound to role 'controller' to check hotpluggable deployment of oneagent on controller ndoes

This commit is contained in:
Dirk Wallerstorfer 2016-12-08 12:49:22 +01:00
parent d72fbc96ea
commit 57cba10c81
3 changed files with 17 additions and 14 deletions

View File

@ -7,3 +7,6 @@
- name: additional_service:dynatrace
label: "Install Dynatrace"
description: "Installs Dynatrace in your OpenStack cluster"
compatible: []
requires: []
incompatible: []

View File

@ -1,5 +1,5 @@
- id: dynatrace-oneagent
role: [dynatrace-oneagent]
role: [primary-controller, controller]
type: puppet
version: 2.1.0
required_for: [post_deployment_end]

View File

@ -1,23 +1,23 @@
dynatrace-oneagent:
#dynatrace-oneagent:
# Role name
name: "Dynatrace OneAgent"
#name: "Dynatrace OneAgent"
# Role description
description: "Installs the Dynatrace OneAgent"
#description: "Installs the Dynatrace OneAgent"
# If primary then during orchestration this role will be
# separated into primary-role and role
has_primary: false
#has_primary: false
# Assign public IP to node if true
public_ip_required: false
#public_ip_required: false
# Weight that will be used to sort out the
# roles on the Fuel web UI
weight: 1000
conflicts:
- compute
- ceph-osd
- cinder
- base-os
- compute-vmware
- virtual
#weight: 1000
#conflicts:
# - compute
# - ceph-osd
# - cinder
# - base-os
# - compute-vmware
# - virtual
dynatrace-security-gateway:
# Role name