Skip to content

Commit 68eb08d

Browse files
(DOCSP-9494): Backup changes for Ops Manager GA (#234)
* (DOCSP-9494): initial commit * (DOCSP-9494): checkpoint * (DOCSP-9494): Backup changes for Ops Manager GA * (DOCSP-9494): add s3 notes * (DOCSP-9494): copy and tech review feedback * (DOCSP-9494): more tech and copy review feedback
1 parent e7abe1f commit 68eb08d

File tree

4 files changed

+283
-144
lines changed

4 files changed

+283
-144
lines changed

source/includes/steps-deploy-k8s-opsmgr.yaml

Lines changed: 169 additions & 101 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ content: |
1717
.. literalinclude:: /reference/k8s/example-opsmgr-minimal.yaml
1818
:language: yaml
1919
:linenos:
20-
:emphasize-lines: 5,7-11,13,15,17-19,21,23-25,27-31,34,38-39
20+
:emphasize-lines: 5,7-11,13,15,17-18
2121
2222
---
2323
title: "Open your preferred text editor and paste the |k8s-obj| specification into a new text file."
@@ -84,81 +84,6 @@ content: |
8484
8585
- ``om-admin-secret``
8686
87-
* - | ``spec``
88-
| ``.backup``
89-
| ``.``:opsmgrkube:`~spec.backup.enabled`
90-
- boolean
91-
- Flag that indicates that Backup is enabled for your You must
92-
specify ``spec.backup.enabled: true`` to configure settings
93-
for the head database, oplog store, and snapshot store.
94-
- ``true``
95-
96-
* - | ``spec``
97-
| ``.backup``
98-
| ``.opLogStores``
99-
| ``.``:opsmgrkube:`~spec.backup.opLogStores.name`
100-
- string
101-
- Name of the oplog store.
102-
- ``oplog1``
103-
104-
* - | ``spec``
105-
| ``.backup``
106-
| ``.opLogStores``
107-
| ``.mongodbRef``
108-
| ``.``:opsmgrkube:`~spec.backup.opLogStores.mongodbResourceRef.name`
109-
- string
110-
- Name of the MongoDB database resource for the oplog store.
111-
- ``my-oplog-db``
112-
113-
* - | ``spec``
114-
| ``.backup``
115-
| ``.s3Stores``
116-
| ``.``:opsmgrkube:`~spec.backup.s3Stores.name`
117-
- string
118-
- Name of the |s3| snapshot store.
119-
- ``s3store1``
120-
121-
* - | ``spec``
122-
| ``.backup``
123-
| ``.s3Stores``
124-
| ``.mongodbResourceRef``
125-
| ``.``:opsmgrkube:`~spec.backup.s3Stores.mongodbResourceRef.name`
126-
- string
127-
- Name of the MongoDB database resource for the |s3| snapshot
128-
store metadata.
129-
- ``my-s3-metadata-db``
130-
131-
* - | ``spec``
132-
| ``.backup``
133-
| ``.s3Stores``
134-
| ``.s3SecretRef``
135-
| ``.``:opsmgrkube:`~spec.backup.s3Stores.s3SecretRef.name`
136-
- string
137-
- Name of the |k8s-secret| that contains the ``accessKey`` and
138-
``secretKey`` fields. The :ref:`backup-daemon` uses the
139-
values of these fields as credentials to access the |s3| or
140-
|s3|-compatible bucket.
141-
- ``my-s3-credentials``
142-
143-
* - | ``spec``
144-
| ``.backup``
145-
| ``.s3Stores``
146-
| ``.``:opsmgrkube:`~spec.backup.s3Stores.s3BucketEndpoint`
147-
- string
148-
- |url| of the |s3| or |s3|-compatible bucket that
149-
:opsmgr:`stores </tutorial/manage-s3-blockstore-storage>` the
150-
database Backup snapshots.
151-
- ``s3.us-east-1.amazonaws.com``
152-
153-
* - | ``spec``
154-
| ``.backup``
155-
| ``.s3Stores``
156-
| ``.``:opsmgrkube:`~spec.backup.s3Stores.s3BucketName`
157-
- string
158-
- Name of the |s3| or |s3|-compatible bucket that stores the
159-
database Backup snapshots.
160-
- my-bucket
161-
16287
* - | ``spec``
16388
| ``.externalConnectivity``
16489
| ``.``:opsmgrkube:`~spec.externalConnectivity.type`
@@ -248,23 +173,159 @@ content: |
248173
- ``true``
249174
250175
---
251-
title: "(Optional) Configure any additional settings for an |onprem| deployment."
176+
title: "Configure Backup settings."
252177
stepnum: 5
253178
level: 4
179+
optional: true
180+
ref: configure-backup-settings
181+
content: |
182+
183+
If you want to enable backup, you must configure all of the following
184+
settings:
185+
186+
.. list-table::
187+
:widths: 20 20 40 20
188+
:header-rows: 1
189+
190+
* - Key
191+
- Type
192+
- Description
193+
- Example
194+
195+
* - | ``spec``
196+
| ``.backup``
197+
| ``.``:opsmgrkube:`~spec.backup.enabled`
198+
- boolean
199+
- Flag that indicates that Backup is enabled. You must specify
200+
``spec.backup.enabled: true`` to configure settings
201+
for the head database, oplog store, and snapshot store.
202+
- ``true``
203+
204+
* - | ``spec``
205+
| ``.backup``
206+
| ``.opLogStores``
207+
| ``.``:opsmgrkube:`~spec.backup.opLogStores.name`
208+
- string
209+
- Name of the oplog store.
210+
- ``oplog1``
211+
212+
* - | ``spec``
213+
| ``.backup``
214+
| ``.opLogStores``
215+
| ``.mongodbRef``
216+
| ``.``:opsmgrkube:`~spec.backup.opLogStores.mongodbResourceRef.name`
217+
- string
218+
- Name of the MongoDB database resource for the oplog store.
219+
- ``my-oplog-db``
220+
221+
You must also configure an :term:` S3 snapshot store <s3 snapshot store>`
222+
or a :term:`blockstore <Backup Blockstore Database>`.
223+
224+
.. note::
225+
226+
If you deploy both an |s3| :term:`snapshot store <s3 snapshot store>`
227+
and a :term:`blockstore <Backup Blockstore Database>`, |onprem|
228+
randomly choses one to use for Backup.
229+
230+
To configure a snapshot store, configure the following settings:
231+
232+
.. list-table::
233+
:widths: 20 20 40 20
234+
:header-rows: 1
235+
236+
* - Key
237+
- Type
238+
- Description
239+
- Example
240+
241+
* - | ``spec``
242+
| ``.backup``
243+
| ``.s3Stores``
244+
| ``.``:opsmgrkube:`~spec.backup.s3Stores.name`
245+
- string
246+
- Name of the |s3| snapshot store.
247+
- ``s3store1``
248+
249+
* - | ``spec``
250+
| ``.backup``
251+
| ``.s3Stores``
252+
| ``.s3SecretRef``
253+
| ``.``:opsmgrkube:`~spec.backup.s3Stores.s3SecretRef.name`
254+
- string
255+
- Name of the |k8s-secret| that contains the ``accessKey`` and
256+
``secretKey`` fields. The :ref:`backup-daemon` uses the
257+
values of these fields as credentials to access the |s3| or
258+
|s3|-compatible bucket.
259+
- ``my-s3-credentials``
260+
261+
* - | ``spec``
262+
| ``.backup``
263+
| ``.s3Stores``
264+
| ``.``:opsmgrkube:`~spec.backup.s3Stores.s3BucketEndpoint`
265+
- string
266+
- |url| of the |s3| or |s3|-compatible bucket that
267+
:opsmgr:`stores </tutorial/manage-s3-blockstore-storage>` the
268+
database Backup snapshots.
269+
- ``s3.us-east-1.amazonaws.com``
270+
271+
* - | ``spec``
272+
| ``.backup``
273+
| ``.s3Stores``
274+
| ``.``:opsmgrkube:`~spec.backup.s3Stores.s3BucketName`
275+
- string
276+
- Name of the |s3| or |s3|-compatible bucket that stores the
277+
database Backup snapshots.
278+
- my-bucket
279+
280+
To configure a blockstore, configure the following settings:
281+
282+
.. list-table::
283+
:widths: 20 20 40 20
284+
:header-rows: 1
285+
286+
* - Key
287+
- Type
288+
- Description
289+
- Example
290+
291+
* - | ``spec``
292+
| ``.backup``
293+
| ``.blockStores``
294+
| ``.``:opsmgrkube:`~spec.backup.blockStores.name`
295+
- string
296+
- Name of the blockstore.
297+
- ``blockStore1``
298+
299+
* - | ``spec``
300+
| ``.backup``
301+
| ``.blockStores``
302+
| ``.mongodbResourceRef``
303+
| ``.``:opsmgrkube:`~spec.backup.blockStores.mongodbResourceRef.name`
304+
- string
305+
- Name of the MongoDB database resource that you create for the
306+
blockstore. You must deploy this database resource in the same
307+
namespace as the |onprem| resource.
308+
- ``my-mongodb-blockstore``
309+
310+
---
311+
title: "Configure any additional settings for an |onprem| deployment."
312+
stepnum: 6
313+
level: 4
314+
optional: true
254315
ref: add-k8s-values
255316
content: |
256317
257318
Add any :ref:`optional settings <optional-om-k8s-settings>` that you
258319
want to apply to your deployment to the |k8s-obj| specification file.
259320
---
260321
title: "Save this file with a ``.yaml`` file extension."
261-
stepnum: 6
322+
stepnum: 7
262323
level: 4
263324
ref: save-object-spec
264325

265326
---
266327
title: "Create your |onprem| instance."
267-
stepnum: 7
328+
stepnum: 8
268329
level: 4
269330
ref: start-k8s-instance
270331
content: |
@@ -278,7 +339,7 @@ content: |
278339
279340
---
280341
title: "Track the status of your |onprem| instance."
281-
stepnum: 8
342+
stepnum: 9
282343
level: 4
283344
ref: track-k8s-instance
284345
content: |
@@ -355,7 +416,7 @@ content: |
355416
356417
---
357418
title: "Access the |onprem| application."
358-
stepnum: 9
419+
stepnum: 10
359420
level: 4
360421
ref: access-opsmgr-instance
361422
content: |
@@ -410,25 +471,27 @@ content: |
410471
411472
---
412473
title: "Create credentials for the Kubernetes Operator."
413-
stepnum: 10
474+
stepnum: 11
414475
level: 4
476+
optional: true
415477
ref: create-credentials
416478
content: |
417479
418-
To configure credentials, you must create an |onprem| organization,
480+
If you enabled Backup, you must create an |onprem| organization,
419481
generate programmatic API keys, and create a |k8s-secret|. These
420482
activities follow the prerequisites and procedure on the
421483
:ref:`create-k8s-credentials` page.
422484
423485
---
424486
title: "Create a project using a |k8s-configmap|."
425-
stepnum: 11
487+
stepnum: 12
426488
level: 4
489+
optional: true
427490
ref: create-project
428491
content: |
429492
430-
To create a project, follow the prerequisites and procedure on the
431-
:ref:`create-k8s-project` page.
493+
If you enabled Backup, create a project by following the prerequisites
494+
and procedure on the :ref:`create-k8s-project` page.
432495
433496
You must set ``data.baseUrl`` in the ConfigMap to the |application|\'s |url|. To find this |url|, invoke the following command:
434497
@@ -466,13 +529,14 @@ content: |
466529
467530
---
468531
title: "Deploy MongoDB database resources to complete the Backup configuration."
469-
stepnum: 12
532+
stepnum: 13
470533
level: 4
534+
optional: true
471535
ref: configure-backup
472536
content: |
473537
474-
By default, |onprem| enables :ref:`mms-backup-functional-overview`.
475-
Create a MongoDB database resource for the oplog and snapshot stores
538+
If you enabled :ref:`mms-backup-functional-overview`,
539+
create a MongoDB database resource for the oplog and snapshot stores
476540
to complete the configuration.
477541
478542
a. Deploy a :ref:`MongoDB database resource
@@ -481,34 +545,38 @@ content: |
481545
482546
.. note::
483547
484-
Create this database as a three-member :ref:`replica set
548+
Create this database as a :ref:`replica set
485549
<deploy-replica-set>`.
486550
487551
Match the ``metadata.name`` of the resource with the
488552
:opsmgrkube:`spec.backup.opLogStores.mongodbResourceRef.name` that you specified
489553
in your |onprem| resource definition.
490554
491-
#. Deploy a :ref:`MongoDB database resource
492-
<k8s-deploy-mdb-resources>` for the |s3| snapshot store in the
493-
same namespace as the |onprem| resource.
555+
#. Choose one of the following:
494556
495-
.. note::
557+
i. Deploy a :ref:`MongoDB database resource
558+
<k8s-deploy-mdb-resources>` for the blockstore in the
559+
same namespace as the |onprem| resource.
560+
561+
Match the ``metadata.name`` of the resource to the
562+
:opsmgrkube:`spec.backup.blockStores.mongodbResourceRef.name`
563+
that you specified in your |onprem| resource definition.
496564
497-
Create the |s3| snapshot store as a replica set.
565+
#. Configure an |s3| bucket to use as the |s3| snapshot store.
498566
499-
Match the ``metadata.name`` of the resource to the
500-
:opsmgrkube:`spec.backup.s3Stores.mongodbResourceRef.name`
501-
that you specified in your |onprem| resource definition.
567+
Ensure that you can access the |s3| bucket using the details
568+
that you specified in your |onprem| resource definition.
502569
503570
---
504571
title: "Confirm that the |onprem| resource is running."
505-
stepnum: 13
572+
stepnum: 14
506573
level: 4
574+
optional: true
507575
ref: confirm-running
508576
content: |
509577
510-
To check the status of your |onprem| resource, invoke the following
511-
command:
578+
If you enabled backup, check the status of your |onprem| resource by
579+
invoking the following command:
512580
513581
.. code-block:: sh
514582

0 commit comments

Comments
 (0)