Ocient System Bootstrapping

the {{ocient}} system runs the bootstrapping process one time per node this process establishes the node identity, configures networking, and accepts nodes into the system the /var/opt/ocient/bootstrap conf file controls the i nitial configuration of each node the system uses this file only when the node initially starts validate the system before bootstrapping the following steps assume a basic {{ocienthyperscaledatawarehouse}} configuration, where every node has a single network interface to verify your system before the bootstrapping process check with your systems administrator to ensure that you meet the operating system configuration docid\ wdbmiwp38yglv1ei2hlyq requirements before bootstrapping, your system must meet the requirements described in the operating system configuration docid\ wdbmiwp38yglv1ei2hlyq and operating system configuration docid\ wdbmiwp38yglv1ei2hlyq sections you can run a system check to validate the compliance of hardware, nodes, and the configuration for the ocient system for details, see checking system configuration before bootstrapping docid\ dixaug3ghtqgo ujj6jz4 initial configuration the system automatically initializes the first node bootstrapped in the system with the sql and administrator roles choose a node to serve as a sql node this node is the initial node in the system the hardware for each node type differs, so ensure that the node you select is intended for a sql node for new clusters, if you do not define the configuration for the sql nodes in a connectivity pool, the ocient system assigns each sql node to their own unique connectivity pool named \<sql node name> default , where \<sql node name> is the name of the sql node however, the most common configuration of an ocient system has all sql nodes in one connectivity pool for an example of adding sql nodes to a connectivity pool, see cluster and node management docid\ xga0pas8wadtq33 a x7v change or troubleshoot the default configuration using the instructions in manage the network configuration of an ocient system docid\ dh zr9fe qvm3p7zqrytx ocient system bootstrapping process if you meet the system prerequisites, you can begin bootstrapping your ocient system the bootstrapping process consists of these steps ocient system bootstrapping docid 4005nflvguw4fqfqa1spu ocient system bootstrapping docid 4005nflvguw4fqfqa1spu bootstrap the first node bootstrap the node connect to the initial sql node with the username and password of your server and the ip address of your node this example connects as the administrator admin to the ip address 10 10 10 10 ssh admin\@10 10 10 10 use your preferred text editor with sudo to create the /var/opt/ocient/bootstrap conf file as root with these contents /var/opt/ocient/bootstrap conf example initialsystem true start the database sudo systemctl start rolehostd verify that the node and the service is active by executing this status command systemctl status rolehostd rolehostd service rolehostd daemon startup loaded loaded (/etc/systemd/system/rolehostd service; enabled; vendor preset enabled) active active (running) since wed 2022 01 26 23 31 36 utc; 7s ago if the rolehostd service is running, you can also check the ocient logs on your node search and ensure there are no \[error] log messages tail f /var/opt/ocient/log/rolehostd log verify connection to the sql node at this point, you have a running database with a single node you should be able to connect to the database using connect using jdbc docid\ fpyaptctcu3mul0c66p8d or connect using pyocient docid\ bu2r7uc0lgh5n3edngtsq and execute commands every new system starts with a system database to connect to a new system, use the username and password configured in the bootstrap conf file or the username admin\@system and password admin if none was provided for example, assume your node named sql0 has an ip address of 10 10 0 1 use the jdbc driver cli to connect with this connection string connect to jdbc\ ocient //10 10 0 1 4050/system user "myuser\@system" using "mypassword"; see the jdbc manual docid 5vn0ryh6u3fbhbr ooaxk for details on using the jdbc driver to see the roles running on the single node, execute this query select name, operational status, software version, array agg(service role type) from sys node status as ns left join sys nodes as n on ns node id = id left join sys service roles as sr on sr node id = n id group by name, operational status,software version; the initial node should be listed as running the sql , admin , health , and operatorvm roles if all of these roles are present and the node is active, you can proceed to the next step to bootstrap the remaining nodes bootstrap the remaining nodes performing the bootstrapping process on the remaining nodes is identical on all nodes the remaining nodes can be bootstrapped in any order on each node, log in using ssh and use your text editor with sudo to create the file /var/opt/ocient/bootstrap conf that contains this text by replacing \<first node ip address> with the ip address of the initial node you created in step 1 /var/opt/ocient/bootstrap conf example adminhost \<first node address> \<first node ip address> is the dns name or ip address of the initial node you can obtain the ip address of the initial node by executing ifconfig on that node if the password for the system administrator has changed, set the correct username adminusername and password adminpassword in the bootstrap configuration file bootstrap conf on each node, start the database sudo systemctl start rolehostd when you replace foundation nodes, the ocient system removes the prior node after the creation of the new node some queries of the system catalog tables might not return results until the prior node is removed at this point, all the remaining nodes are not configured with any roles after all nodes have been started, you should see them when you execute this query with only the health role listed this query uses the sys node status , sys nodes , and sys service roles system catalog tables to retrieve node information for the node name, operation status, version, and all service role types the query uses the sorted aggregate functions docid 6ysvgmcg45ereu6od sxn function to retrieve the service role type for all rows select name, operational status, software version, array agg(service role type) from sys node status as ns left join sys nodes as n on ns node id = id left join sys service roles as sr on sr node id = n id group by name, operational status,software version; more bootstrapping options for options on bootstrapping your ocient system, see node bootstrapping reference docid\ wztcsct8uijhzzx mhl0k next step when you have completed the bootstrapping process, you can proceed to the ocient application configuration docid\ nneedy7yn8g1pennmamng page to finish configuring ocient related links installation reference docid\ gpjrtqjbvx3fkuke6effy install an ocient system docid\ ohaih2 yvgdxfvej8iu w