Installing Netezza on IBM Cloud

Read the instructions
Installing from linux
Installing the nz-cloud CLI
Collect information for the ibm_infra.properties files
Validate permissions
Starting the install of Netezza
Using Netezza on IBM Cloud

Read the instructions

Review the installation instructions. I will document how I did it and any gotchas.

Back to Table of Contents

Installing from linux

If you have a linux desktop or access to a linux system then feel free to proceed to the next section with this system.
If you do not have a linux system, follow these instructions on creating bastion node

Back to Table of Contents

Add prereqs to the bastion node and test permissions on IBM Cloud account

Install the Development Tools to install unzip, Python 3, which and gettext
- sudo yum groupinstall -y "Development Tools"
Install jq
- yum install epel-release -y
- yum install jq -y
- jq --version
Install Python on RHEL 8.
- yum install python3
- python3 --version
I install IBM Cloud CLI to run a few sanity checks on my account prior to trying to install NZ CLoud
- Run curl -sL https://ibm.biz/idt-installer | bash
Log in through the CLI, using your IBM Cloud ID.
- ibmcloud login
- Select the account you want to use.
- Select the region - in my case us-south
- Send usage statistics (up to you on the answer)

Let’s check our Kubernetes infrastructure permissions.

Run ibmcloud oc infra-permissions get

In my case below, I should have proper permissions to create an OpenShift cluster.

 [root@nz-install ~]#  ibmcloud oc infra-permissions get
 Analyzing the infrastructure permissions for resource group ...
 Retrieved suggested and required infrastructure permissions that are missing for account ID 21#####6 with infrastructure access set up by linked account API key.
 OK
 Missing Virtual Worker Permissions
 No changes are suggested or required.
 Missing Physical Worker Permissions
 No changes are suggested or required.
 Missing Network Permissions
 No changes are suggested or required.
 Missing Storage Permissions
 No changes are suggested or required.
 To set infrastructure permissions, see 'https://ibm.biz/infra-permission'

Back to Table of Contents

Get the installer

While you can go to Software Access catalog to get the installer, it may make more sense to get it from Fix Central. These are only the client side or installer. Note: If using the bastion node as you don’t have linux, you can download this to your laptop then move it to the bastion node.
You can get the sftp details and proceed to pull down the nz-cloud client directly to the bastion node.

Back to Table of Contents

Use sftp from fix central

Go to Fix Central to pull the latest binaries.
Check the most recent version, at this writing, I am using 11.1.1.0-IM-INZCPD-fp200831
Click continue then click I Agree

Use the values from the Fix package location section. These values change every time you go to fix central, so ignore the ones you see inline.

Fix package location
.
The following location information can be used to download the fix files.
.
FTPS/SFTP server:	delivery04-bld.dhe.ibm.com
User ID:	plieRnJu
Password:	ZAAHyZ8sCncjB6n

Move to the /root/nz and execute the sftp id@hostname from above.

[root@bastion nz]# sftp LpctfUwD@delivery04-bld.dhe.ibm.com
The authenticity of host 'delivery04-bld.dhe.ibm.com (170.225.15.104)' can't be established.
RSA key fingerprint is SHA256:QRJpOHdTFuPmP2NLOQHTpB+IrDSNrque7RadzKcFyFc.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added 'delivery04-bld.dhe.ibm.com,170.225.15.104' (RSA) to the list of known hosts.
plieRnJu@delivery04-bld.dhe.ibm.com's password:
Connected to plieRnJu@delivery04-bld.dhe.ibm.com.
sftp> mget *
Fetching /nzcloud-linux-v11.1.1.0.tar.gz to nzcloud-linux-v11.1.1.0.tar.gz
/nzcloud-linux v11.1.1.0.tar.gz     100%   45MB  20.3MB/s   00:02    
sftp> exit
[root@bastion nz]# ls
nzcloud-linux-v11.1.1.0.tar.gz
[root@bastion nz]#

Back to Table of Contents

Installing the nzcloud CLI

