You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PNDA stack parameters, flavors and environmnent files
Stack Parameters
PNDA flavor
The PNDA flavor defines the distribution of roles across instances.
PndaFlavor:
Mandatory:
yes
Purpose:
Flavor for the PNDA deployment.
Type:
string
Default value:
None
Example value:
'standard'
Valid values:
[ standard ]
Swift containers
A PNDA deployment makes use of swift containers to backup applications and packages on a regular basis. These containers shall be created in a tenant prior to the PNDA stack creation process.
pnda_apps_container:
Mandatory:
yes
Purpose:
container name containing PNDA deployed applications.
Type:
string
Default value:
None
Example value:
'apps'
pnda_archive_container:
Mandatory:
yes
Purpose:
name of the container handling PNDA archives.
Type:
string
Default value:
None
Example value:
'archives'
pnda_apps_folder:
Mandatory:
yes
Purpose:
name of the folder within the apps container handling application files.
Type:
string
Default value:
None
Example value:
'releases'
Instance Flavors
Defining the virtual machines flavors (size)
EdgeFlavor:
Mandatory:
no
Purpose:
Flavor of the EDGE instance
Type:
string
Default value:
m1.xlarge
Example value:
m1.large
PNDA flavors
standard
BastionFlavor:
Mandatory:
no
Purpose:
Flavor of the BASTION instance
Type:
string
Default value:
m1.large
Example value:
m1.large
PNDA flavors
standard
SaltmasterFlavor:
Mandatory:
no
Purpose:
Flavor of the SALT MASTER instance
Type:
string
Default value:
m1.large
Example value:
m1.large
PNDA flavors
standard
CMFlavor:
Mandatory:
no
Purpose:
Flavor of the CLOUDERA MANAGER instance
Type:
string
Default value:
m1.xlarge
Example value:
m1.xlarge
PNDA flavors
standard
Manager1Flavor:
Mandatory:
no
Purpose:
Flavor of the MANAGER1 instance
Type:
string
Default value:
m1.xlarge
Example value:
m1.xlarge
PNDA flavors
standard
Manager2Flavor:
Mandatory:
no
Purpose:
Flavor of the MANAGER2 instance
Type:
string
Default value:
m1.xlarge
Example value:
m1.xlarge
PNDA flavors
standard
Manager3Flavor:
Mandatory:
no
Purpose:
Flavor of the MANAGER3 instance
Type:
string
Default value:
m1.xlarge
Example value:
m1.xlarge
PNDA flavors
standard
Manager4Flavor:
Mandatory:
no
Purpose:
Flavor of the MANAGER4 instance
Type:
string
Default value:
m1.xlarge
Example value:
m1.xlarge
PNDA flavors
standard
LogserverFlavor:
Mandatory:
no
Purpose:
Flavor of the LOGSERVER instance
Type:
string
Default value:
m1.large
Example value:
m1.large
PNDA flavors
[ standard ]
ToolsFlavor:
Mandatory:
no
Purpose:
Flavor of the TOOLS instance
Type:
string
Default value:
m1.large
Example value:
m1.large
PNDA flavors
standard
OpentsdbFlavor:
Mandatory:
no
Purpose:
Flavor of the OPENTSDB instance
Type:
string
Default value:
m1.large
Example value:
m1.large
PNDA flavors
standard
DatanodeFlavor:
Mandatory:
no
Purpose:
Flavor of the DATANODE instance
Type:
string
Default value:
m1.xlarge
Example value:
m1.xlarge
PNDA flavors
standard
JupyterFlavor:
Mandatory:
no
Purpose:
Flavor of the JUPYTER instance
Type:
string
Default value:
m1.xlarge
Example value:
m1.xlarge
PNDA flavors
[ standard ]
KafkaFlavor:
Mandatory:
no
Purpose:
Flavor of the KAFKA instance
Type:
string
Default value:
m1.large
Example value:
m1.large
PNDA flavors
standard
ZookeeperFlavor:
Mandatory:
no
Purpose:
Flavor of the ZOOKEEPER instance
Type:
string
Default value:
m1.large
Example value:
m1.large
PNDA flavors
standard
PkgserverFlavor:
Mandatory:
no
Purpose:
Flavor of the PKGSERVER instance
Type:
string
Default value:
m1.medium
Example value:
m1.medium
PNDA flavors
standard
Cluster sizing
Define the cluster sizes (instances count) as part of the PNDA deployment.
ZookeeperNodes:
Mandatory:
no
Purpose:
Number of ZOOKEEPER instances
Type:
string
Default values:
standard:3
Example value:
3
KafkaNodes:
Mandatory:
no
Purpose:
Number of KAFKA instances
Type:
string
Default values:
standard:1
Example value:
3
OpentsdbNodes:
Mandatory:
no
Purpose:
Number of OPENTSDB instances
Type:
string
Default values:
standard:1
Example value:
3
DataNodes:
Mandatory:
no
Purpose:
Number of Hadoop DATANODE instances
Type:
string
Default values:
standard:1
Example value:
3
Networking
PNDA is deployed on top of a private network, providing isolation. These parameters define this created network's properties.
private_net_cidr:
Mandatory:
no
Purpose:
Created private network cidr
Type:
string
Default values:
192.168.10.0/24
Example value:
192.168.0.0/24
private_net_pool_start:
Mandatory:
no
Purpose:
First DHCP address available
Type:
string
Default values:
192.168.10.10
Example value:
192.168.0.10
private_net_pool_end:
Mandatory:
no
Purpose:
Last DHCP address available
Type:
string
Default values:
192.168.10.250
Example value:
192.168.0.250
private_net_gateway:
Mandatory:
no
Purpose:
Created private network gateway
Type:
string
Default values:
192.168.10.1
Example value:
192.168.0.1
public_net:
Mandatory:
yes
Purpose:
UUID of the external network
Type:
string
Default values:
None
Example value:
de671752-cc2d-4251-9ac9-fc71d334c497
name_servers:
Mandatory:
yes
Purpose:
Array of name servers ip addresses
Type:
string
Default values:
None
Example value:
['8.8.8.8', '8.8.4.4']
Swift Authentication
Access to the created swift containers from the deployed PNDA instances requires authentication.
block device to which to attach the created volume
Type:
string
Default values:
'/dev/vdb'
Example value:
'/dev/vdb'
DatanodeVolumeSize
Mandatory:
no
Purpose:
Size in GB of the created volume
Type:
string
Default values:
200
Example value:
1024
Deployment from git
When deploying, one can choose git repo sources for salt recipes. Both http and ssh are supported to clone the platform-salt repository. If ssh is used, a private key may be necessary. Its value has to be stored in a file, specified by the git_private_key_file parameter. Defining the platform_git_repo_uri supersedes the definition of the parameters for deployment from tarballs.
no / yes if platform_git_repo_uri is specified and ssh is used
Purpose:
file containing the private key value necessary to clone the platform-salt repository
Type:
string
Default values:
None
Example value:
'master'
Deployment from tarballs releases
When deploying, one can choose to deploy from tarball files (releases) rather than from the git repository. the platform_uri parameter is superseded by the platform_git_repo_uri definition. Meaning that if platform_git_repo_uri is defined it git based deployment takes precedence.
Installing the Cloudera Hadoop cluster might take some time. In an effort to reduce the provisioning time it is possible to specify mirrors for Hadoop parcels or the Oracle JDK installer. If not defined, Installation will grab the Cloudera parcels or the JDK installer from the Cloudera and Oracle servers, respectively.
PNDA instances are created from the image created using the pnda-dib-elements.
image_id
Mandatory:
yes
Purpose:
UUID or name of the PNDA base image
Type:
string
Default values:
'pnda-base'
Example value:
'pnda-base'
ssh access to the Deployment
When deploying PNDA attach an existing keypair to the bastion instance. This keypair is necessary to connect to the instance through ssh.
KeyName
Mandatory:
yes
Purpose:
keypair name of an existing key pair
Type:
string
Default values:
None
Example value:
'pnda_user'
Support for cluster scaling
When scaling a PNDA deployment (adding nodes) it is necessary to pass a deployment unique identifier, which will force the orchestration step for the cloudera clusters.
DeploymentID
Mandatory:
no, unless resizing the deployment
Purpose:
trigerring the Cloudera orchestration/scaling process