Preparing to install Netezza Performance Server

Deployment options: Netezza Performance Server for Cloud Pak for Data

To install Netezza Performance Server on AWS, you must create a properties file with a number of properties that are associated with your AWS account. Learn about the different properties and how to create your properties file to successfully install Netezza Performance Server.

You can find a properties file template in the nz-cloud directory, which is created when you unpack the installation bundle. For more information about the nz-cloud directory, see The nz-cloud directory.

The aws_infra.properties file

#######################################
#   USER REQUIRED INPUT PROPERTIES    #
#######################################
CLOUD_PROVIDER                  AWS  1 
CLUSTER_NAME                    ${CLUSTER_NAME}  2 

# AWS CREDENTIALS
AWS_DEFAULT_REGION              ${AWS_DEFAULT_REGION}  3 

AWS_SECRET_ACCESS_KEY           ${AWS_SECRET_ACCESS_KEY}  4 
AWS_ACCESS_KEY_ID               ${AWS_ACCESS_KEY_ID}  5 

# SERVICE CONTROL POLICIES(SCP) ENFORCED:  true/false 
AWS_SCP_ENABLED 					   false  6 

# BASE DOMAIN created in AWS ROUTE53 SERVICE
ROUTE53_DNS                     ${ROUTE53_DNS}  7 

# SECRET FROM REDHAT PORTAL
PULL_SECRET                     $PULL_SCRET  8 
CP4D_ENTITLEMENT_KEY            $CP4D_ENTITLEMENT_KEY  9 

#######################################
# IF INSTALLING OPENSHIFT	           
#######################################
MACHINE_CIDR                    $MACHINE_CIDR  10 
OCP_WORKER_SINGLE_ZONE          false  11 

# the type of the cluster: PUBLIC / PRIVATE 
# Private clusters can only be accessed from the bastion node
CLUSTER_TYPE                        PRIVATE  12 
# Comma separated list of subnets to use in an existing VPC
SUBNETS_LIST $SUBNET_PRIVATE_1_ID,$SUBNET_PRIVATE_2_ID,$SUBNET_PRIVATE_3_ID  13 

#######################################
# IF OPENSHIFT IS INSTALLED						
#######################################
KUBEADMIN_PASSWORD                   $KUBEADMIN_PASSWORD  14 
AWS_EFS_ID                           &AWS_EFS_ID  15 



# Properties for air-gapped environments

IS_AIRGAPPED true

# AMI used by worker nodes

AIRGAPPED_AMI ami-xxxxxxxxxx

AIRGAPPED_INSTANCE_PROFILE ${CLUSTER_NAME}-worker-profile

AIRGAPPED_AZ_LIST ${AWS_DEFAULT_REGION}a,${AWS_DEFAULT_REGION}b,${AWS_DEFAULT_REGION}c

AIRGAPPED_SUBNET_IDS_LIST $SUBNET_PRIVATE_1_ID,$SUBNET_PRIVATE_2_ID,$SUBNET_PRIVATE_3_ID 13

# worker node security group

AIRGAPPED_SECURITY_GROUP sg-xxxxxxxxxxxx

# Private registry properties (ex. image-registry.domain:5000)

CUSTOMER_REGISTRY_PREFIX <private-registry-url>

CUSTOMER_REGISTRY_USERNAME username

CUSTOMER_REGISTRY_PASSWORD user-password
Where:
 1 
Specifies the cloud provider.
Type AWS to install Netezza Performance Server on AWS.
 2 
Specifies the name of your Red Hat OpenShift cluster in your AWS account.
 3 
Specifies the AWS region and credentials, which have enough permissions to create Netezza Performance Server resources on your AWS account.

Type your AWS region.

 4 
Specifies the AWS secret access key of the AWS account that is used to install Red Hat OpenShift and create extra resources as necessary.
 5 
Specifies the AWS access key ID.
The access key ID of the AWS account that is used to install Red Hat OpenShift and create extra resources as necessary.
 6 
Specifies whether the service control policies are enforced.
The default value is False. If an SCP is enforced on the account, set the value to True. If an SCP is not enforced, set the value to False.
When the value is set to True, you can skip the permission validation step during the installation process. The permission validation command evaluates whether you have all of the IAM level user permissions that are necessary to complete the installation and deploy your instance.
As it is not possible to dynamically validate IAM level user permissions when SCP is enabled, you are expected to configure SCP and IAM. Refer the permission requirement list that is available at https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html, and configure SCP and IAM.
If you do not properly configure the IAM and SCP levels, the installation process fails.
Note: SCP configurations are supported only on Red Hat OpenShift 4.6 and later.
 7 
Specifies the HOSTED_ZONE_PRIVATE_NAME value that you used when you created Route53.
 8 
Specifies your pull secret.
Download your Red Hat OpenShift installation pull secret from the Red Hat OpenShift Cluster Manager.
 9 
Specifies the Cloud Pak for Data entitlement key.
This property is needed if you want to upgrade your instance to version 11.2.1.6 or later.
 10 
Specifies the CIDR used for the VPC.
 11 
Specifies the Red Hat OpenShift worker single zone. Set it to false to distribute workers across different zones (for example, us-east-1a, us-east-1b) or true to create them all in the same region.
 12 
Specifies the type of the cluster; private or public.
Private clusters can be accessed only from the bastion node.
Set it to PRIVATE to allow access to the cluster only from the bastion node, or PUBLIC to allow access to the cluster from any node.
PRIVATE is the recommended option.
 13 
Specifies a comma-separated list of subnets to use in an existing VPC.
Provide the IDS of the subnets in the VPC where Red Hat OpenShift is installed.
 14 
Optional. Specifies the Kubeadmin password. If Red Hat OpenShift is already installed and running, you can gey KUBEADMIN_PASSWORD by running the command:
oc whoami -t
 15 
Specifies the AWS elastic file system (EFS) in the VPC.

Type in the ID of your EFS that you created in the VPC of your cluster.

If you have an AWS elastic file system (EFS) and it is attached to the VPC, provide the ID.