Back in the terminal that is logged into the newly minted VM, I move to /root/nz to gunzip the installer.
Add execute permissions to the file chmod +x nzcloud-linux-v11.1.1.0.tar.gz
Unpack the archive tar -xzf nzcloud-linux-v11.1.1.0.tar.gz
Move to the nz-cloud directory
- cd nz-cloud
Copy the ips_ibmcloud_infra.properties.template to ibm_infra.properties
- cp ips_ibmcloud_infra.properties.template ibm_infra.properties

Review the new files

[root@nz-install nz-cloud]# cat ibm_infra.properties
#######################################
#   USER REQUIRED INPUT PROPERTIES    #
#######################################
CLOUD_PROVIDER IBM
CLUSTER_NAME ${CLUSTER_NAME}
# Either zone or region can be specified
ZONE ${ZONE}
#MULTIZONE_REGION ${MULTIZONE_REGION}
APIKEY ${IBM_CLOUD_API_KEY}
#######################################
#   CONFIGURABLE PROPERTIES           #
#######################################
# OPTIONAL: custom subnet CIDR for pod private IP addresses
#IBM_POD_SUBNET ${IBM_POD_SUBNET}
...
#PRIVATE_VLAN ${PRIVATE_VLAN}
#PUBLIC_VLAN ${PUBLIC_VLAN}
# OPTIONAL: Preferred resource group
#PREFERRED_RESOURCE_GROUP ${PREFERRED_RESOURCE_GROUP}
# OPTIONAL: VLANs may be specified for multizone deployment
...
#PUBLIC_VLAN_ZONE_3 ${PUBLIC_VLAN_ZONE_3}

Back to Table of Contents

Collect information for the ibm_infra.properties files

Open up the ibm_infra.properties file.
Replace ${CLUSTER_NAME} with a unique name. I will use NZCluster

Replace ${ZONE} with your preferred zone. I’ll use dal13

find the available zone using ibmcloud oc zone ls --provider classic

If you are not sure what these symbols stand for, look up locations. Anything with a † is a multi-zone ibmcloud oc locations --provider classic
Note: The listing of the locations is random and not consistent in order. This list is subject to change as new data centers on line all the time.

  [root@nz-install nz-cloud]# ibmcloud oc locations --provider classic
  Classic Infrastructure Zones
  Zone    Metro                   Country               Geography   
  hkg02   Hong Kong (hkg-mtr)     Hong Kong (hkg)       Asia Pacific (ap)   
  syd05   Sydney (syd)†           Australia (au)        Asia Pacific (ap)   
  tok02   Tokyo (tok)†            Japan (jp)            Asia Pacific (ap)   
  dal12   Dallas (dal)†           United States (us)    North America (na)   
  mon01   Montreal (mon)          Canada (ca)           North America (na)   
  fra02   Frankfurt (fra)†        Germany (de)          Europe (eu)   
  fra05   Frankfurt (fra)†        Germany (de)          Europe (eu)   
  lon02   London (lon)†           United Kingdom (uk)   Europe (eu)   
  seo01   Seoul (seo)             Korea (kr)            Asia Pacific (ap)   
  wdc06   Washington DC (wdc)†    United States (us)    North America (na)   
  wdc07   Washington DC (wdc)†    United States (us)    North America (na)   
  tok04   Tokyo (tok)†            Japan (jp)            Asia Pacific (ap)   
  mex01   Mexico City (mex-cty)   Mexico (mex)          North America (na)   
  lon04   London (lon)†           United Kingdom (uk)   Europe (eu)   
  tok05   Tokyo (tok)†            Japan (jp)            Asia Pacific (ap)   
  lon06   London (lon)†           United Kingdom (uk)   Europe (eu)   
  tor01   Toronto (tor)           Canada (ca)           North America (na)   
  che01   Chennai (che)           India (in)            Asia Pacific (ap)   
  hou02   Houston (hou)           United States (us)    North America (na)   
  osl01   Oslo (osl)              Norway (no)           Europe (eu)   
  syd04   Sydney (syd)†           Australia (au)        Asia Pacific (ap)   
  fra04   Frankfurt (fra)†        Germany (de)          Europe (eu)   
  ams03   Amsterdam (ams)         Netherlands (nl)      Europe (eu)   
  syd01   Sydney (syd)†           Australia (au)        Asia Pacific (ap)   
  dal13   Dallas (dal)†           United States (us)    North America (na)   
  mil01   Milan (mil)             Italy (it)            Europe (eu)   
  dal10   Dallas (dal)†           United States (us)    North America (na)   
  mel01   Melbourne (mel)         Australia (au)        Asia Pacific (ap)   
  sjc03   San Jose (sjc)          United States (us)    North America (na)   
  sjc04   San Jose (sjc)          United States (us)    North America (na)   
  sng01   Singapore (sng-mtr)     Singapore (sng)       Asia Pacific (ap)   
  lon05   London (lon)†           United Kingdom (uk)   Europe (eu)   
  par01   Paris (par)             France (fr)           Europe (eu)   
  sao01   Sao Paulo (sao)         Brazil (br)           South America (sa)   
  wdc04   Washington DC (wdc)†    United States (us)    North America (na)   

