Creating a Rack - Revision history

Sam at 19:14, 3 April 2025

2025-04-03T19:14:25Z

Sam: /* Display Machine Configuration */

2023-08-17T23:56:12Z

Display Machine Configuration

Sam: /* Display Machine Configuration */

2022-09-17T07:45:17Z

Display Machine Configuration

Sam: /* Managing Configuration */

2021-08-24T11:37:57Z

Managing Configuration

Sam: /* Suggested Drives */

2021-08-17T12:41:12Z

Suggested Drives

Sam: /* Suggested Drives */

2021-08-17T12:40:18Z

Suggested Drives

Sam: /* Storage */

2021-08-17T12:32:18Z

Storage

Sam: /* Managing Configuration */

2021-08-17T11:50:45Z

Managing Configuration

Sam: /* Shared Configuration */

2021-08-17T11:47:58Z

Shared Configuration

Sam at 11:33, 17 August 2021

2021-08-17T11:33:06Z

@@ Line 265: / Line 265: @@
 Now that we have out template and batch files in place, to reconfigure the <code>U05</code> server to be an independent node you would:
-<source lang="txt">
+<source lang="bat">
 C:\> D:\Laptop.bat
 </source>

@@ Line 138: / Line 138: @@
 if __name__ == "__main__":
-   main()
+   sys.exit(main())
 </source>

@@ Line 134: / Line 134: @@
    print( "C:\ProgramData\Truxton\Settings\TruxtonSettings.xml came from " + options.getstring("nodesettings") )
    print( "C:\ProgramData\Truxton\Settings\TruxtonService.xml  came from " + options.getstring("nodeservice") )
 if __name__ == "__main__":

@@ Line 117: / Line 117: @@
 |}
 Once these are saved in the configuration file, we can use the following <code>role.py</code> Python script to show them.
 Running <code>D:\role.py</code> after logging onto the machine will tell you how it is configured.
@@ Line 126: / Line 127: @@
 def main():
    options = truxton.options()
-   print( options.getstring("nodename") )
+   print( "This server " + options.getstring("nodename") + " is using the " + options.getstring("nodeconfig") + " configuration for Truxton version " + t.version )
    print( options.getstring("nodedescription") )
    print( "C:\ProgramData\Truxton\Settings\TruxtonSettings.xml came from " + options.getstring("nodesettings") )
-   print( "C:\ProgramData\Truxton\Settings\TruxtonService.xml came from " + options.getstring("nodeservice") )
+   print( "C:\ProgramData\Truxton\Settings\TruxtonService.xml  came from " + options.getstring("nodeservice") )
 if __name__ == "__main__":

@@ Line 32: / Line 32: @@
 # <code>Configurations</code> - To hold the scripts and configuration files needed to change the configuration of a server
 # <code>Depot</code> - A large storage area to hold Truxton's [[Depot|depot]] files
-# <code>Scratch</code> - This drive has a folder for each server in the rack. It holds files that aren't really temporary but aren't really missed if they are deleted. These include log files, temporary files, and search indexes.
+# <code>Scratch</code> - This drive has a folder for each server in the rack. It holds files that aren't really temporary but aren't really missed if they are deleted. These include log files, temporary files, and search indexes. Having a scratch drive allows you to have a mostly read-only access to drives internal to the server.
 =Sample Rack=

@@ Line 26: / Line 26: @@
 Hashsets need to be on fast media since they are accessed frequently during ETL processing.
 The log folder, temporary file folder, and text indexer folder should be on shared storage dedicated to the machine.
 =Sample Rack=

@@ Line 88: / Line 88: @@
 Keeping track of these different configurations can get out of hand quickly.
 After logging into a machine, you will ask yourself, "How is this machine configured?"
-We recommend using Truxton's [Configuration System|configuration system] to help you know how a server is configured.
+We recommend using Truxton's [[Configuration System|configuration system]] to help you know how a server is configured.
 By adding your own items to <code>TruxtonSettings.xml</code> and using a script to display them, you can instantly determine that machine's configuration.

@@ Line 134: / Line 134: @@
 Here are a couple of examples of shared configuration as well as individual.
-===Shared Configuration===
+===Stand-Alone Configuration===
 This sample is for a stand-alone instance of Truxton.
-Nothing is shared, similar to having three laptops in the rack.
+The servers do not cooperate with each other to process data, similar to having three laptops sitting in the shelves.
 The configuration files will be in the folder <code>C:\ClusterStorage\Configurations\Laptop</code>
@@ Line 182: / Line 183: @@
 ====Batch File====
-Here's the <code>D:\Laptop.bat</code> that will setup the server (<code>U05</code>) to a laptop configuration.
+Here's the <code>D:\Laptop.bat</code> that will configure the server (<code>U05</code>) as an independent laptop.
 <source lang="bat">
@@ Line 222: / Line 223: @@
 TaskKill /fi "IMAGENAME eq Yara.exe" /F
 ECHO Deleting old configurations
