Data3.Network Documentation
  • Introduction to Data3
  • Data3 Concepts
    • Accounts
    • Address
    • Nodes
    • Types of Nodes
    • Node Providers
    • Database Deployment
    • Console
    • Use Case
  • Getting Started
    • Data3 Console
      • Signup on Data3 Console
      • Wallets
    • For Customers
      • Quick Start Guide
      • Signup on Data3 Console
      • Request Databases
      • Manage Your Databases
      • Use Your Databases
    • For Node Providers
      • Quick Start Guide
      • Signup at Data3 Console
      • Bid For Customer Requests
    • For Developers
      • Signup
      • Open Source
      • Contribute
  • For Customers
    • Access
    • Application Configuration
    • Database Configuration
    • Data Migration
    • Security
      • Users
      • Keys
    • Observability
  • For Node Providers
    • Node Provider Service
      • What is the Node Provider Service?
      • Node Provider Service Architecture
      • Node Provider Onetime Setup
        • Prerequisites
        • Docker data3-node-provider
        • Configure
        • Deploy data3-node-provider
        • Validate
        • Troubleshoot
    • Data3 Storage Node
      • What is the Data3 Storage Node?
      • Storage Node Architecture
      • Storage Node Setup
        • Prerequisites
        • Docker data3-storage-node
        • Configure
        • Deploy data3-storage-node
        • Validate
        • Troubleshoot
    • External Pricing Engine
    • External Deployment Engine
    • Node Tokenomics
      • Staking
      • Customer Payments
      • Incentivization
      • Pricing
    • Nodes
      • Validator Node
      • Audit Node
      • Storage Node
    • Console
  • Product
    • Roadmap
    • Releases
    • Updates
  • Data3 Solutions
    • DApps
    • Web3 Social
    • Web3 Gaming
    • Web3 Exchanges
    • Artificial Intelligence
    • SaaS Applications
    • IoT
    • Dev Database
  • Tokenomics
    • Best Practices
    • Bid for Database Requests
  • Governance & Policies
    • Governance Framework
    • Node Provider Policies
    • Data Handling Policies
    • Security Policies
    • Privacy Policies
    • For Developers
      • Architecture
      • API
      • SDKs and Libraries
      • Protocols & Algorithms
  • Community
  • FAQs
  • Legal
Powered by GitBook
On this page
  • Database Instance Configuration
  • Configure proxysql.cnf
  • Environment variables for data3-storage-node
  1. For Node Providers
  2. Data3 Storage Node
  3. Storage Node Setup

Configure

PreviousDocker data3-storage-nodeNextDeploy data3-storage-node

Last updated 1 year ago

Database Instance Configuration

After you have deployed the database(s) as per teh customer's requirements, you have to create the following users in the database so that the DB Proxy and the Observability agents will work as expected:


CREATE USER 'monitor'@'%' IDENTIFIED WITH mysql_native_password BY 'monitorPass123';
GRANT USAGE, REPLICATION CLIENT ON *.* TO 'monitor'@'%';


CREATE USER 'appuser'@'%' IDENTIFIED WITH mysql_native_password BY 'appUserPass123';
GRANT ALL ON *.* TO 'appuser'@'%';


CREATE USER 'proxyuser@'%' IDENTIFIED WITH mysql_native_password BY 'proxyUserPass123';
GRANT ALL ON *.* TO 'proxyuser'@'%';

Configure proxysql.cnf

Please find a sample

  • Configure the backend mysql servers' IP address and port that have been deployed as per the customer specification under mysql_servers (at line 39):

mysql_servers =
(
    { address="192.168.5.168" , port=3308 , hostgroup=10, max_connections=100 , max_replication_lag = 5 }
)
  • Confirm that the mysql_users section (last in the sample proxysql.cnf) has the right credentials as configured above for the appuser and proxyuser in the SQL scripts on the backend databases:

mysql_users =
(
    { username = "appuser" , password = "appUserPass123" , default_hostgroup = 10 , active = 1 },
    { username = "proxyuser" , password = "proxyPass123" , default_hostgroup = 10 , active = 1 }
)
  • Confirm that the monitor user variable in proxysql.cnf has the right credentials as configured above for the monitor user in the SQL scripts on the backend databases:

mysql_variables=
{
    ...
    monitor_username="monitor"
    monitor_password="monitorPass123"
}

Environment variables for data3-storage-node

Configure the data3-storage-node using the following environment variables:

Name
Description
Sample Value

GRAILS_ENV

Environment type for application development , test, production, etc.

development

OBSERVABILITY_SERVER_HOSTNAME

Hostname / IP of the observability server.

192.168.5.168

OBSERVABILITY_SERVER_PORT

Port number of the observability server.

8443

OBSERVABILITY_SERVER_USERNAME

Username for the observability agent to login to the observability server.

admin

OBSERVABILITY_SERVER_PASSWORD

Password for the observability agent to login to the observability server.

observabilityAdminPass123

DBPROXY_ADMIN_USERNAME

Username for the managing the DB proxy.

admin

DBPROXY_ADMIN_PASSWORD

Password for the managing the DB proxy.

adminPass123

NODE_PROVIDER_BASE_URL

API Base URL of the Data3 Data3 Node Provider Service.

http://192.168.5.168:8080/

SELF_STORAGE_NODE_HOSTNAME

Hostname / IP Address of this node (data3-storage-node) that will allow customers to access the database.

192.168.5.169

SELF_STORAGE_NODE_PORT

Port on this node (data3-storage-node) that will allow customers to access the database. This is typically the host port mapping to the DB Proxy in the container at 6033.

16033

DEPLOYMENT_ADDRESS

AAAADDDD

DEPLOYMENT_NAME

Dev Deployment 1

The deployment address that uniquely identifies the customer's request for a deployment. See for how to set value. This is the ENV Variable that strongly ties the storage node to a customer request.

Typically the same name that the customer used while requesting the deployment. See for how to set value.

proxysql.cnf file at the data3-testnet-docker repo in KandolaNetwork's Github.
External Deployment Engine
External Deployment Engine