Next you will need to get your API Key. Either by browser or command line
Browser:
1. Click here to create your apikey to used in the file. You man need to log into IBM Cloud account to retrieve this.
2. Click Create an IBM Cloud API key +
  - Provide a name and description.
  - Click Create
  - For your sanity sake, download the file as you can use it to log in and it saves the apikey value to use another time. You will use this value to replace ${IBM_CLOUD_API_KEY}

Command line

Create via command line using ibmcloud - run ibmcloud iam api-key-create netezza -d nz-key --file nzakikey.json

[root@bastion nz]# ibmcloud iam api-key-create netezza  -d nz-key --file nzakikey.json
Creating API key netezza under f1af5bc92ad34287bbce250dfbe068a2 as mactom@us.ibm.com...
OK
API key netezza was created
Successfully save API key information to nzakikey.json

-  `cat nzakikey.json` and use the value from apikey in the file. ~~~ {
 	"id": "ApiKey-3e1cb4d5-849c-429e-a04c-8f7c1efc091a",  ... "apikey": "SBZ1bF5dTC3mzyg3HNY3EChTk2Co-dp63HQTVjCcCp", ... "created_by": "IBMid-100000A84G", "modified_at": "2020-09-14T18:51+0000" ~~~

Get the Public and Private VLAN ibmcloud oc vlan ls --zone dal13

  [root@nz-install nz-cloud]# ibmcloud oc vlan ls --zone  dal13
  OK
  ID        Name   Number   Type      Router         Supports Virtual Workers   
  2942828          1250     private   bcr01a.wdc06   true   
  2942826          1315     public    fcr01a.wdc06   true   

Find out the resource group you want to assign NZ Cloud. It is easier to control if you use Resource groups. In my case, I will use default

  [root@nz-install nz-cloud]# ibmcloud resource groups
  Retrieving all resource groups under account 10c85c1177aa4ae2959a936b46334bc1 as mactom@us.ibm.com...
  OK
  Name      ID                                 Default Group   State   
  Default   a1083ff7fbd547f390d2b0f4c8735231   true            ACTIVE   

Edit the ibm_infra.properties file and add your selected values.

  #######################################
  #   USER REQUIRED INPUT PROPERTIES    #
  #######################################
  CLOUD_PROVIDER IBM
  CLUSTER_NAME nzcluster
  ZONE dal13
  APIKEY SBZ1bF5dTC3mzyg3HNY3EChTk2Co-dp63HQTVjCcCp
  #######################################
  #   USER OPTIONAL INPUT PROPERTIES    #
  #######################################
  PRIVATE_VLAN 2942828
  PUBLIC_VLAN 2942826
  PREFERRED_RESOURCE_GROUP Default

Validate permissions

Test out the configuration and check for permissions needed.

[root@nz-install nz-cloud]# ./nz-cloud show-permissions -p ibm_infra.properties
========================
Required Access Policies
========================
Service                          Role(s)                         
Kubernetes Service               Administrator (Platform access) and Manager (Service access)
Cloud Object Storage             Administrator
All Account Management Services  Administrator (if creating resource group) or Viewer (using existing resource group)
For more information: https://cloud.ibm.com/docs/openshift?topic=openshift-access_reference#cluster_create_permissions

Verify on IBM Cloud that you have these permissions.

[root@nz-install nz-cloud]# ibmcloud iam user-policies mactom@us.ibm.com
Getting policies of user mactom@us.ibm.com under current account as mactom@us.ibm.com...
OK              
Policy ID:   23d74da4-7473-49de-908c-ebc6b84f9963   
Roles:       Manager, Writer, Reader, Administrator, Editor, Operator, Viewer   
Resources:                        
          Service Name   schematics                   
Policy ID:   829dcb61-cbd5-4462-a6ed-88a04bed1c12   
Roles:       Manager, Writer, Reader, Administrator, Editor, Operator, Viewer   
Resources:            
....
....
....
Policy ID:   e9905a3a-c48c-4006-be80-bb57fd9f92c4   
Roles:       Administrator, Manager   
Resources:                        
          Service Type   All resources in account               

For some reason, I need to have the following IBM Account access policy roles on my specific account, not the group. NOTE: This will be fixed in coming release.
- “Kubernetes Service (Requires Administrator on Platform access and Manager on Service access)”
- “Cloud Object Storage (Requires Administrator)”

Back to Table of Contents

Starting the install of Netezza

Run the installer to create the Openshift cluster on bare metal nodes of ROKS (IBM CLOUD). Note: The script will exit with a message to wait for the bare metal nodes to be in a normal state. This process can take up to a day, which is why the install is separated into different parts.

Back to Table of Contents

Provision OpenShift Cluster

As these are bare metal servers on IBM Cloud, this can take some time to provision. Go get a coffee.
```
./nz-cloud -i ocp -p ibm_infra.properties -v
```

Look for the status of your servers provisioning. These are currently bare metal servers, so they will take sometime. Run ibmcloud oc worker ls --cluster nzcluster

[root@bastion assets]# ibmcloud oc worker ls --cluster nzcluster
OK
ID                                                     Public IP     Private IP      Flavor                State    Status   Zone    Version   
kube-btfuoiod0929a3g5brkg-nzcluster-default-0000014c   52.116.5.52   10.208.89.254   mb3c.4x32.encrypted   normal   Ready   dal13   4.3.35_1538_openshift   
kube-btfuoiod0929a3g5brkg-nzcluster-default-0000027c   52.116.5.61   10.208.89.197   mb3c.4x32.encrypted   normal   Ready   dal13   4.3.35_1538_openshift   
kube-btfuoiod0929a3g5brkg-nzcluster-default-000003c5   52.116.5.60   10.208.89.199   mb3c.4x32.encrypted   normal   Ready   dal13   4.3.35_1538_openshift   

Once you see 3 bare metal servers 4x32 running, you will rerun this command again.
```
./nz-cloud -i ocp -p ibm_infra.properties -v
```
This will make changes to your OCP cluster. As you watch the script you will see nodes cordoned and uncordoned, pods evicted, etc. This is all fine. This could take 30 minutes.
upon completion you should have a envs/<cluster name>/assets/oc_login_details directory.

The contents of this file are what allows you to upgrades, etc. SSH equivalent. (FIX later)

OC_USERNAME=apikey
OC_PASSWORD=<your ibmcloud apikey>
OC_API_URL=https://c106-e.us-south.containers.cloud.ibm.com:31553
OC_CONSOLE_URL=https://console-openshift-console.nzcluster-83506b7a70a1a023393e8317da2d0f35-0000.us-south.containers.appdomain.cloud

Back to Table of Contents

Install Netezza and Cloud Pak for Data

Run ./nz-cloud -p ibm_infra.properties -i cpd -i nps-addon -v This will install Cloud Pak for Data and install Netezza tile into the services catalog. This is where you will click through to provision Netezza servers
upon completion you should have a envs/<cluster name>/assets/cp4d_login_details directory.

The contents of this file are what allows you to upgrades, etc. SSH equivalent. (FIX later)

cp4d_USERNAME=admin
cp4d_PASSWORD=VHVlIFNlcCAsAxNjoyNzoxOCBDRF
cp4d_CONSOLE_URL=https://zen-cpd-zen.nzcluster-8a2d0f35-0000.us-south.containers.appdomain.cloud

Back to Table of Contents

Provision the infrastructure for the NPS Host and SPUs

Before we progress with installing the NPS engine and SPUs, we will want to procure the hardware. When you create these, the cluster name should match. Hold off on doing this as we may make changes down the line. Also if you are migrating from on box to another, you should run a provision of Netezza. It will not let you proceed until the spin up the hardware.
Review what each decision points means for you with this document.
Open up the envs/<cluster name>/assets/cp4d_login_details file and copy the CONSOLE_URL value
Open up a browser and add the copied value into the address bar and click enter. This should bring you to the login page.
Using the USERNAME and PASSWORD from the file, log into Cloud Pak for Data.
On the home page, there is a link underneath Welcome Admin, that reads Create a service instance. Click this link.
Click the Netezza tile. Click Provision Instance or New Instance
This is the configuration panel. This is where you will get the number of VPCs and Storage.
Add a value for namespace, you will use this in the next steps.
Select the workload type. New for something new or if you need a demo, leave at new and lowest values. If you are migrating from an existing rack toggle the list box and select the workload.
Click Next
Scroll through the output. When you get the the bottom, there are some commands that you will use to build out the infrastructure for this system. Once these are complete, you can go forward with the provision.
Take note of the values and fill out the following exports.
To be consistent run these exports: NOTE: Alter these values for your configuration.
```
  export NAMESPACE_NAME=nz
  export CLUSTER=nzcluster
  export ZONE=dal13
```

find the vlan for the zone. ibmcloud oc vlan ls --zone ${ZONE}

  [root@bastion nz-cloud]# ibmcloud oc vlan ls --zone ${ZONE}
  OK
  ID        Name   Number   Type      Router         Supports Virtual Workers   
  2947050          857      private   bcr01a.dal13   true   
  2947048          1677     public    fcr01a.dal13   true     

Export the following based on the previously run command

  # this comes from the private vlan
  export PR_VLAN=2947050  
  # this comes from the public vlan
  export PUB_VLAN=2947048  

Before just copying and pasting, validate that the flavor is the same as the Provision UI. It is expected that these values may change as hardware and cloud infrastructure change.
Create a worker pool with 2 nodes. This pool will be used for the NZ engines. Run ibmcloud oc worker-pool create classic --name ${NAMESPACE_NAME}_host --cluster ${CLUSTER} --flavor mb3c.16x64.encrypted --size-per-zone 2 --label nodetype=hostworker --label namespace=${NAMESPACE_NAME} --entitlement cloud_pak --hardware dedicated
```
  [root@bastion nz-cloud]# ibmcloud oc worker-pool create classic --name ${NAMESPACE_NAME}_host --cluster ${CLUSTER} --flavor mb3c.16x64.encrypted --size-per-zone 2 --label nodetype=hostworker --label namespace=${NAMESPACE_NAME} --entitlement cloud_pak --hardware dedicated
  OK
```
Create a worker pool with 3 nodes. This pool will be used for the SPU engines. Run ibmcloud oc worker-pool create classic --name ${NAMESPACE_NAME}_spu --cluster ${CLUSTER} --flavor ms3c.16x64.1.9tb.ssd.encrypted --size-per-zone 3 --label nodetype=spuworker --label namespace=${NAMESPACE_NAME} --entitlement cloud_pak --hardware dedicated
```
  [root@bastion nz-cloud]# ibmcloud oc worker-pool create classic --name ${NAMESPACE_NAME}_spu --cluster ${CLUSTER} --flavor ms3c.16x64.1.9tb.ssd.encrypted --size-per-zone 3 --label nodetype=spuworker --label namespace=${NAMESPACE_NAME} --entitlement cloud_pak --hardware dedicated
  OK
```
Add nodes to the VLAN. Run ibmcloud ks zone add classic --cluster ${CLUSTER} --zone ${ZONE} -p ${NAMESPACE_NAME}_host -p ${NAMESPACE_NAME}_spu --private-vlan ${PR_VLAN} --public-vlan ${PUB_VLAN}
```
[root@bastion nz-cloud]# ibmcloud ks zone add classic --cluster nzcluster --zone dal13 -p nz_host -p nz_spu --private-vlan 2947050 -- public-vlan 2947048
OK
```

You can validate by running ibmcloud oc worker ls --cluster ${CLUSTER}

[root@bastion nz-cloud]# ibmcloud oc worker ls --cluster ${CLUSTER}
OK
ID                                                     Public IP        Private IP      Flavor                           State    Status   Zone    Version   
kube-btfuoiod0929a3g5brkg-nzcluster-default-0000014c   52.116.5.52      10.208.89.254   mb3c.4x32.encrypted              normal   Ready    dal13   4.3.35_1538_openshift   
kube-btfuoiod0929a3g5brkg-nzcluster-default-0000027c   52.116.5.61      10.208.89.197   mb3c.4x32.encrypted              normal   Ready    dal13   4.3.35_1538_openshift   
kube-btfuoiod0929a3g5brkg-nzcluster-default-000003c5   52.116.5.60      10.208.89.199   mb3c.4x32.encrypted              normal   Ready    dal13   4.3.35_1538_openshift   
kube-btfuoiod0929a3g5brkg-nzcluster-nzhost-00000485    67.228.200.196   10.208.89.220   mb3c.16x64.encrypted             normal   Ready    dal13   4.3.35_1538_openshift   
kube-btfuoiod0929a3g5brkg-nzcluster-nzhost-00000517    52.116.5.53      10.208.89.247   mb3c.16x64.encrypted             normal   Ready    dal13   4.3.35_1538_openshift   
kube-btfuoiod0929a3g5brkg-nzcluster-nzspu-0000062f     67.228.200.197   10.208.89.240   ms3c.16x64.1.9tb.ssd.encrypted   normal   Ready    dal13   4.3.35_1538_openshift   
kube-btfuoiod0929a3g5brkg-nzcluster-nzspu-000007d5     52.116.5.54      10.208.89.208   ms3c.16x64.1.9tb.ssd.encrypted   normal   Ready    dal13   4.3.35_1538_openshift   
kube-btfuoiod0929a3g5brkg-nzcluster-nzspu-000008c8     52.116.5.55      10.208.89.212   ms3c.16x64.1.9tb.ssd.encrypted   normal   Ready    dal13   4.3.35_1538_openshift

Once these are all up and running. you can click the provision button. This should take about 20 minutes to complete.

Back to Table of Contents

Using Netezza on IBM Cloud

From the Cloud Pak for Data UI, you can access Netezza via My Instances. If you don’t remember how to get to Cloud Pak for Data, then go to the <installation>/envs/<clustername>/assets and look at the cp4d_login_details file.
Click on the link in the name of the instance to show details.
Click on the 3 vertical dots on the right and select Open to get to the Console.
This should be familiar to you.

Back to Table of Contents

Installing Netezza on IBM Cloud

Read the instructions

Installing from linux

Add prereqs to the bastion node and test permissions on IBM Cloud account

Get the installer

Use sftp from fix central

Installing the nzcloud CLI

Collect information for the ibm_infra.properties files

Browser:

Command line

Validate permissions

Starting the install of Netezza

Provision OpenShift Cluster

Install Netezza and Cloud Pak for Data

Provision the infrastructure for the NPS Host and SPUs

Using Netezza on IBM Cloud