-
Notifications
You must be signed in to change notification settings - Fork 100
/
azure.reference.conf
1571 lines (1321 loc) · 48.5 KB
/
azure.reference.conf
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
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
#
# Copyright (c) 2017-2019 Cloudera, Inc.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
#
# Sample Cloudera Altus Director configuration file based on the Cloudera Azure reference architecture:
# http://www.cloudera.com/documentation/other/reference-architecture/PDF/cloudera_ref_arch_azure.pdf
#
# Highly Available cluster with 3 master nodes and 5 worker nodes
#
#
# Cluster name
#
# If environmentName and deploymentName are not defined they will get the value of 'name'.
# Must be unique.
#
name: C6-Reference-Azure
#
# Environment name
#
environmentName: Azure-HA
#
# Deployment name
# Used to name the Cloudera Manager instance in Cloudera Altus Director.
# Must be unique.
#
deploymentName: Cloudera-Manager-on-Azure
#
# Cloud provider configuration (credentials, region or zone, and more)
#
provider {
type: azure
#
# ID of Azure region to use. NOTE: region must support Premium Storage
# See: https://azure.microsoft.com/en-us/global-infrastructure/regions/
#
region: "region_REPLACE_ME"
#
# Azure Cloud Environment to use. Valid values are:
# - azure
# - azure-us-government
# - azure-germany
#
azureCloudEnvironment: "azureCloudEnvironment_REPLACE_ME"
#
# Azure Active Directory Subscription ID.
#
subscriptionId: "subscriptionId_REPLACE_ME"
#
# Tenant ID (from AAD)
#
tenantId: "tenantId_REPLACE_ME"
#
# Azure Active Directory Application Client ID.
#
clientId: "clientId_REPLACE_ME"
#
# Client Secret
#
clientSecret: "clientSecret_REPLACE_ME"
}
#
# SSH credentials to use to connect to the machines
#
ssh {
username: "username_REPLACE_ME"
privateKey: privateKey_REPLACE_ME # with an absolute path to .pem file, ${HOME} may be used
}
#
# Instance templates
#
# A list of instance templates to use for groups of nodes or management services. Some configuration
# sections serve as bases for other, fully-realized templates via HOCON substitution. For more about
# HOCON substitution: https://github.com/lightbend/config/blob/master/HOCON.md#substitutions
#
# The format of this section:
# - base: core config fields that are common to all templates
# - master-base: core config fields that are common to all master templates
# - master-1: config fields for fully defining the master-1 template
# - master-2: config fields for fully defining the master-2 template
# - worker: config fields for fully defining the worker template
# - edge: config fields for fully defining the edge template (used for CM as well)
#
instances {
# fields that are common to all nodes
base {
#
# The VM type. See the Azure RA for more detail.
#
type: STANDARD_D32S_V3
#
# The image ID used for instances is an alias defined in the plugin configuration file.
#
image: cloudera-centos-72-latest
#
# Whether to use an Azure Virtual Machine Scale Set (VMSS) for a group of instances.
# Changing the size of the VMSS must be done through Altus Director, not through the Azure Portal.
# By default, Altus Director will not use a VMSS.
# Allowed values: true, false
# See: https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/overview
#
automatic: false
#
# The Resource Group for the Network Security Group for VMs. The Resource Group you specify
# must exist within the region you selected.
# See: https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-overview#resource-groups
#
networkSecurityGroupResourceGroup: "networkSecurityGroupResourceGroup_REPLACE_ME"
#
# The Network Security Group for VMs. It must be within the resource group named by
# networkSecurityGroupResourceGroup. NSG configuration allows you to limit access to the VM
# with firewall-like rules.
# See: https://docs.microsoft.com/en-us/azure/virtual-network/security-overview
#
networkSecurityGroup: "networkSecurityGroup_REPLACE_ME"
#
# The Resource Group for the Virtual Network for VMs. The Resource Group you specify must
# exist within the region you selected and should be the same for all instances that will
# be used in the same cluster.
# See: https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-overview#resource-groups
#
virtualNetworkResourceGroup: "virtualNetworkResourceGroup_REPLACE_ME"
#
# The Virtual Network for VMs. It must be within the resource group named by
# virtualNetworkResourceGroup and should be the same for all instances that will be used in
# the same cluster.
# See: https://docs.microsoft.com/en-us/azure/virtual-network/
#
virtualNetwork: "virtualNetwork_REPLACE_ME"
#
# The name of the Subnet that will be used. It must be within the virtual network.
#
subnetName: "subnetName_REPLACE_ME"
#
# OPTIONAL: The DNS domain configured in your custom DNS server. Example values include:
# cdh-cluster.internal, cluster.your-company-name.com. The host FQDN is configured on each
# VM with the following format:
# {instanceNamePrefix}-{truncated-UUID}.hostFqdnSuffix
#
hostFqdnSuffix: "hostFqdnSuffix_REPLACE_ME"
#
# OPTIONAL: Tags to apply to all instances
#
tags {
owner: ${?USER}
}
#
# Bootstrap Scripts
#
# Provide scripts, that run as root, which can customize instances immediately
# after boot and before any other Cloudera Altus Director action. Scripts run
# in the order listed. Interpeters other than sh/bash may be used.
#
# Use exit code 0 to indicate success.
# Use exit code 91 to indicate an unretryable failure.
# Altus Director will automatically retry script execution for all other exit codes.
#
# Script content can be provided in a simple string, or as part of of an object
# with an ID (for easier tracking) and an optional map of environment
# variables to set before running the script.
#
# bootstrapScripts: ["""#!/bin/sh
#
#echo 'Hello World!'
#exit 0
#
#""",
# {
# id: bootstrapScript2,
# env {
# KEY1: VALUE1
# KEY2: VALUE2
# },
# content: "echo The values are $KEY1 and $KEY2"
# }
# ]
#
# This script, included from azure-os-generic-bootstrap.conf, is needed to configure DNS.
#
bootstrapScripts: [ ${?bootstrap-script.os-generic} ]
#
# More complex scripts can be supplied via local filesystem paths. They will
# run after any scripts supplied in the previous bootstrapScripts section.
#
# bootstrapScriptsPaths: ["/tmp/test-script.sh",
# {
# id: bootstrapScriptFromPath2,
# env: {
# KEY3: VALUE3
# },
# path: "/tmp/test-script.py"
# }
# ]
#
# Pre-terminate Scripts
#
# Provide scripts, that run as root, which can run cleanup steps on instances
# immediately before termination. If an instance has already been terminated,
# the scripts will be skipped for it. Scripts run in the order listed.
# Interpeters other than sh/bash may be used.
#
# Use exit code 0 to indicate success.
# Use exit code 91 to indicate an unretryable failure.
# Altus Director will automatically retry script execution for all other exit codes.
#
# Script content can be provided in a simple string, or as part of of an object
# with an ID (for easier tracking) and an optional map of environment
# variables to set before running the script.
#
preTerminateScripts: ["""#!/bin/sh
echo 'Goodbye World!'
exit 0
""",
{
id: preTerminateScript2,
env {
KEY1: VALUE1
KEY2: VALUE2
},
content: "echo The values are $KEY1 and $KEY2"
}
]
#
# More complex scripts can be supplied via local filesystem paths. They will
# run after any scripts supplied in the previous preTerminateScripts section.
#
# preTerminateScriptsPaths: ["/tmp/test-pre-terminate-script.sh",
# {
# id: preTerminateScriptFromPath2,
# env: {
# KEY3: VALUE3
# },
# path: "/tmp/test-pre-terminate-script.py"
# }
# ]
#
# Flag indicating whether to normalize the instance. Not setting normalization here implies that
# your bootstrap script will take care of normalization. This is an advanced configuration that
# requires assistance from Cloudera support.
#
# Defaults to true
#
# normalizeInstance: true
#
# Configuration allowing for granular control over the normalization steps of an instance.
# By default, all of these steps are on. This is an advanced configuration. None of these steps
# will run if normalizeInstance is set to false.
#
# Normalization includes:
# prewarming the parcel directory
# downloading, installing, and adjusting packages
# minimizing swappiness
# increasing the maximun number of open files
# resizing the root partition
# mounting ephemeral disks
#
# normalizationConfig {
# prewarmDirectory: true
# installPackages: true
# miscellaneousServiceAdjustment: true
# minimizeSwappiness: true
# increaseMaxNumberOfOpenFiles: true
# resizeRootPartition: true
# mountAllUnmountedDisks: true
# }
#
# By default Director does not do host key verification when performing SSH on an instance.
# This can be changed for added security by setting the SSH Host Key Retrieval Type.
#
# NONE : Host key fingerprints will not be stored or verified during SSH (default)
# PROVIDER : Retrieve the host key fingerprints from the cloud provider. This does not
# work for all images and will likely increase bootstrap time.
# INSTANCE : Retrieve the host key fingerprints upon first connection into the instance. This
# is less secure than the PROVIDER method since the first connection isn't guaranteed
# to be secure.
# FALLBACK : Attempt to retrieve host key fingeprint form the cloud provider first, if that
# fails, attempt to retrieve upon first connection into the instance.
#
# sshHostKeyRetrievalType: NONE
}
# fields for master nodes
master: ${instances.base} {
#
# Resource Group for VMs. The Resource Group you specify must exist
# within the region you selected.
# See: https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-overview#resource-groups
#
computeResourceGroup: "master_computeResourceGroup_REPLACE_ME"
#
# OPTIONAL: Availability Set for VMs. VMs within the same availability set have staggered
# maintenance times. With a default availability set configuration, no more than 1/5 of the
# VMs will be offline at a time (rounded up). Sharing an Availability Set between master and
# worker nodes is strongly discouraged.
# See: https://docs.microsoft.com/en-us/azure/virtual-machines/linux/manage-availability
#
availabilitySet: "master_availabilitySet_REPLACE_ME"
#
# Prefix for VM names and hostnames. Each VM name has the following format:
# {instanceNamePrefix}-{UUID}
# where {UUID} is generated by the Cloudera Altus Director server.
#
instanceNamePrefix: "master_instanceNamePrefix_REPLACE_ME"
#
# OPTIONAL: The storage account type to use. The dataDiskSize parameter should be updated
# based on this property. The allowed values are:
# - Premium_LRS (default)
# - Standard_LRS
# See the RA for the supported ways to use standard storage.
#
storageAccountType: "Premium_LRS"
#
# OPTIONAL: The size of each data drive. For disks allocated in a premium storage account, only the
# following GB values are allowed:
# 512 (P20 disk)
# 1023 (P30 disk) - for backwards compatibility
# 1024 (P30 disk) - default
# 2048 (P40 disk)
# 4095 (P50 disk)
# For disks allocated in a standard storage account, any size between 1 and 4095 inclusive
# can be used.
# See: https://docs.microsoft.com/en-us/azure/storage/common/storage-introduction
# See: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/disks-types#premium-ssd
#
dataDiskSize: 512
#
# OPTIONAL: Whether or not to use managed disks. Managed Disks are enabled by default. To
# use Storage Accounts, set this field to "No". In order for managed disks to be used, the
# Availability Set must be aligned to use managed disks.
# Allowed values: Yes, No
# See: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/managed-disks-overview
#
managedDisks: Yes
#
# OPTIONAL: Whether or not to use a custom (managed) image. Custom images are only supported
# when using Managed Disks (managedDisks must be Yes).
# Allowed values: Yes, No
#
useCustomManagedImage: No
#
# The custom VM image purchase plan. The purchase plan for the original VM image used to
# create the custom image. This can be:
# - an empty string ("")
# - a string with the format /publisher/<publisher>/product/<product>/name/<name>
#
# customImagePlan: ""
#
# Should each VM have a Public IP Address and DNS Label? If Yes, each VM will have a
# publicly resolvable hostname with the following format:
# {instanceNamePrefix}-{UUID}.{region}.cloudapp.azure.com
# Allowed values: Yes, No
#
publicIP: No
}
# fields for master-1 nodes
master-1: ${instances.master} {
#
# OPTIONAL: The number of data drives. The size is specified with dataDiskSize. The default
# value is 5.
# Data drives are mounted on /data0 .. /data[n]
# /data0 - Dedicated Log Device
# For Masters-1:
# /data1 - HDFS JournalNode Data
# /data2 - Zookeeper Data / DataLog
# /data3 - NameNode Data
# For Masters-2:
# /data1 - HDFS JournalNode Data
# /data2 - Zookeeper Data / DataLog
# For Workers:
# /data1 .. /data[n] will be used for HDFS data
#
dataDiskCount: 4
}
# fields for master-2 nodes
master-2: ${instances.master} {
dataDiskCount: 3
}
# fields for worker nodes
worker: ${instances.base} {
computeResourceGroup: "worker_computeResourceGroup_REPLACE_ME"
availabilitySet: "worker_availabilitySet_REPLACE_ME"
instanceNamePrefix: "worker_instanceNamePrefix_REPLACE_ME"
storageAccountType: "Standard_LRS"
dataDiskCount: 11
dataDiskSize: 1024
managedDisks: Yes
publicIP: No
}
# fields for edge nodes
edge: ${instances.base} {
computeResourceGroup: "edge_computeResourceGroup_REPLACE_ME"
availabilitySet: "edge_availabilitySet_REPLACE_ME"
instanceNamePrefix: "edge_instanceNamePrefix_REPLACE_ME"
storageAccountType: "Standard_LRS"
dataDiskCount: 1
dataDiskSize: 512
managedDisks: Yes
# Change this to Yes to allow accessing edge/CM nodes via public IP
publicIP: No
}
}
include "azure-os-generic-bootstrap.conf"
#
# Optional external database server configuration.
#
# Cloudera Altus Director can create databases on existing database servers,
# including MySQL servers running in Azure MySQL.
#
# To properly setup a database see:
# https://www.cloudera.com/documentation/director/latest/topics/director_get_started_azure_set_up_msql_postgres.html
#
databaseServers {
#
# Use an existing MySQL server (possibly running in Azure MySQL)
#
existingmysql1 {
#
# The type of database to use. Allowed values are:
# - mysql
# - postgresql
#
type: mysql
#
# The static internal IP (recommended) or internal FQDN of the database server.
#
host: mysql_host_REPLACE_ME.mysql.database.azure.com
#
# The database server's port.
#
port: 3306
#
# The user Cloudera Altus Director will use. The user must have privileges to create databases,
# create users, and grant the users access to those databases. For Azure MySQL, be sure to
# include the short hostname of the database server.
#
user: "root@mysql_host_REPLACE_ME"
#
# The password for the database user.
#
password: "rootpassword"
}
#
# Use an existing PostgresSQL server
#
# existingpostgres1 {
# type: postgresql
# host: REPLACE_ME # with IP address of database server
# port: 5432
# user: postgres
# password: rootpassword
# }
}
#
# Configuration for Cloudera Manager. Cloudera Altus Director can use an existing Cloudera
# Manager installation, or bootstrap everything from scratch for a new cluster.
#
cloudera-manager {
instance: ${instances.edge} {
#
# Additional tags for the Cloudera Manager instance
#
tags {
application: "Cloudera Manager 6"
}
}
#
# Licensing configuration
#
# There are three mutually exclusive options for setting up Cloudera Manager's license.
# 1. License text may be embedded in this file using the "license" field. Triple quotes (""")
# are recommended for including multi-line text strings.
# 2. The "licensePath" can be used to specify the path to a file containing the license.
# 3. The "enableEnterpriseTrial" flag indicates whether the 60-Day Cloudera Enterprise Trial
# should be activated when no license is present. This must not be set to true if a
# license is included using either "license" or "licensePath".
#
#
# Embed a license for Cloudera Manager
#
# license: """
# -----BEGIN PGP SIGNED MESSAGE-----
# Hash: SHA1
#
# {
# "version" : 1,
# "name" : "License Owner",
# "uuid" : "license id",
# "expirationDate" : 0,
# "features" : [ "FEATURE1", "FEATURE2" ]
# }
# -----BEGIN PGP SIGNATURE-----
# Version: GnuPG v1.4.11 (GNU/Linux)
#
# PGP SIGNATURE
# -----END PGP SIGNATURE-----
# """
#
# Include a license for Cloudera Manager from an external file
#
# licensePath: "/path/to/license.txt.asc"
#
# Activate 60-Day Cloudera Enterprise Trial
#
enableEnterpriseTrial: true
#
# Specify the billing ID.
#
# Altus Director will use the billing ID to report usage information to a metering service for
# usage based billing.
#
# Usage reporting starts as soon as you assign a billing ID and a license to a Cloudera Manager.
# If you remove a billing ID, Director will stop reporting to the metering service.
#
# When usage reporting stops, you will not have access to Cloudera Support with this deployment.
# If you want a billing ID, please contact Cloudera. An enterprise license is required.
#
# billingId: "billingId_REPLACE_ME"
#
# Select the strategy for installing a JDK. Choices are:
#
# - AUTO (default): Altus Director installs the JDK on the Cloudera Manager instance, and
# Cloudera Manager installs the JDK on cluster instances
# - DIRECTOR_MANAGED: Altus Director installs the JDK on all instances
# - NONE: Neither Altus Director nor Cloudera Manager installs the JDK on any instances
#
# javaInstallationStrategy: AUTO
#
# Install the unlimited strength JCE policy files for higher levels of encryption.
# Prior to setting this to true, confirm that you understand the legal ramifications
# of using unlimited JCE policy files in your country.
#
# unlimitedJce: true
#
# Automatic TLS
#
#
# Set up TLS connections automatically between Cloudera Altus Director and Cloudera Manager,
# as well as among the cluster services. Automatic TLS includes installation of
# unlimited strength JCE policy files (see unlimitedJce).
#
# tlsEnabled: true
#
# Pass TLS configuration properties to Cloudera Manager to refine how automatic TLS
# is configured. All TLS configuration properties are optional and have sane defaults.
# Additional properties are available beyond those listed here.
#
# tlsConfigurationProperties {
# subject_suffix: "O=example.com,L=Cityville,ST=CA,C=US"
# ca_sig_hash_algo: "SHA512"
# email_address: "[email protected]"
# }
#
# Optional database configuration
#
# There are three mutually exclusive options for database usage in Cloudera Altus Director.
# 1. With no configuration, databases in the Cloudera Manager embedded PostgreSQL database
# server will be used. This option is NOT supported for production use.
# 2. Alternatively, existing external databases can be used.
# 3. Finally, databases can be created on the fly on existing external database servers.
#
# Note that using an external database here necessitates using an external database
# for the cluster services. This reference configuration is using Option 3.
#
#
# (Option 2) Optional configuration for existing external databases
#
# databases {
# CLOUDERA_MANAGER {
# type: postgresql
#
# host: db.example.com
# port: 123
#
# user: admin
# password: 1231ed
#
# name: scm
# }
#
# ACTIVITYMONITOR { ... }
#
# REPORTSMANAGER { ... }
#
# NAVIGATOR { ... }
#
# NAVIGATORMETASERVER { ... }
# }
#
# (Option 3) Optional configuration for creating external databases on the fly
#
# When a database is created on the fly, Altus Director generates a random database name using the specified
# database name prefix, a random username based on the specified username prefix, and a random password. The
# password is stored by Altus Director and made available to the service that uses the database. If multiple
# services reference the same external database server, Altus Director will create a database for each.
#
# MySQL limits usernames to sixteen characters. Therefore, limit usernamePrefix values for databases on MySQL to
# seven characters; the remaining nine characters are used by the randomized suffix generated by Director.
#
# Note that the databaseServerName must correspond to an external database server named above.
#
databaseTemplates {
CLOUDERA_MANAGER {
name: scmt
databaseServerName: existingmysql1
databaseNamePrefix: scm
usernamePrefix: scmu
}
ACTIVITYMONITOR {
name: amont
databaseServerName: existingmysql1
databaseNamePrefix: amon
usernamePrefix: amonu
}
REPORTSMANAGER {
name: rmant
databaseServerName: existingmysql1
databaseNamePrefix: rman
usernamePrefix: rmanu
}
NAVIGATOR {
name: navt
databaseServerName: existingmysql1
databaseNamePrefix: nav
usernamePrefix: navu
}
NAVIGATORMETASERVER {
name: navmst
databaseServerName: existingmysql1
databaseNamePrefix: navms
usernamePrefix: navmsu
}
}
#
# Configuration to override Cloudera Manager package repositories. These are
# optional, and default to the Cloudera Enterprise release corresponding to
# the Altus Director version.
#
# repository: "https://archive.cloudera.com/cm6/6.3/redhat7/yum/"
# repositoryKeyUrl: "https://archive.cloudera.com/cm6/6.3/redhat7/yum/RPM-GPG-KEY-cloudera"
# OR use an existing Cloudera Manager installation
# hostname: "192.168.33.10"
# username: REPLACE_ME # default is admin
# password: REPLACE_ME # default is admin
#
# Configuration for Cloudera Manager and its management services
#
# Configuration properties for CLOUDERA_MANAGER are documented at
# https://www.cloudera.com/documentation/enterprise/6/properties/6.3/topics/cm_props_cmserver.html
#
# Configuration properties for the Cloudera Management services are documented at
# https://www.cloudera.com/documentation/enterprise/6/properties/6.3/topics/cm_props_mgmtservice.html
#
# Configuration properties for Hosts are documented at
# https://www.cloudera.com/documentation/enterprise/6/properties/6.3/topics/cm_props_host.html
#
# Properties here ensure that non-ephemeral disks are used for all directories and files
#
configs {
#
# CLOUDERA_MANAGER corresponds to the Cloudera Manager Server configuration options
#
CLOUDERA_MANAGER {
# enable_api_debug: true
custom_banner_html: "Managed by Cloudera Altus Director"
}
#
# CLOUDERA_MANAGEMENT_SERVICE corresponds to the Service-Wide configuration options
#
# CLOUDERA_MANAGEMENT_SERVICE {
# enable_alerts : false
# enable_config_alerts : false
# }
SERVICEMONITOR {
mgmt_log_dir: /data0/log/cloudera-scm-firehose
firehose_storage_dir: /data0/lib/cloudera-service-monitor
}
ACTIVITYMONITOR {
mgmt_log_dir: /data0/log/cloudera-scm-firehose
}
HOSTMONITOR {
mgmt_log_dir: /data0/log/cloudera-scm-firehose
firehose_storage_dir: /data0/lib/cloudera-host-monitor
}
REPORTSMANAGER {
headlamp_scratch_dir: /data0/lib/cloudera-scm-headlamp
mgmt_log_dir: /data0/log/cloudera-scm-headlamp
}
EVENTSERVER {
mgmt_log_dir: /data0/log/cloudera-scm-eventserver
eventserver_index_dir: /data0/lib/cloudera-scm-eventserver
}
ALERTPUBLISHER {
mgmt_log_dir: /data0/log/cloudera-scm-alertpublisher
}
NAVIGATOR {
mgmt_log_dir: /data0/log/cloudera-scm-navigator
}
NAVIGATORMETASERVER {
audit_event_log_dir: /data0/log/cloudera-scm-navigator/audit
data_dir: /data0/lib/cloudera-scm-navigator
mgmt_log_dir: /data0/log/cloudera-scm-navigator
}
# Configuration properties for all hosts
# HOSTS { ... }
}
#
# Deployment Post-create Scripts
#
# Provide scripts, that run as root, which can customize the Cloudera Manager
# instance after the deployment has been created. Scripts run in the order
# listed. Interpeters other than sh/bash may be used.
#
# Use exit code 0 to indicate success.
# Use exit code 91 to indicate an unretryable failure.
# Altus Director will automatically retry script execution for all other exit codes.
#
# Deployment post-creation scripts have access to the following environment
# variables:
#
# DEPLOYMENT_HOST_PORT
# ENVIRONMENT_NAME
# DEPLOYMENT_NAME
# CM_USERNAME
# CM_PASSWORD
#
# Script content can be provided in a simple string, or as part of of an object
# with an ID (for easier tracking) and an optional map of additional environment
# variables to set before running the script. Environment variables set here
# override the values of default ones above.
#
postCreateScripts: ["""#!/bin/sh
echo 'Hello World!'
exit 0
""",
{
id: depPostCreateScript2,
env {
KEY1: VALUE1
KEY2: VALUE2
},
content: "echo The values are $KEY1 and $KEY2"
},
"""#!/usr/bin/python
print 'Hello again!'
"""]
#
# More complex scripts can be supplied via local filesystem paths. They will
# run after any scripts supplied in the previous postCreateScripts section.
#
# postCreateScriptsPaths: ["/tmp/test-script.sh",
# {
# id: postCreateScriptFromPath2,
# env: {
# KEY3: VALUE3
# },
# path: "/tmp/test-script.py"
# }
# ]
#
# Optional custom service descriptors for external parcels
#
# csds: [
# "https://archive.cloudera.com/exampleProduct/csd/example-csd.jar"
# ]
#
}
#
# Cluster description
#
cluster {
# The table of products and their versions that need to be installed. Each
# product must have a corresponding parcel in the parcelRepositories
# configured in this section. The specified version for a product will be
# used to find a suitable parcel. Specifying a version that is satisfied by
# more than one parcel among those available will result in a configuration
# error. Specify more granular versions to avoid conflicts.
products {
CDH: 6
# EXAMPLEPRODUCT: 1
}
#
# Optional override of CDH parcel repositories
#
# This defaults to the Cloudera Enterprise release corresponding to the
# Altus Director version.
#
# parcelRepositories: ["https://archive.cloudera.com/cdh6/6.3/parcels/"]
#
# Services to include in the cluster
#
# NOTE: On CM 5.9+ Sentry and Kafka 2.0 can't coexist in the same cluster.
# If this is needed, use CM 5.8 repository and parcels, or use Kafka
# 2.1 or higher.
#
services: [
HDFS,
YARN,
ZOOKEEPER,
HBASE,
HIVE,
HUE,
IMPALA,
OOZIE,
SPARK_ON_YARN
]
#
# Custom service configurations
#
# Configuration keys containing special characters (e.g., '.', ':') must be enclosed in double
# quotes.
#
# Configuration properties for CDH roles and services are documented at
# https://www.cloudera.com/documentation/enterprise/6/properties/6.3/topics/cm_props_cdh620.html