Install TimesTen Databases
The ttclassic
chart contains all the information necessary to deploy an active standby pair of TimesTen Classic databases in your namespace. The chart contains a default configuration for deploying TimesTen. You have the option of customizing the chart to meet your preferred configuration. Specifically, the TimesTen Operator provides several variables whose values you can change to meet your configuration needs. For information about these variables, see The ttclassic Chart.
-
The method you are using to place metadata files into the
/ttconfig
directory of TimesTen containers. If you are using Kubernetes ConfigMaps or Secrets:-
You do not need to create them. The
ttclassic
chart installation generates ConfigMaps and Secrets for you. -
You must create a directory in the
helm/ttclassic
directory tree of thettclassic
chart. Place all your metadata files in this directory. All of the files in this directory are added to the generated ConfigMap or Secret. -
You must specify the
dbConfigMap
(if using a ConfigMap) ordbSecret
(if using a Secret) variable in your customized YAML manifest file. For more information about these variables, see The ttclassic Chart.
The example in this section illustrates how to use a ConfigMap for your metadata files. For more information about using ConfigMaps or Secrets, see Populate the /ttconfig Directory.
-
-
If you are using
helm
test
to test TimesTen:-
You must define a
test
user. The test connects to the TimesTen database as this user. -
The TimesTen Operator provides a metadata file called
testUser
. Use this metadata file to define thetest
user. This file must contain one line of the form:testuser/testuserpassword
where
testuser
is the name of your test user andtestuserpassword
is the password for this test user.
For more information about testing TimesTen using Helm, see Test TimesTen.
-
-
Create a YAML file that defines the variables that you want to use to configure your environment. Next, to install the chart, pass this YAML file to the
helm
install
command by specifying the-f
option. -
Specify the variables on the command line by running the
helm
install
command with the--set
option.
For more information about these options, see https://helm.sh/docs/intro/using_helm/.
The examples in the section use a YAML file.
ttclassic
chart, which deploys an active standby pair of TimesTen Classic databases. In this example, let's do the following:
-
Create a directory for the metadata files. In this example, the
ttclassic
chart installation generates a ConfigMap from the files in this directory. -
Create the
testUser
metadata file. This file defines atest
user. This user must be defined in order to test TimesTen using Helm. -
Make modifications to the following
ttclassic
chart's variables:-
imagePullSecret
: Let's assume thatsekret
is the name of the Secret used to pull images from the repository. Therefore, let's specifysekret
for theimagePullSecret
variable. - Container image: Rather that use a container image in
container-registry.oracle.com/timesten
, let's assume you built you own container image as discussed in Option 2: Build the TimesTen Container Image. Let's assume the name of the container image you built and want to use isphx.ocir.io/youraccount/tt2211190image:1
. Based on this container image, let's modify the following variables:-
repository
: For therepository
variable, specify a value ofphx.ocir.io/youraccount/tt2211190image
. -
tag
: For thetag
variable, specify a value of1
.
-
-
storageClassName
: Let's specifyoci-bv
for the storage class name. Since there is no default for this variable, you must specify it. storageSize
: Rather than use the default value of50Gi
, let's specify a value of10Gi
for the storage size.dbConfigMap
: Since you are using a ConfigMap for the metadata files, you must specify thedbConfigMap
variable. This variable requires that you specify a name for the ConfigMap as well as the directory where the metadata files are located. The use of this variable is shown later in this example.
-
In addition, lets' assume you have created a kube_files/helm/customyaml
directory for your customized YAML files.
ttclassic
chart. An active standby pair of TimesTen Classic databases is deployed in your namespace. Both the active and standby databases are up and running.