-IF EXIST "C:\ProgramData\Truxton\Settings\TruxtonService.xml" DEL "C:\ProgramData\Truxton\Settings\TruxtonService.xml"
+IF EXIST "C:\ProgramData\Truxton\Settings\TruxtonService.xml"         DEL "C:\ProgramData\Truxton\Settings\TruxtonService.xml"
-IF EXIST "C:\ProgramData\Truxton\Settings\TruxtonSettings.xml" DEL "C:\ProgramData\Truxton\Settings\TruxtonSettings.xml"
+IF EXIST "C:\ProgramData\Truxton\Settings\TruxtonSettings.xml"        DEL "C:\ProgramData\Truxton\Settings\TruxtonSettings.xml"
-IF EXIST "C:\ProgramData\Truxton\Settings\TruxtonService.xml.backup" DEL "C:\ProgramData\Truxton\Settings\TruxtonService.xml.backup"
+IF EXIST "C:\ProgramData\Truxton\Settings\TruxtonService.xml.backup"  DEL "C:\ProgramData\Truxton\Settings\TruxtonService.xml.backup"
 IF EXIST "C:\ProgramData\Truxton\Settings\TruxtonSettings.xml.backup" DEL "C:\ProgramData\Truxton\Settings\TruxtonSettings.xml.backup"
 ECHO Installing Laptop Configuration Files
 MKDIR "D:\Temp"
 MKDIR "C:\ProgramData\Truxton\Settings"
-COPY "C:\ClusterStorage\SampleData\Rack Management\Configurations\Laptop\Laptop_TruxtonService.xml" "C:\ProgramData\Truxton\Settings\TruxtonService.xml"
+COPY "C:\ClusterStorage\Configurations\Laptop\Laptop_TruxtonService.xml" "C:\ProgramData\Truxton\Settings\TruxtonService.xml"
-COPY "C:\ClusterStorage\SampleData\Rack Management\Configurations\Laptop\U05_131_TruxtonSettings.xml" "C:\ProgramData\Truxton\Settings\TruxtonSettings.xml"
+COPY "C:\ClusterStorage\Configurations\Laptop\U05_131_TruxtonSettings.xml" "C:\ProgramData\Truxton\Settings\TruxtonSettings.xml"
 ECHO Clearing out old SOLR
 IF EXIST "C:\ClusterStorage\Scratch\U05\Search" RMDIR /s /q "C:\ClusterStorage\Scratch\U05\Search"
@@ Line 242: / Line 243: @@
 ECHO Clearing Local Database
 SET PGPASSWORD=Truxton4n6
-"C:\Program Files\PostgreSQL\12\bin\psql.exe" --host=localhost --port=5432 --username=postgres --dbname=Truxton --tuples-only --file="C:\ClusterStorage\SampleData\Rack Management\Database Scripts\Load Test Resets\Reset Truxton Database.sql"
+"C:\Program Files\PostgreSQL\12\bin\psql.exe" --host=localhost --port=5432 --username=postgres --dbname=Truxton --tuples-only --file="C:\ClusterStorage\Configurations\Database Scripts\Load Test Resets\Reset Truxton Database.sql"
 ECHO Clearing Local Message Bus
-"C:\Program Files\PostgreSQL\12\bin\psql.exe" --host=localhost --port=5432 --username=postgres --dbname=TruxtonMessageBus --tuples-only --file="C:\ClusterStorage\SampleData\Rack Management\Database Scripts\Load Test Resets\Clear All Queues.sql"
+"C:\Program Files\PostgreSQL\12\bin\psql.exe" --host=localhost --port=5432 --username=postgres --dbname=TruxtonMessageBus --tuples-only --file="C:\ClusterStorage\Configurations\Database Scripts\Load Test Resets\Clear All Queues.sql"
 ECHO Enabling the Load Status Monitor (Les) on this machine
 SC config Les start=auto

@@ Line 1: / Line 1: @@
 If you have a plethora of equipment lying around, you can make your own [[Truxton Forensic Rack]] solution.
 This article will discuss how to configure the rack as a Truxton solution.
 =Equipment=
@@ Line 8: / Line 9: @@
 =Storage=
 Truxton ETL servers require a single view of [[Depot|depot]] storage.
-When an ETL process writes to a depot file, a process on a different machine must be able to read from it.
+When an ETL process writes to a depot file, another ETL process on a different machine must be able to read from it.
 ETL's require fast IO.
-For this reason we leave this to the operating system.
+For this reason Truxton relies on the operating system to handle this problem.
 One possible solution is to use [https://docs.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-direct-overview Windows Storage Spaces Direct.]
-The remainder of this article will assume that all rack servers will have the mount point for the shares file system to be <code>C:\ClusterStorage</code>.
+The remainder of this article will assume that all rack servers will have a shared file system in <code>C:\ClusterStorage</code>.
 Each server will have a rather small <code>C:</code> drive which will host the operating system and applications.
@@ Line 66: / Line 69: @@
 These do not need to be hosted on every server.
 =Configurations=