-
Notifications
You must be signed in to change notification settings - Fork 140
/
modify-ops-man.html.md.erb
113 lines (91 loc) · 7.27 KB
/
modify-ops-man.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
---
title: Modifying Your Ops Manager Installation and Product Template Files
owner: Ops Manager
---
<style>
.note.warning {
background-color: #fdd;
border-color: #fbb
}
.note.warning:before {
color: #f99;
}
</style>
This topic describes how to modify your Ops Manager installation by decrypting and editing the YAML files that Ops Manager uses to store configuration data.
Operators can use these procedures to view and change values that they cannot access through the Ops Manager web interface. They can also modify the product templates that Ops Manager uses to create forms and obtain user input.
Operators might want to modify the Ops Manager installation and product template files for a number of reasons, including the following:
* To change the User Account and Authentication (UAA) admin password of their deployment
* To retrieve key values
* To migrate content across different <%= vars.platform_name %> releases
<p class="note warning"><strong>WARNING: </strong> Be careful when making changes to your Ops Manager installation and product template files. Use spaces instead of tabs, and remember that YAML files use whitespace as a delimiter. Finally, <%= vars.company_name %> does not officially support these procedures, so use them at your own risk.</p>
##<a id='understand-files'></a> Understand Installation and Product Template Files ##
During the installation process, Ops Manager combines information from the installation and product template files to generate the manifests that define your deployment.
* **Installation files:** <%= vars.platform_name %> stores user-entered data and automatically generated values for Ops Manager in installation YAML files on the Ops Manager VM. <%= vars.platform_name %> encrypts and stores these files in the directory `/var/tempest/workspaces/default`. You must decrypt the files to view their contents, edit them as necessary, then re-encrypt them.
* **Product templates:** Ops Manager uses product templates to create forms and obtain user input. The `job_types` and `property_blueprint` key-value pairs in a product template determine how the `jobs` and `properties` sections display in the installation file. Ops Manager stores product templates as YAML files in the directory `/var/tempest/workspaces/default/metadata` on the Ops Manager VM. These files are not encrypted, so you can edit them without decrypting. User input does not alter these files.
<p class="note"><strong>Note</strong>: Upgrading Ops Manager might eliminate your changes to the installation and product template files.</p>
##<a id='installation'></a> Modify the Installation Files
Perform the following steps to locate, decrypt, and edit the Ops Manager installation files `installation.yml` and `actual-installation.yml`.
1. SSH into the Ops Manager VM by following the steps in the [SSH into Ops Manager](trouble-advanced.html#ssh) section of the _Advanced Troubleshooting with the BOSH CLI_ topic.
1. On the command line, navigate to the scripts directory:
<pre class="terminal">
$ cd /home/tempest-web/tempest/web/scripts/
</pre>
1. Run the following command to decrypt the installation YAML file and make a temporary copy of the decrypted file. When prompted for a passphrase, enter the decryption passphrase you created when you launched Ops Manager for the first time:
<pre class="terminal">
$ sudo -u tempest-web SECRET_KEY_BASE="s" ./decrypt /var/tempest/workspaces/default/installation.yml /tmp/installation.yml
</pre>
1. Open `/tmp/installation.yml` to view or edit values.
1. If you plan to make changes, make a backup of the original installation YAML file:
<pre class="terminal">
$ cp /var/tempest/workspaces/default/installation.yml ~/installation-orig.yml
</pre>
1. If you have made changes to your copy of the installation YAML file, you must encrypt it and overwrite the original with it:
<pre class="terminal">
$ sudo -u tempest-web SECRET_KEY_BASE="s" RAILS_ENV=production /home/tempest-web/tempest/web/scripts/encrypt /tmp/installation.yml /var/tempest/workspaces/default/installation.yml
</pre>
When prompted, enter a passphrase.
1. Delete the temporary copy of the decrypted file:
<pre class="terminal">
$ rm /tmp/installation.yml
</pre>
1. Repeat steps 2 through 7 for `/tmp/actual-installation.yml`. Each step you see `installation.yml`, replace with `actual-installation.yml`. For example, for step 3 you run:
<pre class="terminal">
$ sudo -u tempest-web SECRET_KEY_BASE="s" ./decrypt /var/tempest/workspaces/default/actual-installation.yml /tmp/actual-installation.yml
</pre>
1. Restart the Ops Manager web interface:
<pre class="terminal">
$ sudo service tempest-web stop && sudo service tempest-web start
</pre>
1. Navigate to Ops Manager in a browser and enter your decryption passphrase.
1. Log in to Ops Manager.
1. Click **Review Pending Changes**, then **Apply Changes**.
1. If Ops Manager cannot load your changes, see the [Revert To Your Backup](#revert) section of this topic to restore your previous settings.
##<a id='templates'></a> Modify Product Template Files
Perform the following steps to locate and edit your Ops Manager product template files:
1. SSH into the Ops Manager VM by following the steps in the [SSH into Ops Manager](trouble-advanced.html#ssh) section of the _Advanced Troubleshooting with the BOSH CLI_ topic.
1. On the Ops Manager VM, navigate to the `/var/tempest/workspaces/default/metadata` directory.
<pre class="terminal">
$ cd /var/tempest/workspaces/default/metadata
</pre>
1. The `/var/tempest/workspaces/default/metadata` directory contains the product templates as YAML files. If you plan to make changes, make a backup of the original product template YAML file:
<pre class="terminal">
$ cp /var/tempest/workspace/default/metadata/YOUR-PRODUCT-TEMPLATE.yml ~/YOUR-PRODUCT-TEMPLATE-orig.yml
</pre>
1. Open and edit the product template YAML file as necessary. For more information about product templates, see the [Product Template Reference](https://docs.pivotal.io/tiledev/product-template-reference.html) topic.
1. Navigate to Ops Manager to see your changes.
1. If Ops Manager cannot load your changes, see the [Revert To Your Backup](#revert) section of this to restore your previous settings.
##<a id='revert'></a> Revert to Your Backup
Perform the following steps to revert to your backup of an installation or product template file:
1. SSH into the Ops Manager VM by following the steps in the [SSH into Ops Manager](trouble-advanced.html#ssh) section of the _Advanced Troubleshooting with the BOSH CLI_ topic.
1. Overwrite the modified file with the backup:
* For the installation file, run the following command:
<pre class="terminal">$ cp ~/installation-orig.yml /var/tempest/workspaces/default/installation.yml</pre>
* For a product template file, run the following command:
<pre class="terminal">$ cp ~/YOUR-PRODUCT-TEMPLATE-orig.yml /var/tempest/workspaces/default/metadata/YOUR-PRODUCT-TEMPLATE.yml</pre>
1. Restart the Ops Manager web interface:
<pre class="terminal">
$ sudo service tempest-web stop && sudo service tempest-web start
</pre>
1. Navigate to Ops Manager in a browser and enter your decryption passphrase.
1. Log in to Ops Manager.
1. Click **Review Pending Changes**, then **Apply Changes**.