Table of Contents
The configuration will vary based upon the version of Tungsten software you are running. For versions less than 7.0.0, you will need to configure APIv1. For Tungsten v7.0.0 and higher, please configure for APIv2.
Configure the Tungsten Cluster APIv1 for Dashboard - Needed for Tungsten software versions LESS THAN v7.0.0
Add the following to /etc/tungsten/tungsten.ini
under the [defaults] section:
mgr-api-port=8090 mgr-api=true mgr-api-address=0.0.0.0 mgr-api-full-access=true
Either SHUN the individual nodes one at a time and WELCOME each one after running the update, or set policy to MAINTENANCE via cctrl and update all nodes, then set the policy back to AUTOMATIC when all nodes have been completed.
Inform the running manager of the changed configuration:
shell> tpm updateYou may need to restart the manager.
Verify that the port is listening:
shell> sudo netstat -pan | grep 8090Configure the Tungsten Cluster APIv2 for Dashboard - Needed for Tungsten software versions v7.0.0 and higher
This feature was first introduced in Tungsten Dashboard version 1.0.10-125
Do these steps only if you have already enabled APIv1 and are upgrading to v7.0.0 or higher.
Remove the following APIv1-specific options from
/etc/tungsten/tungsten.ini under the
[defaults] section:
mgr-api-port=8090 mgr-api=true mgr-api-address=0.0.0.0 mgr-api-full-access=true
Perform these steps BEFORE installing or upgrading to v7 from a version less than 7.
For NON-secure deployments, check for the following in
/etc/tungsten/tungsten.ini under the
[defaults] section:
disable-security-controls=true enable-connector-ssl=false datasource-enable-ssl=false
If you located the above options, then your deployment is NON-Secure.
ADD the following to /etc/tungsten/tungsten.ini
under the [defaults] section:
rest-api-admin-user={desiredLoginHere}
rest-api-admin-pass={desiredPasswordHere}
connector-rest-api-address=0.0.0.0
connector-rest-api-authentication=true
connector-rest-api-port=8096
connector-rest-api-ssl=false
manager-rest-api-address=0.0.0.0
manager-rest-api-authentication=true
manager-rest-api-full-access=true
manager-rest-api-port=8090
manager-rest-api-ssl=false
replicator-rest-api-address=0.0.0.0
replicator-rest-api-authentication=true
replicator-rest-api-port=8097
replicator-rest-api-ssl=false
For Secure deployments, check for the following in
/etc/tungsten/tungsten.ini under the
[defaults] section:
disable-security-controls=false enable-connector-ssl=true datasource-enable-ssl=true
If you located the above options, then your deployment is SECURE. ADD
the following to /etc/tungsten/tungsten.ini under
the [defaults] section:
rest-api-admin-user={desiredLoginHere}
rest-api-admin-pass={desiredPasswordHere}
connector-rest-api-address=0.0.0.0
connector-rest-api-authentication=true
connector-rest-api-port=8096
connector-rest-api-ssl=true
manager-rest-api-address=0.0.0.0
manager-rest-api-authentication=true
manager-rest-api-full-access=true
manager-rest-api-port=8090
manager-rest-api-ssl=true
replicator-rest-api-address=0.0.0.0
replicator-rest-api-authentication=true
replicator-rest-api-port=8097
replicator-rest-api-ssl=true
Either SHUN the individual nodes one at a time and WELCOME each one after running the update, or set policy to MAINTENANCE via cctrl and update all nodes, then set the policy back to AUTOMATIC when all nodes have been completed.
Inform the running manager of the changed configuration:
shell> tpm updateYou may need to restart the Manager, Connector and Replicator.
Verify that the three ports (Manager, Connector and Replicator) are listening:
shell>sudo netstat -pan | grep 8090shell>sudo netstat -pan | grep 8096shell>sudo netstat -pan | grep 8097