forked from jasonkeene/docs-rabbitmq-staging
-
Notifications
You must be signed in to change notification settings - Fork 0
/
expert-override-config.html.md.erb
126 lines (98 loc) · 6.15 KB
/
expert-override-config.html.md.erb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
---
title: Expert Mode: Overriding RabbitMQ Server Configuration
owner: RabbitMQ
---
This topic explains how to override the configuration set by the broker on RabbitMQ service instances.
For more information about the RabbitMQ configuration, see the
[RabbitMQ documentation](https://www.rabbitmq.com/configure.html).
<p class='note warning'>
<strong>Warning:</strong>
This feature is for expert users only. Any override configuration set on the RabbitMQ
cluster might conflict with other configurations set by the <%= vars.product_short %> broker.
Any invalid configuration set through an override causes a deployment to fail.<br><br>
VMware recommends that you thoroughly test any configuration you plan to apply through an override
on a test environment, and use this feature with caution.
</p>
## <a id='overview'></a> Overview
On RabbitMQ service instances, the <%= vars.product_short %> broker applies and maintains
configuration on the RabbitMQ server.
You can override this configuration, or provide your own additional configuration to apply on the
RabbitMQ service instance.
This configuration takes priority over any set by the <%= vars.product_short %> broker and is applied
last on the server.
Depending on which service offering you are using, you must provide the configuration in either the
newer sysctl-style configuration format or the older Erlang-style format. Where possible, use the
newer format. For more information, see the
[RabbitMQ documentation](https://www.rabbitmq.com/configure.html#config-file-formats).
## <a id='applying'></a> Apply the Override Configuration
Both the on-demand and pre-provisioned service offering support overriding the instance configuration.
### <a id='applying-od'></a> Override Configuration for On-Demand
To provide override configuration on a per-plan basis for on-demand service plans:
1. Navigate to the <%= vars.product_short %> tile in <%= vars.ops_manager %>.
1. Select the on-demand plan you want to provide override configuration for from the sidebar.
Any service instances created under this plan will have this override configuration applied to them.
1. In on-demand, you can provide override configuration in sysctl-style or Erlang-style config format.
* **To provide configuration in the newer sysctl-style format:**
1. Paste the configuration into the **Expert Mode: Override Server Config** field.
You can make this configuration a multiline string if you require multiple configuration items.
<%= image_tag("images/override-config-od.png",
:alt => "Screenshot of the 'Expert Mode: Override Server Config' field. The field contains a multiline string; the lines are 'management.rates_mode = detailed', 'management.ssl.ciphers.1 = ECDHE-ECDSA-AES256-GCM-SHA384' and 'management.ssl.ciphers.2 = ECDHE-RSA-AES256-GCM-SHA384'") %>
1. Click **Save**.
* **To provide configuration in the older Erlang-style format:**
1. Encode the configuration as a base64 string.
For example, to provide the same config as above in the older format, you can do so on Linux
by running:
```
echo -n '[
{rabbitmq_management, [
{rates_mode, detailed},
{ssl_options, [
{ciphers, [
"ECDHE-ECDSA-AES256-GCM-SHA384",
"ECDHE-RSA-AES256-GCM-SHA384"
]}
]}
]}
].' | base64
WwogIHtyYWJiaXRtcV9tYW5hZ2VtZW50LCBbCiAgICB7cmF0ZXNfbW9kZSwgZGV0YWlsZWR9LAogICAge3NzbF9vcHRpb25zLCBbCiAgICAgIHtjaXBoZXJzLCBbCiAgICAgICAgIkVDREhFLUVDRFNBLUFFUzI1Ni1HQ00tU0hBMzg0IiwKICAgICAgICAiRUNESEUtUlNBLUFFUzI1Ni1HQ00tU0hBMzg0IgogICAgICBdfQogICAgXX0KICBdfQpdLg==
```
1. Paste this base64-encoded config into the **Expert Mode: Override Server Advanced Config** field.
<%= image_tag("images/override-adv-config-od.png",
:alt => "Screenshot of the 'Expert Mode: Override Server Advanced Config' field.
The field contains a base64 encoded configuration that begins with the characters 'WwogIHty'.") %>
1. Click **Save**.
After applying changes, new service instances using this plan implement this new configuration.
Existing service instances implement the configuration after they are upgraded.<br><br>
You can provide both sysctl-style and Erlang term-style configuration for an on-demand service
plan. Where the same configuration is set in both, the Erlang term-style config takes
priority.<br><br>
For example, if you set the `rates_mode` property above to `detailed` in the
**Override Server Config** and `none` in the **Override Advanced Server Config**, the resultant
server takes the `none` value.
### <a id='applying-pp'></a> Override Configuration for Pre-Provisioned
In pre-provisioned, to set configuration on all service instances:
1. Navigate to the <%= vars.product_short %> tile in <%= vars.ops_manager %>.
1. Select **Pre-Provisioned RabbitMQ** from the sidebar.
1. Encode your desired config as a base64 string. The pre-provisioned service offering only supports
the older Erlang-style format of override configuration.
For example, you can do this on Linux by running:
```
echo -n '[
{rabbitmq_management, [
{rates_mode, detailed},
{ssl_options, [
{ciphers, [
"ECDHE-ECDSA-AES256-GCM-SHA384",
"ECDHE-RSA-AES256-GCM-SHA384"
]}
]}
]}
].' | base64
WwogIHtyYWJiaXRtcV9tYW5hZ2VtZW50LCBbCiAgICB7cmF0ZXNfbW9kZSwgZGV0YWlsZWR9LAogICAge3NzbF9vcHRpb25zLCBbCiAgICAgIHtjaXBoZXJzLCBbCiAgICAgICAgIkVDREhFLUVDRFNBLUFFUzI1Ni1HQ00tU0hBMzg0IiwKICAgICAgICAiRUNESEUtUlNBLUFFUzI1Ni1HQ00tU0hBMzg0IgogICAgICBdfQogICAgXX0KICBdfQpdLg==
```
1. Paste this base64-encoded config into the **Expert Mode: Override Server Advanced Config** field.
<%= image_tag("images/override-adv-config-pp.png",
:alt => "Screenshot of the 'Expert Mode: Override Server Advanced Config' field.
The field contains a base64 encoded configuration that begins with the characters 'WwogIHty'.") %>
1. Click **Save**.
After applying changes, pre-provisioned service instances implement this new configuration.